No Data From PMI Java Agents

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 J2EE Engine
Validity:	J2EE Engine 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 in the Visual Administrator
PMI Java agent not active	Check whether the PMI Java agents are active and whether PMI monitoring is active
Incorrect HTTP destination	Check the HTTP destination pmistore.

Decision Roadmap

Prerequisites

-

Main Tools

Visual Administrator

Log Viewer

Analysis

Possible reasons for this problem are as follows:

...

1. The PMI service has not been started

Solution:

Start the PMI service in the Visual 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://:/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 J2EE Engine’s destination service. This destination points to the HTTP service of the SAP Web AS ABAP stack receiving the tracking records from PMI service, that is, http://:/sap/bc/spi_gate

Check whether HTTP destination pmistore is defined in the J2EE Engine’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.

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 http://localhost:5000/, HTTP response: none. Check the HTTP destination "pmistore".