The first step in preparing your ATG module for assembly to a standalone EAR file is to export your web application. Before exporting an archived WAR file back into the ATG module J2EE structure, first remove the existing WAR file:
Navigate to your WAR file. For example:
<ATG9dir>/HelloWorld/j2ee-apps/helloworld/helloworld.war.Delete or rename the existing WAR file.
Select File > Export > WAR file.
Select your web project.
For Destination, specify the path to your ATG module’s J2EE application and name your WAR file exactly as it was initially named when you first created your module (if the name of the file to be exported does not match the
<web-uri>value in thej2ee-apps/helloworld/META-INF/application.xml, assembly fails). For example:C:\ATG\ATG9\HelloWorld\j2ee-apps\helloworld\helloworld.warSelect the Overwrite option to overwrite any existing work. Delete any old WAR files before exporting new ones.
Click Finish. You have an archived WAR file under your
j2ee-apps/eardirectory, and can assemble your application.Select File > Export > ATG J2EE Application.
Select your ATG module.
Specify a path and name for your exported standalone EAR file. It is a good practice to have separate directories for your standalone and development EAR files.
Select the Pack Ear, Standalone, Omit Licenses, and Admin Console options. Do not specify a server. You must configure your application to use a non-default server instance by setting a system property, similar to setting a system property in the WSAD internal server.
Click Finish.
