System requirements

Verifying installation

This section contains information about planning the installation, requirements, and considerations.

Hardware requirements

Follow PATROL Agent best practices for capacity requirements in relation to the number of CCMS parameters that you plan to monitor.

Required BMC product components

BMC PATROL for SAP Solution Manager requires the following PATROL components:

  • PATROL Agent version 9.0 or later
  • PATROL Console (for Windows and UNIX) 3.5.80
  • Common Installer 7.5.64 or later
  • (Optional) Distribution Server version 7.8.12 or later on the server and version 7.8.20 or later on the client

Note

You must install the same version of BMC PATROL for SAP Solution Manager on both the PATROL Agent and the PATROL Console.

After you have fulfilled the prerequisite requirements for installing the product, proceed to Installing BMC PATROL for SAP Solution Manager.

Java requirements

BMC PATROL for SAP Solution Manager requires that you install Java version 1.6 or 1.7 (J2EE 6 or 7) on the PATROL Agent computer.

Note

If the location of the Java file that runs the Java Data Collector is different from the default Java path defined by the host computer's system variables, you can change the path. For more information, see Editing executable variables.

According to SAP JAVA connector requirements.

BMC PATROL for SAP Solution Manager requires about 0.5 megabytes of Java process memory for each monitored CCMS parameter. To adjust the Java memory heap size after product setup, you can use the javaExecuteArguments pconfig variable, as described in Java problems impact data collection.

SAP requirements

Before you install BMC PATROL for SAP Solution Manager, ensure that the following requirements are met and that you have performed the following prerequisite tasks.

Supported operating systems and SAP components

BMC PATROL for SAP Solution Manager supports the following major SAP components and operating systems:

IPv6 Support

The KM supports IPv6 in terms of OS types  and SAP Basis release, derived from  SAP support for IPv6.

 SAP user with required SAP authorizations

Create an SAP user on the SAP Solution Manager or SAP satellite computer for use by BMC PATROL for SAP Solution Manager, or verify that an existing SAP user complies with the following requirements:

  • User of type CPIC (Common Programming Interface for Communications)
  • User is assigned a minimum level of authorization for the following authorization objects:
    • S_RFC
    • S_RZL_ADM
    • S_XMI_PROD
    • S_TABU_DIS
    • S_ADMI_FCD
    • S_TABU_RFC
      For each of these authorization objects, specify full authorization using the asterisk (*** ) wildcard. Add these authorization objects to a special role for the BMC product or to an existing role through the Profile Generator (transaction PFCG).
      If you cannot specify full authorization for any of these authorization objects, refer to Additional information about SAP authorizations and roles, for more specific definitions of minimum attribute values that you must include in each authorization object.
  • For SAP PI monitoring: The user for connecting to the System Landscape Directory (SLD), the user for connecting to the Runtime Workbench (RWB), and the user for connecting to Business Systems must also have the following roles assigned. Assign these roles through the User Management (SU01) transaction:
    • SAP_SLD_ADMINISTRATOR
    • SAP_XI_RWB_SERV_USER
    • SAP_XI_IS_SERV_USER

    • SAP_XI_MONITOR_J2EE
      To monitor J2EE Adapter Engine channels, the RWB user must also be assigned the xi_af_channel_admin_display role through the UME (User Management Engine) of the SAP J2EE Engine on each server where the adapter is located. For more detailed instructions, see Enabling the RWB user to query SAP PI J2EE Adapter channels.

      Note

      As an alternative to setting up a user for SAP PI monitoring, you can use the following existing users:

      • PISUPER for connecting to the SLD
      • PIRWBUSER for connecting to the RWB
      • PIAPPLUSER for connecting to Business Systems

SAP Java Connector support

Download the SAP Java Connector (JCo) version 3 .x to each computer that hosts a PATROL Agent for BMC PATROL for SAP Solution Manager. For more information, see Deploying the SAP Java Connector files.

Note

When choosing a host computer for the PATROL Agent, ensure that the SAP Java Connector supports the computer platform.

SAP Java archive files for SAP PI monitoring

To prepare for SAP PI monitoring , download a group of required Java archive (.jar ) files to each computer that hosts a PATROL Agent for BMC PATROL for SAP Solution Manager. For more information, see Deploying Java archive files for SAP PI monitoring.

SAP configuration information

Obtain the following information for each SAP Solution Manager system that you want to monitor. During the configuration process, you are asked to provide this information. For more information, see Configuring SAP Solution Manager systems and SAP satellite systems.

Field

Description

MS Host

Message server host name of the SAP Solution Manager system.

ABAP MS RFC port

Message server RFC port number of the SAP Solution Manager system (4 digits).

User

User name configured with the authorizations discussed in SAP user with required SAP authorizations.

Password

Password for the user configured with the above authorizations.

SAP Client

SAP Solution Manager system working client (3 digits, default: 000).

Language

Language to log in to SAP system (default: EN).

Obtaining installable product files

BMC PATROL for SAP Solution Manager version is packaged with the BMC ProactiveNet Performance Management Suite solution for Microsoft Windows or for Linux. The solution is available for download from the BMC Electronic Product Distribution (EPD) website at http://webapps.bmc.com/epd. To use the website, you must register and set up a user name and password.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*