Show TOC Start of Content Area

Background documentation No Data From PMI Java Agents  Locate the document in its SAP Library structure

Problem Description

There is no information from PMI Java agents monitoring the XI Adapter Framework available in the End-to-End-Monitoring view of the XI Runtime Workbench. Although an XI message has passed the XI Adapter Framework, the End-to-End-Monitoring does not show any information about this XI message.

Scenario Type:

Error analysis

NetWeaver Component:

SAP Exchange Infrastructure (BC-XI)

PMI Service on the AS Java (BC-SRV-PMI)

Validity:

AS Java version >= 6.30 SP7

There is only one other way to see the monitored data: switch on the PMI service trace, that is, set the log severity of the log location com.sap.pmi to ALL and see the PMI service trace after an XI message has been sent through the XI Adapter Framework.

Possible Error Sources

Error Source

Analysis

PMI service not started

Start the PMI service

PMI Java agent not active

Check whether the PMI Java agents respective the PMI monitoring is active

Incorrect HTTP destination

Check the HTTP destination pmistore.

Decision Roadmap

Prerequisites

-

Main Tools

SAP NetWeaver Administrator

Analysis

Possible reasons for this problem are as follows:

...

1.   The PMI service has not been started

Solution:

Start the PMI service in the SAP NetWeaver Administrator.

Entry in system/server log

Location

com.sap.pmi.Agent

Message

PMI service not running (most likely because HTTP destination pmistore is missing), so no PMI agent data can be written.

2.   PMI Java agents not active

Solution:

Check whether PMI Java agents are active by calling http://<AS Java_server>:<port>/pmi/config.

This shows a list of the active agent signatures in XML format. If this list is empty, check whether PMI monitoring is activated for the XI Adapter Framework (see Integrating Process-Monitoring in XI).

Entry in system/server log

Location

com.sap.pmi.Agent

Message

PMI agent configuration missing, most likely because no PMI process is active.

3.   HTTP Destination “pmistore” incorrect

Solution:

For the PMI service to work correctly, there must be a HTTP destination pmistore configured in the AS Java’s destination service. This destination points to the HTTP service of the SAP NetWeaver Application Server ABAP stack receiving the tracking records from PMI service, that is, http://<abap_server>:<port>/sap/bc/spi_gate

Check whether HTTP destination pmistore is defined in the AS Java’s destination service and whether it is correct. The user used in this destination must exist in the ABAP system und must have sufficient privileges.

See note 771436.

Entries in system/server log

a)

Location

com.sap.pmi.j2ee.PmiServiceFrame

Message

No HTTP destination pmistore found. See the PMI documentation.

b)

Location

com.sap.pmi.Agent

Message

PMI service not running (most likely because HTTP destination "pmistore" is missing), so no PMI agent data can be written.

c)

Location

com.sap.pmi.io.HttpPostThread

Message

Error sending PMI records to <url>, HTTP response: none.

Check the HTTP destination "pmistore".

 

Additional Information

Process Monitoring with PMI

PMI Service

Integrating Process-Monitoring in XI

 

End of Content Area