Software AG Products 10.5 | Administering Integration Server | Configuring Integration Server for webMethods Messaging | Working with Messaging Connection Aliases | Specifying the Default Messaging Connection Alias
 
Specifying the Default Messaging Connection Alias
The default messaging connection alias determines the messaging provider to which messages are sent when the Connection alias name property for the publishable document type is set to DEFAULT or is blank.
*Services that publish instances of the publishable document type use the default messaging connection alias to connect to the messaging provider and publish the document.
*webMethods messaging triggers that subscribe to that publishable document type use the default messing connection alias to connect to the provider and retrieve the messages.
That is, when the publishable document type has a Connection alias name property set to DEFAULT or is blank, the default messaging connection alias determines which messaging provider receives and routes published instances of the document.
The first time Integration Server starts, Integration Server sets a default messaging connection alias based on whether Integration Server was migrated from a previous version and on what other products are installed in the same location.
*To change the default messaging connection alias
1. Open the Integration Server Administrator.
2. In the Settings menu of the Navigation panel, click Messaging.
3. Under webMethods Messaging Configuration, click webMethods Messaging Settings.
4. Click Change Default Connection Alias.
5. Under Select New Default Connection Alias, in the Connection Alias Name list, select the name of the messaging connection alias that you want to use as the new default messaging connection alias.
6. Click Update.
Notes
*After you change the default connection alias, Integration Server reloads all of the webMethods messaging triggers that subscribe to publishable document types that use the default messaging connection alias.
*After you change the default connection alias, you need to synchronize publishable document types that use the default alias with the messaging provider. This ensures that the provider definitions on the new default messaging provider are synchronized with publishable document types that use the default messaging connection alias.