Dynamically Changing a Service's Connection at Run Time
You may 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.
If you have multiple instances of a JMS provider running, you can use the dynamic connections feature to override the default and switch between the instances.
Both connections-the default and override-must use the same JMS destination type (topic or queue).