Creating a Migration Set

Migration sets are assembled through a dedicated Integration Point - Configuration Migration Integration Point. This IP allows the user to create a full migration set.

Including Configuration Items

Below is the comprehensive list of configuration items that can be included automatically, per individual record, in a configuration migration data set. Each entry mentions which dependent items are auto-included.

Top Level Item	Automatically Includes	Optional Excludes
access role	access restriction access restriction grant
agent configuration	agent configuration integration integration	integration
boilerplate text
destination
dynamic logic	message	message
exchange property
floorplan	floorplan tag details
integration	access restriction destination dynamic logic integration parameter integration step subflow	access restriction destination dynamic logic subflow
subflow	destination dynamic logic integration step	destination dynamic logic
message
user sequence

Optional Excludes

Configuration rules in Oracle Insurance Gateway are hierarchical in nature; complex configuration rules are a composite of more basic configuration rules. For example, a integration is a composite of any combination of integration steps. In turn, the integration step is a composite of dynamic logic.

To assist the user in assembling a migration payload, the migration function automatically determines what other configuration is required to successfully install the selected configuration item on the target environment. The exclude options allow the user to carve out configuration records from that automatic inclusion. Consider the following example to clarify.

Integration A refers to a Dynamic Logic B (through integration steps). In this context, dynamic logic is a dependent item to integration step If integration A is selected for migration, the user has the option to include the dynamic logic as part of that migration as well.

Because an integration is also a top-level item, the user can alternatively choose to migrate integration A without migrating dynamic logic as well. This alternate approach requires that dynamic logic B is already present on the target environment. This allows the user to have separate configuration tracks, for example, the updates to the enrollment product using premium schedule B can be migrated before migrating the updates to premium schedules itself.