Creating a Versioned Module

This chapter shows how to import site content into versioned repositories and schemas, in the following steps:

  1. Copy the Application Module to the Asset Management Server.

  2. Create the Versioned Module that is to store the application’s versioning configuration.

  3. Configure Repository Asset Support, if required.

  4. Register the Versioned Repositories with Content Administration.

  5. Configure JSP File Asset Support, if required.

  6. Configure Support for Other File Assets, if required.

  7. Configure the VersionManagerService to manage versioned repositories and virtual file systems.

  8. Import Initial Repository Assets into Versioned Repositories.

  9. Import Initial File Assets.

Note: This procedure assumes an existing Web site that is packaged as an ATG application module, with well-defined repository definitions and database schemas.

Setup scripts

Content Administration provides two scripts that can help you import content into the versioned repositories. These are described at the end of this chapter:

  • exportRepository exports the contents of one or more standard repositories.

  • importRepository imports the contents of a data file generated with exportRepository into a standard or versioned repository.

Related tasks

Before you set up the versioned database, you must first Create and Install the Versioned Database Schema, as described in the previous chapter.

If your environment includes ATG applications that run on top of ATG Content Administration, such as ATG Commerce or ATG Outreach, you must install database tables that are specific to those applications and import data into them. See the manual that describes your application for instructions.

 
loading table of contents...