Basis Errors and Solutions

Monitored Services do not appear in Monitoring Service/CCMS

June 30, 2009 at 11:06 am

[component] [Engine-Status] [monitored] [monitoring] [monitoring tool] [runtime] [RWB] [smart monitoring] [Workbench]

Message Overview: redirect to Message Monitoring failsSymptom You click on one of the counters in the Message Overview, that shows the number of Messages of a certain scenario and in a certain status. A new window opens that...
Performance enhancements for Channel MonitoringSymptom Loading the channel data in Channel Monitoring takes a long time, especially when there are many channels configured for the Adapter Engine. Even using a more restrictive filter, that would include...
table in message monitoring does not offer all informationSymptom Show Start/End Time in the Message Details list. Solution The change is done for Message Monitoring. For 720 SP01 install “SOAMONBASIC01_00.SCA” or higher patch level. ...
table in message monitoring does not offer all informationSymptom The following changes in the Message List table of the Message Monitoring should be done: - Add additional hidden columns for each of the attributes in the Message Details list. -...
Message Monitoring: Error displayed for some statusSymptom The user starts Message Monitoring for the Adapter Engine. In the filter, he selects a status that only exists for the Integration Engine (e.g. “Application Error”) and starts a search for...
Navigation problem to CAE Cache Monitoring on NWAPISymptom Navigation for Central Adapter Engine Cache Monitoring from the NWAPI main page is incorrect. Reason and Prerequisites The Cache monitoring application with selected Central Adapter Engine page must be opened by...
Issue with Message Monitoring Filtering Display in NWAPISymptom Open Message Monitoring. Go to the “Database” tab and click on the “Advanced” link. This link will display all options of the advanced filter. Clicking on the “Archive” tab. You can...
Different numbers in Message Overview and Message MonitoringSymptom Your system has several server nodes. The Message Overview shows a number of Messages that does not match the number of Messages shown in Message Monitoring or when directly checking the...

Symptom

The Adapter Engine can report the backlog for XI Messages to the Java Monitoring service of the WebAS Java and from there to CCMS. The Monitoring is configured at Service level (header attribute of XI Messages) and can be switched on or off for each Sender and Reciever Service separately. This is done in the Engine Status application which is started from the Component Monitoring in the Runtime Workbench. The Message backlog for a Service should appear in the tree in the Monitoring Service (Visual Administrator) resp. in CCMS, right after monitoring was enabled for the Service in the Engine Status application. But the Service does not appear.
Other terms

RWB, Runtime Workbench, Component Monitoring, Engine-Status
Reason and Prerequisites

A Service only appears in the monitoring tree after Messages with this Service name were processed (with or without errors) since the last restart of the Adapter Engine.
Solution

With the below patch, the problem is corrected and a Service appears right after monitoring was enabled for the Service. The correction is part of the following (and newer) Support Packages:
XI 3.0 SP24XI 7.0 SP18XI 7.01 SP03PI 7.10 SP07PI 7.11 SP01

For older Support Packages, the correction is available as a patch. Please update the software components of the Adapter Engine to the patch levels maintained in section “SP Patch Level” of this note or use newer versions.
The archives and the support package stack guide can be found on the SAP Service Marketplace as described in SAP Note 952402.