search cancel

Firewalls -- Java client cannot connect through firewall

book

Article ID: 90235

calendar_today

Updated On:

Products

CA Automic Applications Manager (AM)

Issue/Introduction

Firewalls -- Java client cannot connect through firewall

Environment

Release: AAMOS499000-8.0-Automic Applications Manager-OS400 Agent
Component:

Resolution

Symptoms

The Applications Manager client cannot communicate with the Applications Manager Master through a firewall.  


Cause

The most common cause is the correct ports not being opened on the firewall.


Resolution

Open the following ports on the firewall:

  • RMIRegistryPortNumber - the default is set to 1099 in the Options.properties file.
  • RMIDataPortNumber - the default is set to 0 in the Options.properties file.

Note: When 0 is entered for the RMIDataPortNumber setting, random ports will be used. When a firewall is present, you must specify an integer above 1 for a port number. Ideally, the port number should be greater than 5000.

If necessary, you can check and change the current settings for the RMI ports in the Options.properties file.

In UNIX, the location of the Options.properties file is:

$AW_HOME/web/classes

In Windows, the location of the Options.properties file is:

%AW_HOME%\web\classes

An AWCOMM port other than the default can be specified in the awenv.ini file in the site directory. The syntax for the entry is AWCOMM_PORT=<port number>. If the default AWCOMM port is used, there will not be an entry in the awenv.ini file.