Creating a Customizing Destination for SAPCCMSR -j2ee 

Use

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 local Java system ( Monitoring service of the Visual 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.

If you register the CCMS agent using the Visual Administrator (see Installing an Agent on a Java Instance (Java Standalone System) and Installing an Agent on a Java Instance (Double Stack System)), the Customizing destination is automatically created during the registration of the agent.

You only require the following procedure if you have manually registered the agent in accordance with Registering SAPCCMS with the Option -j2ee.

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

·        Create an RFC destination in the Visual Administrator of the J2EE Engine (see Connecting J2EE Engine to the CCMS).

·        Create an RFC destination in the ABAP system with which you have registered the agent.

·        Make this destination known to the monitoring architecture.

Procedure

Creating an RFC Destination in the ABAP System

Create the RFC destination in the ABAP system with which you have registered the agent. If the agent is monitoring a Java instance in an ABAP+Java system, this is the local ABAP system. If the agent is monitoring an instance of a standalone Java system, this is CEN (see SAPCCMSR with Option j2ee).

...

       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 Visual Administrator when creating the RFC destination (see Connecting J2EE Engine to the CCMS).

       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

       8.      Call transaction RZ21.

       9.      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.

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

   11.      Save your entries.

Result

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.