Installing the EAR file on the server

Once you have run the DB2 SQLJ profile customizer on the SQLJ customization profiles by using the Ant script, the EAR files are updated with a modified customization profiles. You can now install these updated EAR files on either the test or the production server.

 

Installing the EAR file on WebSphere Application Server

Prerequisites

• You must add the SQLJ run-time JAR file to the class path of the DB2 JDBC Provider which is associated with the data sources that are used by the SQLJ enterprise beans. In the administrative console, add ${DB2_JDBC_DRIVER_PATH}/db2jcc.jar to the DB2 JDBC Provider's class path, on the DB2 JDBC Provider page.

For more information about using WebSphere Application Server, consult the WebSphere Application Server documentation.

 

Parent topic

enterprise beans which use SQLJ as their persistence mechanism is more complicated than regular deployment. As part of the generation of deployment code, one or more SQLJ customization profiles will be created. You can then run the DB2 SQLJ profile customizer against the customization profiles to produce static SQL in the database.">Deploying EJB applications using SQLJ for data access
Previous topic: SQLJ profile customizer, db2sqljcustomize, easier, you can employ an Ant script. This particular Ant script is the one that is created when the batch SQLJ ejbdeploy command is run against an EAR file.">Running the Ant script

 

Related concepts

SQLJ support enables you to build and run SQLJ applets and applications. The DB2 SQLJ profile customizer, db2sqljcustomize, is one of the components of SQLJ, the other two components being the translator and the run time.">DB2 SQLJ profile customizer