Understanding Filtering, Transformation, and Translation
This topic describes how to use filtering, transformations and translations for integrations. This topic also features code examples to help illustrate how to filter, transform and translate integrations.
Note: The code examples in this topic are for illustrative purposes only and are not intended to be used in a production environment.
Filtering, transformation, and translation are all accomplished by applying an Application Engine transform program to an outbound or inbound message. You can use these programs to:
Filter a message based on its content, to determine whether to pass it through to its destination or to subsequent steps of the transform program.
Perform transformation on a message to make its structure comply with the receiving system’s requirements.
Perform data translation on a message so that its data is represented according to the receiving system’s conventions.
Simple translation might be required if the two systems use different values to represent the same information for a given field.
Complex translation might involve augmenting or replacing groups of fields with a completely different structure and encoding.
If your PeopleSoft application uses the PeopleCode XmlDoc or SoapDoc classes to generate or process a message, the message probably doesn’t adhere to the PeopleSoft rowset-based message format.
Filtering, transformation, or translation can be necessary for messages sent between two PeopleSoft Integration Broker nodes, or between a PeopleSoft Integration Broker node and a third-party application.