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:

Configuration file

Location on Linux platform

Location on Windows platform

 

 

 

services.cfg

/etc/opt/fse

%InstallPath%\etc

 

 

 

omniORB.cfg

/etc/opt/fse

%InstallPath%\etc

 

 

 

NOTE: Depending on the network type used for interprocess communication in your FSE implementation (ordinary LAN, private network), omniORB.cfg may not be present in the specified directory. You can always find its template in the directory /opt/fse/newconfig (on Linux systems) or %InstallPath%\newconfig (on Windows systems) and copy the file to its target location, if needed.

You can also change the default path where FSE searches for the omniORB.cfg file using the OMNIORB_CONFIG environment variable.

The reconfiguration procedure

The general procedure for reconfiguring interprocess communication is as follows:

1.Stop all FSE processes with the fse --stopcommand.

Note that you must first stop the processes on external FSE clients, and then stop the processes on a consolidated FSE system or on the FSE server.

2.Stop the omniNames service with the omniNames --stopcommand.

3.Purge the omniNames (CORBA) service data files. Their location is platform-dependent. Linux specific

On Linux platform, omniNames service data files are located in the directory

/var/opt/fse/omniorb. Windows specific

On Windows platform, omniNames service data files are located in the directory

%InstallPath%\var\omniorb.

4.Modify the services.cfg or omniORB.cfg file on all FSE hosts according to the changes in your FSE implementation or changes of the network type employed. The required modifications are described in the following sections.

You can use the FSE proprietary fse_net tool to retrieve the parameters required for the configuration. For more information on fse_net, see ”FSE troubleshooting tools” on page 274.

84 Configuring FSE