Deployment is the process of copying assets from the Merchandising development environment to a staging or production environment.
Each repository that contains deployable assets exists in three forms:
A source repository. This repository runs in the development environment. It supports versioned copies of assets in progress. It points to the ATG Content Administration database.
A destination repository. This repository runs in the development environment. It is an unversioned repository that supports the assets you want to deploy. A destination repository is required for every target repository that receives deployed data, and it points to the same staging or production database as the target repository.
A target (staging or production) repository. This repository runs in the staging or production environment, to support deployed assets. If both environments exist, there is a target repository in each one. The repository is unversioned. It points to the database in the staging or production environment to which you have deployed assets.
Source and destination repositories are already set up for assets that use the standard, unmodified Merchandising repositories. Creating the target repositories is part of the process of defining the target server, which is step 2 of the following procedure.
To configure deployment resources:
Read the Deployment Concepts chapter of the ATG Content Administration Programming Guide to become familiar with the deployment process.
Set up the target server and database, as described in the Setting Up Deployment chapter of the ATG Content Administration Programming Guide.
Note: If you made changes to the standard repositories, such as adding properties to an existing item descriptor, you must make the same changes to the corresponding target repositories. The standard repositories and their locations are the same on the target server as they are on the asset management server.
If you created custom repositories, configure them for deployment, as described in the Setting Up Deployment chapter of the ATG Content Administration Programming Guide.
Add any versioned repositories that are not already there, including custom repositories and the
RefinementRepositorythat is used by Search Merchandising and Faceted Search. Follow the instructions in the Setting Up Deployment chapter of the ATG Content Administration Programming Guide.If you are including a completely new file, reassemble, redeploy, and restart the application. If you used
AssetResolverto add a custom repository, you do not need to build a new.earfile; you need only to restart the application.
