ODFProcessDist.java - Processed distribution exit

Customize your ODF environment in several ways by using the ODFProcessDist.java user exit program.

Use the ODFProcessDist.java program to modify your ODF environment in the following ways:

Customize the details and format of the outgoing emails that contain distributions when the distribution Location value is set to E-mail. Customize the format for any Location value with the Notify by e-mail check box selected. For each distribution location type, you can customize the email content and the maximum size for email attachments within a single email.
Customize the details of distribution output for all other distribution types on Content Manager OnDemand for Multiplatforms and IBM i servers, and for all distribution types on z/OS® except when Location value is set to Print.
Specify your SMTP server name to use for outgoing email.
Specify whether to enable the secure sockets layer (SSL) when you use the SMTP server to send email.
Specify trace parameters.
On Content Manager OnDemand for Multiplatforms and IBM i servers, specify the name of the command to use to submit ODF print requests and the name of the printer queue to use.

The ODFProcessDist.java program uses the ARSODF.XML file as input. A compiled version of the sample ODFProcessDist.java program is shipped with ODF. You can use the program as it exists as shown in the sample program, or you can modify the sample program and recompile it to further customize outgoing distribution details. For more information about the ARSODF.XML file, see Verifying the ARSODF.XML file.

Linux only: AIX only: The sample ODFProcessDist.java program is delivered as a default executable file in the installpath/jars directory, where installpath is the installation directory path you chose when you installed Content Manager OnDemand. A source code sample is provided in the installpath/exits/odf directory.

Windows only: The sample ODFProcessDist.java program is delivered as a default executable file in the installpath/jars directory, where installpath is the installation directory path you chose when you installed Content Manager OnDemand. A source code sample is provided in the installpath/exits/odf directory.

z/OS only: The sample ODFProcessDist.java program is delivered as a default executable file in the installpath/jars directory, where installpath is the installation directory path you chose when you installed Content Manager OnDemand. A source code sample is provided in the installpath/samples directory.

IBM i only: The sample ODFProcessDist.java program is delivered as a default executable file in the /QIBM/ProdData/OnDemand/jars IFS directory. A source code sample is provided in the /QIBM/ProdData/OnDemand/jars IFS directory.

If you need to change the ODFProcessDist.java program, copy the source code sample to a different directory, such as /ODF/modified/samples. With this copy step, you can preserve the original copy if you need to use it later. Then, modify the ODFProcessDist.java program that you copied. Compile the program and place the updated ODFProcessDist.class file in the IBM-supplied jars directory, retaining the original ODFProcessDist name.

You need to specify the path and file names for the jar files that are used by ODF on the CLASSPATH parameter when you recompile your modified ODFProcessDist.java program. To see the required CLASSPATH value, start the ARSODF program in verbose mode, by using the -v parameter in addition to the other parameters that you use to start ODF. One of the resulting messages contains the complete path and file names of all the jar files. For example, on IBM i, the message might look similar to the following, with the actual version numbers of the jar files dependent upon the Content Manager OnDemand server version that you are running.

ARS7900I The config parm ARSODF_PROCESS_CMD = 
'java' -classpath "/QIBM/ProdData/OnDemand/JARS/:
/QIBM/ProdData/OnDemand/JARS/jakarta.activation-api-2.0.1.jar:
/QIBM/ProdData/OnDemand/JARS/jakarta.mail-2.0.3.jar:
/QIBM/ProdData/OnDemand/JARS/jakarta.xml.bind-api-3.0.1.jar:
/QIBM/ProdData/OnDemand/JARS/jaxb-core-3.0.2.jar:
/QIBM/ProdData/OnDemand/JARS/jaxb-impl-3.0.2.jar:
/QIBM/ProdData/OnDemand/JARS/ODFManifest.jar:
/QIBM/ProdData/OnDemand/JARS/ODFTemplate.jar" ODFProcessDist

If you encounter errors when processing distributions, check for messages in the ODFProcessDist0.log file. The log file is created for you if it does not already exist. The file is located in the temporary directory specified by the ARSODF_TMP entry in your ARS.CFG configuration file. If the ARSODF_TMP entry does not exist, the log file is located in the directory specified by the ARS_TMP entry in the ARS.CFG file. If ARSODF_TMP and ARS_TMP entries do not exist, the default directory is /tmp. To control the level of messages that are written to the log file, modify the <tracelevel> element in the ARSODF.XML file. See Configuring ARSODF.XML elements for more information on the <tracelevel> element.