Packaging your enterprise application
From JPPF 6.2 Documentation
Main Page > J2EE Connector > Packaging your enterprise application |
For a J2EE enterprise application to work with the JPPF JCA connector, it is necessary to include a JPPF utility library called jppf-j2ee-client.jar, which can be found in the jca-client/build/lib folder. To ensure that this library can be made visible to all modules in the application, we recommend the following way of packaging it:
- add jppf-j2ee-client.jar in a lib folder under the root of the EAR file
- for each EJB, Web or Resource Adapter module of your application that will use JPPF, add a Class-Path entry in the META-INF/manifest.mf of the module, which will point to the JPPF library, for instance:
Class-Path: lib/jppf-j2ee-client.jar
In a typical J2EE application, it would look like this:
MyApplication.ear/ lib/ jppf-j2ee-client.jar MyEJBModule.jar/ ... META-INF/ manifest.mf: ... Class-Path: lib/jppf-j2ee-client.jar ... ... ... other modules ... MyWebApp.war/ ... META-INF/ manifest.mf: ... Class-Path: lib/jppf-j2ee-client.jar ... ...
Note: If you only need to use JPPF from a web application or module, then you can simply add jppf-j2ee-client.jar to the WEB-INF/lib folder of the war file.
Main Page > J2EE Connector > Packaging your enterprise application |