Setting Up GRMG Monitoring of the Business
Warehouse 
Use
You can use the GRMG to monitoring the availability of the following BW components (for more information about this, see SAP Note 706290):
· UDC Enterprise Beans
· SAP BI Java connectors
· Metamodel Repository
· RFC destination for the BW system
Prerequisites
· You have installed a BI Java component for which you want to monitor the availability with the GRMG.
·
You have installed
the CCMS agent SAPCCMSR with the j2ee option on the host of the J2EE Engine
(see 
Installing and
Registering CCMS Agents) and registered it with the central monitoring
system (CEN).
Procedure
...
1. You can find a template for the GRMG Customizing file in the UD Connect Bean file bi_sdk_grmg.ear. The name of this file is grmg-customizing.xml. Copy this file to a location that is readable from your frontend.
2. Call transaction GRMG in CEN.
3.
Choose the 
Upload button, and then select the above file
grmg-customizing.xml.
4.
Select the line
with the name BI UDC, and choose the button 
Edit GRMG Customizing.
5. Edit the URL/Destination input field. Replace hostname and port number with the corresponding values for your J2EE server, on which you have performed deployment of UD Connect.
6. Enter the values of the property name JNDI_Name for component CONNECT0. This is the JNDI name of a connector for which you have performed deployment.
You can view
the corresponding connectors in the Visual
Administrator; to do this, choose Cluster ® Server
® Services
® Connector
Container in the
navigation bar; you can see the JNDI name for the selected connector on the
tab page Runtime ® Managed Connection
Factory ® Connection
Definition.
By default, the BI Java connectors have the following JNDI names:
Connector |
JNDI Name |
BI JDBC Connector |
SDK_JDBC |
BI ODBO Connector |
SDK_ODBO |
BI SAP Query Connector |
SDK_SAPQ |
BI XMLA Connector |
SDK_XMLA |
If you have cloned your connector, specify the name of the clone.
7. Create GRMG components for additional BI connectors:
a.
Choose the 
Append Line button.
b. Enter the following values in the new line:
Column |
Value |
Component |
CONNECT<n> (start with 1 and increment upwards for each additional connector) |
Version Type |
1 |
Property Name |
JNDI_Name |
Property Value |
<JNDI Name of the connector> |
c. Save your changes and confirm that you want to use a new component name.
d. Enter a description of the component. Use the following naming convention when doing so: SAP BI Java Connectors <n>(where <n> is the value specified for CONNECT<n> above).
e. Choose Continue, and confirm that you have created a new component
8. Adjust the specifications for the component RFC. In doing so, you specify the RFC destination for the BW system. You can find the corresponding values in the SAP Visual Administrator. To do this, in the navigation bar, choose Cluster ® Server ® Services ® JCo RFC Provider.
Choose the RFC destination for the BW system and transfer the values from the Repository group box to the following lines of the editable properties:
ApplicationServerHost
Client
Language
Password
SystemNumber
UserName
9. Save your entries and exit the screen for editing the GRMG Customizing.
10.
Select the scenario
that you have just edited, and choose 
Start. As of this point, the scenario is periodically
executed.
Checking the Configuration (Optional)
11.
After you have
started the scenario, you can find out from the Scenario Execution
Status, whether the
scenario was correctly executed. After the scenario has been executed, there
should be a green check mark (
)
here.
12. To view the availability data for the monitored components, call transaction RZ20 in CEN, and start the Heartbeat monitor in the SAP J2EE Monitor Templates monitor set. Expand the subtree BI UDC ® GRMG: SAP BI UD Connect on <Hostname>.
Result
You have set up and started the availability monitoring of the specified BW components.
Monitoring with the
Generic Request and Message Generator start page