Create a Physical Partner using CAPI Mode

Edit online

You can create a Physical Partner entry as part of the partner profile using the CAPI mode in Sterling B2B Integrator.

Procedure

  1. From the Administration menu, select Trading Partner > Odette FTP Partner Profile > Odette FTP Physical Partner.
  2. Click Go! next to Create Odette FTP Physical Partner.
  3. In the Physical Partner page, complete the following fields and click Next:

    Field Name

    Description

    Physical Partner Name

    Required. Unique name for the Physical Partner.

    Description

    Required. Textual description of the Physical Partner.

    OFTP User Id

    Required. The OFTP ID used in the SSID command. Must be defined in the bilateral agreement with your partner.

    OFTP User Password

    Required. The OFTP password used in the SSID command. Must be defined in the bilateral agreement with your partner.

    In the Sterling B2B Integrator User Interface, the password is encrypted automatically when the profile is saved.

    Mailbox User

    Optional. User name in the Sterling B2B Integrator Mailbox system. The value of this field determines whether the Mailbox Mode is used or not. It is recommended to use the Mailbox Mode.

    Select [None] if you do not want to use the Sterling B2B Integrator Mailbox System. If [None] is selected, the following fields are disabled:
    • Submailbox
    • Extractability Type
    • Extractability Value

    Select a Sterling B2B Integrator user, which is tied to a Mailbox in a Mailbox Virtual Root to use the Mailbox Mode.

    Note: Sterling B2B Integrator Mailbox System requires a separate license.

    Submailbox

    Required for Mailbox Mode.

    Default messages received from your Remote Partner B on your local system (Local Partner A) are saved in the virtual root of Partner Mailbox B (created on the local System A).

    To make message routing simpler, you can specify a submailbox name in the Remote Physical Partner of system A so that inbound messages from Partner B are placed in a submailbox <name> of local Partner Mailbox B.

    Extractability Type

    Required for Mailbox Mode.

    The Mailbox Extractability Type defines the following ways to extract messages from Partner Mailboxes:
    • Extractable, unlimited (Yes/No). Either extraction of messages is forbidden (No) or allowed (Yes) without limitation.
    • Extractable Count (number). Extraction of messages is allowed <Count> times.
    • Extractable Until (YYMMTTHHmmss). Extraction of messages is allowed until a specified data/time stamp.

    Extractability Value

    Required for Mailbox Mode. The value for the extractability type selected in the Extractability Type field. The default value is Yes.

    Leave blank if the message cannot be extracted.

    Depending on the selection in Mailbox Extractability Type, specify an Extractability Value as follows:
    • No = Extraction of messages is forbidden
    • Yes = Extraction of messages is allowed without limitation

    Session Retry Intervals

    Optional. Comma separated list of numbers that indicate the time interval when a subsequent session will retry, if there was a failure.

    SSID User Field

    Optional. Defined in your bilateral agreement.

    Authorization Private Key

    Required, if you select Secure Authentication check box of Secure Authentication in Physical Partner Contract. Available for Odette API Level 2.0 and higher.

    CAPI Mode

    Select CAPI Mode if you want a communication link over an ISDN telephone line. You need an ISDN router hardware with Remote CAPI (Brick).
  4. In the Authentication Certificates page, use the arrows to move the certificates in the Available Certificates list to the Selected Certificates list. You can select one or more Authentication Certificate. Available for Odette API Level 2.0 and higher.
  5. Click Next.
  6. In the CAPI Parameters page, complete the following fields and click Next:

    Field Name

    Description

    Address

    Required. The telephone number that either you or your partner calls.

    Sub Address

    Optional. Additional address part.

    Alternative Addresses

    Optional. Comma separated list of alternative addresses (telephone numbers). List of alternative addresses (in case of a remote physical partner).

    B3 Channel Configuration
    Optional. Comma separated list of B3 channel configuration parameters containing six integer values in the following order:
    • LIC - Lowest incoming channel. Default is 0.
    • HIC - Highest incoming channel. Default is 0.
    • LTC - Lowest two-way channel. Default is 1.
    • HTC - Highest two-way channel. Default is 1.
    • LOC - Lowest outgoing channel. Default is 0.
    • HOC - Highest outgoing channel. Default is 0.

    B Window Size

    Optional. Transmit and receive window size for B -Channel. Default is 7.

    Call User Data

    Optional. X.25 parameters, entered as HEX String. Default is 0.

    Facilities

    Optional. X.25 parameters, entered as HEX String. Default is 0.

    Local NUA

    Optional. Local X.121 address used to call.

    Remote NUA

    Optional. Remote X.121 address used to call.

    Modulo
    Send and Receive sequence number counter in X.25 packet. Valid values are:
    • 8 - normal operation (default)
    • 128 - extended operation
  7. Review the profile settings in the Confirm page.
  8. Click Finish.