Home
Link buses manually for non-federated servers
Link buses between non-federated application servers to allow the news repository to collect messages from the other features
This task is only necessary if you selected the Advanced stand-alone option to install IBM Lotus Connections on multiple server instances using WebSphere Application Server Base, or on multiple server instances in a non-federated WebSphere Application Server Network Deployment environment, or a combination of the two.
In a single server or network deployment, all installed features are deployed onto the same bus and the news repository can collect event messages from them. However, in an advanced stand-alone deployment on non-federated multiple server instances, each server has its own bus. After installation, you need to manually link the news repository bus and these buses so that messages can pass between them.
The Lotus Connections installation wizard creates a bus on each application server. Each bus contains:
- The SiBus destination resources for the installed features
- The JMS resources, including Queues, Queue Connection Factories, and Activation Specifications, for the installed features
To propagate these events to the news repository server, define a link between the bus for each feature and the bus for the news repository.
Apart from the news repository, you do not need to link the buses for features to each other.
- Prepare to create bus links
- Linking buses on different servers
- Configure default forward routing paths
Related tasks
Post-installation tasks
Updating the messaging bus configuration when the connectionsAdmin user ID changes