When the JMS connection alias specified by a JMS trigger connects to the webMethods Broker and is configured to manage destinations, Integration Server can automatically configure load balancing for a JMS trigger that specifies a durable subscriber.

If the durable subscriber specified by the JMS trigger does not exist, when you save a JMS trigger, Integration Server creates the durable subscriber at the Broker. By default, Integration Server enables state sharing for the durable subscriber. Integration Server uses the message processing mode specified for the JMS trigger to set the shared state order mode for the durable subscriber. (A message processing mode of serial maps to a shared state order mode of publisher; a message processing mode of concurrent maps to a shared state order mode of none.)

If the durable subscriber specified by the JMS trigger exists already, Integration Server can update the shared state order mode of the durable subscriber when you save the JMS trigger. To change the shared state order mode for a durable subscriber, change the message processing mode for the JMS trigger and confirm making the change on Broker when prompted by Designer.

If a JMS trigger specifies a durable subscriber that already exists and you want to change the state sharing property of the durable subscriber to true, you need to use the Broker interface in My webMethods to delete the durable subscription. Then, you can either allow Integration Server to re-create the durable subscription by saving the JMS trigger or you can use the Broker interface in My webMethods to re-create the durable subscription with the correct shared state and shared state order values.