Show TOC

Setting Up GRMG Monitoring of the SAP NetWeaver Business WarehouseLocate this document in the navigation structure

Use

If you are operating a SAP NetWeaver Business Warehouse with a release specified in SAP Note 706290 in your system landscape, you can use GRMG to monitor the availability of the following BW components:

  • UDC Enterprise Beans
  • SAP BI Java connectors
  • Metamodel Repository
  • RFC destination for the BW system
Prerequisites
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 front end.
  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.

    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:
    1. Choose the Append Line button.
    2. 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>

    3. Save your changes and confirm that you want to use a new component name.
    4. Enter a description of the component. When doing so, use the following naming convention: SAP BI Java Connectors <n> (where <n> is the value specified for CONNECT<n> above).
    5. 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 NetWeaver Administrator. To do this, choose Start of the navigation path Configuration Management Next navigation step Infrastructure Management Next navigation step JCo RFC Destinations End of the navigation path.

    Choose the RFC destination for the BW system and transfer the values from the Host Information and User Information tab page to the following lines of the editable properties:

    ApplicationServerHostClientLanguagePasswordSystemNumberUserName

  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)

  1. 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.
  2. 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 Start of the navigation path BI UDC Next navigation step GRMG: SAP BI UD Connect on <Hostname> End of the navigation path.
Result

You have set up and started the availability monitoring of the specified BW components.