Troubleshooting the file content extraction tool on AIX or Linux

You can troubleshoot configuration of the file content extraction tool, in an AIX® or Linux environment only, by running the Export utility separately from IBM® Connections. You can also check the environment variables and permissions.

About this task

IBM Connections uses the Stellent (Oracle Outside In Technology) Export utility to extract text from documents of various types. The extracted text is added to the Search index allowing users to find documents based on the content. When the Stellent utility is not configured correctly, file content will not be extracted or indexed. Therefore, search results within IBM Connections will not contain any matches on file content.

Procedure

  1. Ensure that Copying Search conversion tools to local nodes is complete.
  2. Run the exporter on the command line in isolation from IBM Connections to verify that the exporter is working correctly. To run the exporter executable on the command line, run the following command as the user that the Search WebSphere® Application Server is running under:
    1. Change directory to the Stellent binary location, for example:$ cd /opt/IBM/Connections/data/local/search/stellent/dcs/oiexport
    2. Run the exporter command. The exporter command has the following syntax: exporter inputpath=<path_to_input_file> outputpath=<path_to_extracted_text_output> outputid=FI_SEARCHTEXT, for example: 
      $ ./exporter inputpath=/root/translation.pdf \ outputpath=/root/testStellent.txt outputid=FI_SEARCHTEXT
      If the text extraction worked successfully, you will see the output: Export complete. If you see the following message, however, continue to the next step.
      ./exporter: error while loading shared libraries: libsc_ex.so: cannot open shared object file: No such file or directory
  3. Ensure that the operating system environment variable PATH is set correctly in Section 1 and contains the Stellent installation directory.
    • To verify that the Stellent exporter executable can be found through the PATH environment variable, run the following command: $ which exporter. The output of this command should contain the full path to the exporter executable, for example: /opt/IBM/Connections/data/local/search/stellent/dcs/oiexport/exporter.
  4. Using the WebSphere Application Server administrative console, ensure that the WebSphere environment variable FILE_CONTENT_CONVERSION points to the exporter executable, for example: /opt/IBM/Connections/data/local/search/stellent/dcs/oiexport/exporter
  5. Ensure that the user account that the Search WebSphere Application Server is running under has sufficient privileges. They should have read/write/execute permissions on the exporter executable and read/write file permissions on the other files in the Stellent installation directory.
  6. Verify that the libraries deployed with Stellent are compatible with your platform. For example, on a 64-bit Linux system: 
    $ uname -a
Linux host1 2.6.18-308.11.1.el5 #1 SMP Fri Jun 15 15:41:53 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux

$ cd /opt/IBM/Connections/data/local/search/stellent/dcs/oiexport
$ file libsc_ex.so
libsc_ex.so: ELF 64-bit LSB shared object, AMD x86-64, version 1 (SYSV), not stripped
    Note: The Stellent installation might contain 32-bit libraries even though you are running on 64-bit platform. This is not an issue, provided that the 32-bit compatible libraries are on the LD_LIBRARY_PATH or can be found on the shared library search path.

Results

The Stellent exporter executable has a number of dependencies on both the shared libraries packaged with Stellent and on shared libraries installed on your system. To verify that all the required shared libraries can be found, use the ldd command on the exporter executable as follows: $ ldd -v exporter. Check the output of this command for any shared libraries marked as => not found.. For example:
  • Stellent shared library not found. If a Stellent shared library cannot be found, then check that the setting of your LD_LIBRARY_PATH operating system environment variable contains the Stellent installation directory.
  • System shared library not found. If a system shared library cannot be found, then a prerequisite library is missing.
    Note: It is still possible to pick up libraries from locations other than those included in the LD_LIBRARY_PATH operating system environment variable, as long as they can be found elsewhere on the system's default search path. In addition to libc.so.6, Stellent is dependent upon the following libraries:
    • libstdc++.so.5 libgcc_s.so.1
    • For Red Hat Enterprise Linux 6.0 and later, it is possible that you are missing the package compat-libstdc++-33, which contains libstdc++.so.5.