To build a standalone-mode EAR file that uses a non-default server, you can run the application assembler with the –standalone and –server flags. For example:
runAssembler –standalone –server myServer MyApp.ear –m MyApp DSS
Note: If your production environment is clustered, do not specify the ATG server when you build the EAR. Instead, omit the –server flag and create a single EAR that can be deployed to all servers in the cluster. When you run the application, supply the Java argument -Datg.dynamo.server.name=server-name to specify the named instance of each server.
There are four localconfig directories at the end of the application’s configuration path. They appear in the following order:
atg_bootstrap.war/WEBINF/ATGINF/localconfig(a copy of<ATG9dir>/home/localconfig)ATGData/localconfigatg_bootstrap.war/WEBINF/ATGINF/home/servers/servername/localconfig(a copy of<ATG9dir>/servers/servername/localconfig)ATGData/servers/servername/localconfig
For output files, the application uses the logs and pagebuild subdirectories in the ATGData/servers/servername directory. You should not use the same server for more than one EAR file. If multiple EAR files are using the same output directories, errors or deadlocks can result.
