The following diagram shows how repositories are used in a content development environment.
A content development environment has three types of repositories:
Versioned Repositories store an application’s repository assets
A single Versioned Content Repository (the PublishingFileRepository) stores metadata for application file assets.
Standard Repositories store data required by ATG Content Administration.
Asset types
Project assets are of two types: repository assets or file assets. The following table briefly describes how repository and file assets are maintained in content development and production environments:
Asset type | Content development environment | Production environment | Examples |
|---|---|---|---|
Repository asset | Stored in a versioned repository, an instance of a VersionRepository. | Stored in a standard repository, instance of GSARepository. | ATG Commerce assets such as product catalogs |
File asset | Metadata is stored in a versioned content repository, an instance of VersionRepository. Exposed via a ContentRepositoryVFSService virtual file system for use in various contexts, such as deployment. | Stored in a virtual file system. | ATG personalization assets: targeters, content and profile groups, user segments, scenarios, slots JSPs and JSP fragments Static text files: HTML and readme files Binary files: Microsoft Word files, PDFs |
