Name Resolution

If you have server and client on different machines, Redcell requires name resolution, whether by host files or domain name system (DNS). The Application Server cannot respond to clients based on its IP address alone (since a host may be on a different network and therefore the client would be unable to connect).

Whether it uses the OWARE.CONTEXT.SERVER URL (see Client Failover) or not, when a client connects to the Application Server it receives a stub with the real URL used to communicate with RMI. This stub always returns a URL with the host name, if available.

If your network does not have DNS, you can also assign hostnames in %windir%\system32\drivers\etc\hosts on Windows®. On Linux or Solaris, the hosts file is located in /etc. You must assign a hostname in addition to an IP address in that file. Here are some example hosts file contents (including two commented lines where you would have to remove the # sign to make them effective):

# 102.54.94.97 rhino.acme.com # source server

# 38.25.63.10 x.acme.com # x client host

127.0.0.1 localhost:

The following might appear in a host file for a distributed installation:

# Do not remove the following line, or various programs

# that require network functionality will fail.

127.0.0.1 localhost.localdomain localhost

192.168.1.174 fairtex #application server

192.168.1.175 tapout # mediation server

192.168.1.176 form # remote client 1

192.168.1.177 punish # remote client 2

If a successful hostname resolution is not available to the application server, the following error may appear in the server.log at startup.

ERROR [org.jboss.invocation.http.server.HttpInvoker] (main:jboss:service=invoker,type=http HttpInvoker) Starting failed jboss:service=invoker,type=http

java.net.UnknownHostException:

Refer to your operating system’s documentation for more about configuring the hosts file.

[spacer]

This software does not support installation to anything but the local file system. Avoid installing to shared drives.