Copying Search conversion tools to local nodes 

Copy Search conversion tools to local nodes to enable full indexing of data.

Before starting

Perform this task only on nodes in the Search cluster.

Steps 1-3 and 7-8 are required for all supported operating systems. (If your deployment has only one node, skip steps 1-3.) Steps 4-6 are required only if you are using the AIX or Linux operating system.

If you have added a node to an existing cluster, as described in the Add a node to a cluster topic, complete this task only if the new node is a member of the Search cluster.

 

About this task

The Search conversion tools make it possible to index Files and Wiki attachments. The tools work best when available locally on each node. However, when IBM Connections was installed, the conversion tools were deployed on a network share. Therefore, copy the tools to each node in the Search cluster.

To copy Search conversion tools to local nodes...

Procedure

1. Identify nodes in the Search cluster.
a. Log in to the WAS Integrated Solutions Console and click Servers -> Clusters -> WebSphere application server clusters.
b. Click <cluster_name>, where <cluster_name> is the name of the Search cluster.
c. In the Additional Properties area, expand Cluster members and then click Details.
d. In the table of cluster members, make a note of the nodes that host the cluster members.
Note: References to nodes in the remaining steps of this task apply only to nodes in the Search cluster.

2. Copy the shared_data_directory_root/data/shared/search/stellent/dcs/oiexport 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 system:
AIX or Linux: /opt/IBM/LotusConnections/data/local/search/stellent
Microsoft Windows: C:\IBM\LotusConnections\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:
 
For Microsoft Windows: C:\IBM\LotusConnections\data\local\search\stellent\dcs\oiexport\exporter
For AIX/Linux: /opt/IBM//LotusConnections/data/local/search/stellent/dcs/oiexport/exporter

Note: 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. (AIX and Linux only) Back up the setupCmdLine.sh file on each node. This file is located in the app_server_root/AppServer/bin directory.
5. (AIX and Linux only) 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 that you specified in Step 2.

6. (AIX and Linux only) Add the following text to the end of the setupCmdLine.sh file on each node:

a. AIX: export LIBPATH=$LIBPATH:<SearchBinariesHome>/dcs/oiexport
b. Linux: export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:<SearchBinariesHome>/dcs/oiexport
where <SearchBinariesHome> is the path to the directory that you specified in Step 2.

7. Restart all node agents.
8. Restart WAS on each node.

Parent topic

Mandatory post-installation tasks

Related tasks
Add a node to a cluster
Change WAS environment variables

+

Search Tips   |   Advanced Search