Before you begin
If you want to use existing Java 2 Platform, Enterprise Edition (J2EE) Version 1.2 modules in your J2EE Version 1.3 application, migrate them to the Version 1.3 specification first.Why and when to perform this task
Assemble an Enterprise JavaBeans (EJB) module to contain enterprise beans and related code artifacts. Group Web components, client code, and resource adapter code in separate modules.An EJB module is installed as a stand-alone application or is combined with other modules into an enterprise application.
To increase performance, break CMP enterprise beans into several enterprise bean modules during assembly. The load time for hundreds of beans is improved by distributing the beans across several JAR files and packaging them to an EAR file. Load time is faster when the administrative server attempts to start the beans, for example, 8-10 minutes versus more than one hour when one JAR file is used.
The Application Assembly Tool (AAT) provides flexibility in assembling EJB modules. Options described below include:
Steps for this task
If you change the session type (stateful or stateless) of a session bean, you must click Apply before making any other changes to the same bean. Otherwise, certain input fields on the GUI become inactive. (You will know they are inactive because they are grayed out on the GUI.) After making all of your changes, click Apply again to commit them.
What to do next
Assemble any other new modules of your choice:
You can also migrate existing modules.
Another option is to proceed directly to assembling a new application module. While assembling an application module, you can create any new modules that you need.