Installation Manual

40 Installing FSE software
The initial configuration must be performed after the FSE software package installation, before the FSE
implementation is put into operation for the first time. Afterwards, if the implementation or the network type
is changed, the communication settings must be reconfigured.
CAUTION: An appropriate configuration of the FSE interprocess communication is of crucial importance
for normal FSE operation. Incorrectly configured interprocess communication may lead to a non-operating
FSE implementation.
FSE interprocess communication settings consist of two plain text files installed on each FSE host. The files
and their locations are the following:
NOTE: Before configuring the FSE interprocess communication, you may need to manually copy the file
omniORB.cfg from the directory /opt/fse/newconfig to the corresponding location.
You can also change the default path where the FSE software searches for the omniORB.cfg file using the
OMNIORB_CONFIG environment variable.
CAUTION: In the following procedures for configuring a LAN connection, if you reconfigure a system with
several network adapters enabled, you need to configure the parameters in the section
--- Private network parameters --- in the omniORB.cfg file as described in the procedures
for private network communication configuration, instead of commenting them out.
In this case, the parameters you specify in omniORB.cfg must be verified against the actual LAN
configuration for that system.
CAUTION: Configuring communication on a consolidated FSE system or an FSE server
NOTE: You can use the fse_net command to test the connection between external FSE clients and the
FSE server. Details are given in the FSE user guide, chapter ”Troubleshooting”.
No external FSE clients or ordinary LAN connection
If your FSE set-up includes only a consolidated FSE system and you do not plan to connect external clients
to it, or if your external FSE clients are connected to the consolidated FSE system or the FSE server through
ordinary LAN, you do not need to modify the default configuration of the services.cfg file. Instead,
perform the following:
1. In the omniORB.cfg file on the consolidated FSE system or the FSE server, verify that all lines in the
section --- Private network parameters --- are inactive (commented out).
Private network connection
If your external FSE clients use a private network for communication with the consolidated FSE system or the
FSE server, you must make the following modifications to the consolidated FSE system or to the FSE server:
1. Add the hostname variable to services.cfg and provide as its value the fully-qualified domain
name (FQDN) that identifies the system inside the private network.
Configuration file Location
services.cfg /etc/opt/fse
omniORB.cfg /etc/opt/fse