|
|
Introduction
Web NMS can be installed over Windows, Linux and Solaris platforms. Distribution feature is available as a feature pack and can be applied over the latest version of AdventNet Web NMS. To enable the distribution feature, download the platform-specific AdventNet Web NMS - Remote Management Edition binary from www.adventnet.com and follow the installation instructions as explained in the following sections.
The procedure to enable distribution in both the versions is same. Web NMS Remote Management Edition can be installed in three modes: GUI mode, Command/Console mode, and Silent Mode.
This is an interactive GUI-based installation mode. The user can install Web NMS Remote Management Edition easily by using the user interface provided.
To install in GUI mode
Download the binaries from the www.adventnet.com.
AdventNet_WebNMS_DMP_4_7_0_Windows.exe file for Windows
AdventNet_WebNMS_DMP_4_7_0_Linux.bin for Linux
AdventNet_WebNMS_DMP_4_7_0_Solaris.bin for Solaris
Check the executable permission of the .bin file. If the file is not executable, then execute the following command:
chmod a+x <filename> where <filename> is the corresponding .bin file
Execute the downloaded file to invoke the InstallShield Wizard
For Windows : AdventNet_WebNMS_DMP_4_7_0_Windows.exe
For Linux : ./AdventNet_WebNMS_DMP_4_7_0_Linux.bin
For Solaris : ./AdventNet_WebNMS_DMP_4_7_0_Solaris.bin
The installation main screen displays the Welcome message. Click the Next button to move to the License Agreement screen.
Select "I accept" option in License Agreement screen and click the Next button to go to the Options screen.
The Options screen provides the choice of upgrading the existing back-end server, front-end server and client or installing the Distribution Mediation Server. The options screen will be as follows
To upgrade the existing combo installation (Back-end+Front-end+Client) to enable distribution
To upgrade the existing Web NMS combo installation, choose Upgrade BE. Enter the location where the combo installation is present. Also specify the JDK Home. Click Next to upgrade the existing Web NMS combo installation. This completes the upgrade process for BE+FE+Client installation. After the context change, the combo installation will be referred to as Central Server.
To upgrade the existing front-end server to enable distribution
To upgrade the existing Web NMS front-end server, choose Upgrade FE. Enter the location where the front-end server is installed. Also specify the JDK Home. Click Next to upgrade the existing Web NMS front-end server. This completes the upgrade process for front-end.
To upgrade the existing client to enable distribution
To upgrade the existing Web NMS client, choose Upgrade Client. Enter the location where the standalone client is installed. Click Next to upgrade the existing Web NMS client. This completes the upgrade process for client.
Note: If the Client is not upgraded, a message "Unable to connect Update Manager Server in" is displayed when you try to connect the Client to the Server. You can still proceed with connecting the client, but exceptions may be thrown in the Client logs. This is because, in Web NMS Standard and Professional editions, the Update Manager uses TCP communication, while in Web NMS RME, HTTP communication is used. Hence, ensure to upgrade the Client also.
To install the Distributed Mediation Server
Choose the Install DMS option and click the Next button to move to Locale screen.
Choose English, Japanese or Chinese. By default, English is selected. Click Next to go to the DMS Details screen.
Enter the details of the Central Server to which the Distributed Mediation Server must connect. Click Next to go to the DMS Location screen.
Enter the location where the Distributed Mediation Server needs to be installed and click Next to view the pre-installation summary and click Next to initiate the installation process.
Select Readme option to view the README and click Finish to complete the installation.
Installation in Command/Console Mode
The Command or Console mode is an Interactive and Non-GUI based installation mode. You can install Web NMS from the command prompt by following a series of questions prompted at the console.
Windows
Download the AdventNet_WebNMS_DMP_4_7_0_Windows.exe file in the system where you want to install.
To install AdventNet_WebNMS_DMP_4_7_0_Windows.exe from a remote system, telnet to the system where the exe file is downloaded and give the following command:
AdventNet_WebNMS_DMP_4_7_0_Windows.exe -console
The above command will guide the user in installing the Web NMS Remote Management Edition in a Non-GUI mode.
Linux/Solaris
Download AdventNet_WebNMS_DMP_4_7_0_Linux.bin file or the AdventNet_WebNMS_DMP_4_7_0_Solaris.bin file in the system where you want to install.
To install AdventNet_WebNMS_DMP_4_7_0_Linux.bin or AdventNet_WebNMS_DMP_4_7_0_Solaris.bin from a remote system, telnet to the system where the bin file is downloaded.
Check the executable permission of the AdventNet_WebNMS_DMP_4_7_0_Linux.bin or AdventNet_WebNMS_DMP_4_7_0_Solaris.bin for Linux/Solaris. If the file is not executable, then execute the following command:
chmod a+x (Or) chmod 777 AdventNet_WebNMS_DMP_4_7_0_Linux.bin / AdventNet_WebNMS_DMP_4_7_0_Solaris.bin
Execute the bin file for Linux/Solaris as follows:
./AdventNet_WebNMS_DMP_4_7_0_Linux.bin
-console
./AdventNet_WebNMS_DMP_4_7_0_Solaris.bin -console
The above command will guide the user in installing Web NMS Remote Management Edition in a Non-GUI mode.
The Silent mode is a Non-interactive and Non-GUI based installation mode. This mode of installation is generally useful in automated setups. The user can specify all the options required in a text file and the installation process continues without manual intervention.
Download the AdventNet_WebNMS_DMP_4_7_0_Windows.exe file for Windows, AdventNet_WebNMS_DMP_4_7_0_Linux.bin for Linux and AdventNet_WebNMS_DMP_4_7_0_Solaris.bin for Solaris.
Check the executable permission of the .bin file. If the file is not executable, then execute the following command: chmod a+x <filename> where <filename> is the corresponding .bin file
For building the installoptions.txt file required for installation, open a new text file and copy the following contents and save the file as installoptions.txt.
|
#****************************************************** -W DMPCategory.selectedValue=BE -W WebNMS.home=/home/username/AdventNet/WebNMS -W locale.lang=English -W DMS.hostName=localhost -W DMS.portNumber=9090 -W DMS.id=dms -G replaceExistingResponse="yesToAll" #******************************************************* |
The editable options beginning with "-W" can have the following values.
|
Option |
Description | |
|---|---|---|
|
DMPCategory.selectedValue |
Specifies the category for installation
| |
|
WebNMS.home |
Specifies the location of the base Web NMS installation. | |
|
Options specific to Install DMS option in UI or IDMP in selectedValue category. |
locale.lang |
Specifies the locale for installation, the values can be
|
|
DMS.hostName |
Specifies the name of the Central Server to which the Distributed Mediation Server connects. | |
|
DMS.portNumber |
Specifies the port number in which the Central Server listens for Distributed Mediation Server connections. | |
|
DMS.id |
Specifies the name of the Distributed Mediation Server which identifies it uniquely. | |
Execute the .exe or .bin files as follows where <InstallLocation> should be replaced by the path where Web NMS distributed Component - Central Server, front-end server, client or Distributed Mediation Server has to be installed.
For Windows: AdventNet_WebNMS_DMP_4_7_0_Windows.exe -is:javaconsole -silent -options installoptions.txt -P ProductRoot.installLocation=<InstallLocation>
For Linux: ./AdventNet_WebNMS_DMP_4_7_0_Linux.bin -is:javaconsole -silent -options installoptions.txt -P ProductRoot.installLocation=<InstallLocation>
For Solaris: ./AdventNet_WebNMS_DMP_4_7_0_Solaris.bin -is:javaconsole -silent -options installoptions.txt -P ProductRoot.installLocation=<InstallLocation>
Here,
installoptions.txt is the text file which supplies different arguments to the installer as explained above.
InstallLocation is any writable location in the system, where the product has to be installed. For example, if you have chosen c:\test as the installation directory in windows, specify the command as follows:
AdventNet_WebNMS_DMP_4_7_0_Windows.exe -is:javaconsole -silent -options installoptions.txt -P ProductRoot.installLocation=c:\test
All the files related to Web NMS Remote Management Edition will be extracted directly under c:\test directory.
In Windows, do not add a slash(\) at the end of the <InstallationLocation> as c:\test\. This would lead to improper installation of Web NMS Remote Management Edition in silent mode.
Points to Remember while Installing in Silent Mode
Avoid installing Web NMS Remote Management Edition using silent mode in a previously installed location.
Changing the variable name in the installoptions.txt file (value on LHS of "=") leads to installation failure
The "WebNMS.home" variable will not have any effect, when the value of "DMPCategory.selectedValue" is set to IDMP
The variables "DMS.hostName", "DMS.portNumber", "DMS.id", "locale.lang" and ProductRoot.installLocation will have effect only when the "DMPCategory.selectedValue" is set to IDMP
|
|