Universal Messaging 10.5 | Migrating webMethods Broker to Software AG Universal Messaging Documentation | Migrating from webMethods Broker to Universal Messaging Guide | Performing Post-Migration Configuration | Universal Messaging Configuration
 
Universal Messaging Configuration
Use Universal Messaging Enterprise Manager to:
*Update the migrated assets based on the migration messages. For descriptions of the warnings logged in the JNDI and JMS migration log files, see JNDI and JMS Migration Warnings.
Important:
Make sure you select the JNDI Lookup option for the JMS connection alias in Integration Server.
*Select the Connection Factory (Shared Durable) option when you create the connection factory, if you want to use durable subscribers.
*Set the MaxBufferSize configuration property to be large enough for the largest message you want Universal Messaging to transport. The MaxBufferSize property is set to 1 MB by default. An Integration Server client will be disconnected fromUniversal Messaging server when a message exceeding the MaxBufferSize is transmitted.
*Increase the client queue window size if you want a concurrent Integration Server trigger to process more than 10 documents at a time. The default Universal Messaging window size is 10 documents. For example, if a concurrent trigger has max execution threads set to 30, set the client queue window size to 30.
For more information about using Universal Messaging Enterprise Manager, see the Universal Messaging Webhelp on the Software AG Documentation website at http://documentation.softwareag.com.