Asynchronous Service Operation Publication

Understanding Asynchronous Service Operation Publication

This section describes the flow of an asynchronous service operation publication through PeopleSoft Integration Broker, as well as the status of the service operations as they appear in Service Operations Monitor.

Asynchronous Publish of Service Operation Instances

This topic describes asynchronous publishing of service operation instances in PeopleSoft Integration Broker.

This example illustrates asynchronous publish of a service operation instance in the messaging system:

Asynchronous publication of an operation instance

The following table describes the processing steps of an asynchronous publication of a service operation instance in PeopleSoft Integration Broker:

Step	Process
1	The service operation is published and enters the message queue. The instance is written to the PSAPMSGPUBHDR table in the database, but is not yet dispatched. The broker dispatcher process picks up the service operation instance from its queue. During this stage, the service operation instance status in the Service Operations Monitor is New.
2	The broker dispatcher process passes the service operation instance to the broker handler process. During this stage, the service operation instance status in the Service Operations Monitor is Started.
3	The broker handler process accepts the service operation instance, reads the data, and runs the routing rules to determine where the publication needs to be delivered. The broker handler process then writes a publication contract in the PSAPMSGPUBCON table and notifies the publication contractor service that it has an item to process. During this stage, the service operation instance status in the Service Operation Monitor is Working.
4	After the service operation is stored in the publication contact queue, the status of the publication contract in the Service Operations Monitor is New, the service operation instance status is Done, and the publication dispatcher process picks up the publication contract from its queue.
5	The publication dispatcher process passes the service operation instance to the publication handler process. During this stage, the publication contract status in the Service Operations Monitor is Started.

You view service operation instance status information on the Operation Instances page of the Service Operations Monitor. To access the page select PeopleTools, and then Integration Broker, and then Service Operations Monitor, and then Monitor, and then Monitor Asynchronous Services, and then Operation Instances.

See Integration Broker Service Operations Monitor: Monitoring Asynchronous Service Operation Instances.

Asynchronous Publish of Publication Contracts

This topic discusses asynchronous publishing of publication contracts in PeopleSoft Integration Broker.

This example illustrates the flow of an asynchronous publication contract through the messaging system.

The following table describes the processing steps of an asynchronous publish of a publication contract in PeopleSoft Integration Broker:

Step	Process
1	The publication dispatcher picks up the publication contract from the publication contract queue.
2	The publication contract is written to the PSAPMSGPUBCON table in the database, but is not yet dispatched. The publication dispatcher process passes the publication contract to the publication handler process. At this stage the status of the publication contract in the Service Operation Monitor is Started.
3	The publication handler process accepts the publication contract and attempts to deliver the service operation to the integration gateway. At this stage, the status of the publication contract in the Service Operations Monitor is Working.
4	The integration gateway attempts to pass the publication contract to the destination node.
5	The integration gateway passes the status of the publication contract back to the publication handler.
6	The publication handler updates the Service Operations Monitor with the status of the publication contract. The typical statuses that displays in the Service Operations Monitor are: Done. The subscribing node successfully  received the contract. Timeout.  The system timed out before the  transaction processing was completed. Retry.  The system encountered and error.  The retry is automatic. When service operations have Retry status, the service operations are not resent until an internal ping is successful. This ping is similar to a node ping. The publication Contract dispatcher, as part of its on idle processing, pings a node that is in Retry status and verifies if the connection is reestablished. When the ping is successful the publication Contract dispatcher resends the service operation. The service operation goes back to the publication handler process and returns to Working status.

You can view the status information for the publication contract using the publication Contracts page in the Service Operations Monitor. To access the page, select PeopleTools, and then Integration Broker, and then Service Operations Monitor, and then Monitor, and then Monitor Asynchronous Services, and then Publication Contracts.

See Integration Broker Service Operations Monitor: Monitoring Publication Contracts.

The Service Operations Monitor may display statuses for publication contracts other than those discussed in this section.

See Integration Broker Service Operations Monitor: Understanding Asynchronous Service Operations Statuses