Installation Manual

42 Installing FSE software
NOTE: SUSE Linux Enterprise Server 9 (SLES 9) systems only: Do not run YaST2 after you have configured
this FSE host to use a private network for the FSE interprocess communication. Running YaST2 modifies
/etc/hosts in such a way that subsequent FSE system startups will fail.
Alternatively, you can modify /etc/sysconfig/suseconfig by changing the line
CHECK_ETC_HOSTS="yes" to CHECK_ETC_HOSTS="no". You can then run YaST2 without affecting
the FSE system operation, but you cannot modify host names with it.
Configuring communication on external FSE clients
NOTE: This configuration step is mandatory regardless of the platform of the consolidated FSE system or
FSE server.
Ordinary LAN connection
If the external FSE clients and the consolidated FSE system or the FSE server communicate through the
ordinary LAN, you only need to modify the services.cfg file on each external FSE client and comment
out some parameters in the omniORB.cfg file. Do the following:
1. Modify the value of the server variable in services.cfg to include the fully-qualified domain
name (FQDN) of the consolidated FSE system or the FSE server the client is connected to. For example:
2. In the omniORB.cfg file on the external FSE client, verify that all lines in the section
--- Private network parameters --- are inactive (commented out).
Private network connection
If the external FSE clients and the consolidated FSE system or the FSE server communicate through a private
network, you must modify both configuration files, services.cfg and omniORB.cfg, on each external
Linux client. The following procedure includes the necessary modification steps:
1. Modify the value of the server variable in services.cfg to contain the fully-qualified domain
name (FQDN) that identifies the consolidated FSE system or the FSE server inside the private network.
2. Add the hostname variable to services.cfg and provide as its value the FQDN that identifies the
Linux FSE client system inside the private network.
The following is an example of a properly configured services.cfg file in FSE setups using a private
network:
3. In the omniORB.cfg file, configure the parameters in the section
--- Private network parameters --- with the following information:
• the FQDN that identifies the system inside the private network
• the IP address of the system
•the subnet mask
All these parameters must be verified against the actual private network configuration. Ensure that the
FQDN you specify in omniORB.cfg matches the FQDN specified for the hostname variable in the
services.cfg file.
The following example is an excerpt from a properly configured omniORB.cfg file:
server = fse-server1.company.com
hostname = fseclient.fsenet
server = fseserver.fsenet
# --- Private network parameters ---
#
# Which network interface omniORB uses for IORs