Introduction
The pages in this section of the guide describe the configuration migration feature, also referred to as the configuration migration tool. This feature is embedded in several of the Oracle Health Insurance applications, and it enables you to select and extract configuration rules from one environment into a portable file, and subsequently import file with the selected rules onto another environment.
The primary purpose of the configuration migration feature is to support the development life cycle of new configuration on an Oracle Health Insurance application, for example, moving the new and updated configuration rules from a development environment, to a user-acceptance environment, and eventually to the production environment.
The configuration migration feature supports several use cases, including the 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.
The configuration migration feature is access protected, and requires the appropriate access privileges to operate.
The pages that describe configuration migration feature use the following terms specific to the feature:
- Configuration Item
-
Any single instance of a user configured rule or piece of setup.
- Migration Set
-
A file that includes a selected set of configuration items.
- Source Environment
-
The environment from which the migration set is exported.
- Target Environment
-
The environment on which the migration set is imported.
There are two kinds of configuration items: top-level items and dependent items. Top level items can be individually selected and included in a migration set; dependent items are the configuration details integral to a parent top-level item; these cannot be explicitly selected, but instead are automatically included in any migration set that includes their parent top level item. See Including Configuration Items for a comprehensive list of top-level and dependent items.
For example, a provider group is a top-level item and can be individually selected and included in a migration set. Provider group affiliations [1] are dependent items representing the link between a provider and a provider group. These cannot be individually selected, but instead are automatically included in the same migration set as the parent provider group.
Some configuration items are both a top-level item and a dependent item. These are typically re-usable configuration items referenced by more than one rule. These items can be migrated individually, but can also be a required building block of a parent configuration rule. For example, consider a user configured error message or dynamic logic condition used by more than one rule.
The configuration migration feature enables the user to optionally exclude specific dependent items from a configuration migration set. This enables the user to include a configuration rule without being forced include - and potentially overwrite - any shared configuration used by that rule. For example, consider a scenario where you want to migrate a rule, without wanting to update the shared dynamic logic condition that it uses.
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.