To assemble your application to run on your application server, use the runAssembler command-line script. This script takes a set of ATG application modules and assembles them into an EAR file (or the equivalent exploded directory structure).
The syntax of the command is:
runAssembler [options]output-file-name–mmodule-list
For example, if you develop your application as an application module named MyApp, and you want to assemble an EAR file that includes your application plus the DSS and DPS modules, you would use the following command:
runAssembler MyApp.ear –m MyApp DSS
You don’t need to specify the DPS module, because the application assembler examines the manifest file for each application module specified, and includes any modules that the specified modules depend on. The DSS module requires the DPS module, so it is included without being specified.
In addition to the modules containing core ATG functionality (such as the DSS module), you can also include ATG demos and reference applications in your EAR file. For example, to assemble an EAR file that includes the Quincy Funds demo, include DSSJ2EEDemo in the list of module for the runAssembler command.
Note that when runAssembler creates an EAR file, unless otherwise instructed it copies only CLASSPATH entries, CONFIGPATH entries, and J2EE modules. If you want to include other files, which are not included in your CLASSPATH, CONFIGPATH, etc., in your module, add an ATG-Assembler-Import-File attribute to your module’s META-INF/MANIFEST.MF file, as shown in this example from the DafEar.base module:
ATG-Required: DSS DAS-UI
ATG-Config-Path: config/dafconfig.jar
ATG-Web-Module: j2ee-components/atg-bootstrap.war
ATG-EJB-Module: j2ee-components/atg-bootstrap-ejb.jar
ATG-Class-Path: ../Tomcat/lib/classes.jar ../WebLogic/lib/classes.jar
../WebSphere/lib/classes.jar lib/classes.jar
Name: ../WebLogic
ATG-Assembler-Import-File: True
In addition, to include a standalone WAR file in your application you must provide runAssembler with a URL and context root for that WAR file. If this information is not provided, runAssembler makes up a unique name based on the directory in which it found the WAR file. To provide the URL and context root, within your WAR file, create a META-INF/MANIFEST.MF file with the following contents:
Manifest-Version: 1.0
ATG-Enterprise-Nucleus: True
ATG-Module-Uri: atg_bootstrap.war
ATG-Context-Root: /dyn
ATG-Assembler-Priority: -1
For a list of modules included in the ATG installation, see Appendix E, ATG Modules. This appendix also contains information about how to access the demos and reference applications.
You can also include the Dynamo Administration UI in your EAR file, so you can monitor and change settings in your application. See the Including the Dynamo Administration UI section later in this chapter for information.
