Export and Import Resources

About this task

If you want to use the same configurations of partners, communities, partner groups, routing channels, routing channel templates, or custom file layers in multiple Sterling File Gateway installations, you can create them in one installation, export them from there, and import them into other installations. This is useful for first creating a test system and then moving the successful configurations to a production system.

It is a good practice to fully implement Sterling File Gateway in a test environment. You can configure the required resources, test to confirm that everything is functioning as you require, and then move to a production environment. You may want to use a staging environment as another step in the process.

Procedure

  1. To export and import from Sterling File Gateway, select Tools > B2B Console > Deployment > Resource Manager > Resource Tags.
  2. Search for or select from the list the resource tag name (same as the community name). When selecting a large number of resources to associate with a resource tag, you may need to use the Tab key three times to view the Finish button.
  3. Click Edit next to the Resource Tag.
  4. Edit the community resource tag to add partner groups, routing channel templates, custom file layers, routing channels, business processes, maps, service configurations, SSH resources, and any other relevant resources.
  5. Select from the following according to your needs:
    • Accounts (if created outside regular partner creation)
    • Service Configurations
    • Digital Certificates
    • SSH Resources
    • PGP Profiles
    • PGP Secret Keys
    • PGP Public Keys
      Note:
      • If you use the command line for import/export of PGP Secret/Public Keys, you must add a passphrase in security.properties or customer_overrides.property files.
      • When you export a secret key, which is a subkey, then the system also exports its corresponding master key.
    • Perimeter Servers
    • Business Processes (if created for dynamic routing channel templates, custom file layers, or other extensibility)
    • Schedules
    • Mailboxes (if created outside regular partner creation or regular routing channel creation)
    • Maps (if created for extensibility)
  6. Select File Gateway Configurations to access selections of the following:
    • Routing Channel Templates
    • Consumer Custom File Layers
    • Producer Custom File Layers
    • Partner Groups
    • Routing Channels
    Note: A partner group is the only Sterling File Gateway object that is updated upon import. All other Sterling File Gateway objects are not updated, regardless of the specification for the “Update Existing Object” value. To update any File Gateway object other than a group on the target system upon import, you must first delete it from target system.
  7. Continue through the wizard, using the right and left arrows to select the components to include in the resource tag.
  8. Click Finish to confirm the edits to the resource tag.
    Note: When selecting a large number of resources to associate with a resource tag, you may need to use the Tab key three times to view the Finish button.
  9. From the Administration menu, select Deployment > Resource Manager > Import/Export.
  10. Click Go! next to Export Resources.
  11. Choose XML Document for the type of format.
  12. Select Yes for tag name.
  13. Choose the resource tag with the name of the community name you want to export from the list.
  14. Select whether to export private certificates.
  15. Click Finish to confirm the report. The export file is created. Examine the export report to confirm that there are no errors.
  16. Save the export file to an accessible directory.
  17. In the target system, import the resources by selecting Tools > B2B Console > Deployment > Resource Manager > Import/Export.

    When importing a community, a page is presented for each kind of resource in the export file. Choose all the objects for each kind of resource so all objects are imported. You cannot specify individual partners for import; all the partners in the exported community are imported at once. Do not change the name of the resource tag. When importing routing rules, do not import any routing rules with a suffix of "_AFTRouter".

  18. After importing, review the Import Report to verify a status of Success for each resource. Correct any conditions noted in the report that did not result in success.