Set up an instance hierarchy

Set up an instance hierarchy that best supports your development life cycle.

Before you begin

Role required: admin

About this task

This example demonstrates how to set up an instance hierarchy where several peer subdevelopment instances have the same parent development instance but a more complex configuration is required.

Don’t use Team Development with production or test instances. When you back out a change on a Team Development instance, it backs out the change, including undoing the work on the source instance. This behavior can cause major problems on test and production instances.

Procedure

1. Provision a parent development instance on the same software version, such as Yokohama, as the target instance.
2. Clone the production instance to the parent development instance.
3. Provision subdevelopment instances on the same software version as the parent development instance.
4. Optional: Log in to the parent development instance and duplicate it with the subdevelopment instances.
5. On each subdevelopment instance:
   1. Define remote instance connections to other instances in the hierarchy that this instance must push and pull with.
   2. Select the parent instance.
   3. Pull all changes from the parent instance.
   4. Grant access rights to appropriate developers.