Home
Change the location of message stores
Change the location of message stores to another or file system.
Make a note of which IBM Lotus Connections features are deployed to the cluster that you going to configure.
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 changing the location of the message stores to another or file system.Notes
- Alternatively, you can mount a network share at a physical location. For more information about mounting a network share at a physical location, see the Configuring shared message stores for buses topic.
- You do not need to define the message store of each cluster in the same physical location.
To change the location of message stores...
- Delete the bus member that is defined for the cluster.
- Stop all cluster processes.
- From the WAS admin console, select Service Integration > Buses > ConnectionsBus > Bus Members.
- Select the bus member to delete and click Remove.
- Add the new cluster bus member.
- From the WAS admin console, select Service Integration > Buses > ConnectionsBus > Bus Members.
- Click Add. In the first step of the wizard, select Cluster and then select the cluster name that you removed in Step 1c. Click Next.
- The File Store message store type is selected by default. Click Next.
- Provide the message store properties.
- Enter the Log path. For example: If the message store share is located at /mnt/messagestore/clusterB, then the value of this field is/mnt/messagestore/clusterB/log.
- Enter the Permanent store path. For example: If the message store share is located at /mnt/messagestore/clusterB, then the value of this field is/mnt/messagestore/clusterB/store.
- Ensure that the Same settings for permanent and temporary stores setting is selected.
- Click Next.
- Review your changes. When you are satisfied that the settings are correct, click Finish.
- Add destinations for the new bus member. For each Lotus Connections feature, complete the following substeps for each destination. Refer to the following table for examples.
- From the WAS admin console, select Service Integration > Buses > ConnectionsBus > Destinations and then click New.
- The Queue option is selected by default. Click Next.
- Enter a destination name in the Identifier field. For example: connections.blogs.events.outbound. Click Next.
- Select the Bus Member that you created earlier and then click Next.
- Click Finish.
- Select the destination that you created.
- On the Details page, enter the value from the Default forward routing path column in the Default forward routing path field. For example: ConnectionsBus:connections.news.events.inbound. Click OK.
Carriage returns have been added to some table entries to improve readability.
Destination settings
Feature Destination type Destination name Default forward routing path Activities Outbound connections.activities.events.outbound ConnectionsBus:connections.news.events.inbound Blogs Outbound connections.blogs.events.outbound ConnectionsBus:connections.news.events.inbound Communities Outbound connections.communities.events.outbound ConnectionsBus:connections.news.events.inbound Inbound connections.communities.events.inbound None Dogear Outbound connections.dogear.events.outbound ConnectionsBus:connections.news.events.inbound Files Outbound connections.files.events.outbound ConnectionsBus:connections.news.events.inbound Home page Outbound connections.homepage.events.outbound ConnectionsBus:connections.news.events.inbound Inbound connections.homepage.events.inbound None News Communities Outbound connections.news.events.outbound.communities ConnectionsBus:connections.communities.events.inbound Home page Outbound connections.news.events.outbound.homepage ConnectionsBus:connections.homepage.events.inbound Inbound connections.news.events.inbound None Profiles Outbound connections.profiles.events.outbound ConnectionsBus:connections.news.events.inbound Wikis Outbound connections.wikis.events.outbound ConnectionsBus:connections.news.events.inbound
- Optional: If there are more destinations for this cluster, repeat this step for each destination.
- Click Save.
- Perform a full synchronization of each node.
- Restart the cluster.
Results
Check the SystemOut.log file for startup messages. For example:
SibMessage I [ConnectionsBus:clusterA.000-ConnectionsBus] CWSIS1585I: The file store is attempting to start its permanent store (/local/IBM/LotusConnections/messagestore2/clusterA/store/PermanentStore) and temporary store (/local/IBM/LotusConnections/messagestore2/clusterA/store /TemporaryStore).
SibMessage I [ConnectionsBus:clusterA.000-ConnectionsBus] CWSIS1588I: The file store has started successfully.
Repeat this task for each cluster in your deployment.
Configure shared message stores for buses