Importing the migration package

After you validate a package and there are no invalid (red) objects, you are ready to import. The import might take some time to process.

About this task

The Object Migration Agent must be running for the import processing to occur.

When you click Import, the platform adds a message in the Objects panel that indicates that the import is started.

Note: You can also click Import Non-Conflicting to import new objects and objects with non-conflicting object labels only. If an object has a conflicting object label, or an object is not new but is not supported by object labels, then the object will not be imported. Be aware that this process can potentially put your environment in an incomplete upgraded state as necessary objects may not be imported.

You receive a notification in your portal Home page when the import is complete. The status also displays in the Import Packages section of the Object Migration screen.

If the package is configured to automatically run a particular workflow, it runs when the import process completes. You optionally specify a workflow to run at import completion when you create the package in the source IBM TRIRIGA Application Platform environment.

In the import package, you can deselect the workflow that was set in the export, but you cannot select other workflows in the package. When the workflow runs upon the completion of the import, a record is created based on several rules.
  • If the workflow is defined on a business object, then a record of that business object is created.
  • If the workflow is not defined on a business object, then a record is created of the base business object of the module.
  • If the workflow is not defined on a business object and the module does not have a base business object, the run fails and therefore, the import fails.
The empty record is created for workflow debug purposes. If the workflow instance is turned on, you can view the workflow instances through the empty record.