The policy administrator can define additional routing JMS endpoints to be used by new policies, but the JMS route message endpoint mentioned in the policies must also be defined on the WebSphere® Message Broker system.
When a new policy is created in WSRR, the new JNDI destination binding definitions must be created for the Route Message Endpoint value set in the policy document. The new JMS destination details must be merged with the existing JMS destinations details in the JMS definition file, JMS.def, that was created when the pattern was instantiated. This means that administrators must take the existing JMS definition file, add the new JMS destination definitions, and regenerate the JNDI bindings file, .bindings, used by Message Broker to connect to the JMS provider.