The staging Integration Service is a new component in BMC ProactiveNet version 9.5. The staging Integration Service provides a single point in the environment where all newly deployed BMC PATROL Agents can register into the BMC ProactiveNet Performance Management solution stack. The staging process can leverage the Integration Service on the BMC ProactiveNet Server.
A staging Integration Service supports a smoother process for deploying PATROL Agents into BMC ProactiveNet environments in three major ways:
BMC PATROL Agent silent installation packages are created so that the staging Integration Service is defined in the package. No other Integration Service is defined in the installation packages. Although technically possible, BMC recommends as a best practice that other Integration Service instances not be defined in the installation packages. When a package is deployed and installed, the PATROL Agent checks in through the staging Integration Service. When the PATROL Agent checks in, Central Monitoring Administration evaluates the agent selection criteria in a staging policy and uses that data to automatically assign a data collection Integration Service (or Integration Service cluster) to the PATROL Agent. The agent selection criterion can include any one or a combination of the following:
Integration Service policies are the only Central Monitoring Administration policies that are applied through a staging Integration Service. Monitoring policies are not applied though a staging Integration Service. Additionally, staging Integration Service policies in Central Monitoring Administration are only applied through a staging Integration Service instance.
The architecture of network connections (communication protocol, ports, and so on) among the staging Integration Service, PATROL Agents, and the BMC ProactiveNet Server is technically the same as with other Integration Service instances.
The following are best practices for staging Integration Services:
The diagrams in the following steps illustrate the process of utilizing a staging Integration Service.
This diagram illustrates three different Integration Service nodes and how they are used:
A newly deployed PATROL Agent silent installation package is installed as shown in the diagram. The installation package for the PATROL Agent contains configuration data that informs PATROL Agent on how to connect to the staging Integration Service. When the new agent starts for the first time, it registers with Central Monitoring Administration through the staging Integration Service. Central Monitoring Administration then applies a staging policy to the agent based on agent selection criteria in the policy. Agent selection criteria define the agents that the policy must be applied to. The staging policy only contains agent selection criteria and information that defines connectivity for a data collection Integration Service node (or Integration Service cluster). No other agent and/or KM configuration data can be defined in a staging policy.
After receiving the staging policy, the newly deployed PATROL Agent switches to the data collection Integration Service node (or Integration Service cluster) defined in the staging policy. (The switch is represented by the blue arrow in the diagram.) The agent then receives monitoring polices that match each monitoring policy’s agent selection criteria defined in Central Monitoring Administration
The PATROL Agent starts monitoring and continues to receive any updates to existing monitoring policies and new monitoring policies that match the monitoring policy’s agent selection criteria.
Agents do not move from development to test, and then to production. All agents must first check in with the appropriate staging Integration Service, and then move to their data collection Integration Service. This supports the concept of creating installation packages for development and test only, separate from production.