Monitoring a Connection Factory Object for Changes
When you create or edit the JMS connection aliases that use a connection factory object to establish a connection to the webMethods Broker, you can indicate whether or not Integration Server monitors the connection factory for changes.
When Integration Server uses a connection factory object to establish a connection to the webMethods Broker, Integration Server uses JNDI Lookup to create the connection. After establishing the connection, Integration Server normally does not lookup the connection factory object again until the connection is restarted. Consequently, in between connection restarts, the connection does not reflect any changes that may have been made to the connection factory object, such as a change to the cluster policy or a change to the webMethods Brokers in a cluster. By monitoring the connection factory, Integration Server can update the related connection automatically after the connection factory changes.
You can configure Integration Server to monitor the connection factory object in one of the following ways:
Poll for changes. Integration Server periodically looks up the specified connection factory object from the JNDI provider and compares it to the connection factory object used to establish the connection. If
Integration Server detects a change, it refreshes the connection automatically.
Listen for changes. Integration Server registers an event listener with the JNDI provider to receive notifications about changes to the cluster connection factory. When
Integration Server receives notification of a change it refreshes the connection automatically.
Regardless of the method used to monitor changes, Integration Server attempts to update and refresh the connection without interrupting any services sending a JMS message or triggers receiving a JMS message. The following sections provide more information about the monitoring options.
