Use the GRMG to monitor the availability of XI Java components. To do this, you must edit an appropriate template for a GRMG Customizing file and upload it to the central monitoring system.
So that all of the data for the XI infrastructure can be displayed in the Alert Monitor, you must create the system group ExchangeInfrastructure_Systems in the central monitoring system (CEN). This system group must contain all systems in your XI infrastructure (see Maintaining System Groups).
...
1. Call SAP Note 634771, and download the file SAP_XI30_GRMG_Cust_Template.txt from the appendix to the note. The template consists of six scenarios (enclosed by <scenario> … </scenario>); each scenario represents a component that can be monitored with the GRMG:
Component |
<scenname> |
Path Prefix |
Integration Repository |
XI_REP1 |
rep/rtc |
Integration Directory |
XI_DIR1 |
dir/rtc |
Runtime Workbench |
XI_RWB1 |
rwb/rtc |
System Landscape Directory |
XI_SLD1 |
sld/rtc |
J2SE Adapter Engine |
XI_ADP1 |
rtc |
J2EE Adapter Engine |
XI_AF1 |
AdapterFramework/rtc |
2. Delete the scenarios that you do not want to monitor with the GRMG from the template.
3. If you want to monitor multiple J2EE/J2SE Adapter Engines, copy the section for the corresponding scenario in the template, insert the copied text between any two scenarios in the template, and change the value of the tag <scenversion> in the newly inserted scenario.
4. Log on to CEN, and create an RFC destination of type HTTP for each scenario in transaction SM59.
a. If the component is running on a J2EE Engine, enter G as the type of the RFC destination; otherwise enter H as the type. By default:
Component |
Type |
Integration Repository |
G |
Integration Directory |
G |
Runtime Workbench |
G |
System Landscape Directory |
G |
J2SE Adapter Engine |
H |
J2EE Adapter Engine |
G |
b. On the Technical Settings tab page, enter:
Field |
Entry |
Target Host |
Name of the host on which the component is running |
Service Number |
Port number of the component; this is assigned during installation and can also be determined in the SLD |
Path Prefix |
One of the values from the table above, depending on the monitored component |
c. On the Logon/Security tab page, enter:
Field |
Entry |
User |
Name of the user; we recommend that you use the XIRWBUSER user here, which should be available on all components |
Password |
User password; XIRWBUSER has the initial password XIPASS (note that this is case-sensitive)
Note that, in the case of HTTP connections, the logon tickets could be intercepted. You should therefore always ensure that Secure Socket Layer (SSL) is used for encryption, or that both systems are in a protected environment. |
Security Options |
In the case of an RFC destination of type G, choose the Basic Authentication button. |
d. Save your entries.
5. In the template, replace the value of the <scenstarturl> tag in the scenarios with the relevant name of the RFC destination of type HTTP that you created above.
6. Save the GRMG Customizing file.
7. Call transaction GRMG in CEN.
8. To upload the GRMG Customizing file into CEN, choose the Upload button, and specify the above file.
9. Select the scenarios that you have just uploaded, and start these by choosing Start sel.
10. Call transaction RZ20 in CEN.
11. Expand the monitor set SAP CCMS Monitor Templates, and start the Exchange Infrastructure monitor. You can view the availability of the activated scenarios.
You have set up and started the availability monitoring of the Exchange Infrastructure.
Monitoring with the Generic Request and Message Generator start page