Importing into Global Mailbox

If you have resources such as mailboxes, virtual roots, and event rules in an existing system, you can create the same resources in another Global Mailbox. The export file created in the source Sterling B2B Integrator or Global Mailbox system is the import file in the target system.

Before you begin

Obtain an import file to specify in the --importFileName option when the importUtility script is run. This file is produced by either a Global Mailbox export, by using the exportUtility script, or a Sterling B2B Integrator export.

About this task

To import records from a source Sterling B2B Integrator system or a source Global Mailbox system to a target Global Mailbox system:

Procedure

  1. Create a importSelectionFileName properties file with the selection criteria for the individual resources that are to be imported and to supply application name mappings.
  2. Run the importUtility with an action of report, specifying the file created in step 1 as the importSelectionFileName.
    The report file is created with the file name specified as --reportFileName.
  3. Review the report and correct any error or warning conditions.
  4. Repeat step 2 until the results are as intended.
  5. Run the importUtility with an action of import, specifying the file created in step 1 as the importSelectionFileName.
    The target Global Mailbox system is modified to include the resources that are imported.
  6. Validate the results by confirming that the mailboxes, virtual roots, and event rules you imported are in the target Global Mailbox system and are working as intended.
  7. Optionally, if the source system is Sterling B2B Integrator, you can run the MigrateMsgsToGlobalMbx business process to copy messages into Global Mailbox.

Results

The mailboxes, virtual roots, and event rules are operational in the target Global Mailbox.