Update the manifest files for any ATG application modules that you have created. For example, suppose your application is stored in an application module named MyApp at the top level of <ATG10dir>. You’ll need to modify the <ATG10dir>/MyApp/META-INF/MANIFEST.MF file to include the manifest attributes used by the runAssembler command. (Note that you do not need to modify the manifest files for any of the application modules that are part of the ATG installation, such as DPS and DSS. The manifest files for those modules already have all of the necessary attributes.) For more information about application modules and manifest attributes, see the Working with Application Modules chapter of the ATG Platform Programming Guide.

Build an EAR file using the runAssembler command. For more information, see the Developing and Assembling Nucleus-based Applications chapter of the ATG Platform Programming Guide.

Deploy the EAR file. Note that if you have a version of the application running, you should undeploy that version before deploying the new EAR file. See your application server documentation for information about deploying and undeploying applications.