Building a Migration Set

The integrated web service for data exchanges can be used to build a migration set. The data sets that is been created using configuration migration date set IP is assembled to a migration set in form of a xml file. 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 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. 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, e.g., because of technical issues (out of memory error or a crash) a message will be logged. This message can be found in the Interface Messages.

If the build fails due to unexpected technical issues (GEN-MIGR-013) the message is not specific. 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.

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}