Author Info
Chris Malek

Chris Malek is a PeopleTools® Technical Consultant with two decades of experience working on PeopleSoft enterprise software projects. He is available for consulting engagements.

About Chris Work with Chris
PeopleSoft Simple Web Services (SWS)
Do you need a quick way to create web services?

Introducing a small but powerful PeopleSoft bolt-on that makes web services very easy. If you have a SQL statement, you can turn that into a web service in PeopleSoft in a few minutes.

Read More & Purchase
Contents
0. About Book
1. Getting Started
2. Service Operations
3. REST Services
4. Security
5. Monitoring & Administration
6. Example Service Operations
7. Data Encoding/Decoding
8. Nodes
9. Services Delivered by Oracle
10. Listening Connectors
11. Handlers
12. Target Connectors
13. Syncing Data Between PeopleSoft Systems
14. API Gateways
15. Best Practices
Search

Asynchronous request / response

Note: This section needs major work.

PeopleBooks:

  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.

Valid Handler Types:

  • OnNotify
  • OnReceive
  • On Response (???? from pbooks)
  • OnRoute
  • OnRequestSend

The sending system invokes a service operation asynchronously and processes the response from the receiving system asynchronously. Unlike a synchronous operation type, the response is not processed on the same thread as the response, and it is processed sometime in the future.

Outbound:

  • The application generates and sends a request.
  • The target system receives and processes the request.
  • Sometime later the target system sends a response which contains the transaction ID from the original request. This ID serves as the correlation ID.
  • 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.

Inbound:

  • A source system generates and sends a request.
  • The application receives and processes the request.
  • 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.
  • The source system processes the response using the correlation ID to map it back to the original request.

Example Delivered Service: QAS_QRY_SERVICE QAS_EXECUTEQRYASYNC_OPER - This only has a “OnNotify” handlers

Copyright 2018-2023 Cedar Hills Group, Inc. All rights reserved.