Building a Migration Set

The integrated web service for data exchanges can be used to build a migration set.

The configuration migration IP assembles a data set in a xml file format and stores the generated files in an internal repository on the source environment.

If one or more configuration records have been deleted after the configuration set was set up, but before its payload was generated, then the payload will not include that configuration record.

Once the payload is generated, two actions become available. The first is the option to save the file on a local file directory.

The alternative option is to use the integrated web service for data exchanges. Once the file is built, the set becomes visible to other (target) environments that are set up to monitor available sets on the source environment.

Target environments can be set up in this way by specifying the end point of the source environment in the application properties file. Refer to Property Management for more information on setting a property. Once visible, the target environment can pull and import the migration payload from the source environment.

The generated files are stored in an internal repository on the source environment.

Build Unsuccessful

If the build fails, for example because of technical issues (out of memory error or a crash), the system logs a message. This message can be found in the Interface Messages Overview page.

If the build fails due to unexpected technical issues the message is not specific (GEN-MIGR-013). The application log file must be analyzed to determine the cause of the failure.

It is not possible to start a build if another build is in progress.

Table 1. Build Unsuccessful

Code	Severity	Text
GEN-MIGR-008	Fatal	It is not possible to start a new build while another build or import is in progress
GEN-MIGR-010	Fatal	It is not possible to start a build with an empty data set
GEN-MIGR-013	Fatal	The migration process failed due to technical issues
GEN-MIGR-014	Fatal	A cycle is detected in the object graph of {entity, key}
GEN-MIGR-015	Fatal	The migration process failed due to non-compatible application-version {application-version}