Application Integration (On-Premises) : Administering Integration Server : Configuring Integration Server for webMethods Messaging : Load Balancing with a Non-Clustered Group of Integration Servers : Important Considerations
Important Considerations
Keep the following points in mind when determining whether to connect a non-clustered group of Integration Servers to the same messaging provider for load-balancing:
*If Universal Messaging is the messaging provider, the Integration Servers in the group must be version 9.5 SP1 or later.
*If Broker is the messaging provider, the Integration Servers in the group must be version 7.1 or later.
*The Integration Servers in the group must be the same version and at the same fix level.
*The Integration Servers in the group can share a document history database and a cross-reference database.
*The actions that Integration Server takes when modifying triggers depends on the following:
*If Integration Servers are in a non-clustered group, how modifications to triggers are handled depends on how the Integration Servers have the Share Client Prefix option set. For more information about setting this option, see Creating a Universal Messaging Connection Alias.
*If the Share Client Prefix option for the Integration Server connection to the messaging provider is set to No, modifying a webMethods messaging trigger on one of the Integration Servers could delete documents and other data on the messaging provider. For example, when the messaging provider is Broker, if you enable a trigger, disable a trigger, or change the processing mode, the Integration Server deletes and then recreates the associated trigger client queue on the Broker. This action deletes any documents that are in the trigger client queue on the Broker.
*If the Share Client Prefix option for the Integration Server connection to the messaging provider is set to Yes, the Integration Servers act as if they are in an Integration Server cluster whenever you perform Integration Server-to-messaging provider administration, such as modifying a trigger.
*When Integration Servers are in an Integration Server cluster, if a webMethods messaging trigger is modified on one of the servers, that server will not synchronize the trigger changes with the associated object on the messaging provider. If you enable or disable a trigger in a cluster of Integration Servers, the associated subscriptions and object remain on the messaging provider. In a non-clustered group of Integration Servers, it is your responsibility to manually update the settings on the messaging provider.
Copyright © 2015- 2016 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback