This model is essential for providing the checks and balances necessary for running a high-availability environment efficiently and to seamlessly manage applications as they move from test to stage to production.

In this deployment you create dedicated instances to keep your development, testing, and production separate.

1. Create three Oracle Content Management instances with the following settings:
   • Development—Instance type: non-primary; Upgrade schedule: immediate upgrade
   • Testing—Instance type: non-primary; Upgrade schedule: immediate upgrade
   • Production—Instance type: primary; Upgrade schedule: delay upgrade

   Setting your development and testing instances to non-primary ensures you won't be double-billed for all of your assets in those instances.

   Setting your development and testing instances to upgrade immediately (as soon as a new release of Oracle Content Management is available) allows you to test the upgrade on those instances, making sure the upgrade doesn't interfere with any sites you've deployed. If you find any issues, you can report them to Oracle Support so they can be fixed before the delayed upgrade is applied to your production instance one release later.

2. Create repositories, channels, localization policies, sites, and assets on your development instance.
3. Duplicate the repositories, channels, and localization policies on your testing and production instances.
4. If you haven't already done so, create a VM Compute instance.
5. Install the Oracle Content Management Toolkit on your VM Compute instance and have it use IDCS authentication.
6. Register your Oracle Content Management source and target instances.
7. Transfer your sites and their assets from your source instance to your target instance.
8. Test that your data is being replicated correctly. Make a few changes (less than five) in the source instance, including changes to each object type, then confirm these changes are accurately reflected in the target instance.
9. Sync any users who may need access to the secondary instances. For example, at a minimum, you'll need your administrators and developers synced.

For more information on the Oracle Content Management Toolkit, see Propagate Changes from Test to Production with Oracle Content Management Toolkit in Building Sites with Oracle Content Management.