Migrating from Sterling B2B Integrator to Global Mailbox

Plan the migration of mailboxes and permissions from traditional mailboxes to Global Mailbox to coordinate the activities in Sterling B2B Integrator and in Global Mailbox.

The flow of migration from Sterling B2B Integrator to Global Mailbox involves the following major steps:
Step Where performed
Plan the migration and create a worksheet. Global Mailbox
Create an export file by using the Resource Manager or command line script. Sterling B2B Integrator
Review the exported files to verify the results. Resolve conditions that caused warnings. Sterling B2B Integrator
Use the Global Mailbox importUtility script in the target system to import mailboxes, permissions, and event rules according to your plan. Global Mailbox
Review the imported resources in Global Mailbox to verify the results. Global Mailbox
Use the Global Mailbox importUtility script in the target system to import virtual roots, which enables the trading partners in Global Mailbox. Global Mailbox
Migrate the messages from the migrated mailboxes. Sterling B2B Integrator
Verify the migration. Global Mailbox
Clean up mailboxes that are no longer active. Sterling B2B Integrator

When you create the export file, if you choose an import option that includes mailboxes and permissions, the system parses the export file and creates the necessary mailboxes and permissions on the target Global Mailbox system.

You can choose from the following modes of mailbox import:
Create Only
Create new mailbox only if it does not exist already. Mailbox import fails if the leaf mailbox already exists without applying any permissions anywhere in the mailbox path. If the leaf mailbox does not exist, it and any other missing mailboxes in the exported path are created and permissions within the export file are applied to existing and created mailboxes.
Merge
Create new mailbox if it does not exist already or merge permission records from export file with existing mailbox. Any mailbox in the path that does not exist is created and permissions within the export file are applied to existing and created mailboxes.
Overwrite
Same treatment for mailboxes as merge, but with different treatment for event rules.
Importing permissions is the same for all import modes, with the following results:
  • If the export file includes permissions for user U on mailbox M, then any existing permissions U has on M are removed and replaced with what is in the export file.
  • If other users have permissions on M and the user is not included in the exported permissions for M, then those user permissions on M remain unchanged.

Application data validation can be optionally enabled for an import operation. When enabled, the importer validates data elements within the import file that reference objects maintained by the application rather than by Global Mailbox.