Skip to Main Content
Return to Navigation

Service Operation Types

PeopleSoft Integration Broker supports four types of service operations:

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.

Operation Types

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.

  1. The application generates and sends a request.

  2. One or more target system receives and processes the request.

Asynchronous — Request/Response.

Outbound.

  1. The application generates and sends a request.

  2. The target system receives and processes the request.

  3. Sometime later the target system sends a response which contains the transaction ID from the original request. This ID serves as the correlation ID.

  4. The application processes the response using the correlation ID to map it back to the original request. The message sent back is a response in the form of a request.

Asynchronous to Synchronous.

Outbound.

  1. The application generates and sends a request.

  2. A single target system receives and processes the request, then generates and sends a response.

  3. The application receives and processes the response.

Synchronous.

Outbound.

  1. The application generates and sends a request.

  2. The application suspends activity and waits for a response.

  3. A single target system receives and processes the request, then generates and sends a response.

  4. The application resumes its activity and receives and processes the response.

Asynchronous — One way.

Inbound.

  1. A source system generates and sends a request.

  2. The application receives and processes the request.

Asynchronous — Request/Response.

Inbound.

  1. A source system generates and sends a request.

  2. The application receives and processes the request.

  3. Sometime later the application sends a response back to the source system. The response includes a unique identifier from the original request, which serves as a correlation ID.

  4. The source system processes the response using the correlation ID to map it back to the original request.

Asynchronous to Synchronous.

Inbound.

  1. A source system generates and sends a request.

  2. The application receives and processes the request, then generates and sends a response.

  3. The source system receives and processes the response.

Synchronous.

Inbound.

  1. A source system generates and sends a request.

  2. The source system suspends activity and waits for a response.

  3. The application receives and processes the request, then generates and sends a response.

  4. The source system resumes its activity and receives and processes the response.