In order to run ATG Content Administration, you must add an ATG Content Administration server to your existing configuration. An ATG Content Administration 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.
Before you set up an ATG Content Administration server, you should have an existing Web site with well-defined repository definitions and database schemas. You produce the versioned repositories and schemas of the content development environment by importing the site content into the ATG Content Administration system.
Note: If you do not have an existing Web site, you should first design and develop the production site to a point where the repositories and database schemas are well defined.
Setup steps
You set up an ATG Content Administration server in the following steps:
Install an ATG Content Administration Server Instance, an ATG instance that you designate for asset development and management.
Copy the Application Module to the ATG Content Administration Server.
Create the Versioning Module that is to store the application’s versioning configuration.
Configure Repository Asset Support, if required.
Configure JSP File Asset Support, if required.
Configure Support for Other File Assets, if required.
Configure the VersionManagerService to manage versioned repositories and virtual file systems.
Import Initial Repository Assets into Versioned Repositories.
Setup scripts
Various sections of this chapter reference the following scripts that you run during various stages of configuring an ATG Content Administration server:
In order to run these scripts on a third-party application server, you must configure the server to use a Dynamo data source and transaction manager, not your native application server’s data source and transaction manager.
For more about these scripts, see the Tools chapter.
