Creating a Local Trading Partner

About the Gateway Local Partner object

Gateway GUI procedure

Gateway command line procedure

About the Gateway Local Partner object

In the Local Trading Partner object you specify local identification information.

You use this information to communicate with remote partners.

Gateway GUI procedure

  1. In the left pane of the Gateway Navigator main window, click to expand the Partner Management node.
  2. Right-click the Trading Partners sub-node and from the context menu select New.
  3. From the context menu, select the type of partner.
    4. ClosedView available partner types
    • SMIME partner
    • AS1 partner
    • AS2 partner
    • AS3 partner
    • RosettaNet partner
    • SWIFTNet partner
    • OFTP partner (for OFTP R2.0 security services)
  4. When you select a partner type, Gateway displays the Local Trading Partner properties window. The parameters displayed depend on the type of partner (protocol).
  5. Complete the fields of the Trading Partner window.
    6. ClosedView 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

    Select this option (local Trading Partner object).

    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 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 are creating a local partner and you...

      • select Use dual certificates:
        A signing certificate is used to sign what is sent, and an encryption certificate is used to decrypt what is received.
      • do not select Use dual certificates:
        A single certificate is used to sign what is sent, and is used to decrypt 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 algo

    This field is visible when you select any option other than none from the Certificate: Type field.

    Select the algorithm to use for signing:

    • SHA1 with RSA (default)
    • MD5 with RSA

    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.

    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.
  6. Click OK.
  7. Gateway creates a new Trading Partner object with the specified characteristics.

Gateway command line procedure

To create a Local Trading Partner object via the command line, use the peladm create_tradepart command.

For details of command line use, refer to the Axway Gateway online documentation.