Simple Approach for CCMS-Monitoring of Communication Channels

The SAP Computing Center Management System (CCMS) provides a special alert monitor for SAP NetWeaver Process Integration (PI). This monitor is able to monitor several components like Integration Engine, qRFC, ESR, Directory, etc, but the monitoring of communication channels is not supported.

http://help.sap.com/saphelp_nw73/helpdata/en/4b/a70e9413f46579e10000000a421937/content.htm

The following approach is trying to close this gap and might be especially helpful for sender communication channels in a non-messaged-based error state. For example. a file sender channel is not able to reach the FTP host. It is applicable for all NetWeaver PI systems >= NW2004 SPS 19.

ChannelAdminServlet

The ChannelAdminServlet provides an API for checking communication channels of the Adapter Engine externally (available since NW2004 SPS 19).

http://help.sap.com/saphelp_nw73/helpdata/en/cf/504a550ae6274495e2ce30d176f33b/frameset.htm

Prerequisite

Users must have the action xi_af_channel_admin_display assigned (default: UME-role SAP_XI_MONITOR_J2EE)

Procedure

To check communication channels externally, you use an HTTP GET or POST request to the following URL:

http(s)://host:port/AdapterFramework/ChannelAdminServlet?action=status&party=party&service=service&channel=channel

party	Identifies the party of the channel to be administered. You can use an asterisk (*) as a placeholder to administer several channels simultaneously.
service	Identifies the communication component of the channel to be administered. You can use an asterisk (*) as a placeholder to administer several channels simultaneously.
channel	Identifies the name of the channel to be administered. You can use an asterisk (*) as a placeholder to administer several channels simultaneously.

In the event of internal runtime errors, the HTTP response code is set to 503. To monitor the status of the selected channels, the field ChannelState is relevant. Possible values are ERROR, OK, INACTIVE, UNKNOWN, UNREGISTERED.

Back

Creating the GRMG-Lite Scenario

You can use the Generic Request and Message Generator (GRMG) to monitor the availability of technical components and entire business processes.

http://help.sap.com/saphelp_nw73/helpdata/en/cf/504a550ae6274495e2ce30d176f33b/frameset.htm

Prerequisite

In general it is possible to use a RFC destination or a direct URL. For operating reasons a RFC destination might be more efficient. Use the already mentioned URL path to the adapter engine. Enter a user with required authorization on the Logon & Security tab. Testing the destination should return the XML response.

Procedure

You can monitor the availability of a URL by creating a GRMG Lite scenario. You do not need to implement a GRMG application to use this function check. Instead, GRMG Lite uses standard capabilities of the HTTP protocol.
http://help.sap.com/saphelp_nw73/helpdata/en/48/29203908e74bbae10000000a42189b/content.htm

Start the GRMG infrastructure by calling transaction GRMG and create a GRMG-Lite scenario.

Scenario Name	Determines the MTE class of the monitoring context (the MTE class of the monitoring context is GRMG_<scenario name>)
Version (Scenario)	Field, which you can leave empty, since GRMG has automatic version numbering
Description (Context Name)	Name of the monitoring context and therefore of the root node under which the scenario is displayed in the Alert Monitor
URL/RFC Destination	RFC destination
Component name	Determines the MTE class of the summary node (GRMG_<scenario name>_<component name>) and of the monitoring object (GRMG_<component name>_OBJ)
Version (Component)	Field, which you can leave empty, since GRMG has automatic version numbering
Description (Superordinate Name)	Name of the summary node and therefore of the subtree that contains the availability and the status messages for the monitored URL
HTTP Test Method	HTTP GET method to scan HTML output for CHECK STRING parameters

Scan the XML output of the ChannelAdminServlet, whether the state of a channel is in error.

Enter the RFC destination created previously.

Start the Scenario

Back

Operating the Alert Monitor

You can use the Alert Monitor to perform complete and detailed monitoring of all SAP and non-SAP systems, the host systems, and the database.

http://help.sap.com/saphelp_nw73/helpdata/en/71/4f3d66a95011d194a500a0c93033f7/content.htm

Start the alert monitor by calling transaction RZ20 and open the Availability and Performance Overview.

All errors generate alerts, which are displayed in a tree structure.

Back

Forwarding Alerts to Alert Management (ALM)

The figure below represents a possible route of the CCMS alerts from the communication channels that triggers the alert through the central monitoring system (CEN) and RFC to the central ALM system. The ALM system forwards the alerts in every case to the relevant display program of the recipients (Alert Inbox, UWL) and as an e-mail, fax, or SMS, if these external communication methods are configured in SAPconnect

http://help.sap.com/saphelp_nw73/helpdata/en/3f/567ddea69d3d4c93a6aedabd08899e/frameset.htm