The procedure for configuring DAF deployment to deploy repository items requires you to create a GSARepository that matches your source repository, and then create a data source for the new repository that points to the database used by the repository that is the target for the deployment. See the diagram in DAF Deployment Architecture earlier for an illustration. It might also be helpful to refer to the deployment setup procedure ATG Content Administration Programming Guide, which contains a detailed example.

  1. Configure a data source to point to the database used by the target repository. To do so, you can copy and rename the Oracle ATG Web Commerce server’s FakeXADataSource and JTDataSource properties files, pointing the new file to the target site’s database. Put the files in the same location as the Oracle ATG Web Commerce server’s FakeXADataSource and JTDataSource.

    For more information on the FakeXADataSource and JTDataSource, see the ATG Installation and Configuration Guide.

  2. Create a destination GSARepository for each source repository/target repository combination. For example, if you have a source repository called MyContent, and a target repository, TargetContent, create an additional GSARepository, DestinationContent. To configure it, copy the source repository’s properties file and rename it as appropriate. Change the value of the repositoryName property, and change the dataSource property to point to the data source you created in step 1, for example:


    Put these files in the localconfig directory on the Oracle ATG Web Commerce server.

  3. Add the repository you just created to the initialRepositories property of the localconfig/atg/registry/ file on the Oracle ATG Web Commerce server.

    Make sure the value you enter matches the RepositoryName property in the repository’s properties file (rather than the name specified in the properties file itself).

  4. Repeat steps 2 and 3 for each additional source/target repository pair.