Actions Required After the Migration Process (Magic xpi 4.13)
After the project has been migrated, you need to perform the following actions:
-
The migration process creates a Logs folder under the Magic xpi folder. Open it and address any issues.
-
Review all NOP services that were created as place holders for unsupported components, and decide how to handle the flow logic.
|
|
-
The Migration utility should be used only if all databases are accessible and all schemas are available. If not, the migration of Data Mapper steps will fail.
-
As a general guideline, we recommend that you examine the Migration log and fix any issues that arise in your iBOLT V2.5 project. You should then run the Migration utility again until all issues are resolved.
|
-
iBOLT V2.5 logical names are not migrated automatically. You need to define the corresponding environment variables in Magic xpi manually.
-
Review all Resource Repository and Service Repository settings. Since these settings do not support expressions, any existing expressions remain in the iBOLT V2.5 expression format. You must use either environment variables or fixed values in these fields.
-
Step ID is no longer displayed in Magic xpi and the option of displaying the Step ID has been removed. The steps in a certain branch are now executed according to their displayed order in the branch, from left to right. After migration, you may experience a change in behavior. You need to check the Step ID order in your older version and make any necessary changes.
-
If you migrate your project from an earlier version that did not contain a specific component, the component will not be available in your migrated project even after the migration process. You will need to add the component manually.
-
The SAP Business One, SAP ERP, Salesforce, JD Edwards Enterprise One, and Notes DB components require reconfiguration, since the location of the created schema files was changed from the ifclib directory to the project directory. Click the Configuration button and then click OK to save changes.
-
The Salesforce component’s Operation Success was changed from numeric in iBOLT V2.5 to logical in Magic xpi. You need to select a logical variable type for the Success property after migration.
-
For Directory Scanner steps, you have to manually change the expression to check if it is NULL instead of an empty string. This is due to a change in behavior. Up until V3.1 SP1, when there was no file to process, the step returned an empty string. In V3.1 SP1, the step returns NULL.
-
If you want to rename a project that you migrated from iBOLT V2.5 to Magic xpi, you must save the project using the original project name before renaming.
-
From the Project menu, select IFS Settings to open the IFS Settings dialog box. Make sure that the value contained in the Assigned License Threads field is the same as the value defined in the Magic xpi Server Settings dialog box.
-
Run the Checker on the entire project to find any possible problems, including Data Mappers that did not complete the migration successfully.
