Configuration Migration

This guide describes the migration feature embedded in Oracle Insurance Gateway. This feature supports the automated transfer of configuration data between two environments for a variation of scenarios, including migration of linked reference data, the propagation of removed configuration items and migration paths that include more than one source environment.

The migration function is an embedded feature: there are integration points to build, publish and load data sets. Access to these integration points is assigned through configurable user roles. Migrations are performed to and from online environments, allowing for full, complete migrations to target environments.

This guide uses the terms 'source environment', 'target environment' and 'migration set'. The migration set is the file that holds all configuration items for a migration, i.e. the migration payload. The source environment is the environment from which the migration set is exported. The target environment is the environment which imports the migration set.

The content of a set, such as integration and events, are called configuration items. There are two kinds: top level items and dependent items. Top level items can be independently included in a migration set; dependent items are the configuration pieces that are integral details of a larger, top level item. Dependent items are automatically included in the migration payload as part of the top level item they belong to.

In addition to the standard auditing features available for all records in the Oracle Insurance Gateway database, the configuration items created on a target environment (through migration) store audit information relating to the source environment.