On the remote administration server, the FT administrator should enter the openFT instances that are to be administered in the partner list. This makes it possible to reference the instances using the names in the partner list, which has the following benefits:
If the address changes, it is only necessary to change the entry in the partner list. This avoids the necessity of modifying and re-importing the configuration file.
It is possible to explicitly use partner checking and authentication, thus eliminating security risks on the path between the remote administration server and the administered openFT instance.
The FT administrator enters the partners in the partner list. To do so, use the command ftaddptn. Alternatively, you can use the openFT Explorer to navigate to the object directory Partner List in the object tree, for instance, and choose New Partner List Entry... from the context menu.
Address format of the partners
Partners using openFT as of V11.0 and openFT < V11.0 have different address formats.
Partners using openFT as of V11.0 must be entered as ADM partners. An ADM partner has the following address format:
ftadm: //host[:port number]port number only needs to be specified if the default ADM port (11000) is not used on the computer host of the instance to be administered.
Partners using openFT < V11.0 must be entered as openFT partners, because the ftexec command is used internally for remote administration:
host[:port number]port number only needs to be specified if the default openFT port (1100) is not used on the computer host of the instance to be administered.
The ADM administrator must additionally specify the attribute Mode="Legacy" in the configuration file for such partners. See the section “Creating a configuration file using a text or XML editor”.