Configuring protocols

PEM Partner Repository enables Sponsor Administrators to configure communication adapters to receive and make connections to trading partners for the purpose of transferring files.

The connections can use various internet protocols such FTP, FTPS, or SFTP. Once you verify that you can transfer files, you can add certificate to securely receive or transfer files.

A Sponsor Administrator can create an activity for each protocol such as FTP, FTPS, SFTP, Certificate, or SSH Key associated with test or production. If the same configuration applies to both test and production, the data can be duplicated. The records that are created are stored in PEM Partner Repository. By using this information, PEM Partner Repository partners can send or receive file from the external systems such as Sterling File Gateway.

All the events that are fired between PEM Partner Repository and PEM Partner Provisioner are managed through queues. The configuration data is served through PEM Partner Repository APIs.

PEM Partner Repository supports REST API configuration profiles. The external system, Sterling File Gateway can use the REST APIs to manage the protocol configurations.

To create and manage the configuration data in PEM Partner Repository, the Partner Administrators can select the appropriate protocol and configure it.

Note: The protocol configuration is available only for active partners. If a partner is inactive, you can view the existing protocol configurations but cannot create or update configurations.

PEM Partner Repository supports CRUD and Action REST APIs. CRUD APIs support Create, Read, Update, and Get. The protocol profiles consist of Action APIs that displays the profile status and firing of events. To access the PEM Partner Repository REST API documentation, see Accessing the PEM Partner Repository REST APIs documentation.