InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.0: About user assistance >
6.6.0.5: Using the Application Assembly Tool interface >
6.6.0.5.2: Generating deployment code for modules

6.6.0.5.2: Generating deployment code for modules

Before installing your application in WebSphere Application Server, you must generate deployment code for the application. This step is required for EJB modules and for any EAR files that contain EJB modules. 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). (You can bypass this step by selecting the Code Generation Only checkbox on the property dialog box.)

  3. Validate the JAR file and display error messages if there are any J2EE specification violations within the JAR file.

  4. For CMP entity beans, generate persistence code.

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.

To generate deployment code for a module in the Application Assembly Tool, perform the following steps:

Note:
A working directory is used to save temporary files while creating the deployed archive. On UNIX systems, if there is insufficient space in this directory, a segmentation violation error can occur. Make sure that there is sufficient space in the working directory. Required space varies depending on the application. By default, the working directory is /tmp on UNIX systems. You can specify a different directory in the Working directory field on the property dialog box.

  1. Click File->Open and select the module. The module is displayed in the main window.

  2. Right-click the name of the module at the top of the navigation pane and choose Generate code for deployment. A property dialog box is displayed. Enter or edit values for 6.6.35.0: Assembly properties for generating deployment code. By default, the newly created archive file has the same name as the current archive file with the prefix Deployed_. Click Generate Now.

  3. View status messages in the window and resolve any errors reported.

  4. To close the window, click Close.

If the modules in an application are already deployed, the Application Assembly Tool regenerates deployment code for them.

Note: Ensure that your JAR files do not contain source code (.java files). On certain platforms, JAR files containing source code can cause compilation errors during deployment code generation.

Go to previous article: Modifying and adding modules to applications Go to next article: Verifying archives

 

 
Go to previous article: Modifying and adding modules to applications Go to next article: Verifying archives