Hierarchy

⤷

⤷

IMG Activity
ID | BW_UDC_CCMS | Install Availability Monitoring for UD Connect in CCMS |
Transaction Code | S_BR9_97000004 | (empty) |
Created on | 20040811 | |
Customizing Attributes | BW_UDC_CCMS | Install Availability Monitoring for UD Connect in CCMS |
Customizing Activity | BW_UDC_CCMS | Install Availability Monitoring for UD Connect in CCMS |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | BW_UDC_CCMS |
Use
The central monitoring system in the CCMS uses the Generic Request and Message Generator (GRMG) to check the availability of the SAP J2EE Engine at set intervals. If the availability check fails, an alert is triggered in the central monitoring system. This helps you to establish whether servers or processes have failed in the J2EE Engine. You can use the CCMS Alert Monitor (transaction RZ20) to check whether alerts have been triggered for the UD Connect scenario.
Before you can use availability monitoring with UD Connect, you have to configure the settings relevant to your installation in transaction GRMG. These settings are saved in file grmg-customizing.xml. This file is delivered with the application BI GRMG (file bi_sdk_grmg.ear) and is stored in the BI-GRMG directory for your installation.
Requirements
- The monitoring system has release level 6.20, SP 29 or 6.40 or higher.
- BIMMRXX_X.SCA and BIUDIXX_X.SCA have been installed successfully in the SAP J2EE Engine.
- File BIUDIXX_X.SCA is available.
Standard settings
Activities
Configuration of Monitoring Settings:
- Unpack the Customizing file grmg-customizing.xml from file bi_sdk_grmg.ear. You will find this EAR file in BIUDIXX_X.SCA.
- Edit file grmg-customizing.xml:
- Replace %SID with your SAP system ID.
- Replace %HOST with the host name of your SAP system.
- Start transaction GRMG.
- Load the Customizing file. Choose Upload, navigate to file grmg-customizing.xml and load the file.
- Choose entry BI UDC from the list of GRMG Availability Monitoring Scenarios.
- Choose Edit GRMG Customizing.
- Modify field URL / Destination. Replace %HOST and %PORT with the values of the J2EE server on which you set up UD Connect.
- Configure the JNDI names. The following JNDI names are valid for the BI Java Connectors as the default:
ComponentName PropertyName PropertyValue
BI JDBC Connector: CONNECT0 JNDI_Name SDK_JDBC
BI XMLA Connector: CONNECT1 JNDI_Name SDK_XMLA
BI ODBO Connector: CONNECT2 JNDI_Name SDK_ODBO
BI SAP Query Connector: CONNECT3 JNDI_Name SDK_SAPQ
- If you have copied your connector or you have installed additional connectors, specify new entries by choosing Insert Rows, and enter the following values:
- Components: CONNECT4 (or CONNECT5, CONNECT6 etc., whereby the number is increased by one for each new connector).
- Version: 1
- Property name: JNDI_Name
- Property name: <JNDI Name for your connector>
- In the UD Connect scenario, JNDI-Names start with SDK_.
- Save your entries.
- In the New Components dialog box, choose Yes to create the new components with the names specified.
- In the Component Description dialog box, enter a description for the new component. Use the following text:
- SAP BI Java Connectors <Name>
- (<Name> cannot be JDBC, XMLA, ODBO, SAPQ; the text for the component description must be unique).
- Choose Continue (Enter) to accept the description and confirm the next window by choosing Continue (Enter).
- Choose Save to save the new component. Repeat steps a - f for each copy of the connector.
- Modify all the properties of the RFC components to the values of the BI-RFC connection properties. You will find these values using the J2EE Administrator in Service JCo RFC Provider. Choose the RFC destination for your BI system to find the properties for the corresponding entry in screen GRMG Customizing:
ApplicationServerHost
Client
Language
Password
SystemNumber
UserName
- Save your entries.
Start Scenario Manually:
To check whether the scenario works, select scenario BI UDC and choose Start (start selected GRMG scenarios). After starting the scenario, a green check should appear in the scenario execution field if the scenario works.
Example
Business Attributes
ASAP Roadmap ID | 262 | Technical and Graphical Settings |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | BW_UDC_CCMS | 0 | ARS0000022 | Warehouse Management |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
IMGDUMMY | D - Dummy object | GRMG |
History
Last changed by/on | SAP | 20050121 |
SAP Release Created in |