Customize and bind SQLJ profiles with the db2sqljcustomize
tool before you install the SQLJ application in the application server.
Before you begin
To perform this task, you must have SQLJ application that
has been deployed, but the application should not be installed in
the application server. If the application is already installed in
the application server, you will need to reinstall the application
after you customize the profiles. You also need serialized profiles
for the SQLJ application.
For SQLJ applications that use container-managed
persistence, you can deploy the application in two ways:
- Deploy the SQLJ application in the application server. See the
topic on deploying SQLJ applications that use container-managed persistence
(CMP) for more information.
- Deploy SQLJ applications with the ejbdeploy tool. See the topic
on deploying SQLJ applications that use container-managed persistence
(CMP) with the ejbdeploy tool.
For SQLJ application that use bean-managed persistence, see the
topic on deploying SQLJ applications that use bean-managed persistence,
servlets, or sessions beans.
About this task
To take advantage of SQLJ applications in the application
server, you need to customize the SQLJ profiles. The customization
process augments the profiles with information that is specific to
the DB2
® database. The database uses this information
at run time. By default, four DB2 packages are created in the
database; one package is created for each isolation level.
The application
server supports customizing and binding the SQLJ profiles in the administrative
console or with scripting:
- For administrative console support, read the topic on customizing
and binding profiles for Structured Query Language in Java (SQLJ) applications.
- For scripting support, see the topic on the application management
command group for the AdminTask object.