InfoCenter Home >
6: Administer applications >
6.3: Assembling applications and generating deployment code >
6.3.3: Generating deployment code for modules

6.3.3: Generating deployment code for modules

Deployment code for an application can be generated when the application is installed in WebSphere Application Server. Alternatively, it can be manually generated before installation. During code generation, the Application Assembly Tool invokes the Deployment Tool for Enterprise JavaBeans (ejbdeploy) to do the following:

  1. Generate and compile container implementation classes.

  2. Process the implementation classes by using the RMIC compiler, which generates the client-side stub and server-side skeletons needed for remote method invocation (RMI).

  3. Validate the JAR file and display error messages if there are any J2EE specification violations within the JAR file. Verifying archive files is important for successful generation of deployment code for the application.

  4. For CMP entity beans, generate persistence code.

  5. Insert the files back into the JAR file.

For CMP entity beans, if the JAR file contains a map and schema document, that schema is used. If the JAR file does not contain a map and schema document, the Application Assembly Tool uses a top-down mapping to generate the following files:

  • META-INF\Table.ddl

  • META-INF\map.mapxmi

  • META-INF\Schema\schema.rdbxmi
Note:
For Advanced Single Server Edition of this product, only the Table.ddl file is generated.

The user must create the database table manually. The generated Table.ddl file can be used as a guide, or the user can create the table by some other means.

If you do not wish to use the default top-down mapping, the recommended tool is VisualAge for Java. For information on default mappings, see the documentation for Deployment Tool for Enterprise JavaBeans.

To migrate CMP entity beans from WebSphere Application Server 3.5 for use in version 4.0, use the -35 option of the Deployment Tool for Enterprise JavaBeans. This option is recommended only if you need to preserve use of the mapping rules that were used in the 3.5 version of the Deployment Tool.

Go to previous article: Setting properties for a module Go to next article: Verifying archives

 

 
Go to previous article: Setting properties for a module Go to next article: Verifying archives