Migrate Communities, Partner Groups, and Partners with Sterling File Gateway Community Resource Tag

After you migrate Custom Protocols, you can migrate the rest of the Sterling File Gateway resources. The Community Resource Tag maintained by the user interface only contains the Community and all of the Partners in that Community. The Communities and Partner Groups that Partners belong to must exist on the target system before you migrate the Partners. You can add the Partner Groups to the Community Resource Tag to migrate the Community, Partner Groups, and Partners in one Resource File. If you add the Partner Groups to the Resource File, the target system imports the resources in the correct order.

Process

To use the Community Resource Tag to migrate the Community, Partners, and Partner Groups:
  1. Edit the Community Resource Tag to add the Partner Groups to the Community Resource Tag.
  2. Use the Community Resource Tag to create a Resource File.
  3. Check the Export Log to be sure there are no errors.
  4. Copy the Resource File to an accessible directory.
  5. Import the Resource File on the target system.

Guidelines and requirements for using Community Resource Tag

The guidelines for migrating a Sterling File Gateway community include:

Table 1. Guidelines and requirements for migrating by using Community Resource Tags
System Guidelines and requirements
Community Management with the Community Resource Tag

When you use the Sterling File Gateway Community Resource Tag:

  • You need to export and import all resources in that tag.
  • You cannot specify individual partners to import to the target system. With the Community Resource Tag you automatically export and import all Partners in the Community.
Community Resource Tag
The Community Resource Tag is managed by the Sterling File Gateway user interface and is updated when Community and Partner additions or updates are made.
  • Never delete the Resource Tag itself. Recreating a Sterling File Gateway Community Resource Tag requires contacting customer support.
  • Never remove Partners from a Community Resource Tag. If you must remove a Partner, delete the Partner from the Community using the Sterling File Gateway user interface. This automatically removes the Partner from the Community Resource Tag. During an import where you removed a Partner on the source system, the import does not remove the Partner from the target system Community or the target system Resource Tag. After the migration, you must manually remove the Partner from the Community on the target system.

Resource file export

Always examine the Export Report after generating the Resource File to verify that no errors were generated before you continue with the migration. If errors were generated in the Export Report, contact customer support to open a case. Provide the Export Report and the Resource File generated to customer support.

Resource file import

All resources within the resource file must be imported. All resources within the Resource File are required for the import to be successful, even if you are doing a migration to insert new resources into the target system Community and not changing any existing resources. The Import All Resources option automatically selects all resources in the resource file for importing. Always use the Import All Resources option. If you do not use this option, you will be prompted to manually select all of the resources to import for each resource type.

During the import you are asked Some objects being imported may exist in the system. Do you wish to update them? This option can be set to either Yes or No. When you migrate the Communities, the Partner Groups, and Partners for the first time, set this to Yes.

Important: Setting this to Yes causes the Resource File being imported to overwrite all the resources within a Sterling File Gateway Community. All of the resources must participate in the import process. There may be planned differences in configuration for some resources between the source and target systems. For example, the Partner User passwords may differ between the source and target systems.

Always examine the Import Report and verify that no errors were generated. If errors were generated, contact customer support to open a case. Provide the Export Report and the Resource File generated to customer support.