Configure a remote Document Conversion Service

To balance processing power, we can perform 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.

Before performing any steps in this task:

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

• Copy RemoteDCS.zip to your file system. Locate RemoteDCS.zip on the Components diso that is included with the WebSphere Portal setup disks.

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

Prerequisites

Recommended fixes and updates for WebSphere Portal and Web Content Management

Local document conversion is supported on z/OS . You do not need to run Document Conversion Services remotely for z/OS. If required, install the following package on the remote server to improve graphics performance with the document conversions: X11R6.

Linux on PowerPC : Document conversion services must be performed on a remote WAS that supports document conversion services. Local document conversion is not supported on Linux for PowerPC. Additionally, the 64-bit zLinux platform does not support running document conversion or spell checker locally. You must run these functions on a remote server.

To enable Document Conversion Services on a remote server:

1. Install WAS on the remote system.

   Restriction: The remote system must be supported by Stellent 8.0.1.

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 WAS.

   1. Log in to the WAS admin 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 admin 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 located in the root of the dcs directory located in the directory where you extracted RemoteDCS.zip.

   3. Run the following command:
      ./setupremotedcs.sh

   4. When prompted, specify the WAS installation directory; for example, WAS_HOME.

   5. When prompted for the profile, specify the directory where dcs.war is installed; for example, WAS_HOME/profiles/profile_name/installedApps/node_name/dcs_war.ear
   The configuration script copies all the required files to new directory named oiexport in the directory where you installed dcs.war; for example, WAS_HOME/profiles/profile_name/installedApps/node_name/dcs_war.ear/dcs.war/WEB-INF/lib/oiexport

6. Add the oiexport directory to the library path variable.

   Platform	Library path variable
   AIX	LIBPATH
   Linux	LD_LIBRARY_PATH
   Solaris	LD_LIBRARY_PATH
   Windows	PATH
   z/OS	LD_LIBRARY_PATH, LIBPATH

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

8. Open wkplc.properties from the WP_PROFILE/ConfigEngine/properties directory.

9. Add the following property 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:port_number/dcs/dcs.

   Important: This property does not exist in wkplc.properties by default. You must add this property and specify a value before you proceed to the next step.

10. Run the appropriate task to delegate some or all of the document conversion functions to the remote server.
    WP_PROFILE/ConfigEngine
    ./ConfigEngine.sh task_name

    Where task_name is one of the following configuration 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.

Restart WebSphere Portal.

For z/OS, start the Customization Dialog. See Configure the Portal Productivity Components for instructions on enabling remote Document Conversion Services. You must follow the Customization Dialog instructions for submitting the customization jobs.

Parent: Enable Document Conversion Services