Monitoring Multiple Systems: Defining RFC Connections 

Use

To monitor a remote system, you must have defined an RFC connection to this system.

For security reasons, we recommend that you define two RFC destinations for every remote system, since there are two requirements that are different in principle between the monitored and the monitoring systems:

·        Performing Data Collection

There are active data collection methods in the monitored system. These methods store values for the monitoring attributes in the shared memory of the monitored system. The monitoring system reads these values using an RFC call (and using a particular user name). In the monitored system, this user is merely an observer that must log on to this system for each query.

·        Executing Analysis Methods

If a data collection method reports an alert, you can stat an analysis method in the alert monitor. Since this analysis method may make changes in the monitored system, it requires more extensive authorizations there.

Since the two types of request access the monitored system in very different ways, and also occur with very different frequencies, we recommend that you assign different authorizations to different users during the definition of the two RFC destinations.

·        Performing Data Collection

Create a CSMREG user on all systems to be monitored and ensure that the user type Communication (SAP Web Application Server 6.10) or CPIC (up to SAP Basis 4.6D) is activated (see Creating the CSMREG User).

·        Executing Analysis Methods

We recommend that you perform the RFC call under your own user name.

Prerequisites

To be able to define RFC connections, you must have created the CSMREG user.

Procedure

...

       1.      Choose CCMS ® Configuration ® Alert Monitor, or call transaction RZ21.

       2.      Choose Technical Infrastructure ® Configure Central System ® Create an Entry for a Remote System.

       3.      Choose Goto ® RFC Connections

Instead of points 1-3, you can also call transaction SM59.

       4.      In the RFC Destinations tree, expand the ABAP Connections node.

       5.      If there is no suitable RFC connection for the system that you want to monitor, choose Create.

       6.      Make the following entries in the definition screen:

¡        RFC Destination: Enter the name for the RFC connection; we recommend <SID>_RZ20_COLLECT for the RFC destination for data collection,  <SID>_RZ20_ANALYZE for the RFC destination to execute the analysis method.

¡        Connection Type: Enter 3 (for ABAP system).

¡        Description: Enter a short description of the RFC connection.

¡        User (RFC destination for data collection): Enter CSMREG as the user and its associated password.

¡        User (RFC destination for executing the analysis methods): Either select the option Current User, or enter any user (in both cases, the user must have authorization for the alert monitor and for system management in the target system).

If you request data for a remote system in a monitor, this is done using the CSMREG user. Since you specified the password in the RFC destination for data collection, no manual logon is required.

If you start the analysis method for an MTE of the remote system, a manual logon may be required, depending on the settings of the corresponding RFC destination.

The RFC connection logs on to the remote system with these users.

       7.      Save the definition. The system displays a few additional fields on the Technical Settings tab page. For Load distribution, choose Yes and save the definition again.

       8.      Complete the definition by filling out the other fields in the Technical Settings group box:

Input Field	Entry
Target System ID	Enter the system ID (such as C11).
Message Server	Enter the host name of the message server. If you are not sure what this is, log on to the target system and start transaction RZ03. The message server is the instance with M in the Services column. The host name is the first part of the instance name: host1_C11_01.
Group	Enter the logon group to be used on the target system. If you are not sure, call transaction SMLG in the target system to display the available groups.
Save as	Choose IP Address. The host name of the message server or the IP address is automatically entered in the adjacent field.

       9.      Save the completed definition.

   10.      Test the RFC connection with Test Connection and Remote Login.

For more information, see Maintaining Remote Destinations.

Result

You have defined the required RFC destinations. If you want to monitor the relevant system with the alert monitor, follow the procedure described in Monitoring Multiple Systems.