Kontakt

Ansicht
Dokumentation

BW_BEX_CCMS - Availability Monitoring for Information Broadcasting and BEx Web

BW_BEX_CCMS - Availability Monitoring for Information Broadcasting and BEx Web

rdisp/max_wprun_time - Maximum work process run time   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.
SAP E-Book

You want to monitor the availability of information broadcasting or BEx Web applications.

The central monitoring system uses the Generic Request and Message Generator (GRMG) to check the availability of AS Java 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 AS Java. You can use the CCMS Alert Monitor (transaction RZ20) to check whether alerts have been triggered from this scenario.

Before using monitoring, you need to configure the relevant settings for your installation. The settings are saved in grmg-customizing.xml gesichert. You can find this file under the following path:

In Windows:

<DRIVE>:\usr\sap\<SID>\JC<INSTANCE_NO>\j2ee\cluste r\server0\apps\sap.com\irj\servlet_jsp\irj\root\portalapps\ com.sap.ip.bi.portalheartbeat\xml

In Unix: /usr/sap/<SID>/JC<INSTANCE_NO>/j2ee/cluster/server0/apps /sap.com/irj/servlet_jsp/irj/root/portalapps/com.s ap.ip.bi.portalheartbeat/xml

There are two ways of configuring file grmg-customizing.xml:

  • Using the J2EE Visual Administrator
  • Using transaction GRMG

For more information on how to load file grmg-customizing.xml using the J2EE Visual Administrator, see the documentation in the Application Server Administration Guide under http://help.sap.com/saphelp_nw04/helpdata/en/8c/d7e73f2dc6f106e10000000a1550b0/frameset.htm

The following section describes how to load file grmg-customizing.xml using transaction GRMG.

Configuring the Monitoring Settings

  1. Edit file grmg-customizing.xml:
  • Search for placeholder %PASSWORD. If the placeholder does not exist, insert the following XML tags:

<! This paragraph already exists: >

<property>

<propname>initialization</propname>

<propvalue>do not change</propvalue>

</property>

<! After this point, insert the following: >

<property>

<proptype>PW</proptype>

<propname>LOGON_PASSWORD</propname>

<propvalue>%PASSWORD</propvalue>

</property>

<property>

<proptype>No_Encrypt</proptype>

<propname>LOGON_USER</propname>

<propvalue>%USER</propvalue>

</property>

<property>

<proptype>No_Encrypt</proptype>

<propname>USE_BASIC_AUTHENTICATION</propname>

<propvalue>X</propvalue>

</property>

  1. Start transaction GRMG.
  2. Load the Customizing file. Choose Upload, navigate to file grmg-customizing.xml and upload it.
  3. Select BI_WEB from the list of GRMG availability monitoring scenarios.
  4. Choose Edit/Delete and then Edit a scenario.
  5. In the Edit GRMG Customizing screen, modify the URL/Destination field.
  • Replace "%HOST" and "%PORT" with the values for the J2EE server where you configured information broadcasting or BEx Web applications.

  • Replace %SID with your SAP system ID.

  • Replace %USER with the user name of an administrator user in your SAP J2EE Engine.

  • Replace %PASSWORD with the password of the user who you have entered for %USER.

  1. Save the changes and quit the Edit GRMG Customizing screen.
  2. To check whether the scenario works, save the GRMG Availability Monitoring Scenarios screen, choose scenario BI_WEB, choose Start/Stop and then Start Scenarios. After the scenario has started, a green checkmark should appear in the Run Status field if the scenario is working properly.

Checking Monitoring Alerts

To check whether this scenario has triggered alerts, proceed as follows:

  1. In CCMS Alert Monitor, call transaction RZ20.
  2. Expand the SAP CCMS Technical Expert Monitors node and double-click the System / All Monitoring Segments / All Monitoring Contexts subnode.
  3. Expand the SAP_CCMS_<APPSERVER>_<SID>_<INSTANCE_NO> node and then the GRMG: BI_WEB: v1.0.0. %SID:%HOST node. (Replace %SID and %HOST with the values for your server). A green traffic light indicates that there are no alerts exist for a particular node. A red traffic light indicates that there are alerts for a node.
  4. Expand the subnodes for the alert that you want to see.

For more information about availability monitoring for BEx Web Applications and Information Broadcasting, see SAP Note 883356.

For more information about GRMG, see the SAP Community Network (http://sdn.sap.com). In the navigation toolbar, choose Lifecycle Management -> Operations. Then choose Monitoring -> Monitoring Availability -> Availability Monitoring GRMG. in the Knowledge Center.






TXBHW - Original Tax Base Amount in Local Currency   General Material Data  
This documentation is copyright by SAP AG.

Length: 6575 Date: 20240524 Time: 014214     sap01-206 ( 104 ms )