Asynchronous Service Operation Subscription
This section discusses:
-
Asynchronous subscription of a service operation instance.
-
Asynchronous subscription contracts.
Understanding Asynchronous Service Operation Subscription
This section describes the flow of an asynchronous service operation subscription through PeopleSoft Integration Broker, as well as the service operation status at each stage of the process.
Asynchronous Subscription of Service Operation Instances
This topic describes asynchronous subscription process of service operation instances in PeopleSoft Integration Broker.
This example illustrates the flow of an asynchronous service operation subscription through PeopleSoft Integration Broker.
The following table describes the processing steps of an asynchronous subscription of a service operation instance in PeopleSoft Integration Broker:
| Step | Process |
|---|---|
|
1 |
The service operation enters the message queue. The instance is written to the database, but not yet dispatched The broker dispatcher process picks up the service operation instance from its queue. During this stage, the status of the service operation instance 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 status of the service operation instance in the Service Operations Monitor is Started. |
|
3 |
The broker handler process accepts the service operation instance, reads the data, and runs the subscription routing rules to determine if the service operation needs to be processed locally. During this stage, the status of the service operation instance in the Service Operations Monitor is Working. |
|
4 |
The broker handler process then writes a subscription contract in the PSAPMSGPUBCON table (the subscription contract queue) and notifies the subscription contractor service that it has an item to process. During this stage, the status of the service operation instance in the Service Operations Monitor is Working. |
|
5 |
Once the service operation is stored in the subscription contact queue, the status of the service operation instance in the Service Operations Monitor is Done. Processing of the subscription contract begins as the subscription dispatcher process picks up the subscription contract from its queue, and the status of the subscription contract in the Service Operations Monitor is New. In this example, at the point when the status of the asynchronous service operation instance is Done, the subscription contract status is New. Asynchronous subscription contract processing is described in the next section. |
You can view service operation instance status on the Operation Instances page of the Service Operations Monitor. To access this page, select
See Integration Broker Service Operations Monitor: Monitoring Asynchronous Service Operation Instances.
The Service Operations Monitor may display statuses for subscription instances other than those discussed in this section.
Asynchronous Subscription Contract
This topic discuses asynchronous subscription contract processing in PeopleSoft Integration Broker.
This example illustrates the flow of an asynchronous subscription contract.
The following table describes the processing steps of an asynchronous subscription contract in PeopleSoft Integration Broker:
| Step | Process |
|---|---|
|
1 |
The subscription dispatchers picks up the contract from the subscription contract queue. |
|
2 |
The subscription dispatcher process passes the subscription contract to the subscription handler process. At this stage the status of the subscription contract in the Service Operations Monitor is Started. |
|
3 |
The subscription handler process accepts the subscription contract and runs the notification PeopleCode. |
|
4 |
In the example shown in the diagram, the notification PeopleCode then uses the service operation data to update application data tables. However, the notification PeopleCode can use the service operation data as input to look up information, create and publish another service operation, and so forth. At this stage, the status of the publication contract in the Service Operations Monitor is Working. |
|
5 |
The subscription handler passes the status of the subscription contract to the Service Operations Monitor. The typical statuses that display in the Service Operations Monitor for an asynchronous subscription contract are:
|
To view status information for subscription contracts, use the Subscription Contracts page in the Services Operation Monitor. To access the page select
See Integration Broker Service Operations Monitor: Monitoring Subscription Contracts.
The Service Operations Monitor may display statuses for subscription contracts other than those discussed in this section.