Repository key Concepts in ATG Merchandising development environment

The process of copying the assets you created in your ATG Merchandising development environment to a staging or production environment is called deployment. In order to deploy assets, you need to configure your deployment resources to recognize the repositories those assets are associated with. The deployment process requires three copies of each repository that contains deployable assets:

!. Target Repository,
2.Unversioned Repository,
3.Versioned Repository

Target Repository:

A target repository is an unversioned repository that supports deployed assets. It corresponds with the database in the environment – staging or production – that you have deployed assets to. both unversioned and target repository are same but only difference is Target repository resides in staging or production environment and Unversioned Repository resides in CA environment.


          1. Configure data sources that connect to the two databases.  
          2. Configure a SwitchingDataSource to switch between the two underlying data
              sources,                    
          3. Configure the repository components to point to the SwitchingDataSource. Also,
              set each repository component’s cacheSwitchHot property to true.
          4. Add the SwitchingDataSource to the agent’s list of switchable data stores in
              DeploymentAgent.switchableDataStores.

Unversioned Repository


A destination repository is an unversioned repository that supports the assets you want to deploy. This repository runs in the development environment and corresponds with the production database. See Important information about unversioned Repsoitory :-

1. Resides in CA Environment.

2. Instance of GSA Repository.                                                                                                       

3. No modifications are required in  Unversioned Repository Definitions.                                                                                      

4. No Extra properties are required.                   

5. 'this' attribute is not applicable here     

                                           
Versioned Repository


Versioned repositories store an application’s repository assets—that is, assets that are deployed as repository items to a GSARepository in the production environment, See important information about Versioned Repository

1. Resides in Production Environment.

2. Instance of Version Repository

3. Needs modifications in Versioned Repository Definition,eg: Remove Foreign key     
    relationships,Remove unique attribute if used.

4. Other versioning properties,such as asset_version,is_head etc.are automatically added to 
    tem definition  by CA server.

5. Set versionable attribute to specify which assets needsVersioning.By default all asset are 
    versionable.