Creating a Remote Trading Partner

View fields for S/MIME, AS1, AS2, AS3, RosettaNet and OFTP

Field	Definition
Identification criteria
Alias	Enter a name for the Trading Partner object to use for local identification operations. The name must be unique. Gateway stores this alias as part of the data of each Transfer Request. You can use the alias as a substitute for the partner name parameter when depositing Transfer Requests.
Format	This field displays the protocol format that you selected when creating the new Trading Partner.
Local Partner	Do not select this option.
Name/Email	For S/MIME or AS1, enter an email address. For other protocols, enter a unique name for the Trading Partner object. Maximum: 128 characters.
Comments	Optional Enter a free-text description of the Remote Trading Partner object. Maximum: 80 alphanumeric characters. This description is included in the displayed list of available Trading Partners.
Certificate/Key The fields displayed depend on the type of partner and the selected options.
Use dual certificates	Click this button to toggle between the use of single or dual certificates. The effect of this button varies according to the context: If you: select Use dual certificates: An encryption certificate is used to encrypt what is sent, and a signing certificate is used to check the signature of what is received. do not select Use dual certificates: A single certificate is used to encrypt what is sent, and to check the signature of what is received.
Certificate: Type	This field is visible when you do not select the Use dual certificates button. Select a single certificate type to handle both outgoing and incoming messages: None Secs alias: local Axway Gateway PKI PassPort PS entity: for use with the PassPort PS server. Refer to the Axway PassPort documentation for details. PassPort PS certificate: for use with the PassPort PS server. Refer to the Axway PassPort documentation for details.
Certificate: Name	This field is visible when you do not select the Use dual certificates button. Enter the name of the certificate to be used to handle both outgoing and incoming messages.
Certificate: Key password	This field is visible when you do not select the Use dual certificates button. Enter the password of the certificate key to be used to handle both outgoing and incoming messages. This parameter is not available if you select SECS ALIAS as the Certificate Type.
Signing certificate: Type	This field is visible when you select the Use dual certificates button. Select a certificate type for message signing: None Secs alias: local Axway Gateway PKI PassPort PS entity: for use with the PassPort PS server. Refer to the Axway PassPort documentation for details. PassPort PS certificate: for use with the PassPort PS server. Refer to the Axway PassPort documentation for details.
Signing certificate: Name	This field is visible when you select the Use dual certificates button. Enter the name of the certificate to use for signing.
Signing certificate: Key password	This field is visible when you select the Use dual certificates button. Enter the password for signing certificate key use. This parameter is not available if you select SECS ALIAS as the Signing Certificate Type.
Encryption certificate: Type	This field is visible when you select the Use dual certificates button. Select a certificate type for message encryption or decryption: None Secs alias: local Axway Gateway PKI PassPort PS entity: for use with the PassPort PS server. Refer to the Axway PassPort documentation for details. PassPort PS certificate: for use with the PassPort PS server. Refer to the Axway PassPort documentation for details.
Encryption certificate: Name	This field is visible when you select the Use dual certificates button. Enter the name of the certificate to use for the encryption of sent messages.
Encryption certificate: Key password	This field is visible when you select the Use dual certificates button. Enter the password for the use of the certificate to be used for the encryption of sent messages. This parameter is not available if you select SECS ALIAS as the Encryption Certificate Type.
Encryption algo	This field is visible when you select any option other than none from the Encryption certificate: Type field. Select the algorithm to use for message and/or acknowledgement encryption: AES128 (default) AES256 DES 3DES
Key encryption algo	This field is visible when you select any option other than none from the Encryption certificate: Type field. The only available value for this field is: RSA (default)
Use Multiple Certificates	Only if you are using PassPort PS Select this option to use multiple certificates. Refer to the Axway PassPort documentation for details.
Default parameters for file sending These fields are active only when you are creating or modifying a remote Trading Partner object (Local Partner checkbox unselected)
Associated originator Partner	Either: Enter the originator partner to use when sending a file, or Select a partner from the drop-down list
Default outgoing Site	Either: Enter a default outgoing Site name, or Select a Site name from the drop-down list The Site must be an existing Site on your local Axway Gateway. When you send a file to a remote exchange partner, the remote partner uses this value to process the sent message.
Remote directory (url complement)	Not available for all types of partner Specify: For AS2, the URL path of the directory where the remote exchange partner stores received data For AS3, the directory where the remote partner stores received data Your remote destination exchange partner must provide you with this information. This parameter is only significant when the remote exchange partner is operating as a server.
Requested services: Encrypt file	Select this option to activate encryption.
Requested services: Sign file	Select this option to activate message signing.
Requested services: Compress file	Select this option to activate message compression. If you select this option, select a compression algorithm in the Compression algo field.
Requested services: Compression algo	If you select the Compress file option, select a compression algorithm from the drop-down list.
Requested services: Request receipt	Specify whether or not you want to receive a receipt on reception of a file you send. If you choose to receive a receipt, specify whether the receipt is signed or unsigned. Enter one of the following values: None = no receipt requested (default) Signed = request signed receipt Unsigned = request unsigned receipt If you select either the Signed or Unsigned values for this option, enter a receipt reception address in the Receipt url/email field.
Requested services: Synchronize receipt	Only for AS2. Specify whether or not you want to synchronize receipt delivery: selected: your remote partner returns a reception acknowledgement immediately on file reception and unpacking not selected: your remote partner returns a reception acknowledgement in a protocol session independent of the original transfer session
Requested services: Receipt url/email	Not available for the S/MIME protocol. If you choose to receive receipts of sent messages, specify the address to which the receiving partner sends the receipt.
Parameters for file reception These fields are active only when you are creating or modifying a remote Trading Partner object (Local Partner checkbox unselected)
Force signed	Select this option to specify that you want Gateway to require message signing on reception. If you request signing by selecting the Sign file option above, you should also activate this function.
Force encrypted	Select this option to specify that you want Gateway to require message encryption as criteria for reception. If you request encryption by selecting the Encrypt file option above, you should also activate this function.
Force receipt requested	Specify whether or not you want Gateway to require receipt requests on reception. Select one of the following values: Undefined = Do not require a receipt request (default) None = Ensure that no receipt is requested. Gateway rejects messages with receipt requests Signed = Ensure that a signed receipt is requested. Gateway only accepts messages with requests for signed receipts Unsigned = Ensure that a unsigned receipt is requested. Gateway only accepts messages with requests for unsigned receipts
Force receipt url/email	If you enter an address as a value for this parameter, Gateway checks to confirm that the receipt return path specified in the incoming message is the same. If the check fails, Gateway rejects the message.
Advanced parameters...: Local file location for encoding/decoding Click the Advanced... button to display the following two fields. These fields enable you to specify the directory and name format of the file where transfers are processed for encoding (outgoing files) and decoding (incoming files). You may want to specify a secure directory for this file, keeping in mind that the files that are decoded in this directory can be read by malicious intruders. If you do not specify a directory, Gateway creates the files in <Gateway install directory>\runtime\tmp
Directory path	Enter the local physical path of the directory where transferred files are encoded and decoded.
File name pattern	Enter a specific file name format to enable you to identify the transferred file in the specified out directory.

Creating a Remote Trading Partner

About the Gateway Remote Trading Partner object

Gateway GUI procedure

Gateway command line procedure