Before deploying applications on the server, if the application modules contain EJB modules, you must generate deployment code for the enterprise beans in the application. The Application Assembly Tool (AAT) provides this ability, or you can use the ejbdeploy command line tool.
Before you begin
This task assumes you have already assembled an EJB module, added it to an application module, saved the application module, and verified the application module.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 Enterprise application (EAR) files that contain EJB modules. During code generation, the Application Assembly Tool invokes the EJBDeploy tool to prepare entity bean (JAR) files for deployment in run time environment. To deploy a J2EE application, you can install the application in the administrative console.
The following steps assume that you are using the Application Assembly Tool to generate code for deployment.
Steps for this task
Note: For Container managed persistence (CMP) entity beans, if the JAR file that you opened (inputJar 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 files that contain mapping and database schema information.
Note: Do not change the default output file name to be the same as the input filename, as the AAT cannot read and write to the same file name, and therefore, an error will occur.
Results
After deployment code is generated for an application, the deployable archive is renamed with the prefix Deployed_.What to do next
Install the application on your server machine.Note: Before deploying the application in your run time environment, you might need to set classpaths.