Communication profiles

A communication profile contains the technical details for making connections between clients and servers to transfer data. The two types of profiles are based on the roles of senders and receivers in file transfers.

• A server communication profile contains details for a client to transfer data, via a protocol, to either a sender or a receiver acting as a server.
  • The sender acts as a server when it publishes files for the receiver.
  • The receiver acts as a server when it receives files pushed by the sender.
• A client communication profile contains details for the sender or receiver to connect via a protocol to the server.
  • The sender acts as client when it pushes files to the receiver.
  • The receiver acts as a client when it pulls files from the sender.

PeSIT requires communication profiles for acknowledgments to enable sending receipts (ACKs) when requested. Note that you cannot use a PeSIT login for an acknowledgment that differs from the one used in the source server communication profile definition. The same is true for a certificate for an acknowledgment, meaning that the certificate you use must be the same as the one in the source server communication profile.

Therefore, you should use the same values on both the server and client communication profiles. If there is a difference, however, then the client communication profile values are used.

Communication profiles are used in flow segments between source and target, source and relay, relay and relay, and relay and target. The user interface prompts when communication profiles are required.

Registered products and partners own server communication profiles. The following section describes how to view the communication profiles of these objects.

Products

Click Products on the top toolbar, click the name of a product and click Configuration.

SecureTransport profiles are listed under Server Communication Profiles.

Transfer CFT profiles are listed under Network > Server communication profiles or Client communication profiles.

Partners

Select Partners on the top toolbar and click the name of a partner. The profiles are listed under Server Communication Profiles.

Applications do not own communication profiles. They inherit the profiles of their associated products.

Note

Communication profiles are not deployed to Transfer CFT until they are deployed in a flow.