[OO Tip] Procedure for rebuilding the flow repository index
What is the correct procedure for rebuilding the Operations Orchestration (OO) flow repository index in a clustered environment?
When performing a rebuild of the repository index in a clustered or complex environment there are additional considerations when rebuilding the index:
1. Make sure all flows are checked in and all Studio users are disconnected.
Hint: Go to the main \Library in Studio and perform a ‘Check In Tree'. Do this as the OO ‘admin’ user, which will then provide the ability to perform a force check in, if needed. Also, the ‘admin’ user will see the full contents of the repository, where other users may not, depending on their account rights.
2. Shut down all OO services on every cluster node.
NOTE: To determine the location of the shared cluster repository, use the value shown for the repository in the configuration file found at %ICONCLUDE_HOME%/Central/conf/central.properties file on the line that begins with dharma.repository=location=
3. Under the <repository location>/rcrepo/ delete the entire .idx folder.
4. Under <repository location>/rcrepo/workspaces/<user name>/ delete the entire .idx folder, do this for all users.
5. Restart all the OO services on one node, and connect with Studio and confirm proper operation. It will take a few minutes for the repository to rebuild.
6. Bring up the remaining nodes in the cluster.
7. Perform a final repository verify operation with the provided repoutil.exe. Open a cmd window/DOS prompt under ICONCLUDE_HOME%/Central/tools and then run this command to do a basic integrity check on the repository:
repoutil.exe –verify -1 repo1
Direct link to the document here:
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.