Configuring RESTful HTTP or HTTPS exchange profiles

An exchange profile facilitates the exchange of data between a sender organization and a receiver organization. A RESTful HTTP or HTTPS exchange profile facilitates the exchange of data using HTTP or HTTPS as the transport protocol.

An exchange profile also defines the participating organizations (owner organization and trading partner), receivers, destinations, and connections and security settings. A RESTful HTTP or HTTPS exchange profile requires details of the participating organizations, exchange pattern, credential information that is required to authenticate each party with the other, and messaging and RESTful HTTP or HTTPS destinations.

RESTful HTTP or HTTPS inbound push exchange profiles that have a Sterling File Gateway-based trigger do not require a user-configured action to push a file that is received from SFTP to a File Gateway Mailbox. This allows you to integrate directly with existing File Gateway processes.

To enable public-key cryptography and further secure the communications of a RESTful HTTP or HTTPS exchange profile, you can associate a public key with user credentials.

You can import and export exchange profiles to and from AS4 Microservice.