If you run the application assembler without specifying a server name, the resulting application uses the default Oracle Commerce Platform server. This means that the application gets site-specific configuration settings from standard configuration directories, such as <ATG11dir>/home/localconfig.

If the application is assembled in development mode, the localconfig directory in the Oracle Commerce Platform installation is set as the last entry in the application’s configuration path. If the application is in standalone mode, the assembler copies that directory from the Oracle Commerce Platform installation into the atg_bootstrap.war/WEB-INF/ATG-INF directory in the EAR file (as described in Development Mode and Standalone Mode). This directory is added to the configuration path just before the ATG-Data/localconfig directory, which is the last entry in the configuration path . For output files, the application uses the logs and pagebuild subdirectories in the <ATG11dir>/home directory (in development mode) or the ATG-Data/home directory (in standalone mode).

If you configure additional Oracle Commerce Platform server instances (see the Platform Installation and Configuration Guide for information), you can build your application with a particular server’s configuration. The effect of specifying a server differs depending on whether you are assembling a development-mode or standalone EAR file.