Each \deploy\<component> directory contains a <component>.jar. This JAR file is the Java Proxy. You can deploy the proxy JAR file (and its runtime) for use by an application in various ways. In general, all the techniques ensure that the generated classes and the runtime classes are loadable from within the target application. Depending on the target application, the class files can be handled individually as part of JAR files, an executable JAR file, and a larger WAR or EAR file. The generated samples demonstrate the executable JAR file and the EAR file techniques.
Usually, the concept of loadable means having the class file or the JAR file containing it within the CLASSPATH environment variable. With EAR file deployments, the EAR file is not present in the CLASSPATH, but there is an internal CLASSPATH setting within the EAR file specified in various manifest files.
The development group must treat the proxy JAR file and the runtime JAR files as third party libraries and deploy them appropriately. The following sections explain some concepts that may help in the deployment, but you should not consider them the only way to deploy.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|