Exporting resources to migrate to Global Mailbox
To enable trading partners in Global Mailbox, export trading partner resources to an export file, then import that file into Global Mailbox.
Remove access to traditional mailboxes that are going to be migrated, so that no operations are pending.
To export records for migration to Global Mailbox:
- From the Sterling B2B Integrator Administration menu, select .
- Start the Export wizard.
- For Output Format Type, choose XML Document.
- For Resource Group, choose No.
- For Export Type, choose Standard.
Consulting the migration worksheet, select the Mailboxes resource, and
the following subtypes:
- Mailbox Metadata
- Mailbox Routing Rules
- Mailbox Virtual Roots
- On the Resource Selection pages for Mailbox Metadata, Mailbox Routing Rules, and Mailbox Virtual Roots, select the resources identified on the planning worksheet.
Do not select Skip Users and Groups from Mailbox export if you want to
Important: Consider the following behaviors when selecting resources for export:
- Mailboxes associated with exported virtual roots and routing rules are exported, along with permissions, even if the mailboxes are not explicitly selected.
- Routing rules that are manually executed in Sterling B2B Integrator are imported, but not enabled, as Global Mailbox event rules.
- If intermediate mailboxes are not explicitly selected for export, the Global Mailbox import tool creates the intermediate mailboxes without any permissions.
- Group permissions are not supported.
To include all information about the export process, select Show Verbose
Warnings on the Mailbox Metadata Selection page.
Tip: Turn on system logging to see more detailed verbose warnings in the system log with longer lists of involved resource names.
- Review the selected resources in the wizard confirmation page.
- Confirm the export.
Download the export xml and export report.
The export report contains the following information:
- High-level summary of what will be moved to Global Mailbox, including what mailboxes or trading partners were selected to be migrated
- Errors - things that might prevent a successful migration and must be fixed manually
If you selected Show Verbose Warnings, the report contains warnings for
suspicious or missing resources that might prevent successful migration, including the following
Tip: In the export report there is a limit of one line item per resource per routing rule. Within that line item, there is a limit of 3 example offenses, in a comma separated list. If there are more than 3 offenses of that rule for that resource, then all the warnings are not shown in the report. Details are in the system log. An example is the following the system log entry:
- Mailbox has virtual roots for users [...] that were not exported.
- Users [...] have this permission but virtual roots were not exported.
- Routing rules [...] of this mailbox were not exported.
- Child mailboxes [...] were not exported.
- Skipping users and permissions for all mailboxes.
- Routing rule matches all mailboxes, will have different results depending on mailboxes in environment.
- Mailboxes [...] of this rule were not selected but were automatically exported.
datestamp... W Mailbox /myMbx: Exported mailbox has non exported virtual root for users [userA,userB,userC,userD,userE,userF,userG,userH,userI,userJ,userK,userL,userM,userN,userO]
- Review the report for errors.
Correct the errors.
Important: Do not edit the export file. Correct the errors in the source system and perform the export steps again.
- Redo the export until it is correct.