|
|
To start Web NMS from any Directory
This document explains the steps to be followed in starting Web NMS from any directory in systems using the communication protocols TCP and RMI. The procedure is the same for different platforms though it varies depending upon the communication protocol.
Using TCP
Edit the NMS_HOME environment variable in setEnv.(bat/sh) file located in the
<WEB NMS HOME> directory
and set it to absolute <Web NMS Home>.
For example, if you have installed Web NMS in "c:/mydir/AdventNet/WebNMS"
directory and want to start Web NMS from "d:/test"directory,
then the environment variable in setEnv.(bat/sh)
file should be edited as follows
NMS_HOME=c:/mydir/AdventNet/WebNMS
In startnms.(bat/sh) give the absolute path of the setEnv.(bat/sh) file. By default it is given as, ./setEnv.(bat/sh). You must now give it as <absolute path>/setEnv.(bat/sh).
Using RMI
If you want to start Web NMS using RMI connection, in addition to the above edit the following file.
In startnms.(bat/sh) file located in the <Web NMS Home>/bin add the arguments BE_FE RMI and change the NMS_BE_PORT from 2000 to 1099 in the NmsMainBE process.
To Add Your Own Jar Files
To add your own jar files into AdventNet Web NMS edit CODEBASE_LIST in <Web NMS Home>/setEnv.bat/sh. (Windows uses http, while Linux uses file protocol). The jar file path is set relative to <Web NMS Home> directory.
|
|
Note: The above change is required only if you are trying to run Web NMS from any other directory other than the default directory, where Web NMS was installed. |
|
|
