Understanding Messaging System Performance Statistics

The Service Operations Monitor provides a Statistics page that enables you to view performance statistics for asynchronous and synchronous service operations that flow through PeopleSoft Integration Broker. The statistics can help you to identify bottlenecks and other performance issues in your integration system.

The Service Operation Monitor provides performance statistics for the following service operation transaction types:

  • Inbound asynchronous.

  • Outbound asynchronous.

  • Inbound synchronous.

  • Outbound synchronous.

Definitions for these service operations are provided elsewhere in the product documentation.

See Service Operation Types.

The following table lists the system processing components for which PeopleSoft Integration Broker captures performance statistics and briefly describes the types of processing that each performs:

Field or Control

Definition
Application Server

The application server performs all data handling, processing event handlers, performs security, routes service operations, performs transformations, and manages load balancing and master/slave processing, and more.
Broker (Handler)

The broker analyzes all service operations in the queue and determines the transaction type. Based on the transaction type, it creates a subscription contract, publication contract, or both.
Gateway

On inbound requests, the integration gateway performs request serialization/deserialization, request authentication, applies transformations, and performs the Jolt request to the application server. On outbound requests, the integration gateway applies transformations, and determines the target connector for the request and hands off the request accordingly.

For statistics to display for the integration gateway processing you must enable the statistics feature on the integration gateway.

See Enabling the System Performance Statistics Feature.
Publication (Contract Handler)

The publication contract handler routes service operations to another destination.
Remote Server

When you perform synchronous transactions with PeopleSoft system, those systems send back processing statistics with their requests and/or responses. These statistics appear in the category Remote Server on the statistics pages.
Subscription (Contract Handler)

The subscription contract handler runs PeopleCode associated with a service operation.
Tuxedo Queue

PeopleSoft Integration Broker includes a set of Oracle Tuxedo servers that monitor database tables and process items in the tables. The processing can include running PeopleCode programs, creating publication and subscription contracts, and so forth.

Several of the Statistics pages provide information for the processing on these queues.

When you view the statistical details of system processing, some of the numbers fall into the categories of Overhead. and Connection Overhead.

Statistics in these categories are for miscellaneous processing that do no fall into the major categories shown, but count toward the overall processing on a component or for the transaction.

The following table lists types of overhead processing that can be included in these categories. The information in the table is not exhaustive, and other items, processing, and even system configuration and capacity may contribute to overhead processing statistics generated on your system:

Component

Example of Overhead Processing

All

  • Calls between processing.

  • Receiving/handing off a transaction to another component.

  • Internal processing.

  • And so on.

Broker handler

  • Time taken to determine the contracts to create.

  • And so on.

Integration gateway

  • Determining the connector to use for a transaction.

  • Data deserialization and serialization.

  • Authentication.

  • Performing the Jolt request to the application server.

  • And so on.

Application server

  • Authentication.

  • Data compression.

  • And so on.

Note the following information regarding processing times that appear in the Statistics pages:

  • All processing times are averages.

  • Processing times are displayed in milliseconds (ms.).

  • Processing times appear in the following format: Avg.(x) nn.nn ms.

    The value of x in parentheses is the number of transactions on which the average processing time is based.

    The value of nn.nn is the average processing time in milliseconds (ms.).

  • Processing times of less than one millisecond appear as 00.00 ms.

  • In some instances the system displays No Data Available for a system component.

    In such situations no processing was performed on the component.

    As an example, the link for the Gateway component might display No Data Available if you were viewing statistics for transactions processed with the InBoundPublish method, whereby the integration gateway is bypassed to publish transactions.