User's Manual

78 Configuring FSE
Private network connection
If the external (distributed) Linux FSE clients will communicate through a private network to the FSE server,
you must modify both configuration files, services.cfg and omniORB.cfg, on each external Linux
client, as follows:
1. Modify the value of the server variable in services.cfg to contain the fully-qualified domain
name (FQDN) that identifies the consolidated FSE implementation or the FSE server inside the private
network.
2. Add the hostname variable (if not present) to services.cfg and set its value to the FQDN that
identifies the Linux FSE client inside the private network.
The following is an example of a properly configured services.cfg file in FSE implementations
using a private network:
3. Rename the omniORB.cfg backup file (for example, omniORB.bak) back to omniORB.cfg. Modify
the following parameters in the file:
• the FQDN that identifies the consolidated FSE implementation or the FSE server 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 server variable in the
services.cfg file.
The following is an example of a properly configured omniORB.cfg file:
Reconfiguring communication on external Windows FSE clients
Ordinary LAN connection
If the external Windows FSE clients and the consolidated FSE implementation or the FSE server will
communicate through an ordinary LAN, you have to modify the services.cfg file on each external
Windows client, as follows:
hostname = fse-client.fsenet
server = private-server.company.com
# Which interface omniORB uses for IORs
endPoint = giop:tcp:private-server.company.com:
# The order of network interfaces to use for accepting connections:
# Only localhost and private network. Others are denied.
clientTransportRule = localhost tcp
clientTransportRule = 192.168.240.0/255.255.255.0 tcp
clientTransportRule = * none
# The order of network interfaces to use for opening new connections:
# Only localhost and private network. Others are denied.
serverTransportRule = localhost tcp
serverTransportRule = 192.168.240.0/255.255.255.0 tcp
serverTransportRule = * none