Dynamic reloading of configuration files
Updates to configuration information are dynamically passed to the server if we use dynamic reloading of configuration files. These updates are available to a messaging engine even if it is not started.
The information that defines the configuration of service integration buses (including any linked foreign bus connections) and their resources is saved in a set of configuration files. When a server starts up, it reads the current information about service integration from those configuration files. When a messaging engine is started, it uses the information in the server that it is running in.
If the information in the configuration files is changed while the server is running, the server must either be dynamically updated or restarted to use the updated information.
We can enable dynamic reloading of configuration files for servers and for service integration buses, including the configuration information for any linked foreign bus connections. There are different results depending on whether we enable dynamic reloading for either the bus or the server or both:
- If we enable dynamic reloading on the bus, but not on the application server, we will need to restart the server for updates to take effect.
- If we enable dynamic reloading on the server, but not on the bus, then we will need to restart only the messaging engine for the updates to take effect.
- If we enable dynamic reloading on both the bus and the server, then all updates occur automatically without the need for restarts.
To enable dynamic reloading of configuration files on an application server, click Application servers -> server -> SIB service to display the Application Servers window, and select Configuration reload enabled. To ensure that dynamic configuration updates are made to each node, click...
System administration -> Console Preferences to display the Console Preferences window and select Synchronize changes with nodes.
To enable dynamic reloading of configuration files for a service integration bus, click Service integration -> Buses -> bus_name to display the bus details, and select Configuration reload enabled.
If we choose not to enable dynamic reloading of configuration files, we must restart the server to pick up changes to the configuration files.
In a cluster deployment with failover, it is likely that the configuration information is updated between the initialization and start up of a messaging engine. (When a server starts a messaging engine is initialized, however the messaging engine might not start for a long time after that). Therefore we should enable dynamic reloading of configuration files in a cluster deployment with failover, because restarting a server to pick up configuration changes causes a failover. To get predictable behavior on failover, ensure that the standby (inactive) servers have been updated and recycled before the active server.
Add additional messaging engines to a cluster bus member Configure bus properties createSIBus command SIB service [Settings]