Monitoring Asynchronous Integration Network Service Operations
This section discusses how to:
-
Filter asynchronous network service operation data.
-
Monitor general asynchronous network service operation data.
-
Monitor asynchronous network service operation instances.
-
Monitor asynchronous network service operation publication contracts.
-
Monitor asynchronous network service operation subscription contracts.
Common Elements Used to Filter and View Network Monitor Asynchronous Service Operation Data
The following elements are used to filter and view the query results of Network Monitor service operation data.
| Field or Control | Description |
|---|---|
|
|
Click the button to show sender and receiver details in one view, instead of on separate sender and receiver tab. Click the button again to collapse the view. |
|
Alias |
Service operation alias name if defined for the service operation. |
|
Correlation ID |
Identifier used to correlate messages sent separately into a single transaction. |
|
Creation Dttm |
Creation date and time. |
|
External Service Name |
The name of the inbound service operation received from an integration partner. This name is equivalent to the routing alias. |
|
Filter |
Click the button to filter the fetched data using the filters selected. |
|
Group By |
Indicates how the system groups returned data. The valid values are:
|
|
Last Update Dttm |
Last update date and time. |
|
Orig Transaction ID |
The original transaction ID generated and used for the service operation instance. As contracts are created another transaction ID is created for each publication or subscription contract. However, the original transaction ID is always available as a reference. |
|
Publish, Publish Node, Node Name |
Indicates the node that published the service operation. |
|
Publish Dttm |
Publish date and time. |
|
Queue Level |
Indicates the pub/sub queue for which to display information. The valid values are:
|
|
Queue Name |
Name of the service operation queue. |
|
Queue Sequence ID |
Identifies the sequence of a particular service operation in a queue. This field is applicable to only service operations in ordered queues. |
|
Segment Number |
When message segments are implemented, indicates the number of the segment message |
|
Service Operation |
Name of the service operation. |
|
Service Operation Version, Version |
Indicates the version of the service operation. |
|
Status, Status String |
Processing status of the service operation. The Network Monitor uses the same processing statuses as those that appear in the Service Operations Monitor. See Integration Broker Service Operations Monitor: Understanding Asynchronous Service Operations StatusesIntegration Broker Service Operations Monitor: Understanding Synchronous Service Operation Statuses. |
|
Sub Node |
The name of the subscribing node. |
|
Sub Queue |
If queue partitioning exists for a queue, a Sub Queue column appears in the Results grid on the Operation Instances page, Publication Contracts page and Subscription Contracts page . Click the link to open the Sub Queue Message Queue page to view all transactions in the sub queue. |
|
Timestamp |
Date and time of the publication. |
|
Time Period |
Use the options in the Time Period group box to limit the query results to transactions that occurred during a specific date range or that occurred between a specific date and time range. The Time Period group box features four fields for searching by date and time: From Date, To Date, From Time and To Time. If you complete just the date fields, the time fields automatically populate from 12:01 a.m. to 11:59 p.m. When left blank, no date or time is used as part of the search criteria. |
|
Transaction ID |
The unique identifier for a transaction. |
Monitoring General Asynchronous Network Service Operation Information
Use the Monitor Overview page (IB_INTNET_OVRVIEW) for a high-level overview of the status of asynchronous service operation transactions in the integration network. You can group transactions by queue or service operation for viewing. To access this page, select
This example illustrates the Network Monitor – Monitor Overview page.

When you access the page, the system automatically synchronizes the with the database for the selected node in the Network Node List. The processing status of asynchronous transactions appears in the Results grid at the bottom of the page. The number of operation instances in a particular status display as a linked value. Click the link to open the data in the Operation Instances page where you can view more detailed information.
If you change the node for which to view information, by clicking a different node name in the Network Node List, the system automatically resynchronizes the page with the most up-to-date transaction information for the node.
By default, the system queries the database by service operation queue for operation instance information.
You can query the database by modifying the query filters and then clicking the Filter button. The filters available on the page are:
-
Publish.
-
Query Level.
-
Group By.
-
Time Period.
The data filters and data elements that appear in the Results grid are described in the Common Elements Used to Filter and View Asynchronous Network Monitor Data section of this topic.
Monitoring Asynchronous Network Service Operation Instances
Use the Operation Instances page (IB_INTNET_PUBHDR) to monitor the status and details related to individual asynchronous service operation instances. To access this page, select and click the Operation Instances tab.
This example illustrates the Network Monitor – Operation Instances page.

The example shows a partial view of the query results appearing in the Results grid.
If you change the node for which to view information, by clicking a different node name in the Network Node List, the system automatically resynchronizes the page with the most up-to-date transaction information for the node.
By default, the system queries the database by service operation queue and the asynchronous processing status Done.
You can query the database by modifying the query filters and then clicking the Filter button. The filters available on the page are:
-
Node Name.
-
External Service Name.
-
Service Operation.
-
Queue Name.
-
Transaction ID.
-
Correlation ID.
-
Status.
-
Time Period.
Query results appear in the Results Grid. If the queue in which a transaction is processed is partitioned, a hyperlinked transaction ID appears in the Sub Queue column in the Results grid. Click the link to view all network service operations in the sub queue.
For each transaction in the Results grid a Details link appears. Click the Details link access the Asynchronous Details page and to view additional details for the transaction. Based on the processing status of the transaction, the Asynchronous Details page enables you to view any transaction error messages and resubmit or cancel the transaction.
The data filters and data elements that appear in the Results grid are described in the “Common Elements Used to Filter and View Asynchronous Network Monitor Data” section of this topic.
Monitoring Asynchronous Network Service Operation Publication Contracts
Use the Publications Contracts page (IB_INTNET_PUBCON) to monitor the status and details related to asynchronous service operation publication contracts. To access this page, select and click the Publication Contracts tab.
This example illustrates the Network Monitor – Publication Contracts page. A partial view of the query results appear in the Results grid at the bottom of the example..

If you change the node for which to view information, by clicking a different node name in the Network Node List, the system automatically resynchronizes the page with the most up-to-date transaction information for the node.
By default, the system queries the database by service operation queue and the asynchronous processing status Done.
You can query the database by modifying the query filters and then clicking the Filter button. The filters available on the page are:
-
Node Name.
-
Service Operation.
-
Queue Name.
-
Status.
-
Transaction ID.
-
Correlation ID.
-
Subscriber Node.
-
Time Period.
Query results appear in the Results grid.
The data filters and data elements that appear in the Results grid are described in the Common Elements Used to Filter and View Asynchronous Network Monitor Data section.
If the queue in which a transaction is processed is partitioned, a hyperlinked transaction ID appears in the Sub Queue column in the Results grid. Click the link to view all network service operations in the sub queue.
For each transaction in the Results grid a Details link appears. Click the Details link to access the Asynchronous Details page (IB_INTNET_DET) and to view additional details for the transaction. Based on the processing status of the transaction, the Asynchronous Details page enables you to view any transaction error messages and resubmit or cancel the transaction.
This example illustrates the details for an asynchronous network publication contract.

The top portion of the Asynchronous Details page shows the information that appears in the Results grid of the Publication Contracts page.
The Publication Contracts grid at the bottom of the page shows additional information about the transaction.
The Actions tab shows each node that is subscribing to the contract. In this example, the QE_LOCAL is subscribing to the contract. Depending on the processing status, the Resubmit and Cancel buttons are active and you can perform those related actions.
See Resubmitting and Cancelling Integration Network Transactions.
If there are any processing errors with a transaction, a View Info Details link appears. Click the link to view the error information. .
The Information tab reveals details about the publication transaction, including the transaction ID, the transaction time stamp, and so on.
Monitoring Asynchronous Network Service Operation Subscription Contracts
Use the Subscription Contracts page (IB_INTNET_SUBCON) to monitor the status and details related to asynchronous service operation subscription contracts. To access this page, select and click the Subscription Contracts tab.
This example illustrates the Network Monitor – Subscription Contracts page.

If you change the node for which to view information, by clicking a different node name in the Network Node List, the system automatically resynchronizes the page with the most up-to-date transaction information for the node.
By default, the system queries the database by service operation queue and the asynchronous processing status Done.
You can query the database by modifying the query filters and then clicking the Filter button. The filters available on the page are:
-
Node Name.
-
Service Operation.
-
Queue Name.
-
Status.
-
Transaction ID.
-
Correlation ID
-
Time Period.
Query results appear in the Results grid.
The data filters and data elements that appear in the Results grid are described in the Common Elements Used to Filter and View Asynchronous Network Monitor Data section.
If the queue in which a transaction is processed is partitioned, a hyperlinked transaction ID appears in the Sub Queue column in the Results grid. Click the link to view all network service operations in the sub queue.
For each transaction in the Results grid a Details link appears. Click the Details link to access the Asynchronous Details page and to view additional details for the transaction. Based on the processing status of the transaction, the Asynchronous Details page enables you to view any transaction error messages and resubmit or cancel the transaction.
This example illustrates the Network Monitor – Asynchronous Details page for an asynchronous network subscription contract.

The top portion of the Asynchronous Details page shows the information that appears in the Results grid of the Subscription Contracts page.
The Subscription Contracts grid at the bottom of the page shows additional information about the transaction.
The Actions tab shows the service operation handler name for the subscription contract. Depending on the processing status, the Resubmit and Cancel buttons are active and you can perform those related actions.
See Resubmitting and Cancelling Integration Network Transactions.
If there are any processing errors with a transaction, a View Info Details link appears on the Actions tab. Click the link to view the error information.
The Information tab reveals details about the subscription transaction, including the transaction ID, the transaction time stamp, and so on.