An asset management server is an ATG instance that runs ATG Content Administration and whose SQL repositories and database schema are configured to manage multiple versions of assets. Unlike the development server, ATG Content Administration tables use a versioned schema, so it requires its own set of repositories and database tables.
In general, it is good practice to design your databases so that ATG Content Administration and production data are maintained separately, and transactions that pertain to one have no affect on the other. Transactions that are initiated by ATG Content Administration can sometimes incur considerable overhead; by separating versioned and production data, you can ensure that these transactions have no effect on production data processing.
Note: After you import the application’s content into the versioned repositories of ATG Content Administration, you cannot re-export the content and import it into another system.
This chapter shows how to create and import the basic data required by an asset management server, in the following steps:
CIM Usage
You can use ATG’s Configuration and Installation Manger (CIM) to perform these tasks. For more information, see ATG Installation and Configuration Guide.
For descriptions of the ATG Content Administration database tables, see Appendix A, Database Schema.
Prerequisites
Before you set up the asset management server database tables:
Install the latest versions of ATG Content Administration and other ATG applications that depend on ATG Content Administration, such as Oracle ATG Web Commerce Merchandising. For more information, see ATG Installation and Configuration Guide.
Determine which database system you will use in your production environment, and install an instance of that database on the asset management server.
Set the following environment variables:
DYNAMO_HOME:<ATG10dir>/homeJAVA_HOME: Java installation directory—on Windows, to the JDK directory
