Configuring custom protocol

In addition to the preconfigured protocols in Sterling File Gateway, a system administrator of Sterling File Gateway can add support of custom protocols for listening consumers. To onboard partners that use custom protocols in Sterling File Gateway, custom protocol configuration in PEM Partner Repository can be used.

Custom protocol configurations in Sterling File Gateway contain extensions and their values. To onboard partners in Sterling File Gateway by using IBM PEM, these extensions must be replicated as fields in custom protocol configurations of the PEM Partner Repository.

For every partner that needs to be on-boarded in Sterling File Gateway, the corresponding partner in IBM PEM must have the following configurations:
  1. A custom protocol configuration in PEM Partner Repository.
  2. The custom protocol extensions in Sterling File Gateway must be created as fields for this custom protocol configuration in PEM Partner Repository.

If a custom protocol configuration in Sterling File Gateway has multiple extensions, each such extension must be created as a separate field in a custom protocol configuration in the PEM Partner Repository.

For example, you want to onboard a trading partner P1 in Sterling File Gateway. P1 uses the following custom protocol extensions and the corresponding values in Sterling File Gateway.
  • RemoteHost - 12.34.56.78
  • RemotePort - 5000
  • SystemCert - mysystemcert
  • PartnerCert - ABCCo_cert
You must create a Custom Protocol configuration for partner P1 in PEM Partner Repository and add fields with each of these extensions and their corresponding values.

IBM PEM and PEM Partner Provisioner do not contain any default activity for custom protocols. Sponsors can create their own activities by using the custom protocol configurations and can then roll out these activities to partners.