Home
Validate SIBus links
After defining the SIBus link on the feature server and the News repository, validate the link.
You can validate an SIBus link by stopping and restarting the servers and then checking the log files for confirmation, or you can use the WAS admin console.
If you choose to use the administrative console, you can only view the runtime status of objects through the console for that particular server. If you are using WebSphere Application Server Base and multiple server instances, then you need to log into each administrative console to validate.
To validate an SIBus link stop and start both of the application servers...
- Feature server
- News repository server
When the link is successfully defined and started, the following log messages are displayed in the SystemOut.log file on each server:
[25/02/09 22:18:18:281 GMT] 00000026 SibMessage I [:] CWSIT0032I: The inter-bus connection CoreServer_server1_link from messaging engine homedev3Node01.server1-Connections_server1_Bus in bus Connections_server1_Bus to messaging engine homedev3Node01.CoreServer-Connections_CoreServer_Bus in bus Connections_CoreServer_Bus started.
[25/02/09 22:18:30:359 GMT] 0000002a SibMessage I [Connections_server1_Bus:homedev3Node01.server1-Connections_server1_Bus] CWSIP0382I: Messaging engine homedev3Node01.AppsServer-Connections_CoreServer_Bus responded to subscription request, Publish Subscribe topology now consistent.
To validate using the WAS admin console:
Service Integration | Buses | Topology | Messaging Engines | messaging_engine | Additional Properties | Service integration bus links
..and verify the SIBus link is displayed, and that state is: Started.
If the link is in a starting or unavailable state, this means that the server has not successfully initiated the link. This result might indicate one of the following:
- One of the servers is not started. The link is reattempted after an interval and should establish once both servers are started.
- The configuration is incorrect. This is the most likely cause of the link being in a starting or unavailable state. Check and recheck the configuration of the foreign bus and SIBus links on both servers, paying attention to the following:
Foreign Bus names Ensure that the foreign bus name matches the exact name of the bus on the other server. SIBus Link name Check that this is the same on both ends. SIBus Link settings Make sure that the settings are correct, especially that the bootstrap endpoint definition is using the correct host name and port. Communication error This problem is likely to have occurred because SSL certificates have not been exchanged between the two servers if they are not in the same WebSphere Application Server profile.
If you encounter problems with the foreign bus, see Chapter 24, Foreign bus problem determination, in the WebSphere Application Server V6.1: JMS Problem Determination IBM Redpaper.
Linking buses on different servers
Previous topic:
Define a SIBus link on the News repository server
Next topic:
Configure authorization for foreign bus connections