Creating a Customizing Destination for SAPCCMSR -j2ee

Use the CCMS agent SAPCCMSR with Option j2ee to transfer monitoring data for a Java instance to a central monitoring system (CEN). You can display this monitoring data both in the Alert Monitor and in the SAP NetWeaver Administrator.

A Customizing destination between the CEN and the relevant J2EE Engine is required, so that you can change the properties of the agent nodes from the Alert Monitor. This destination is used to transfer the property changes from the Alert Monitor directly to the J2EE Engine.

To create the Customizing destination yourself, you must perform the following steps:

• In the SAP NetWeaver Administrator of the J2EE Engine, create an RFC destination.
• In the ABAP system with which you have registered the agent, create an RFC destination.
• Make this destination known to the monitoring architecture.

Creating an RFC Destination in the Java System

For you to be able to change the threshold values for performance attributes of the monitored Java system from the alert monitor of CEN, there needs to be a program ID with the naming convention SAP.CCMS.J2EE.<SID> in the JCo RFC Provider Service of the Java system, which points to the agent that you registered. <SID> is the system ID of the monitored Java system. If this does not yet exist, create it as follows:

1. Log on to the SAP NetWeaver Administrator and choose Configuration Management → Infrastructure → JCO RFC Provider or use the direct link /nwa/jco-destinations.
2. In the Program ID input field, enter the name SAP.CCMS.J2EE.<SID>.
3. In the other input fields (Server and Repository Configuration), enter the connection data for the ABAP system with which you registered the agent. The user that you specify under Repository Configuration must have sufficient authorizations to open an RFC connection.
4. Save your entries and start the JCo server with the relevant parameters.
   Note

   For more information about creating the Customizing destination, refer to SAP Note 1373897.

Creating an RFC Destination in the ABAP System

1. To create an RFC destination, call transaction SM59 and choose the Create button. The RFC Destination screen appears.
2. Enter the name of the destination in the RFC Destination input field. Use the naming convention SAP.CCMS.J2EE.<JSID>, where <JSID> is the system ID of the monitored Java instance.
3. Enter T (Start an External Program via TCP/IP) as the connection type, and enter a description of the destination. Confirm your entries by choosing the  (Enter) button.
4. Switch to the Technical Settings tab page. In the Activation Type group box, choose the Registered Server Program radio button, and enter SAP.CCMS.J2EE.<JSID> in the Program ID input field.
5. In the Gateway Options group box, enter the gateway information for the local ABAP system, which you have already entered in the SAP NetWeaver Administrator when creating the RFC destination.
6. Switch to the Special Options tab page, and choose the Unicode radio button in the Character Width in Target System group box.
7. Save your entries.

Making the RFC Destination Known to the Monitoring Architecture

1. Call transaction RZ21.
2. If the agent is monitoring a Java instance in an ABAP+Java system, choose the Agents for the  Local System radio button in the Topology group box, and choose  Display Overview.

   If the agent is monitoring an instance of a standalone Java system, choose the Agents for Remote Systems radio button in the Topology group box, and choose  Display Overview.

3. Switch to change mode by choosing  (Display «Change), and enter the name of the RFC destination created above, SAP.CCMS.J2EE.<JSID>, as the agent in the column J2EE Customizing Destination.
4. Save your entries.

You have now created the required RFC destination and made it known to the monitoring architecture. You can now also change the properties of the nodes for the corresponding CCMS agent SAPCCMSR -j2ee in the Alert Monitor.