Chapter - 3 : Troubleshooting the Client

Here are some things to check if the Docupresentment Client is not communicating with Docupresentment Server.

Note: The test connection from client to server will fail if the port numbers are not valid. Use unused port numbers to avoid this issue.

Checking the DOCCLIENT.XML File

First, make sure the docclient.xml file is set up correctly. Here is an example docclient.xml file, including all of the queue sections with ActiveMQ active:

Checking the CLASSPATH and other Environment Variables

The following values are added to the CLASSPATH variable when you install the Docupresentment Client:

CLASSPATH=C:\docclnt\clientlib\DocucorpMsg.jar;C:\docclnt\clientlib\DocumentServer.jar;
C:\docclnt\clientlib\commons-collections.jar;C:\docclnt\clientlib\commons-fileupload.jar;C:\docclnt\clientlib\commons-pool.jar;C:\docclnt\clientlib\DocuCorpUtil.jar;
C:\docclnt\clientlib\DSIJavaMsg.jar;C:\docclnt\
clientlib\IDSJSP.jar;C:\docclnt\clientlib\jdom.jar;
C:\docclnt\clientlib\xerces.jar;C:\docclnt\clientlib\log4j.jar;

The following values are added to the PATH variable when you install the Docupresentment Client:

PATH=C:\docclnt;C:\docclnt\jre\bin\client;C:\docclnt\jre\bin;e:\docclnt\.\.install4j

These values are added to the following variables when you install the Docupresentment Client:

ids_client_configuration=C:\docclnt\docclient.xml
java_endorsed_dirs=C:\docclnt\clientlib\endorsed

logging_client_configuration=C:\docclnt\logclientconf.xml

Installing Third-Party JAR Files

Note: If you are using IBM MQ (WebSphere MQ or MQ Series) or ActiveMQ for the queuing method, you must make the IBM MQ or ActiveMQ jar files available to Docupresentment. See the “Installing Third-Party Jar Files” section of the Docupresentment Guide for more information.

Installing the Docupresentment with a Response File

You can run the Docupresentment in unattended mode from the command line. To do this you must create a response file to provide the information the installer needs. A response file is a text file which contains the information a user would typically provide while running the Setup wizard or responding to command-line prompts. This information is in name=value format.

To create a response file that contains the necessary data, first run the command-line installer in one of these ways:

• Using default mode, with no arguments. After the installation finishes, the installer creates a response file named response.varfile.
• Using the command-line installation with the -console parameter. This lets you specify the name you want to assign to the response file.

After the installation finishes, the installer creates the response file and stores it in the.install4j directory. This file contains name=value data captured during the installation process. You can edit this file if necessary to modify the values. Here is an example:

You can then pass this response file to the installer using the -varfile parameter. For example, to run the installer in unattended mode using a response file, include these parameters:

-q -console -c -varfile varfilename

Here is an example: