Activating Priority Monitoring for an individual SID

You can activate Priority Monitoring for any SAP system (SID) that was discovered through a connection to an SAP Solution Manager system. This configuration change redefines the SAP system as an SAP satellite system and adjusts the mode of data collection, so that data is collected directly from the SAP system, rather than through the SAP Solution Manager.

When activating Priority Monitoring for an SAP system, you can control the following additional settings:

  • Whether to begin direct monitoring of the SID instead of or in addition to monitoring the SID through the SAP Solution Manager. That is, whether to remove the SID (SSM_SID_CONT) from under the parent SAP Solution Manager (SSM_SOLMAN) branch when duplicating these branches as an independent SAP satellite system.
  • Whether to maintain all customization performed on the original SID (for example, enabled and disabled child CCMS Contexts) when creating the new branches for the independent SAP satellite system.

Note

For instructions on defining a new connection to an SAP satellite system (rather than redefining the configuration of a previously discovered SAP system), see Configuring SAP Solution Manager systems and SAP satellite systems.

To activate Priority Monitoring for a discovered SID

  1. From the PATROL Console work area, right-click a discovered SAP system.
  2. Select KM Commands > Set Priority Monitoring On.
  3. Choose whether to copy all customization performed on the original SID that was discovered through the SAP Solution Manager into the new branches for the independent SAP satellite system.
    In response to the confirmation message " Do you want to copy the existing customization for the SAP system?," select either Yes or No.
  4. Choose whether to suspend monitoring of the original SID that was discovered through the SAP Solution Manager and remove it from under its parent SAP Solution Manager in the tree.
    In response to the message " Do you want to remove SAP System... from SAP Solution Manager...?," select either Yes or No.

    A new SAP satellite system is created in the tree, with a single child SAP System (SSM_SID_CONT) branch under an SSM_SOLMAN branch. Data for this SAP system is collected directly, and not through an SAP Solution Manager system.

    If you chose (in step 4) to duplicate the original SID discovered by the SAP Solution Manager, rather than replace it, BMC PATROL for SAP Solution Manager is now monitoring this SID both through an SAP Solution Manager system and as an independent SAP satellite system.

    If you chose to suspend monitoring of the original SID through its parent SAP Solution Manager and replace it with monitoring as an SAP satellite system, you can resume monitoring through the SAP Solution Manager at any later time, as described in Data displayed for SAP PI systems.
Was this page helpful? Yes No Submitting... Thank you

Comments