Customizing and binding profiles for Structured Query Language in Java (SQLJ) applications
Simplify the process of customizing and binding SQLJ profiles for your applications by performing these functions in the administrative console or with scripting. SQLJ profiles must be customized and bound before the enterprise application can use the application's embedded SQL.
Before you begin
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.
About this task
In addition to profile customization, you need to bind the customized profiles to the DB2 database. Profile binding should only take place after the SQLJ profiles are customized.
You can also customize and bind
profiles with scripting or the db2sqljcustomize tool:
- For scripting support, read the topic on the application management command group for the AdminTask object.
- For information on the db2sqljcustomize tool, read the topic on customizing and binding SQLJ profiles with the db2sqljcustomize tool for more information. If you customize profiles with the db2sqljcustomize tool, you will need to reinstall the application.
Procedure
Results
If the operation completed successfully, the
following message will be printed to the system
log:
ADMA0507I=ADMA0507I: The SQLJ operation on application {0} completed successfully. Exit code: {1}
ADMA0507I.explanation=This informational message indicates the program status.
ADMA0507I.useraction=No user action is required.
If
the operation did not complete successfully, the following message will be printed to the system out
log:ADMA0506I=ADMA0506I: The SQLJ operation on application {0} did not complete successfully. Exit code: {1}
ADMA0506I.explanation=The SQLJ operation encountered a problem. This informational message indicates
the program status. Prior messages in the command output give details of the problem.
ADMA0506I.useraction=Check the command output for the cause of the problem.