Outbound and inbound events

Describes the outbound processing logic used by the adapter to retrieve, update, or create a PeopleSoft component interface and populate it with business data, and states the custom project requirement for inbound processing.

To perform an outbound operation on an inbound business object the adapter follows these steps:
  1. It extracts metadata from the InteractionSpec that identifies the appropriate component interface to access.
  2. It extracts properties from the InteractionSpec that determine the outbound operation to perform.
  3. Within the component interface, the adapter sets the keys from values specified in the business objects.
  4. The adapter instantiates an existing component interface to retrieve, update, or create a component interface, and then it populates that component interface with data from the hierarchy of business objects.
Note: The adapter processes attributes in the order defined in the business object. For example, if there is a complex attribute between two simple attributes, the adapter processes the simple attribute at the first position, then the complex attribute followed by the simple attribute. After the changes are made, the component interface is saved to commit the data to the PeopleSoft database. This pattern of processing is used for Create and Update operations only.

The adapter can support inbound events as well. If your environment requires inbound support, you must first use PeopleTools Application Designer to create a custom event project.

Related concepts
Asynchronous event delivery
Related tasks
Creating a custom event project in PeopleTools

Terms of use |

Last updated: Sun Mar 12 11:24:18 2006

(c) Copyright IBM Corporation 2005.
This information center is powered by Eclipse technology (http://www.eclipse.org)