An Oracle ATG Web Commerce application runs in your application server’s J2EE container. When you assemble the application, resources such as class libraries, web applications, and EJB modules are copied from the Oracle ATG Web Commerce installation into an EAR file. You deploy and run the EAR file on the application server. If you make changes to resources in your Oracle ATG Web Commerce installation, you might need to recreate and redeploy the EAR file to see the changes reflected.

Development versus Standalone Modes

If you assemble an EAR file in development mode, the application draws configuration information for Nucleus components from properties files in the Oracle ATG Web Commerce installation. Most of these properties files are stored in application modules; for example, the directory <ATG10dir>/DSSJ2EEDemo has a config subdirectory, which includes properties files for Nucleus components used by the Quincy Funds application.

If you assemble an EAR file in standalone mode, the properties files that configure your Nucleus components are imported into the EAR file and stored in directories that correspond to the Oracle ATG Web Commerce modules included in the application.