After you install

After installing Sterling File Gateway, there are additional instructions for configuring and using it.

Adjust IBM DB2 settings
For optimal performance, some values in the IBM® DB2® registry may need to be adjusted.
Starting Sterling File Gateway in a Microsoft Windows environment
Sterling File Gateway must be started before use.
Starting Sterling File Gateway in a UNIX or Linux environment
Sterling File Gateway must be started before use.
Accessing Sterling File Gateway
To use Sterling File Gateway, you must first log in.
About export and import
The export and import features enable you to save time and increase the accuracy of duplicating supported resources on different Sterling B2B Integrator or Sterling File Gateway environments that are set up for unique purposes.
Export and Import Resources
Migrate Sterling File Gateway resources
You can migrate Sterling File Gateway resources from one system to another. You may have a staging system where you test new Partners and other resources before you migrate them to a production system. You may want to migrate resources from one software version to another.
Migrate Custom Protocols with Import and Export
Custom Protocols are not Community specific and can be migrated before the Sterling File Gateway Community. The Custom Protocol should not be added to the Community Resource Tag. Because Custom Protocols are custom configurations within the system, the migration steps and the resources migrated will vary between different implementations. Custom Protocol migration is a two-step process because some of the migration is done through the user interface and some is done outside of the user interface.
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.
Migrate Sterling File Gateway configurations
You can use import to create the rest of the Sterling File Gateway configurations, but not to update them. To update these resources with an import, you must delete them on the target system first. Migrate these resources separately from the Community, Partners, and Partner Groups.
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.