ATG Applications - Module Direcory Structure

    To develop an (ATG) application on ATG platform, it can be included as a module or set of modules in the ATG Nucleus-based applications. The Nucleus-based applications are J2EE applications that include ATG Nucleus Framework. The Nucleus framework gives you access to a set of features of the ATG platform that are portable across application servers.

    Based on the above description, ATG application modules should follow core features to develop and assemble as a J2EE application (EAR).

 

• Application components are packaged in a simple, modular directory structure.
• Modules can reference other modules on which they depend, and which can be automatically loaded.
• The correct class path, configuration path, and main Java class for a given set of modules are dynamically calculated for both client and server.
• Updated modules are automatically downloaded from server to client.

Application Module Directory Structure

 An Oracle ATG Web Commerce installation must have a single module root (DYNAMO_ROOT) directory that contains all ATG application modules and your custom application modules. We should package classes and configuration files into that module. Module may not contains directly under module root. If that is the case, the module name uses parent-dir.module-dir format.

    Each module directory and its subdirectories can contain any number of module resource files such as platform libraries, Nucleus component configuration files, J2EE applications, web applications, HTML documents, and EJB modules.

The META-INF directory containing the manifest file MANIFEST.MF. 
The config directory contains the configuration files for Nucleus components. 
The j2ee-apps directory contains the J2EE web applications

   We can develop our code some other directory structure. But at the time of packaging the application as an ear, all required modules should be in a single module root  (DYNAMO_ROOT).