Copying Search conversion tools to local nodes

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

Before you begin

Perform this task only on nodes in the Search cluster. If you added a node to an existing cluster, as described in the Adding a node to a cluster topic, complete this task only if the new node is a member of the Search cluster. References to nodes in the steps of this task apply only to nodes in the Search cluster.

About this task

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

The copying method differs depending on your operating system:

For AIX and Linux
For Windows
For IBM i

For AIX and Linux

About this task

To copy Search conversion tools to local nodes, complete the following steps:

Procedure

Identify the nodes in the Search cluster.
1. Log in to the Integrated Solutions 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.
Set the Path Variables for Search.
During the IBM Connections installation, the stellent folder is added to the Shared drive ( "/opt/IBM/IC_Share/search/stellent") and the FILE_CONTENT_CONVERSION is set to point to this folder. In a multi-node cluster, run this on the nodes themselves and not the shared area.
1. Copy the stellent folder from the shared drive (/opt/IBM/IC_Share/search/stellent) to the local drive (/opt/IBM/LotusConnections/stellent or /opt/IBM/Connections/stellent depending on your installation) on all nodes in your cluster.
2. Change the rights on the folder to 777:
```
cd /opt/IBM/Connections
mkdir stellent
cd stellent
cp -rf /opt/IBM/IC_Share/search/stellent/* .
chmod -Rf 777 *
```
3. Navigate to Environment > WebSphere Variables > FILE_CONTENT_CONVERSION and change the path from the shared area to the local area on your nodes. This should be the same across all nodes.
  For more information about WebSphere® variables, see the Changing WebSphere Application Server environment variables topic.
4. Navigate to Application servers > Connections Server > Process definition > Environment Entries, and edit the Environment Entry for the JVM running search to include the path to the local drive. This saves the step of setting the operating system level profile as it is contained within the JVM. For example:
```
LD_LIBRARY_PATH
$LD_LIBRARY_PATH:/opt/IBM/Connections/stellent/dcs/oiexport

PATH
$PATH:/opt/IBM/Connections/stellent/dcs/oiexport
```
Repeat the procedure for all nodes in the cluster.
Synchronize the nodes in the cluster and restart the servers.
Refer to Linux: Troubleshooting when files content is not found after searching for more information.

For IBM i

About this task

To copy Search conversion tools to local nodes, complete the following steps:

Procedure

Identify the nodes in the Search cluster.
1. Log in to the Integrated Solutions 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.
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 your operating system: /QIBM/UserData/IBM/Connections/data/local/search/stellent/
The new directory contains the exporter executable file.
In qshell, run the command: chown -R QEJBSVR /QIBM/UserData/IBM/Connections/data/local/search/stellent.

Run the CL command to add a system level environment variable:

LIBPATH:
ADDENVVAR ENVVAR(LIBPATH) VALUE('/QIBM/UserData/IBM/Connections/data/local/search/stellent/dcs/oiexport') LEVEL(*SYS) REPLACE(*YES)

On the Deployment Manager, update the FILE_CONTENT_CONVERSION Websphere variable to point to the exporter file in the local directory on each node.
For example: /QIBM/UserData/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 Changing WebSphere Application Server environment variables topic.
Restart WebSphere Application Server on each node.

For Windows

About this task

To copy Search conversion tools to local nodes, complete the following steps:

Procedure

Identify the nodes in the Search cluster.
1. Log in to the Integrated Solutions 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.
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.
Make sure to point to your local folders on the nodes and not to the shared area. For example, change the default path shared_data_directory_root\IBM/IC_Share\search\stellent\dcs\oiexport\exporter to a local folder, such as C:\IBM\Connections\data\local\search\stellent\dcs\oiexport\exporter.
The new directory contains the exporter executable file.
Navigate to Environment > WebSphere Variables > FILE_CONTENT_CONVERSION and change the path from the shared area to the local area on your nodes. This should be the same across all nodes.
For example: C:\IBM\Connections\data\local\stellent\dcs\oiexport\exporter
The exporter file must be in the same file path on all nodes.
Repeat the procedure for all nodes in the cluster.
Synchronize the nodes in the cluster and restart the servers.