To assemble your application to run on your application server, use the runAssembler
command-line script. This script takes a set of Oracle Commerce Platform application modules and assembles them into an EAR file (or the equivalent exploded directory structure).
The basic syntax of the command follows this format:
runAssembler
earfile
name
–m
module-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, use the following command:
runAssembler MyApp.ear –m MyApp DSS
You do not 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 Oracle Commerce Platform functionality (such as the DSS
module), you can also include Oracle Commerce Platform 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.
When runAssembler
creates an EAR file, unless otherwise instructed, it copies only CLASSPATH
entries, the configuration path entries, and J2EE modules. To include other module files, specify them via the ATG-Assembler-Import-File
attribute in the 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 an application you must provide runAssembler
with the WAR file’s URL and context root. If not provided, runAssembler
creates a unique name based on the directory where it found the WAR file. To provide the URL and context root, within your WAR file, create a META-INF/MANIFEST.MF file as follows:
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 Oracle Commerce Platform installation, see Appendix C: Oracle Commerce Platform Modules. This appendix also contains information about how to access the demos and reference applications.
You can also include the Dynamo Server Admin in your EAR file, so you can monitor and change settings in your application. See the Including the Dynamo Server Admin section later in this chapter for information.