Owner's Manual

44 Installation
Basic Network Considerations
This application communicates with devices over a network. In fact, you must be connected to a
network for Application Server to start successfully. Firewalls, or programs using the same ports on
the same machine where this application is installed can interfere with its ability to communicate
with devices. See Ports Used on page 35.
Your corporate network may have barriers to communication with this software that are outside the
scope of these instructions. Consult with your network administrator to ensure this application has
access to the devices you want to manage with the Protocols described below.
NOTE:
One simple way to check connectivity with a device is to open a command shell with Start -> Run cmd .
Then, type ping [device IP address] at the command line. If the device responds, it is
connected to the network. If not, consult your network administrator to correct this. No useful
information comes from disconnected devices.
Name Resolution
If you have server and client on different machines, this application requires resolution of
equipment names, whether by host files or domain name system (DNS). The Application Server
cannot respond to clients based on its IP address alone. It may be on a different network and
therefore the client would be unable to connect.
Whether it uses the
OWARE.CONTEXT.SERVER URL 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®. 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
CAUTION:
This software does not support installation to anything but the local file system. Avoid installing to shared
drives.
Protocols
This application uses the following protocols: TCP/IP, SNMP, HTTP, UDP Multicast. You can
bypass multicast, if it is disabled on your network. To allow a client to connect without multicast,
add the following property to the client’s
owareapps\installprops\lib\installed.properties file.
OWARE.CONTEXT.SERVER.URL=jnp://[HostName]:1099