This topic answers some Frequently Asked Questions (FAQs) about Infrastructure Management. BMC Software recommends that you review this FAQ when planning a new deployment or an upgrade.
Yes. All trended data in BMC PATROL is now visible in the operator console. Attributes that are "availability" in nature, may be filtered from "storing" the data in the Infrastructure Management Server; however, Infrastructure Management supports graphing these attributes by querying the PATROL Agent for data. You can also see annotated data from BMC PATROL in the operator console. Text parameters in BMC PATROL are not visible in the Infrastructure Management UI.
Not all of the BMC PATROL console functionality has been developed in Infrastructure Management yet, but some of the functionality does exist. In general, all configuration aspects are represented. Certain agent actions are also available. Infrastructure Management provides a Query Agent window which is similar (although not exactly the same) to the System Output window in BMC PATROL.
Some of the functions have migrated, but the migration is limited (for example, KM menu commands have not been migrated).
Yes. At a high level, you can use the TrueSight console to perform the features of PATROL Configuration Manager. Some specific features of PATROL Configuration Manager such as compare, reporting, and so on are not available from the TrueSight console. Rule set development in the TrueSight console includes and deployment of policies is much more controlled, automated, and easier in the TrueSight console than in PATROL Configuration Manager.
Yes. BMC Impact Explorer can be used to access Infrastructure Management cells.
BMC recommends that in Infrastructure Management, you use the operator console and not Impact Explorer. If you use Impact Explorer, you will have to register the cell(s) to BMC Event and Impact Manager 7.4.x IAS.
BMC plans to cover most (if not all) BMC PATROL Central Operator console capabilities of which you derive value from, in Infrastructure Management.
No new out-of-the-box reports have been added. Some reports that were based on outdated collectors have been removed. You can still create reports based on the attributes that you select.
Yes and that is the UI from which to manage event cells in Infrastructure Management.
Yes. You can modify the content of the data table but not the structure of the table.
There are no changes to the prediction window.
PATROL Configuration Manager in general is not required but may still be useful because it provides some capabilities that are not available from the TrueSight console. For example, the ability to compare agents. If you use the TrueSight console for configuration management, then use PATROL Configuration Manager to view configuration from agents. Do not use both to apply configuration to agents.
BMC recommends using the TrueSight console. Policy management provides operational benefits over the push/forget model of PATROL Configuration Manager. TrueSight console also has architectural improvements.
Because statistical data is streamed in near real time, the flash check functionality will not be needed. Infrastructure Management also contains the Refresh Parameters menu option to force a collection outside of its normal timing.
Yes, all BMC KMs can be configured from the TrueSight console. Because KMs have their own release cycle, KMs are enabled as and when they are released.
You can see the historical data that is collected from the Tools menu. If the PATROL Agent is sending only events, the data comes from the PATROL Agent in real time to populate the graph and this is a seamless process.
You can initiate PSL commands using the Query Agent command. This is not specifically designed to run scripts; however, with the correct syntax you can run small scripts. For a deep dive debug, you may still require a BMC PATROL console.
BMC recommends that you configure PATROL Agents to generate and forward events for "availability" parameters where sending data (0s and 1s) to the Infrastructure Management Server may not work. Performance parameters must be sent to Infrastructure Management as data only, allowing analytics to evaluate thresholds and generate intelligent events.
instruct a PATROL Agent on what to send to the database and the event cell. By default, any KM that is configured and running sends all of its data and events configured in the PATROL Agent. Filtering provides "agent side" instructions to limit the information that the Infrastructure Management Server must store. Viewing is not restricted by policy filtering. You can graph an attribute that is filtered from sending its data to Infrastructure Management. For these attributes, the Infrastructure Management Server requests data from the PATROL Agent in real time.
in monitoring policies suppress data from being streamed to the Infrastructure Management Server from the PATROL Agent. However, in the Operations Console, you can view an attribute that is filtered.
Use of the "merge" operation opens the doorway to having policies getting applied to an unknown agent configuration. There may be some limited cases where the merge operation is beneficial and some cases where in may even be required. This is an enhancement that will be considered.
Yes. Inheritance cannot be carried for the same application class defined in two or more policies (for example, one policy cannot select three services to monitor and another policy provide additional three services).
No. Service impact is specific to rules and behavior of the Service Impact Management cell. Policies are focused on PATROL Agent configuration and/or monitoring the behavior of the Infrastructure Management Server. For more information, see Infrastructure Management cells and Knowledge Base.
The TrueSight console does not have in-built policy versioning. The lets you leverage your preferred source code control where desired. These capabilities provide a means to create a "new" version of the policy, disable the old and enable the new. If an issue arose you can disable the new and re-enable the old policy.
The PATROL Agent has been updated for event configuration. You can enrich messages while configuring the PATROL Agent. This configuration can be managed in a policy. For details, see .
control PATROL Agent behavior. For external events, you can create a blackout policy using the Event Management Policies tab in the Administrator Console.
No. However, you must either use PATROL Configuration Manager or Infrastructure Management policies from the TrueSight console to manage a PATROL Agent, not both. Areas of agent configuration that are managed by policies override local configurations. In some instances, certain KMs may need to be configured outside of the TrueSight console (for example, custom KMs not enhanced for Infrastructure Management policy control).
Yes. This is supported with older Integration Service nodes integrated with Infrastructure Management. This does not apply to new Integration Service nodes and 9.5 PATROL Agents because there are no adapters. Infrastructure Management includes manual synchronization in the TrueSight console for older instances that were not initially included.
No. In Infrastructure Management, PATROL Agents stream performance data all the way to the Infrastructure Management Server through the Integration Service nodes.
No. However, a policy is disabled by default. You must decide when to enable a given policy.
The Integration Service checks the communication automatically and alerts if it finds communication to be broken.
The TrueSight console on the Presentation Server does not connect directly to agents. It connects through the agent controller on the Infrastructure Management Servers. Policies are passed through the agent controller to the Integration Service nodes. The PATROL Agents initiate the connection to the Integration Service nodes and receive their policies. The default connection port for agents on the Integration Service is 3183. For information about port numbers and connection requests, see Network port schematics for Infrastructure Management.
No. PATROL Configuration Manager threshold rules are the absolute type. Infrastructure Management hasthat leverage . Additionally, the rule format managed from the TrueSight console as policy content for thresholds has changed in comparison to the older rule format managed in PATROL Configuration Manager. However, PATROL Configuration Manager can be used to collect and view any rules at the agent, even if they come from a policy. Avoid trying to manage the same agent with PATROL Configuration Manager and Infrastructure Management policies.
Yes. PATROL Agents version 3.8.50.01 and later push data to the Integration Service. In Infrastructure Management, the PATROL Agent pushes the data all the way to the Infrastructure Management Server (through communication managed by the Integration Service).
The technology has also changed. Integration Service comprises the Integration Service and the event cell. 9.5 BMC PATROL Agents no longer communicate their data to a "BMC PATROL proxy server." PATROL Agents connect to the Integration Service and data is moved directly to the Infrastructure Management Server. Additionally, events can be sent to the Integration Service on the same port along with the performance data.
Yes, the Integration Service computer acts as the "entry point" to the architecture. All sources of data and events must connect to an entry point. Some integrations may only leverage events into the architecture, but they must still connect to an Integration Server (for example, event only).
Yes. Multiple instances of the Integration Service are supported. Installation of the cell components is required only once. Additional cells are created leveraging and configuring BMC Event Manager commands. Additional Integration Service instances can be installed on the same node as well. Installation of additional Integration Services provides a notation that cell components will be skipped during installation.
Yes. Clustering of staging Integration Services is not supported. It is important to note that clustering Integration Services creates a comma-separated list of Integration Services for the PATROL Agent. Because the TrueSight console does not provide the staging Integration Service instruction to the PATROL Agent (this happens during the installation of the PATROL Agent), clustering may not be feasible. However, you can , use a comma-separated list of these Integration Services. The PATROL Agent then connects to the first one it finds available in the list.and when
Yes. The Monitor to Monitor KM is not needed on Integration Service hosts and it will not monitor the Integration Service processes. The KM was designed for the older Integration Service processes. Built-in self monitoring replaces the KM. You must also install a PATROL Agent and an OS KM on the Integration Service nodes so that you can monitor the Integration Service processes externally.
You need not install the Integration Service process if you are using Infrastructure Management only for event management. Third party events can be sent to event management cells directly. If you are using PATROL Agents and KMs for event detection, BMC recommends that you install the Integration Service and configure according to the Integration Service host deployment and best practices for event processing and propagation so that events from PATROL Agents are sent to the Integration Services. This recommendation allows you to easily take advantage of trending performance Key Performance Indicators (KPI) data in Infrastructure Management. In event only Integration Service installations, it is best to ensure that the cells used have all the latest and correct event processing data classes and rules.
Yes. The move is very quick and there is no missing data after the move.
Yes. This is supported as afrom the TrueSight console.
A allows you to automate the PATROL Agent to Integration Service configuration without sending data to the Infrastructure Management Server. It is used to automate which normal Integration Service or Integration Service cluster an agent must connect to. A staging Integration Service does not implement any monitoring policies.
The is used as a common initial place for newly installed PATROL Agents to enter the Infrastructure Management architecture. Staging policies can then decide which "production" Integration Service the PATROL Agents must connect to going forward and optionally assign any agent tags, if required.
When you install a Infrastructure Management Server, a local Integration Service is installed by default. BMC recommends that the Integration Service be used as a . Never use the Integration Service on the Infrastructure Management Server for data collection.
It is not required but it is a best practice. A makes for easier agent deployment.
Yes. A must be created manually. It is then applied based on the agent selection criteria against agents connecting to any staging Integration Service.
A is not required if you know and configure the agent installation packages to contain the production Integration Service you want the agents to connect to. If you define the process and infrastructure so that each agent has the appropriate configuration for the Integration Service nodes, you do not have to use a staging Integration Service. The staging Integration Service is not mandatory. It is available to provide a central point to introduce agents to Infrastructure Management and to streamline the agent deployment process.
You must use a third party load balancer to load balance PATROL Agents across Integration Service nodes. You can also use a to apply tags to the PATROL Agents; however a load balancer eliminates the manual task of assigning tags for this purpose.
There are no known limitations. PATROL Agents connect and get reassigned to a production Integration Service immediately. In general, agents are assigned to the production Integration Service in less than a minute.
No. A does not apply to the PATROL Agent. It only applies to that contain final the Integration Service configuration and optionally, tags for the PATROL Agent.
The PATROL Agent connects to the based on the configuration in the agent installation package, the first time the agent starts. The staging Integration Service then applies a to the agent. The staging policy contains the final Integration Service that the agent then connects to. After the staging policy is applied, the agent connects to the final Integration Service and does not reconnect to the staging Integration Service. It does not reconnect to the staging Integration Service after a restart. If the agent were to be purged, it goes back to the staging Integration Service for reassignment.
Generally. Additionally, a can assign required tags to the PATROL Agent as part of the staging.
You can select to include or exclude the event management cell as part of the installation process. You can also exclude the cell if you are installing an additional Integration Service on a server in which an Integration Service already exists. The event management cell is installed once on a server. Additional instances are configured without running the installation file again.
A correlation cell is a term referencing the type of event management work being done by the cell. Source cells normally perform actions that do not rely on evaluation with events from other sources. Correlation cells provide a common cell where events can be evaluated in context with other events.
Considering the Integration Service cell is the "entry point" or "source" cell for PATROL Agents, it is a best practice to perform message enrichment, deduplication here. Event management configuration KB content must be kept common across Integration Service cells where possible. Correlation cell rules allow for correlating across events that may originate separate communication paths (for example, across PATROL Agents from multiple Integration Service computers).
It depends on a number of factors (event volume, rules to be processed against, other resource constraints). It is best to install the correlation cell as a standalone cell allowing for the use of cell HA configuration.
Yes, the event management software is only installed once, but multiple cells may be created and run after the installation.
The idea is to keep the workload on the Infrastructure Management Server cell reduced as much as possible with relation to enrichment of external event classes. You must add rules/classes to support events that present themselves to the Infrastructure Management Server cell for viewing. However, modify BMC-provided rules and policies only after consulting BMC customer Support. The use of a correlation cell provides a step where customer specific rules can be applied to events prior to presenting them to the Infrastructure Management Server for viewing. Performing these limited workflows at this type of cell minimizes the need to publish these rules across many cells.
It is the same technology. The term "correlation" defines how the cell is used. An Integration Service cell is considered a source cell (feed directly by an event source, for example PATROL Agents) and as much standard processing as possible must be done at these cells. As events rise through the architecture, there are more events to be managed and rule processing must be limited to only those actions that require higher levels of functioning (for example, correlating with other events, configuration item (CI) enrichment, and so on).
A processing cell (for example, an Integration Service cell) provides basic event enrichment and handling that is usually common across "like" processing cells (for example, all PATROL Agent processing cells). A correlation cell usually has customer-specific rules that can be applied to events prior to presenting the events to Infrastructure Management for viewing. Events at this cell can originate from any number of sources (BMC PATROL, SNMP, SCOM, and so on); performing these limited workflows at this type of cell minimizes the need to publish associated rules across many cells and supports correlating events from multiple domains.
Impact Explorer 7.3.01 is not officially supported.
Yes. If the correlation cell is a standalone cell, it can be configured as a service impact management or an event management cell.
The cell on the Infrastructure Management Server is a Service Impact Management cell. For more information see Infrastructure Management cells and Knowledge Base.
The correlation cell can be either located on an Integration Service or (if required) somewhere else. It is just a standard cell that is configured and used as a correlation cell. It is not a special installation.
Events reference the occurrence of availability and performance metric threshold breaches. Events can come from many sources. PATROL Agents normally detect and generate "availability" events that are sent to the Infrastructure Management Server, while "performance" events are raised in the Infrastructure Management Server based on threshold evaluations in the analytics process.
In general, attributes that are "availability" in nature generate events configured in the PATROL Agent and are passed to Infrastructure Management. Performance attributes are sent as data to the Infrastructure Management Server. The Infrastructure Management Server might then have thresholds that generate events based on the data received. These events might be in the form of Critical, Major, Minor, and so on, or as abnormality events. Additionally, all trended data in BMC PATROL is visible in the operator console.
BMC provides comprehensive application response time monitoring with BMC Real End User Experience Management which integrates with Infrastructure Management. BMC also provides many metrics for application monitoring through BMC PATROL KMs. For a list of out-of-the-box KMs, see List of Monitoring Solutions and KMs in Infrastructure Management Performance Management.
Tags can be applied as part of the registration through the Integration Service. They can also be applied through and .
You can specify the sequence of event processing before it reaches the rate process. This includes customizations to events. Customization to events are removed by the rate process.
Yes, there is a mapping which handles this relationship.
Yes. See Integrating with SCOM to view performance data. Infrastructure Management can also consume data and events from third party sources for which there are no pre-built integrations. You have to configure customized integrations when pre-built integrations are not available.
The TrueSight console does not provide default monitoring configurations.
MCxP has not changed in Infrastructure Management. The MCxP rule and class files in the KB define the BMC PATROL event structure and basic handling of BMC PATROL events.
The Integration Service and MCxP are completely separate and do not conflict. Overall, MCxP defines event configuration for BMC PATROL events in the event management cell. The Integration Service receives performance data and events. The Integration Service forwards events to the local event management cell running on the same host with the Integration Service process. The MCxP rules and class files define the structure of BMC PATROL events in the cell and how BMC PATROL events are processed.
You can do this using from the TrueSight console.
Technically yes, but BMC does not recommend it.
For information about the number of models a single Infrastructure Management Server can support, see Sizing charts for event and impact management. MOM and Enterprise use case implementations are intended to support environments where all service models can be configured in a single Infrastructure Management Server.
If you want to publish CIs to a cell, the cell must be a service impact management cell.
Yes. Events from other monitoring tools can be used for status change or impact change in service models.
Not necessarily. It depends on your plans for growth. Be sure to leave some buffer. BMC recommends at least 10%.
Policies allow even more control than manual adapters in earlier releases. In Infrastructure Management, you can filter at the application class, instance, and/or parameter levels. This filtering can include data, events, or both and can be applied at levels appropriate to what you want to view. For more information see, .
In general, a a single Infrastructure Management Server can support 20000 devices, 250000 instances, and 1.7 million attributes (given the proper server resources, for example, 32 GB RAM, 8 CPUs). For more information, see Performance benchmarks and tuning for Infrastructure Management.
Generally 20,000. However, the number of agents is not the only limiting factor. For additional important details, see Sizing charts and guidelines for data and event management environments.
Yes. For more information, see BMC Communities.
SAN is preferred. BMC recommends a tier 1 SAN storage for production environments. For more information, see Hardware requirements to support small, medium, and large environments.
5000 servers can be considered a medium environment sizing from purely a device count perspective. However, without considering all other scalability aspects, 5000 BMC PATROL managed servers cannot be considered medium environment.
A 4 GB RAM and 2 CPU Integration Service host can handle up to 900 PATROL Agents. For more information, see Sizing charts and guidelines for data and event management environments.
No. Events are sent to only one destination. The destination must be an event management cell as recommend in Integration Service host deployment and best practices for event processing and propagation. The cell can then send the events to multiple destinations.
BMC recommends that you have dedicated bandwidth and minimum latency; therefore, the Internet is not recommended. However, BMC supports WAN connections and data compression is included to help manage WAN connections between the Integration Service nodes and the Infrastructure Management Server.
350,000 events per day. For more information see see Sizing charts and guidelines for data and event management environments.
The default port is 3183. This port can be changed. See Ports that can be configured after installation.
Yes; you can use the Integration Service on an Infrastructure Management Server that contains an earlier version of the Integration Service.
This has not changed much from earlier releases. The maximum load depends on many factors including the rules and policies that are enabled, types of events, and so on. In general, a single cell can support about 25 events per second. There may be more, but BMC recommends that you be conservative with this number. Note that events must be actionable messages.
900 is the maximum number of PATROL Agents tested against a single Integration Service. However, agents do not maintain a connection to a . They connect to the staging Integration Service, get their staging policy, and then immediately move to a production Integration Service. They do not reconnect to the staging Integration Service, so there no limit to the number of agents that a staging Integration Service can handle because the connection is transient.
In Infrastructure Management, the Infrastructure Management Server does not make a connection with the PATROL Agents. The connection is between the PATROL Agents and the Integration Service.
You can install the PATROL Agent manually. The TrueSight console allows you to create a repository of silent installation packages that can be deployed and installed on the target servers to be monitored.
From the TrueSight console, you can handle the application of monitoring configuration through and the deployment and installation of KMs. BMC Server Automation can handle the deployment and installation of agents. For more information, see .
Yes. If the location of the PATROL Agent connection is well defined and a is not required, the PATROL Agent can just connect to the required production Integration Service.
There are no scalability recommendations except that you must not simultaneously connect to more than 900 nodes. For more information see, Sizing charts and guidelines for data and event management environments.
The maximum number of supported PATROL Agents is 900 on a large Integration Service host.
The staging Integration Service is installed in the same way as you install an Integration Service. You can then configure the Integration Service to be a . BMC recommends that you edit the Integration Service installed with the Infrastructure Management Server and make it a staging Integration Service. A staging Integration Service can be installed in any computer in which you install a normal Integration Service.
Not exactly. The does not process performance data or events. Its purpose is to apply . This depends on how you want to control initial agent connections into the Integration Service nodes as part of the deployment process and their production Integration Services. Using a staging Integration Service allows you to alter deployment behavior without the need to alter your standard agent installation packages.
If the PATROL Agent cannot connect to the single Integration Service in the configuration list, it connects to the next one in the list. You can also use load balancers between the PATROL Agents and Integration Service nodes.
Infrastructure Management does not have this capability.for easier deployments.
Yes, as long as the appropriate operating system, hardware, storage resources, and connectivity are allocated for it.
There is no way to restrict the number of active instances in Infrastructure Management.
Oracle Standard Edition is supported. Infrastructure Management does not require partitioning. Other Oracle offerings are not required either; however, BMC recommends Data Guard to support Disaster Recovery.
RAC is not supported with Oracle Standard Edition. Oracle may also impose limitations on sockets based on the Oracle editions.
This depends on the size of the managed environment based on an architecture and scalability assessments. This is categorized based on small, medium and large environments. For Microsoft Windows running with i7 CPUs in a large environment, BMC recommends 4 CPUs, 24 GB RAM, 600 Gig of storage for the Oracle database. For more information, see Hardware requirements to support small, medium, and large environments and Tuning the Infrastructure Management database for performance.
Yes. Some Infrastructure Management customers use Oracle Exadata architectures.
No, the use of the embedded SAP SQL Anywhere database is restricted to installing the database as part of the Infrastructure Management Server.
Two, one for each Infrastructure Management environment that supports multiple Infrastructure Management Servers and one per Infrastructure Management Performance Management Reporting environment.
The Infrastructure Management Server does not include Microsoft SQL Server support.
Oracle versions 184.108.40.206.0 and 220.127.116.11.0.
The Infrastructure Management Server does not require Oracle partitioning. Infrastructure Management Performance Management Reporting requires Oracle partitioning in the latest release.
No. Using Oracle does not increase the scalability of the solution. However, it does provide a nominal improvement in performance and supports better database resiliency.
Yes. You can have multiple Infrastructure Management Servers in the same Oracle instance. Each server must have its own schema. For more information, see Configuring multiple Infrastructure Management child servers to connect to the same Oracle database.
No. Infrastructure Management does not provide scripts or a method to migrate data from SAP SQL Anywhere to Oracle.
No. A separate database user and schema is required per Infrastructure Management Server. Infrastructure Management Performance Management Reporting supports a single consolidated schema.
You will need only one Oracle instance for all Infrastructure Management Servers, and only one Oracle instance for Infrastructure Management Performance Management Reporting. This is a total of two instances, regardless of the total number of Infrastructure Management Servers. For more information, see Installing the Infrastructure Management Server on Microsoft Windows with Oracle and Configuring multiple Infrastructure Management child servers to connect to the same Oracle database.
Supported database versions that are documented are the versions that have been tested and supported. It is unlikely that a newer or earlier version of Oracle may not work; however these versions have not been tested. Do not use versions earlier than 11g.
OS clustering is still required in Infrastructure Management to support HA. For more information, see Installing Infrastructure Management in high availability cluster mode and High-availability deployment and best practices for Infrastructure Management.
BMC does not recommend this scenario. If you install the primary and secondary hosts in virtual guest systems, the guests must run on separate ESX Servers so that you have resiliency at the hardware level. If you install the primary and secondary hosts on the same ESX Server, they will both be unavailable if the ESX Server goes offline or if there is a hardware issue.
Yes. Only events and timers are synchronized.
OS clustering can be configured to support basic application aware HA because failover can be triggered based on a process being down and so on. Additional details must be based on your requirements and environment.
Yes. Infrastructure Management has been installed using VMware HA. The Infrastructure Management application is not VMware HA aware.
Yes. However, there have been HA deployments across data centers. The feasibility of this depends on hardware and network capabilities but it can be implemented.
No. The Infrastructure Management Server is the one location where cell HA is not supported.
Yes. There are no changes regarding HA support for VMware. You can install as with earlier versions.
HA requires OS clustering in Infrastructure Management. HA is in-built and application specific to HA cells and Integration Service processes on the Integration Service hosts.
The HA cell is not supported on the Infrastructure Management Server, but is supported on the Integration Service. You can also install remote HA cells for event visualization, including events propagated from Infrastructure Management Servers.
The cell and the start and stop Integration Service processes have been separated to better support cell HA.
Yes. For more information, see Installing the Infrastructure Management Server in HA OS cluster mode on Linux.
In general, do not cluster more than four Integration Service nodes. Create the cluster after you have added all the Integration Service nodes to the Infrastructure Management servers. For more information, see .
The BMC PATROL Agent streams data to the Infrastructure Management Server and this data is stored in the Infrastructure Management Server in the same intervals and granularity as it is collected by the PATROL Agent. Therefore, data in the Infrastructure Management Server is based on the polling frequency set in the PATROL Agent for each specific KM collector running in the PATROL Agent.
Yes. The PATROL Agent first attempts to fill in the data gap using the cache and where required, uses the history files.
Yes. Infrastructure Management ensures continuous communication between the Integration Service and the Infrastructure Management Server. For more information, see Architecture of integration with BMC Cloud Lifecycle Management. Infrastructure Management also contains the ProactiveNet Health node that alerts on technology outages.
Event management cells and Integration Services are independent of each other and do not conflict. You can set the order of how they move from one server to another.
BMC PATROL data collection through the Integration Service nodes in earlier versions involved adapters that defined the data to be collected in the Infrastructure Management Server and the frequency of the data collection. These adapters have been completely eliminated in Infrastructure Management. BMC PATROL data is .to the Infrastructure Management Server. This greatly simplifies the architecture and makes the process more resilient so that data is not lost during network interruptions or other outages. The PATROL agents now control what is sent upstream and the configuration for that is managed through in
The PATROL Agent pushes data to the Infrastructure Management Server using the Integration Service to manage the conversation. The PATROL Agent initiates the connection to the Integration Service. The Infrastructure Management Server initiates the connection to the Integration Service.
The PATROL Agent buffers up to 30 minutes of data at the agent. This is the default setting. BMC recommends not increasing this setting. When the agent reconnects, the buffered data is sent to the Infrastructure Management Server and no data is lost.
BMC recommends that each Integration Service host have an event management cell installed. The cell includes a local database called mcdb. The cell must be configured as an HA cell. The PATROL Agent buffers events if the connection to the Integration Service is broken and/or the cell does not acknowledge the event being received. The cell also buffers events not sent to the Infrastructure Management Server.
Yes. BMC provides out-of-the-box integrations for some third party tools. For more information, see Integrating with SCOM to view performance data.
For Microsoft SCOM, you must leverage the SCOM adapter for performance data. Event integration for SCOM is based on the Seamless integration. For more information see Adapter for SCOM. Zenoss integration is only event based unless you create a custom method for integrating performance data.
"MZ product" refers to the Market Zone product. Market Zone is a third party product developed to work with BMC solutions and is sold by BMC Software.
The database includes data views. If MSBI can fetch data from data views, it can be supported.
Infrastructure Management Performance Management Reporting is included under the same license. The Reporting Studio option that supports creation of custom reports is an add-on license.
The Infrastructure Management native adapter handles performance data. BMC recommends the Seamless integration for events. For more information, see Supported Infrastructure Management integrations with other products.
No. The Seamless integration is from Seamless Technologies: http://www.bmc.com/products/product-listing/Seamless-Technologies-Event-Integration-for-BPPM.html
The new streaming is only for data from PATROL Agents.
Yes. For more information, see Adapter for SCOM.
BMC Remedy and xMatters do not integrate with Central Monitoring Administration. They integrate with the event and service impact management functions in Infrastructure Management. They can be integrated with any or all the Infrastructure Management Servers. The proper architecture for your environment must be reviewed by BMC Consulting Services.
Infrastructure Management can send SMTP emails natively. There is no in-built adapter for receiving emails as events. However this is planned in a future release and the method to support this is documented on BMC communities.
You can integrate Atrium CMDB with a single Child Server or multiple Child Servers. Try to limit service models to a single Child Server if possible. Do not integrate the Central Server with Atrium CMDB.
Yes. For more information, see .
The best practice is to leverage the event management cell on an Integration Service host. You can enable the SNMP trap adapter on the cell to receive SNMP traps as events. To do this, consider the Sizing and scalability considerations for Infrastructure Management. If you plan to receive a very large number of SNMP traps, you must install an event management cell on a dedicated node to handle the volume. Never forward SNMP traps or raw events to the Infrastructure Management Server. For more information see, Managing Infrastructure Management events through SNMP traps in the operator console.
Yes. If you upgrade a previous version of Infrastructure Management that leveraged SNMP monitoring, it is supported. The old Infrastructure Management monitors (non-PATROL Agent monitoring) have been deprecated and are not available in Infrastructure Management.
Not completely. Infrastructure Management supports operational multi tenancy where you can segregate access to data and operational activities based on user roles and permissions. There is no role-based access control for administrative activities. A user has either full administrative access or no administrative access. Also, there is no concept of segregated tenant accounts in Infrastructure Management.
Infrastructure Management does not support multitenancy. You can configure various levels of visual separation and access control. However, this is different from true multitenancy.
Infrastructure Management is not FIPS compliant. For information about security capabilities, see Security planning for Infrastructure Management.
Yes. PATROL Agents do not connect to the Presentation Server. The connection is through the Integration Service. The Presentation Server does not use on the PATROL Agent.
Check with BMC Customer Support. BMC Customer Support covers governing when certain rules are applied to deal with Java rate process change issues.
There is no documentation dedicated to this scenario. In general, install the event management cells on the Integration Service hosts as explained in Sizing and scalability considerations for Infrastructure Management.. Also check
There is no specific documentation about this topic. In general, leverage the access control capability in Infrastructure Management to leverage user groups where appropriate groups are created per client. This type of configuration can vary from one customer to another and requires engaging BMC Consulting Services or other technical assistance to understand how access control works and what the limitations are.