Java Proxy › Preparing for Execution › Deploying a Java Proxy › Java Proxy Runtime Files

Java Proxy Runtime Files

The Java Proxy requires a set of runtime JAR files to be present to execute properly. You can find the runtime files in the CA Gen\classes directory. The following is the list of JAR files:

• Csuxx.jar
• vwrtxx.jar
• odcxx.jar
• jprtxx.jar
• jprtxx.xml.jar (only required if XML API is generated)
• odcxx.jar
• odcxx.tcpip.jar (only if TCPIP communication is required)
• odcxx.mqs.jar (only if MQSeries communication is required)
• odcxx.eci.jar (only if ECI communication is required)
• odcxx.ejbrmi.jar (only if Java RMI communication is required)
• odcxx.tuxedo.jar (only if Tuxedo communication is required)
• odcxx.ws.jar (only if Web Services communication is required)

Note: xx refers to the current release of CA Gen. For the current release number, see the Release Notes.

You should place the following properties files within the CLASSPATH:

• commcfg.properties
• codepage.properties

These properties files can be found at several places: CA Gen directory, CA Gen\classes directory, and CA Gen\classes\resources directory.

There are a set of Java class files that contain the user exits. These are shipped as Java source and class files and not within a JAR file. Because of this, you must deploy the contents of the CA Gen\classes directory to allow usage of the user exit class files. (particularly the com).