Migrate specific Sterling File Gateway resources

After you initially migrate your Sterling File Gateway resources to a production system, you only need to migrate changed resources. The resources that change most often are Partners. With Partner changes you may have Community, Partner Groups, and Routing Channel changes. Use the System Administrator user interface on Sterling B2B Integrator to select the specific resources to export from one system to another. Only migrate resources that are not already on the target system or that need to be updated on the target system. If the Community and Partner Groups that the Partners belong to already exist on the target system, only migrate the Partners. If the Community or Partner Groups do not exist on the target system, migrate them with the Partners.

In the user interface, you specify specific Partners to export and one or more Communities to export:

Table 1. User interface fields
Field Description
Partner Sterling File Gateway Partners are part of the Sterling File Gateway Configurations. When you create an export file with File Gateway Configurations, you can select Partners as a resource to export and then specify which partners you want to export.
Communities Communities are selected from the top level export page. When you create an export file and you select Communities, you can specify one or more Communities to include in the export file.

You can specify the Partners and Communities that you want to export from one system to another. There are some constraints on what resources must exist on the target system and what resources must be imported with the Partner or Community.

The import process for migrating Partners and Communities without using the Community Resource Tag has these constraints:
Table 2. Constraints on importing Partners and Communities without the Community Resource Tag
When importing a . . . If the . . . Then . . .
Partner Community for the Partner does not already exist on the target system The import will fail. Create or import the necessary Community on the target system, then repeat the Partner import.
Partner Sterling File Gateway Partner Group for the Partner does not already exist on the target system The Partner is imported with a warning in the Import Report that says the Sterling File Gateway Partner Group could not be found. Create or import the necessary Partner Group on the target system, then repeat the Partner import. Select Yes for Some objects being imported may exist in the system. Do you wish to update them? to add the Partner to the Partner groups you created on the target system.
Partner Export file contains one or more Partners You must import everything in the export file to ensure that all dependent objects that the Partner needs are included in the import.
Community Export file contains one or more Communities You must import all resources in the export file to ensure that all dependent objects that the Community needs are included in the import.
Partner Groups Partner Groups contain new Partners for Partner Groups that are already on the target system Select Yes for Some objects being imported may exist in the system. Do you wish to update them? to add the new Partners to the Partner Groups that exist on the target system.
Consumer Custom File Layers, Producer Custom File Layers, Routing Channels, and Routing Channel Templates Consumer Custom File Layers, Producer Custom File Layers, Routing Channels, and Routing Channel Templates already exist on the target system Delete the existing Consumer Custom File Layers, Producer Custom File Layers, Routing Channels, and Routing Channel Templates from the target system before you do the import. These Resources can not be updated. They can only be created. Selecting Yes for Some objects being imported may exist in the system. Do you wish to update them? does not update these resources.