The ejbdeploy tool

Before you can successfully run your enterprise beans, you need to generate deployment code for the enterprise beans. The ejbdeploy tool provides a Qshell command-line interface that you can use to generate enterprise bean deployment code. The tool also allows you to run a build process to automatically invoke the ejbdeploy tool in batch mode.

To invoke the ejbdeploy tool from the Qshell command line, enter the ejbdeploy command. When you run the command, you specify a JAR or EAR file that contains one or more enterprise beans. The tool then generates a JAR or EAR file that contains deployment code in the form of .class files. For more information about the command and its parameters, see Syntax and parameters of the ejbdeploy tool.

The ejbdeploy tool supports these functions:

• Meet-in-the-middle mapping
• Enterprise bean single and multiple table inheritance
• Converters, which translate a database representation to a Java object type
• Composers, which map a single complex bean field to multiple database columns

The ejbdeploy tool supports three levels of access intent:

• Optimistic indicates a preference for optimistic concurrency control.
• Access type indicates whether the application intends to read or update the entity bean.
• Read ahead indicates how deeply to read ahead in an enterprise bean relationship graph.

Mapping to multiple back-end databases is also supported. The schemas and the generated .ddl file are stored in the following directory of the JAR or EAR file:

beanname/ejbModule/META-INF/backends/backend_id/schemaname.schxmi
beanname/ejbModule/META-INF/backends/backend_id/tablename.ddl

where

• beanname is the name of the enterpise bean.
• backend_id is the ID for the type of database store. This value is determined by the -dbvendor parameter, and should be specified as DB2UDBISERIES.
• schemaname is the name of the schema, collection, or library that contains the table that the enterprise bean uses for container-managed persistence.
• tablename is the name of the table that the enterprise bean uses for container-managed persistence.

If you have only one .ddl file, it appears both in the directory described above and in the META-INF folder.

These topics describe how to use the ejbdeploy tool and the tasks that you can perform with it:

Syntax and parameters of the ejbdeploy tool
This topic describes the syntax and parameters of the ejbdeploy command.

Generate deployment code from the command line
This topic describes how to use the ejbdeploy command to generate deployment code for your enterprise beans.