Previous Topic: Java Proxy Runtime FilesNext Topic: Executing the Sample Applications


Deploying Java Proxy Runtimes

For the list of all the runtime files that must be deployed for the Java proxy to function, see Java Proxy Runtime Files in this chapter. You may find the task of deploying and coordinating these files complicated. Therefore, CA Gen provides a BAT file to help consolidate the runtime files into one deployable JAR file.

The mkjavart.bat file located in the CA Gen \classes is designed to build complete 'custom' runtime JAR files. The BAT file is capable of building runtimes customized for Java Proxies, Web Clients, and EJBs. The user exit classes are also packaged within the built JAR file. For more information on types of runtimes that can be constructed, see the usage of the BAT file (execute mkjavart.bat usage).

The easiest way to build a custom runtime JAR file for the Java proxy is by executing the following command:

mkjavart.bat runtime.jar  JavaProxy  commcfg AllComms   XML

This command builds a file called runtime.jar with the Java proxy, all installed communication runtimes, and the optional XML runtime within it. To make the JAR file smaller, you should specify the particular communication types instead and omit the optional XML runtime if you do not need it.

The commcfg.properties file is designed to be modified after deployment and therefore may not be a good candidate for inclusion within the JAR file. In that case, omit the commcfg parameter. It then becomes necessary for the commcfg.properties to be deployed separately.

More information:

Configuring the Java Proxy Communications