With openFT, you can run several openFT instances at the same time on a single host. These instances allow you to switch to a different computer already running openFT so that you can continue to use the openFT functionality when the initial host fails. You will find examples on how to use openFT in a cluster of Unix or Windows systems in the appendix.
A requirement for this is that openFT uses only the TCP/IP transport system. Other transport systems are not supported in a cluster and must also not be configured in the TNS. As a result, you are recommended to work without TNS and CMX. If you work without CMX then you also automatically work without TNS. In a cluster, the same version of openFT must be running on all the computers.
For systems that do not have TCP/IP there is currently only the standard instance.
openFT commands that call preprocessing, postprocessing or follow-up processing run in the same instance as the request that initiated the pre-, post- or follow-up processing.
If you administer openFT via SNMP, then please note when switching to the cluster that SNMP can only work together with one instance.
The decisive factor is which instance is set when the agent is started see section “openFT instances and cluster operation”.
Command for administering instances
As an openFT administrator you can create, modify and delete instances. You can also set up instances and obtain information on instances.
Creating or activating an instance
Using the command ftcrei, you can create a new instance or re-activate (switch on) a deactivated instance.
When an instance is created, the operating parameters, the profile files, and on Unix systems the startup and shutdown files are initialized as during a new installation.
When an existing instance is activated on Unix systems, the existing instance file tree, with the operational resources of the instance, is linked to the directory /var/openFT.
If you create a new instance and wish to continue using the standard instance std, You must assign the standard instance a separate address in order to avoid address clashes.
Modifying an instance
You can assign a different Internet host name to an instance with the ftmodi command.
Please note:
If you assign the standard instance std a host name, local requests to the address 127.0.0.1 used for test purposes, for instance, are no longer possible.Deactivating an instance
You can deactivate an instance with the ftdeli command. Deactivating an instance in this manner only removes:
the symbolic link in the local /var/openFT directory (Unix systems)
the instance from the openFT instance management (Windows systems)
The instance file tree is not changed.
Setting up an instance
You can select the openFT instance you want to work with using the ftseti command.
The command sets the OPENFTINSTANCE environment variable to the name of the instance.
You can also set up the instance via the openFT Explorer. As soon as there is more than one instance, then a list appears in the tool bar of the openFT Explorer from which you select the instance.
The list box is only displayed if the instance is already present when the openFT Explorer is started. If the instance is created after the start of the openFT Explorer then this must be restarted.Outputting information on instances
You can query information on the instances using the ftshwi command.
Updating an instance file tree
Using the ftupdi command, you can modify the instance file tree of an older version of openFT for use in the current version. That is only necessary for instances that were not active at the time of an update installation.
If you work with more than one instance on a Unix system, then in this case a separate ftalarm call is required for each instance.
Please consider also the section “Note on the ftalarm function in single-usermode”.
You will find detailed descriptions of the ftcrei, ftmodi, ftupdi and ftdeli commands in the manual "openFT (Unix and Windows systems) - Command Interface".
Startup and shutdown file (Unix systems)
In openFT on Linux, HP-UX and AIX, there is one global startup and shutdown file that operates on all instances. In addition, every instance present also has its own startup and shutdown file.
During a system startup / shutdown, the global startup and shutdown file is called. This file then calls the startup and shutdown files of all openFT instances.
Global startup and shutdown file:
It is set up under /etc/init.d (Linux) or in a corresponding directory on an other Unix platform during the installation of openFT. This startup and shutdown file calls the startup and shutdown files of all instances when the system is started or when it is shut down.
Startup and shutdown file specific to one instance:
The startup and shutdown file openFTinst is created in the /var/openFT/std/etcinit directory for the std instance during the installation of openFT.
If you create another instance with frcrei, then a startup and shutdown file openFTinst is also set up for this instance. This file is located in the directory etcinit of the openFT instance tree.
On Solaris, automatic stop/start is performed via manifests. A manifest is automatically generated for each instance.