Understanding Configuration Movement

Configuration Movement is the process through which one or more Config ID, and thereby all the underlying configuration changes that are being tracked under the Config IDs, are moved or copied from one customer tenancy to another tenancy. For example, from Non-Production to Pre-Production and from Pre-Production to Production.

Customer Tenancies

On Oracle Financial Services Cloud, every customer is provisioned with three tenancies: Non-Production, Pre-Production, and Production. The Non-Production tenancy is where you first create all configurations as per your business needs. These configurations are then moved or copied to the Pre-Production tenancy for business users to test and verify. This is an iterative process until the business users verify the various configurations and thereby provide approval to make the same configurations available to the Production environment.

Bundling and Moving Configuration Changes

Oracle Financial Services Cloud tracks all the configuration changes done in the Non-Production environment through a Config ID. OFSC prompts you to select a Config ID before creating, editing, or deleting any configurations in the Non-Production tenancy. One Config ID can track multiple configuration changes and bundles these configuration changes in the Non-Production environment.

Once the configuration changes are completed for a given Config ID, close the Config ID so that it is not used for tracking any further configuration changes. Closing the Config ID makes the configuration updates available for movement (copy) to other customer tenancies on the Oracle Financial Services Cloud.

Configuration Movement Process

Configuration Movement is the process through which a Config ID, and thereby all the underlying configuration changes that are being tracked under the Config ID, are moved from one customer tenancy to another tenancy. For example, from Non-Production to Pre-Production and then from Pre-Production to Production.

The Configuration Movement process is always initiated from the target tenancy. Therefore, to move from the Non-Production tenancy to the Pre-Production tenancy, you need to initiate the movement process from the Pre-Production tenancy. Similarly, for configuration in the Pre-Production tenancy to be moved/copied to the Production tenancy, you need to initiate the movement from the Production tenancy.

Note:

The direction of configuration data flow, that is from Non-Production to Pre-Production, and then from Pre-Production to Production, is fixed and pre-configured by Oracle Financial Services Cloud tenancy automated provisioning process itself. You cannot reconfigure or change the direction of configuration data flow.

Every time a Configuration Movement is initiated, the configuration tracking system identifies a list of all the closed Config IDs that are available in the source tenancy since the last successful movement process completed, and then moves them one after the other to the target tenancy. Thus the Configuration Movement process works in an 'All or None’ mode. It either results in moving the configurations for all the Config IDs identified for movement, or does not move any of it (that is, in case of any unforeseen errors).