Home

 

Configure shared message stores for buses


Overview

Configure shared message stores for buses to make the message store available to all nodes in a cluster.

Make a note of which IBM Lotus Connections features are deployed to the cluster that you going to configure.

In a network deployment environment with multiple nodes, the SIB used by LC requires the file-based message store to be available to all nodes in a cluster. In practice, this means that the message store must be a network-mounted share. When more than one node is a member of a cluster, the message store must be available to all nodes in the cluster at the same physical location. You can accomplish this by mounting a network share at the physical location.

Alternatively, you can change the location of the message stores to another file system.

By default, in a Network Deployment installation, the LC installation wizard creates a message store for each defined cluster in the following directories:

The <cluster_name> contains a log and store When all servers are stopped, you can delete the existing log and store directories. You can also delete any existing message store directory provided that the that you mount has the same structure with the same <cluster_name> subdirectories. The subdirectories will be created the next time the servers start.


Convert the existing message store to a shared

  1. Stop all WebSphere Application Server processes.

  2. Delete the existing message store on each node. For example:

      /opt/IBM/LotusConnections/messagestore

  3. Create a network or SAN space to store the message store. Each cluster requires 500 MB of disk space.

  4. Mount the network share or SAN space on each node. For example: mount the share or space on...

      /opt/IBM/LotusConnections/messagestore

  5. Ensure that the operating system user who runs the WebSphere Application Server processes has read and write access to the mounted

  6. Create a directory under the message store for each cluster. The name of the should match the name of the cluster.

 

Related tasks

Post-installation tasks
Convert data directories manually
Add subsequent nodes to a cluster

+

Search Tips   |   Advanced Search