Monitoring with Process Integration Monitoring (PIMON)

Since PO 7.31 SP06, the message monitoring of the AEX (PIMON) displays the messages in the XI Message protocol and the SOAP Messages.

To call the PIMON with pre-selected message IDs, you can choose the Show Related PI Messages link. In this case, only the XI messages appear.

The AEX tool site is started through the following url: http:// <host>:<Port>/dir. The monitor is called through the Configuration and Monitoring Home link . The WS calls in the message list appear here as well.

The Business Log is accessed through the SAP NetWeaver Administrator Troubleshooting tab, under Processes and Tasks → Business Logs. Selecting an item in the Business Log allows you to view details about that item. Choosing the Container ID(that is, process ID) for the item in the Details tab allows you to go to the applicable process.

The figure shows the required settings to see all logs.

When the monitoring is started, you see tabular displays.

The figure, PIMON Overview, shows the tabular view of the message overview, including status and other relevant data. Depending on your needs, you can select a predefined hourly, daily, weekly, monthly, or yearly time range.

You can make a selection by choosing one of the columns containing the message statuses on the left of the screen. The specific set of messages for that particular integration scenario will be opened on the Database tab. Take note that your log and trace and message retention settings should be properly configured in order to display messages with certain statuses on the Database tab.

Once the messages are displayed, you can either apply additional filters or select a particular message from the list presented on the Database tab. You can then proceed to analyze different attributes (processing context data, header information, payload, logs, etc.) of the message, or (if permitted by the message status) you can cancel or retry all messages with that particular status. The third and last tab (Archive) shows all messages (or their metadata) that have been previously archived.

Each AEX installation has its own SAP PI local monitoring tool that you can use to monitor different system areas, including message traffic and communication channels and data and runtime caches.

SAP PI local monitoring (PIMON) can be accessed at http://<hostname>:<port>/ pimon. Via SAP PI local monitoring, you can access the following AEX monitoring tools:

• Message Monitoring

  Main message monitoring tool for all messages processed via the AEX. It shows aggregated and fine-grained information about the status of messages sent and received. Manage individual messages, for example, by resending individual message versions.

• IDoc Adapter Monitor

  Extensive IDoc monitoring tool, with an overview of all message traffic and metadata processed via the AEX Central Adapter Engine.

• Channel Independent Logs

  Display execution steps (in a very simple way) of adapters that cannot be assigned to a particular communication channel.

• Adapter Engine Status

  Provides detailed information about the adapter engine, including queues, message traffic (for example, amount of asynchronous or synchronous message backlog), database locks, overview of messages processed or being processed per sender, and receiver components.

• Cache Monitor

  Provides an overview of current cache objects maintained by the adapter engine and mapping runtime.

• Performance Monitoring

  Monitor the performance of message processing by inspecting the amount of processed data over various periods of time and the message processing time for individual adapter modules. Additional configuration is needed in the configuration tool for this functionality to work properly.

• Background Job Monitor

  
Displays an overview of background jobs (for example, adapter engine, adapter framework scheduler jobs, and so on) and offers the ability to manage them.

• CPA Cache History

  The traditional CPA cache monitor that displays an overview of cache refresh actions and their statuses.

The figure illustrates the typical steps of debugging a process.

The SAP NetWeaver Developer Studio (NWDS) Process Debugger includes the following features:

• Debugging of running process instances at the model level.

• Stepping over, into, and out of a subflow.

• Stopping at breakpoints.

• Resuming process execution.

• Inspecting process context.

• Sending notification of process errors.

• Initiating new processes.

• Attaching new processes started outside of NWDS.

The Process Debugger must be configured to initiate process debugging. Depending on your configuration, either a new process instance is created or the debugger waits for a new process instance to start. Once the target process starts, the debugger attaches to it.

To set up a process debug configuration, use the following high level procedure (as shown in the figure, Process Debug Configuration — Main Tab):

1. In the Debug Configuration window, choose the process type, then choose the New button.

2. Enter a name for the new debug configuration.

3. Choose the project and the process you want to debug.

4. Choose the AS Java you want to debug on.

The figure illustrates the steps, performed in this screen.

The process debugger can be used to initiate a new process from SAP NWDS or to attach to new processes that are started outside of SAP NWDS. This is configured on the Arguments tab.

1. Choose the radio button Attach to all process instances for the debugger to attached to all process instances started outside of NWDS.

2. Choose the radio button Attach to a new process instances to start a new process instance from NWDS. You must also enter the Web service input values here.

In the debug configuration, choose Debug for the debug configuration you are using. The Debug perspective opens. Depending on the configuration, either a new process instance is created, or the debugger will wait for a new process instance to be started.

The figure shows the area on the very far right side, which contains the required Start command.