Your production Web site must be packaged as an ATG application module. This module includes all the class files, configuration files, JSPs, and HTML files that the site uses. You copy the application module from the production (or development) server to the asset management server.
The nature and complexity of the application module determines whether you copy over the entire module. For example, in the case of commerce applications, you can omit components for the checkout process, because these components are not utilized by ATG Content Administration. However, it might be simpler to copy over an entire module with complex dependencies.
The list of specific class files, configuration files, and JSPs to copy varies for each application module; however, you must copy the following module resources to the asset management server:
Any custom events, actions, and conditions that you added to the Scenarios module, if you intend to create and manage scenarios with ATG Content Administration.
Definition and configuration files for all repositories that you want to manage with ATG Content Administration, including any configuration files on which the repositories depend. You must copy the definition files for repositories that contain read-only data, such as Product Catalog and Price Lists repositories. You can omit definition files for repositories that contain read/write data that can be modified in the production environment, such as Profile, Order, and Inventory repositories.
If application repositories have secured repositories layered above them, you can also copy their definition and configuration files. This lets you define access rights to the assets for ATG Content Administration users. For more information on defining access rights to assets, see Managing User Access and Security.
