Use Cases for Application Integration Framework

Use cases fall into two categories:

• Key-mapping transforms using the dynamic cross-reference framework

• Static value transforms using the domain value map framework

These two frameworks are assumed to be separate; however, they in fact share common elements. The values of keys are open-ended and are usually extended; thus they are created programmatically during the transformation process, not in advance of the transform. Static value transforms generally have all values entered into the maps prior to the transformation process, and are less frequently extended.

In addition to these two categories, the integration use case depends on whether the third party is using AIA middleware.

This table shows where the transformations take place depending on whether AIA middleware is used:

Use Case	PeopleSoft Integration Broker	AIA Middleware	Third Party
Integration Broker Transformations without AIA middleware	Transform PeopleSoft ABM to EBM for outbound Transform EBM to PeopleSoft ABM for inbound	not used	Transform EBM to third-party ABM for inbound Transform third-party ABM to EBM for outbound
Integration Broker Point-to-Point transformation	Transform PeopleSoft ABM to third-party ABM for outbound Transform third-party ABM to PeopleSoft ABM for inbound	not used	No transformations are necessary Optionally, the third party can do the outbound transformation to PeopleSoft ABM.
Integration Broker Transformation in which third party uses AIA middleware	Transform PeopleSoft ABM to EBM for outbound Transform EBM to PeopleSoft ABM for inbound	Transform EBM to third-party ABM for outbound from PeopleSoft application Transform third-party ABM to EBM for inbound to PeopleSoft application	No transforms are performed