SIB service [Settings]
The service that provides service integration functions.
To view this page in the console, click the following path:
Servers -> Server Types -> WebSphere application servers -> server_name -> [Server messaging] SIB service.
Configuration tab
The Configuration tab shows configuration properties for this object. These property values are preserved even if the runtime environment is stopped then restarted. See the information center task descriptions for information about how to apply configuration changes to the runtime environment.
General Properties
Enable service at server startup
Whether or not the server attempts to start the specified service when the server starts.
If we want applications to use service integration technologies provided by this application server, including JMS resources of the default messaging provider of this application server, this option must be selected. The SIB Service is enabled automatically when we add a server to a service integration bus. We can choose to disable the SIB service, for example if we have removed the only bus member for a server.
Enable or disable the SIB Service has the same effect as enabling or disabling the Control Region Adjunct (CRA).
For information about using service integration technologies, see Administer service integration.
| Information | Value |
|---|---|
| Required | No |
| Data type | Boolean |
Configuration reload enabled
Select this option to enable the dynamic reloading of the SIB configuration files for this server.
The information that defines the configuration of service integration buses and their resources is saved in a set of configuration files. When a server starts up, it uses the current information about service integration read 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.
With dynamic reloading of configuration files, any updates to the configuration information are dynamically passed to the server, and therefore made available to messaging engines whether or not they are started. We can enable dynamic reloading of configuration files for servers and for service integration buses.
If we choose not to enable dynamic reloading of configuration files, you must restart the server to pick up any changes to the configuration files.
In a cluster deployment with failover, the configuration information is likely to be updated between the initialization and start up of a messaging engine (A messaging engine is initialized when the server starts, but might not get started for a long time after that). Therefore you 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, you must ensure that the standby (inactive) servers had been updated and recycled before the active server.
| Information | Value |
|---|---|
| Required | No |
| Data type | Boolean |
Related concepts
Related tasks
Related information:
Reference topic