+

Search Tips   |   Advanced Search

Configure a remote Document Conversion Service

To balance processing power, we can run document conversion services on a remote IBM WebSphere Application Server that supports document conversion services. Enable the delegation of document conversion services to a remote server requires steps on both IBM WebSphere Portal and the remote server.

  • If the remote Document Conversion Service (DCS) was set up on a remote machine with the remote search installer, then skip steps 1 - 7.

  • Update the content-types.properties file to ensure that document conversions are configured for different file types. For instructions, read Enable Document Conversion Services.

  • Copy the RemoteDCS.zip file to the file system. Locate RemoteDCS.zip on the Components disk included with the WebSphere Portal setup disks.

    Updated versions of RemoteDCS.zip might be available online. Check the Recommended fixes and updates for WebSphere Portal and Web Content Management site.

Linux on PowerPC: Run document conversion services on a remote WebSphere Application Server that supports document conversion services. Local document conversion is not supported on Linux for PowerPC . Additionally, the 64-bit Linux on System z does not support running document conversion or spell checker locally. Run these functions on a remote server.

  1. Install WebSphere Application Server on the remote system.

    Restriction: Stellent version 8.01 must support the remote system.

  2. Copy RemoteDCS.zip to the remote server and extract it in any directory with an appropriate archiving tool. A directory named dcs becomes available. Contains several files and subdirectories.

  3. Deploy dcs.war to WebSphere Application Server.

    1. Log in to the WAS console.

    2. Select Applications > Install New Application.

    3. Browse to the directory where you extracted RemoteDCS.zip then locate and select dcs.war.

    4. Specify dcs as the context root and click Next.

    5. Leave all other values as default.

      Restriction: The application name must be dcs_war. Do not change the default name.

    6. Map the application to the appropriate servers and specify the installation options as required.

    7. Click Finish and save the changes to the master configuration.

  4. Ensure dcs.war is running.

    1. Log in to the WAS console.

    2. Select Applications > Enterprise Applications.

    3. Locate dcs_war in the list of installed applications.

    4. Select dcs_war and click Start if the application is not started.

  5. Run the configuration script.

    1. Open a command prompt.

    2. Change to the dcs directory. The configuration script is in the root of the dcs directory in the directory where you extracted RemoteDCS.zip.

    3. Run the following command:

      • UNIX: ./setupremotedcs.sh
      • Windows: setupdcs.bat

    4. When prompted, specify the WAS installation directory. For example, APPSERVER_ROOT.

    5. When prompted for the profile, specify the directory where dcs.war is installed. For example, APPSERVER_ROOT/profiles/profile_name/installedApps/node/dcs_war.ear
    The configuration script copies all the files to the oiexport directory where we installed dcs.war; for example, APPSERVER_ROOT/profiles/profile_name/installedApps/node/dcs_war.ear/dcs.war/WEB-INF/lib/oiexport

  6. To add environment variables to the remote search server:

    1. Log on to the WAS console and go to....

        Servers | Server Types | WebSphere application servers

    2. Select the remote DCS server.

    3. Go to Java and Process Management > Process definition.

    4. Click Environment Entries.

    5. Click New to create the following entries:

      If the entries exist, click the entry and update the value.

        LD_LIBRARY_PATH
        APPSERVER_ROOT/profiles/profile_name/installedApps/node/dcs_war.ear/dcs.war/WEB-INF/lib/oiexport

        LIBPATH
        APPSERVER_ROOT/profiles/profile_name/installedApps/node/dcs_war.ear/dcs.war/WEB-INF/lib/oiexport

        PATH
        APPSERVER_ROOT/profiles/profile_name/installedApps/node/dcs_war.ear/dcs.war/WEB-INF/lib/oiexport

        SHLIB_PATH
        APPSERVER_ROOT/profiles/profile_name/installedApps/node/dcs_war.ear/dcs.war/WEB-INF/lib/oiexport

    6. Save the changes.

  7. Restart the server. Document Conversion Services is now installed on the remote server.

  8. Open wkplc.properties with any text editor from WP_PROFILE/ConfigEngine/properties.

  9. and value to wkplc.properties: DcsRemoteHost=URL of the remote host.

    Where URL of the remote host is the URL of the remote server to which you plan to delegate document conversion services. For example, DcsRemoteHost=http://server_name:port/dcs/dcs.

    This property does not exist in wkplc.properties by default. We must add this property and specify a value before proceeding to the next step.

  10. Run the appropriate task to delegate some or all of the document conversion functions to the remote server.

    1. Open a command prompt.

    2. Change to the following directory:

        WP_PROFILE/ConfigEngine

    3. Run the following task:

      Run the following command on all nodes in a cluster, if applicable.

        ./ConfigEngine.sh task_name

      Where task_name is one of the following ConfigEngine tasks:

      Task Description
      delegate-all-conversions This task delegates all file conversion services to a remote server.
      delegate-text-conversions This task delegates text document conversions to a remote server.
      remove-conversion-delegation This task ends the delegation of all file conversion services to a remote server.

  11. Restart WebSphere Portal.


Parent Document Conversion Services