Dynamically Changing a Service's Connection at Run Time
You can run a service using a connection other than the default connection that was associated with the service when the service was created. To override the default, you must code your flow to pass a value through the pipeline into a service's $connectionName field.
For example, you could design a flow for an international company that has multiple geographically separated production systems. With the run-time connection switching capability, you do not need to configure the same service multiple times. Instead, all you need do is map the appropriate value of a connection name to the $connectionName field in the pipeline and pass it along to the services.
Keep in mind these restrictions when using dynamic connections:
Both connections - the default and override - must be to
Oracle Applications instances accessed with the APPS user name.
The connection with which you override the default (that is, the value provided for $connectionName) must be configured to use the same transaction type as the default connection.
The $connectionName field is present only in services created with
Designer.
Predefined transaction services do not have $connectionName in their service signatures. However, users can use an Integration Server map step to place this value in the pipeline before the service is invoked.