Installation and Startup

Application server produces the Open Manage Network Manager information for web clients. It monitors devices, and produces the output which the web server then makes available for those web clients. See Install on Linux for advice about installing to Linux only.

Initiate installation by opening index.html and clicking the install link (or executing win_install.exe [Windows]1 or linux_in­stall.sh2 [Linux]). Click through the installation wizard, accepting the license and making the appropriate entries.

Do not install if you are logged in as user “admin.”

During some installations, one screen lets you select the application’s memory size. Best practice is to select the largest available on your hardware while leaving sufficient memory for the operating system.

Heap

Heap settings let you, in effect, customize the number of devices being monitored by Open Manage Network Manager and the number of concurrent users. The default settings typically support 100 devices or less and 25 concurrent users. See Single Server Hardware for more about memory requirements.

Memory on a single machine installation serves the operating system, database and web server. You can configure the selected application server heap memory size any time, with the following properties in \owareapps\install­props\lib\installed.properties. For example:

oware.server.min.heap.size=4096m

oware.server.max.heap.size=4096m

To manually change Open Manage Network Manager web portal heap settings, change the setenv.sh or setenv.bat file:

set "PORTAL_PERMGEN=256m"

set "PORTAL_MAX_MEM=3072m"

set "PORTAL_INIT_MEM=768m"

set "PORTAL_32BIT_MAX_MEM=768m"

These files are in the Tomcat***/bin directory.

Installation and startup include:

• Running the installer, responding to its prompts.

Starting application server. In Windows, you can use the Start button (Start > Open Manage Network Manager > Start application server), or type startappserver in a command shell, or right-click the server manager tray icon and select Start (if you have installed Open Manage Network Manager as a service and that icon is red, not green).

A message declares “Application server is now up” in My Alerts in the bottom left corner of the screen of the web client when application server startup is complete. You can also make server monitor appear with the pmtray command either in a shell or from a start menu icon.

Starting web server. If this does not auto-start, you can use the Start button (Start > Open Manage Network Manager > Synergy Manager), or right click the web server’s tray icon to start it. You can also double-click this icon and automate web server startup. From a command line, you can also start this manager with [installation root]\oware\synergy\tomcat*\bin\startsynergy.

To start web server in Linux, in a shell type /etc/init.d/synergy start. Stop web server with /etc/init.d/synergy stop.

If you are using Open Manage Network Manager in an environment with a firewall, ports 8080 and 80 must be open for it to function correctly. If you want to use cut-thru outside of your network then ports 8082 – 8089 must be open. Open Manage Network Manager uses the first one available, so typically 8082, but if another application uses 8082, Open Manage Network Manager uses 8083 and so on. Web Services for Open Manage Network Manager previously used port 80, but for this version, they use 8089.

Start using Open Manage Network Manager as outlined in Getting Started, or below.Here are the various ways to start (and stop) Open Manage Network Manager elements:

Windows Start Menu Program Shortcut

Windows Command Line

Linux Command Line

Server Monitor

pmtray

N/A

Start Application Server

startappserver

startappserver

Synergy Manager

startsynergy.com

 

Note: this is in the oware\synergy\tomcat*\bin directory, and is not on the path.

While no monitor display appears, you can start the web server with these commands: startportal.sh start / startportal.sh stop

 

These are in the oware/synergy/tomcat-x.x.x/bin directory, and are not on the path.

Synergy

http://[application server host IP]:8080

http://[application server host IP]:8080

See Starting Web Client for more information.

See the Troubleshooting chapter of Installation Guide to solve Open Manage Network Manager problems.

/dell/openmanage/networkmanagerPort Forwarding

When you run the install root setup script for Linux it automatically re-routes event traffic from port 162 to port 8162.

Important: Configure File Handles in Linux

Best practice is to modify file handles for Linux. If you do not do this, exceptions appear in application server log every fifth minute. To prevent this, alter /etc/security/limits.conf. Here, administrators can set hard and soft limits for the file handles and number of user processes for users and user groups. These settings take effect on reboot. Best practice is to set at least the following for Open Manage Network Manager on a single machine or on each machine in a distributed system:

<Installing User> soft nofile 65536

<Installing User> hard nofile 65536

<Installing User> soft nproc 65536

<Installing User> hard nproc 65536

<Installing User> is the installing user login. Set these higher for more heavily used systems. You can also check/set file handles temporarily using the ulimit -H/Sn command. Like the following:

$ ulimit -Hn

$ ulimit -Sn

If you enter ulimit -a in a shell, open files should NOT be 1024, and User Processes should NOT be 1024. These are defaults that must be changed.

Web Client on Linux Systems

Xvfb must be running to have a web client work correctly. This is automated when application server starts automatically. You can manually start this process with root access using the following:

[root@redhat6 X11]Xvfb :623 -screen 0 1152x900x8 2>/dev/null &

Confirm xvfb is running as follows:

>ps -ef | grep Xvfb

root 25991 21329 0 16:28 tty2 00:00:00 Xvfb :623 -screen 0 1152x900x8

qa 26398 26053 0 16:31 pts/3 00:00:00 grep Xvfb

This is an example; the path that appears when you grep depends on your operating system.

Set Linux Permissions

These following ensures appropriate permissions exist so that the install succeeds on Linux. Your steps may vary slightly depending on the version on which you install.

1. Create a user, for example “redcell.”

2. Typically the redcell user’s home directory resembles /export/home/redcell.

3. In any case, ensure that user redcell owns its home directory (the /export/home/redcell directory).

4. Create /dell/openmanage/networkmanager, and ensure that your user (redcell) owns /dell/openmanage/networkmanager, Open Manage Network Manager’s installation root.

5. If necessary, unzip the downloaded installation package into a subdirectory under user redcell’s home directory.

6. Ensure the unzipped script file linux_install.sh has execute permissions.

7. Log in as user redcell

Do not install root. During the installation a prompt appears to execute a script as root. This means you need root password and must open another shell where you act as root.

8. Execute linux_install.sh, this begins the installation process, and follow the prompts.




  1. Windows installation sometimes installs Internet Informa­tion Services (IIS)--formerly called Internet Information Server. Typical installations do not turn IIS on by default. Do not enable IIS on the host(s) running Open Manage Network Manager.
  2. Linux installation can start in the following ways: a) type ./linux_install.sh in a shell. This lets application server, autostart function. b) Double click on the linux_install.sh file in the installation directory. This produces a screen with running options. if you click Run application server autostart functions. If you click on Run in Terminal it does not. Finally, follow the instructions in Important: Config­ure File Handles in Linux.