Introduction
When you are working on enterprise applications with different software development life cycle (SDLC) environments [1], your configuration data needs to be consistent between environments.
A configuration migration tool enables you to move configuration data across environments.
This document describes the configuration migration feature embedded in Oracle Health Insurance. Oracle Health Insurance offers user interface pages to configure, build, and load configuration data sets and an integration point for the actual migration of the payload.
- NOTE
-
Oracle Health Insurance strongly recommends to use the supplied user interface pages for creating the integration point payload.
Oracle Health Insurance configuration migration supports scenarios like migration of subsets of the configuration, migration of linked reference data, propagation of removed configuration items and migration paths that include more than one source or target environment.
Access privileges and configurable user roles allow restricting access to the migration function.
Oracle Health Insurance configuration migrations are performed to and from online environments, allowing for small, selective migrations to target environments.
This document uses the following terms:
- Source Environment
-
The source environment is the environment from which the migration set is exported.
- Target Environment
-
The target environment is the environment which imports the migration set.
- Migration Set
-
The migration set is the file that holds all configuration items for a migration, that is, the migration payload.
- Configuration Items
-
The content of a migration set, for example, products, dynamic logic, messages, definitions and schedules. The migration payload.
There are two kinds of configuration items: 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. See Including Configuration Items for a detailed list of top-level and dependent items. Configuration Migration automatically includes dependent items in the migration payload as part of the top-level item they belong to. For example, a provider group is a top-level item and can therefore be individually selected for migration. Provider group affiliations [2], however, are dependent items that can’t be individually selected and that are automatically migrated together with the group account they belong to.
Some configuration items can be both a top-level item and a dependent item. These are typically rudimentary re-usable configuration items referenced by more than one rule. Examples are messages and dynamic logic. To prevent unnecessary large payloads and unwarranted updates to these items, the user can 'trim down' a top-level item by specifying which dependent top-level items can be carved out of the migration set. This does require that these items are already present on the target environment.
In addition to the standard auditing features available for all records in the Oracle Health Insurance database, the configuration items created on a target environment through migration store additional audit information relating to the source environment.
The Oracle Health Insurance system tracks the changes made during a configuration migration import process. When enabled, this feature tracks all changes made as a result of the import.