Users Guide

Understanding Installation Types | Preparing for Installation
OMNM 6.5.3 Installation Guide 23
Paired load-balancers/proxy servers direct Web users to an available Web server, and distribute Web
server traffic to an available Application server, and Mediation servers communicate with managed
devices.
Web Portal Installation
By selecting one of the custom installation options during the installation process, you can install
OpenManage Network Manager’s Web server on a separate machine. This is particularly desirable
if you plan to support a larger number of web clients (see
Verifying System Requirements on page
15 for sizing information).
When you install a separate Web server, installation assumes you have already installed the
Application server, and can supply its IP Address/Hostname, a port where Web server
communicates with Application server, and a heap size for this server. The default heap is 1G, but
you can configure a larger heap to support more clients. The default port is 8089. Make sure that no
firewall restricts communication between Application server and Web server on this port. See the
OpenManage Network Manager User Guide for information about installing with SSL.
Since the web portal needs a database, installing the Web portal also means you must select the
database type (MySQL or Oracle) and location host and port number. The port default: 3306.
As in the Complete installation, the Web server starts automatically once installation is complete.
In Windows, right-click the Apache Web server icon to Configure it (heap size, for example), Start
and Stop this service.
You can change the appserver IP reference in the
portal-ext.properties (location:
\oware\synergy\tomcat-x.x.xx\webapps\ROOT\WEB-INF\classes ).
The URL for the portal itself on port 8080 on any IP address where it is installed, including
127.0.0.1 if you access it from the host where the Web server itself is installed.