Understanding Using Routing Deployment Configuration

Prior to a new application release or patch create an integration group or subgroup. For any new or modified integrations, add the services and service operations to the newly defined integration group or subgroup.

After quality assurance testing with other PeopleSoft integration partners, and prior to creating the final project, examine the new or modified integrations and determine if you need to add any routing definitions. If so, use the Deployment Configuration page in the Service Utilities component to add the routing definitions. The routing metadata gets saved as part of the service operation version.

Note:

The routing information you define using the routing deployment configuration pages is saved as part of the service operation version.

The associated physical routing(s) defined in the Routings component can then be deleted.

Integration partners then upload the project and use the Integration Network Introspection and Deployment feature to introspect and deploy the integrations to all PeopleSoft integration partners using the integration group name you created earlier.

When introspection takes place the receiving system is interrogated to get the application version information. The information is used to determine the PeopleSoft application (for example, HCM, SCM, and so on) for look up against the deployment configuration metadata to determine an integration match.

Note:

You need to add routing information to the deployment table using the Deployment Configuration page only if specific routing data needs to be part of an auto-generated routing, such as transformation information, alias name (if different from the default), and so on. Therefore, not all PeopleSoft-to-PeopleSoft routing definitions need to be added to the deployment table using the Deployment Configuration page.

Routing deployment configuration metadata is only applicable for a defined PeopleSoft application. This means that the source system where introspection is invoked can have deployment configuration information, while the receiving system does not have deployment configuration information. As a result, you only need to update the deployment data for your own application.

The introspection process uses the following order to determine proper integration bindings:

  1. Valid routing. The sending and receiving nodes match, the alias name matches.

  2. Deployment configuration metadata (as defined in the Deployment Configuration page). Routing name matches.

  3. Service operation and version match.

During introspection processing, the system examines the deployment configuration metadata and can determine the proper routing (if one is available) based on the PeopleSoft application name and application version.