Before you begin
A graphical interface is available for packaging code artifacts into various archives (modules) and configuring their J2EE 1.3 compliant deployment descriptors. The Application Assembly Tool (AAT) is available from the Windows Start menu, or you can invoke the tool from a command line as described in the Steps for this task.
On z/OS, the user must FTP (in binary) the setup.exe file from the AppServer/lib directory and install it on their Windows platform. This support is for the Windows platform Only.
If you access the Application Assembly Tool from a remote browser and select the Help, the Help files do not display. You can only view the Help files from a locally installed browser. To view the Help files and avoid this problem, close all the Netscape sessions on the remote machine and click Help. A new Netscape session starts, and you can then view the Help files.
Steps for this task
Results
The navigation tree displays a hierarchical structure used to build the contents of a new module, or to work with the contents of an existing module. Icons in the tree represent the components, assembly properties, and files for the module. The assembly properties appear in the AAT workspace.What to do next
Consider whether you have any existing J2EE 1.2 application modules that you would like to migrate to J2EE 1.3.You can create new modules of the following types, to assemble into an application module later:
Rather than create new modules to assemble an application, you can proceed directly to assembling a new application module. While assembling an application module, you can create any new modules that you need.