Configuring SAP Solution Manager systems and SAP satellite systems

To start using BMC PATROL for SAP Solution Manager, you must define connections with the relevant SAP Solution Manager systems.

You can also define connections with SAP satellite systems, which are not controlled by SAP Solution Manager. For such SAP systems, you activate Priority Monitoring, so that data is obtained directly from the SAP system, rather than through SAP Solution Manager.

The following procedures describe how to define, edit, or delete connections with SAP Solution Manager systems and SAP satellite systems.

To configure SAP Solution Manager connections and SAP satellite connections

1. From the PATROL Console work area, right-click an existing SAP Solution Manager system (SSM_SOLMAN) or the SSM_SETUP icon.
2. Select KM Commands > SAP Solution Manager Setup.
3. In the SAP Solution Manager Systems dialog box, perform one of the following actions:
   • To add a new SAP Solution Manager connection or SAP satellite connection, select Add and click Accept.
   • To edit an existing SAP Solution Manager connection or SAP satellite connection, select it in the list, then select Edit, and click Accept.
   • To delete an existing SAP Solution Manager connection or SAP satellite connection, select it in the list, then select Delete, and click Accept. Then click OK to confirm.
4. If defining or editing, enter the information, as follows:
   • Label - A unique, user-defined name for display of the SAP Solution Manager system or SAP satellite system in the PATROL Console. This field is enabled only when you add a new system.
   • MS Host - Message server host of the SAP Solution Manager system or SAP satellite system

   • ABAP MS RFC Port - Message server RFC port number of the SAP Solution Manager system or SAP satellite system (4 digits)

     Note

     The combination of the MS Host and ABAP MS RFC Port values must be unique per system.

   • User - Name of a user authorized to log in to the SAP system
   • Password - Password for the specified user
   • SAP Client - SAP system working client (3 digits, default: 000 )
   • Language - Language to use for logging on to the SAP system (default: EN)
   • Group Logon - Name of the logon group used by the SAP Logon Load Balancing function

   • RFC INI File Destination - Path to the RFC INI file, which stores optional configuration data. This data overrides configuration information that has been defined for this system.

     Note

     • The external SAP system availability feature functions correctly only if the computer on which the PATROL Agent is installed can ping the host name of the satellite computer that is defined in the SAP Solution Manager system landscape. For example, when a server for a certain system is defined as myhost (short name), then myhost must be accessible by ping from the PATROL Agent computer.
     • If you want to configure a password for multiple systems, prepare and save a set of variables in PATROL Configuration Manager, as follows: Variable: /SecureStore/SSM_SOLMAN/ < SAP Solution Manager Label> /sysPass Value: SSM_SOLMAN;SSM_SID_CONT;SSM_CONTEXT_CONT;SSM_PARAM_CONT;SSM_SID_AVAIL/ <password>

5. Under Priority Monitoring mode, select the type of SAP system connection, either SAP Solution Manager (the default) or SAP Satellite System.

   Note

   Priority Monitoring is available for dual stack systems (R/3 + J2EE), but not for SAP J2EE stand-alone systems. If you are editing a previously defined connection, you might need to redefine an SAP satellite system connection as an SAP Solution Manager connection. However, do not use the Priority Monitoring mode option buttons to redefine a connection in the opposite direction, that is, to redefine an SAP Solution Manager connection as an SAP satellite system connection. You can turn on Priority Monitoring only at the SID level, for a single SAP system. For more information on how to do that, see Activating Priority Monitoring for an individual SID.

6. If you want to test the connection between the product and the defined SAP Solution Manager system or SAP satellite system, select the Perform Connection Testcheck box.

   Note

   If the test fails and you do not find mistakes in the SAP connection information that you entered, verify that the appropriate SAP Java Connector files for your platform were deployed, as described in Deploying the SAP Java Connector files and in accordance with SAP instructions.

7. To continue with auto configuration and discovery of SAP Solution Manager system, disable the Open Configuration Wizard check box. The Open Configuration Wizard is enabled by default. To open the Configuration Wizard and set the active or inactive SAP Solution Manager instances, keep the check box enabled and click Apply.
8. Click Apply.
9. In the Configuration Wizard Manager SIDs for SAP Solution Manager instances (SIDs) dialog box, choose and move the SIDs from active SIDs list to inactive SIDs list by using the Move arrows.

10. To continue selecting SIDs in the Active SIDs list, select Save & Continue with selected SIDs list. To save the details and continue with configuring SAP Solution Manager system, select Save & Back to Solution Manager Configuration.

    Note

    To add the new discovered SIDs to Active SIDs or Inactive SIDs list, select the Active SIDs or Inactive SIDs option.

11. When you have completed all necessary configuration, click Save & Exit, click Apply in the SAP Solution Manager Systems dialog box. For a new connection, a new branch of the SSM_SOLMAN application class is created to represent the SAP Solution Manger System or SAP satellite system that you defined, and data collection is started.
    
    For an SAP Solution Manager System, BMC PATROL for SAP Solution Manager discovers all associated SAP systems (SIDs) and creates child SAP System (SSM_SID_CONT) branches under the SAP Solution Manager (SSM_SOLMAN) branch.
    
    For an SAP satellite system, a single child SAP System (SSM_SID_CONT) branch is created under the SSM_SOLMAN branch.

    Note

    To enable successful availability monitoring of discovered SAP 7.30 systems, you must manually create the SAPVersion configuration variable for each discovered SAP 7.30 system. For more information, see the description of the SAPVersion configuration variable see Configuring-pconfig-settings.

12. If you want to filter the list of discovered SAP systems and discovered CCMS Contexts, that is, choose the SAP systems and CCMS Contexts that you want to monitor after configuring SAP Solution Manager systems and SAP Satellite systems, select the Open Configuration Wizard check box under Post Configuration.