Changing Message Processing When Universal Messaging Is the Messaging Provider

You can change the message processing after you create a webMethods messaging trigger. For example, capacity planning might indicate that a concurrent trigger should be changed to serial. Keep the following points in mind when changing the processing mode from serial to concurrent or vice versa for a webMethods messaging trigger that receives documents from Universal Messaging:

When you change the processing mode for a webMethods messaging trigger that uses a Universal Messaging connection alias that does not share a client prefix, Integration Server deletes and recreates the named object that corresponds to the trigger on Universal Messaging. The trigger and its associated named object on Universal Messaging remain in sync.

Note: A Universal Messaging connection alias does not share a client prefix if the Shared Client Prefix property for the connection alias is set to No.

When you change the processing mode for a webMethods messaging trigger that uses a Universal Messaging connection alias that shares a client prefix, Integration Server does not delete and recreate the named object that corresponds to the trigger on Universal Messaging. As a result, the trigger on Integration Server will be out of sync with the associated named object on Universal Messaging. If the same trigger exists on other Integration Server, such as in a cluster or a non-clustered group of Integration Server, the changed trigger will also be out of sync with the trigger on other Integration Server. This affects document processing. One of the following situations occurs:

If you changed the processing mode from serial to concurrent, the corresponding named object on Universal Messaging remains a priority named object. The trigger continues to process documents concurrently, However, if the trigger exists on more than one Integration Server, such as in a cluster or a non-clustered group of Integration Servers, Universal Messaging distributes documents to the trigger on the first Integration Server to connect to Universal Messaging only. This trigger has priority and will receive and process all the documents to which the trigger subscribes. The other Integration Servers are connected to Universal Messaging but are in fail-over mode and will not receive or process documents unless the first trigger disconnects.

If you changed the processing mode from concurrent to serial, the corresponding named object on Universal Messaging remains a shared named object. Integration Server does not change the named object to be a priority named object. Consequently, if the trigger exists on more than one Integration Server, such as in a cluster or a non-clustered group of Integration Servers, Universal Messaging distributes documents to the trigger on each connected Integration Server. Universal Messaging does not distribute documents in a way that ensures that processing order matches publication order.

For information about how to synchronize the trigger and the named object when the processing mode is out of sync, see Synchronizing the webMethods Messaging Trigger and Named Object on Universal Messaging .

Software AG does not recommend changing the processing mode for a trigger when more than one Integration Server connects to the same named object that corresponds to the trigger. For example, if the trigger is on an Integration Server that is part of a cluster or a non-clustered group, more than one Integration Server can share the same named object.