Common Elements Used

Asynchronous

Messages that do not require a response. These messages are sent to the destination system as one-way messages, and are used for publish and subscribe messages where there may be a lapse in time between the message being sent and received.

Batch Publish

Use this design pattern to publish messages from a batch application. The batch application can be a COBOL or Structured Query Report program that takes either a procedural or set-based approach, or it can be an Application Engine set-based program.

Batch Subscribe

This design pattern enables you to perform edits against messages in sets. This can be a useful technique for high volume data, including millions of inbound rows. This design pattern is useful when you know that a single message definition may contain multiple instances of a transaction, or when you must reuse an existing batch program.

Component Publish

In this design pattern, the transaction or setup data that you want to send out of PeopleSoft is being updated by using a PeopleSoft component. In this case, the data is already in the component buffer, and the Publish PeopleCode function is used to publish a message.

Full Table Publish

Use this design pattern to populate an entire copy of a table onto a remote database or legacy system. Generally, full data replication occurs with setup tables, or relatively static, low-volume tables that are keyed by SetID. When a copy of a table exists on the remote system, incremental updates can be used.

Full Table Subscribe

Use this design pattern to subscribe to messages that contain an entire copy of a table that is published from a remote database or legacy system. Generally, full data replication occurs with setup tables, or relatively static, low-volume tables that are keyed by SetID. When a copy of a table exists on the remote system, incremental updates can be used.

Synchronous

Occurring or existing at the same time. Used for messages that are sent out and receive an immediate response.