Service Operation Types
PeopleSoft Integration Broker supports four types of service operations:
Asynchronous one-way.
Asynchronous request/response.
Asynchronous to synchronous.
Synchronous
Note: In this section the term transaction is used to describe the exchange of data between integration partners.
When PeopleSoft Integration Broker sends a service operation, the receiving system returns a response back to the sender. With asynchronous transactions, the response is automatically generated by the integration gateway, and it serves only to notify the sending system of the transmission status of the request . It is processed automatically by the application server, which uses that status information to update the Service Operations Monitor. With synchronous transactions, however, the response includes the content that is requested by the sending system, and it must be generated and returned by the receiving system.
PeopleSoft Integration Broker supports the operation types listed in the table.
For any operation type, the application must invoke PeopleCode, a component interface or data mover script to generate and send a service operation or to receive and process a service operation.
Operation Type |
Routing |
Actions |
---|---|---|
Asynchronous — One Way. |
Outbound. |
|
Asynchronous — Request/Response. |
Outbound. |
|
Asynchronous to Synchronous. |
Outbound. |
|
Synchronous. |
Outbound. |
|
Asynchronous — One way. |
Inbound. |
|
Asynchronous — Request/Response. |
Inbound. |
|
Asynchronous to Synchronous. |
Inbound. |
|
Synchronous. |
Inbound. |
|