Copy Search conversion tools to local nodes

To enable full indexing of data, copy the Search conversion tools to local nodes.

Perform this task only on nodes in the Search cluster. If we added a node to an existing cluster, complete this task only if the new node is a member of the Search cluster.

The Search conversion tools index Files, Activities, and Wiki attachments. The tools work best when they are available locally on each node. When Connections was installed, the conversion tools were deployed on a network share. Therefore, copy the tools to each node in the Search cluster.

For AIX and Linux

To copy Search conversion tools to local nodes:

1. Identify the nodes in the Search cluster.

   From the WAS console, go to...

   Servers | Clusters | WebSphere application server clusters | search_cluster | Additional Properties | Cluster members | Details

   ...and in the table of cluster members, make a note of the nodes that host the cluster members.

2. Copy...
   shared_data_directory_root/search/stellent

   ...from the shared content folder to a local directory on each node. Use exactly the same path on each node. For example...

   /opt/IBM/Connections/data/local/search/stellent

   The new directory contains the exporter executable file.

3. On the dmgr, to point to the exporter file in the local directory on each node, set variable...
   FILE_CONTENT_CONVERSION

   For example:

   /opt/IBM/Connections/data/local/search/stellent/dcs/oiexport/exporter

   The exporter file must be in the same file path on all nodes.

4. On each node, make a backup of...
   app_server_root/AppServer/bin/setupCmdLine.sh

5. Add the following text to the end of the setupCmdLine.sh file on each node:
   export PATH=$PATH:SearchBinariesHome/dcs/oiexport

   ...where SearchBinariesHome is the path to the directory specified in Step 2.

6. Choose the option for the operating system:
   • AIX: export LIBPATH=$LIBPATH:SearchBinariesHome/dcs/oiexport
   • Linux: export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:SearchBinariesHome/dcs/oiexport

7. Restart all node agents.

8. Restart WebSphere Application Server on each node.

9. If there are errors, refer to Linux: Troubleshooting when files content is not found after searching.

For Windows

To copy Search conversion tools to local nodes:

1. Identify the nodes in the Search cluster.

   1. Log in to the WAS console and click...
      Servers > Clusters > WebSphere application server clusters

   2. Click cluster_name, where cluster_name is the name of the Search cluster.

   3. In the Additional Properties area, expand Cluster members and then click Details.

   4. In the table of cluster members, make a note of the nodes that host the cluster members.

2. Copy the shared_data_directory_root/search/stellent directory from the shared content folder to a local directory on each node. Use exactly the same path on each node. The following path is an example only and might be different on the Windows operating system: C:\IBM\Connections\data\local\search\stellent

   The new directory contains the exporter executable file.

3. On the dmgr, update the FILE_CONTENT_CONVERSION Websphere variable to point to the exporter file in the local directory on each node.

   For example: /opt/IBM/Connections/data/local/search/stellent/dcs/oiexport/exporter

   The exporter file must be in the same file path on all nodes.

   For more information about WebSphere variables, see the Change WAS environment variables topic.

4. Restart all node agents.

5. Restart WebSphere Application Server on each node.

Parent topic:
Post-installation tasks

Related:
Add a node to a cluster
Change WAS environment variables
Make search-related configuration changes to newly added nodes