Scenario 2: Creating a centralized cache : Mashup Center 2.0Added by IBM on November 20, 2009 | Version 1 (Original)
Contents: Planning, installing, and configuring Mashup Center : Mashup Center 2.0
In this step, you will create a centralized cache for all MashupHub objects shared between nodes in a cluster. The hubclustercache.py script creates a centralized cache for all MashupHub objects shared between nodes in a cluster.
About this task
A centralized cache provides a consistent view of feed data because the data that is shared between nodes is synchronized. To run the script to centralize the cache, do the following steps:
- Copy the hubclustercache.py file from the MashupCenter_install_root/Config/scripts directory in one of the node installations to the profile/bin directory of the WebSphere Application Server Deployment Manager for the cluster (where Mashup Center is not installed).
- On WebSphere Application Server, run the following command: wsadmin -f path_to_script -user username -password password Optional: To verify that the script runs successfully, in the WebSphere Application Server administrative console on the Deployment Manager, select Resources -> Cache instances -> Object cache instances. Only one instance each of the MashupHub feed region cache and MMMS feed region cache should be displayed. These cache instances should have the cluster scope setting in the scope column of the caches table. Changes to feed objects will be visible immediately on all nodes in the cluster regardless of which node in the cluster handles a user's request.
- Do the following steps to run the hub-cluster-setup command on each secondary nodes to set up the ECM plug-in and set permission for the TDI scripts:
- On each secondary node, go to the MashupCenter_install_root/Config directory, and run the following command:
Total time: 43 seconds
Without this setup, the ECM plug-in on the secondary nodes and the TDI startup will not function.
- If the cluster was started previously, stop and restart the cluster.
- Log into the Deployment Manager administrative console, and start the cluster. Now users can go to http://WEBserver.domain/mum/enabler to access the Mashup Center server.
Parent topic: Scenario 2: Configuring a Lotus Mashups cluster using a standalone MashupHub server : Mashup Center 2.0
Previous topic: Scenario 2: Verifying the cluster : Mashup Center 2.0