Security/Firewall Requirements: Ports To Be Opened When Monitors Are Behind The Firewall

Security/Firewall Requirements
This section explains how the Applications Manager can be accessed

behind a firewall. Fire walls act as barriers preventing unauthorized
access to a network. They act as entrance through which authorized
people may pass and others not.
You need to configure the firewall so that the host on which

Applications Manager runs, can access the monitor at the relevant
port.
Ports to be opened when Monitors are behind the firewall:
Monitors Port Details

WMI Mode of monitoring:
Windows Management Instrumentation (WMI) --

Port: 445
Remote Procedure Call (RPC) -- Port: 135

Windows
SNMP Mode of monitoring:
SNMP Agent Port: 161

Telnet Port: 23 (if mode of monitoring is Telnet)
Linux / Solaris / AIX
SSH Port: 22 (if mode of monitoring is SSH)
/ HPUnix /Tru64
Unix
SNMP Agent Port: 161 (if mode of monitoring is
SNMP)
Port in which JBoss is running (for eg., 8080) and
JBoss also, the Hostname should be accessible.
RMI Object port (eg., 4444)
WebLogic HTTP Port of WebLogic, for eg., 7001
Oracle Application HTTP Port of Oracle Application Server, for eg.,
Server 7200
Tomcat HTTP Port of Tomcat, for eg., 8080
WebSphere HTTP Port of WebSphere (default:9080)
Oracle HTTP Port of Oracle (default:1521)
DB2 HTTP Port of DB2 (default: 50000)
SQL Server HTTP Port of SQL Server (default:1433)
MySQL Port on which MySQL is running eg., 3306
SMTP Server port: 25 (default), to send mails from
Mail Server
Applications Manager
Exchange Server HTTP Port of Exchange Server (default:25)
Web Server -
HTTP Port of Web Server (default:80)
Apache / IIS / PHP
HTTP Port of JMX agent (default:1099)
To monitor JMX behind firewall the following

changes have to be done.
• Edit startApplicationsManager.bat/sh file. Add
-Dmonitor.jmx.rmi.port=<port number for

JMX [ MX4J / JDK RMI socket communication> to the Java
1.5] runtime options.
• Restart Application Manager server
• Ensure that you have the RMI Socket port
(step1) and JNDI Port (step4) are opened up
in the firewall
• Add the JMX Applications monitor after
providing the relevant details.
• The monitor should be added successfully

Service Monitoring HTTP Port of Services (default:9090)
SNMP HTTP Port of SNMP (default:161)
Telnet HTTP Port of Telnet (default:23)
Port in which the agent is deployed (default:
Web Transaction
55555)
When there is a two way communication, and the monitors need to

access Applications Manager, then the following ports need to be
opened.
Port Description
Should be opened for accessing the Applications
Manager WebClient and also for monitoring WebLogic
WebServer
and JBoss.
Port: 9090
If Traps are configured to be received in Applications

Trap Port:
Manager, then you need to open up Trap Port: 1620.
1620
More
Apart from this, Applications Manager makes sure that data is secure;
internal mysql database allows only localhost to access the database
through authenticated users. User Names and Passwords are stored in
the MySQL database that is bundled along with the product. The
passwords are encrypted to maintain security.
Privileges required for different monitor types:
Monitor
Privileges
s
Windows Administrator username/password [WMI mode]
Linux Guest user privilege
Solaris Guest user privilege
Guest user privilege is sufficient but for collecting Memory related details, a u
IBM AIX
required. Hence, it is preferable to use a "root" account to view all details
HP Unix Guest user privilege
MS SQL System Administrator/Owner for the "master" database
User name specified should have access to the databases that are to be mon
MySQL
configured to allow the host on which App Manager is running to accesss the
DB2 Permission of "sysproc procedure" user of the DB2 database
Oracle Permission of "system" user of the Oracle database
WebSphe
If Global Security is enabled, the username/password for the same. Else no u
re
WebLogic If WebLogic is authenticated, the username/password for the same. Else no u
JBoss If JBoss is authenticated, the username/password for the same. Else no usern
If 5.x, you need to have username and password to connect to Tomcat Manag
Tomcat
username/password is required. The user specified should have 'manager' ro
SNMP
SNMP Community string with read privileges
Agent
Top
Enterprise Edition
Path Ports
Managed Server to
SSL Port (default 8443)
Admin
SSL Port (default 8443) - for
Admin to Managed
database syncing
Server
Webserver (default 9090)
Note: Production Environment gives you the configuration details that

you need to take care of, when moving Applications Manager into
Production.

Security/Firewall Requirements: Ports To Be Opened When Monitors Are Behind The Firewall

Uploaded by

Copyright:

Available Formats

Security/Firewall Requirements: Ports To Be Opened When Monitors Are Behind The Firewall

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Security/Firewall Requirements: Ports To Be Opened When Monitors Are Behind The Firewall

Uploaded by

Copyright:

Available Formats

Security/Firewall Requirements

This section explains how the Applications Manager can be accessed

You need to configure the firewall so that the host on which

Ports to be opened when Monitors are behind the firewall:

Monitors Port Details

Windows Management Instrumentation (WMI) --

Remote Procedure Call (RPC) -- Port: 135

SNMP Mode of monitoring:

SNMP Agent Port: 161

To monitor JMX behind firewall the following

• Edit startApplicationsManager.bat/sh file. Add

-Dmonitor.jmx.rmi.port=<port number for

• The monitor should be added successfully

When there is a two way communication, and the monitors need to

If Traps are configured to be received in Applications

Privileges required for different monitor types:

Note: Production Environment gives you the configuration details that

You might also like