Understand BPPM As A Decision Maker - Part 4: Implementation - console and data

Once you have decided what to do with installation of BPPM server(s), BPPM integration service(s), BPPM cells, and PATROL local/remote agents, your next decision is about console - the user interface that your operations support staff will use to interact with BPPM on daily basis. And a related decision is about data - what data you want to save in BPPM server database.

When you install BPPM server, you automatically install BPPM operations console, a web interface that displays data and events.  From historical point of view, BPPM operations console is evolved from native ProactiveNet console, as BPPM is an integrated product from PATROL, BMC Event Manager, and ProactiveNet.  What about native PATROL console?  Do you need to install it?

It is BMC's intention to replace PATROL console with BPPM operations console.  At this time, BPPM operations console still cannot completely replace all the features available in PATROL console though your operations support staff can perform most of their work with BPPM operations console. However menu commands that help you configure PATROL KMs interactively or diagnose system issues are only available with PATROL console.

A key differentiator here is where data are stored.  PATROL was initially architected back in 1995 when network was not as fast and reliable as it is today.  All PATROL data are stored locally.  When PATROL was integrated into BPPM, selected or all PATROL data can be saved in BPPM server database.

When you are using PATROL console, you are viewing PATROL data stored on each PATROL agent.  When you are using BPPM operations console, you are viewing PATROL data stored in BPPM server database.  You can use BPPM operations console to view PATROL data stored on each PATROL agent (but not in BPPM server database) as 'non-streamed' data on demand, but the data are about 10-minute-old based on my observation consistently.

Along with a decision on PATROL console, you must decide what PATROL data you want to save in BPPM server database.  There are three major reasons to save PATROL data in BPPM server database: 1) To compute dynamic thresholds - Dynamic thresholds will be discussed in a later post; 2) To be included in reports - Data in report database are based on data in BPPM server database; 3) To see real-time (not 10-minute-old) data in BPPM operations console.

It would be nice to save all PATROL data in BPPM server database so that you don't have to decide which data to eliminate.  If you have a small site, this is entirely possible.  But if you have a large site, you must consider the cost and complexity of multiple BPPM servers as each BPPM server can only contain 1,700,000 attributes or 250,000 instances.  It is a trade-off between having more PATROL data in BPPM server database and keeping the cost of BPPM servers under control.

In summary, in order to decide if PATROL console should be implemented, you need to have an in-depth discussion with your implementation team (consultants or employees) and operations staff regarding to the requirement of PATROL console for PATROL KM configuration, their preferred tools for troubleshooting, and guidelines on what data should be stored in BPPM server database.