When you assemble your application, the application assembler includes all of the Oracle Commerce Platform servers you have configured (see Assembling Applications in the Platform Programming Guide for information on application assembly). This means that you can build your application once for each JBoss partition, deploy it on each partition, and enable the appropriate Oracle Commerce Platform server on each instance simply by changing the value of the atg.dynamo.server.name system property when you start up JBoss:

standalone.sh|bat --server-config=JBoss_server_config
-Datg.dynamo.server.name=ATG_server

To assemble and configure your Oracle Commerce Platform application to run on a JBoss partition, use the -liveconfig, -standalone, -distributable, and -pack flags when you invoke the application assembler, as in this example:

bin/runAssembler –liveconfig –standalone –distributable –pack
output_file_name.ear –m module-list DafEar.Admin –jboss

The –pack flag is optional. The –distributable flag is required to enable JBoss session failover. Do not use the –server flag to specify an Oracle Commerce Platform server configuration. If you are using a named configuration layer, specify that as well (see Managing Properties Files in the Platform Programming Guide for information on named configuration layers).

The –jboss flag is required for all applications running on JBoss.