Alternative IP addresses

This section describes how to define additional IP addresses in case the primary host:port pair for the partner server communication profile fails on flows between SecureTransport and a partner. This option is available for FTP, HTTP, SFTP and PESIT partner server communication profiles only (not client communication profiles).

Using the Central Governance REST API for partners, you can define or update a partner server communication profile with an unlimited number of additional host:port entries (called alternative addresses). Add the alternativeAddresses option to the partner request as demonstrated below. If you enter multiple alternative addresses, the position in the list defines the order in which the host:port pairs are tried.

POST /api/v2/partners

{

     "name" : "partner_ftp",

     "communicationProfiles" :  [

         {

        "name": "ftp1",

        "type": "SERVER",

        "protocol": "FTP",

        "enabled": true,

        "enableSSL": false,

        "fipsEnabled": false,

        "securityModes": [

          "EXPLICIT"

        ],

        "connectionModes": [

          "PASSIVE"

        ],

        "hosts": [

          "h2"

        ],

        "port": 2,

        "clientAuthenticationRequired": "Yes",

        "portRange": {

          "from": 1024,

          "to": 65535

"alternativeAddresses":[

  {  

    "host":"10.133.67.98",

    "port":"21",

    "position":"1"

  }

]

    }  

  ]

}

Note To use an HTTP URL instead of host:pair in the alternativeAddresses section, enter the URL as the host value; the port setting is ignored.

Limitations

  • You cannot use the Central Governance UI to manage alternative host:port entries for a partner Server communication profile.
  • You cannot use Central Governance to configure the retry policy; this is handled by SecureTransport.

 

Central Governance | Document Directory

Related Links