If your Performance Management server is connected to a MongoDB on a remote server, you can switch to use the
local MongoDB at any time.
Procedure
Complete the following steps as the root user on the system where you installed the
Performance Management server:
- Go to the install_dir/mongodb/bin directory. For example:
cd install_dir/mongodb/bin
- Delete the /mongodb/mongodb-remote file.
- Run the activate-mongodb.sh command to apply the change.
- Configure communications between the local MongoDB and the Performance Management server:
- If you are not already logged in to the Performance Management console, log in now. (See Starting the Performance Management console.)
- Click
and click Mongo Configuration.
- In the Host Name field, enter localhost.
- Click Save to save the configuration.
After you click Save, the transaction tracking components begin
communicating with the local MongoDB.
- If the remote MongoDB was using a custom password rather than the default
mongoUsrpasswd@08 password, run the
install_dir/ccm/mongopasswd.sh script to configure the local MongoDB and
Performance Management server to use your password.
Results
The
Performance Management server is connected to the local
MongoDB.
After you switch to the local version of MongoDB, new threshold events and
new transaction tracking data are transferred between the Performance Management server and the local
MongoDB.
Existing open events and existing transaction tracking data are not migrated to MongoDB on the local system. Use the Linux touch command to modify
the date and time of all of the private_situation.xml files in the
subdirectories under the install_dir/wlp/usr/servers/min/dropins/CentralConfigurationServer.war/data_source
directory to view existing open events in the Performance Management console.