The Nirva software is available for download in http://nirva-systems.com/NAP/Downloads/downloads.html.
Download the version corresponding to the target platform, unzip the file and put the unzipped files on a temporary directory of the target platform.
The installation of NIRVA is different for the WINDOWS and UNIX environments.
On all platforms, the NIRVA server must be stopped in order to re-install or update it.
Administrator rights are mandatory for installing or updating the server.
On Windows, the installation may fail if some programs are using the library nvc.dll. These programs must be closed if this is the case.
Run the program nvinstall.exe.
Follow the instructions. The installation program creates all necessary files and directories in the given target directory. It also detects if the installation is an update or a new installation. The target directory itself is created by the installation program but only at the lowest level. For example, if the target directory is “c:\Myprgms\Nirva”, the installation program will fail if the directory “c:\Myprgms” does not exist.
The install program then creates or modifies the environment variables NIRVA and PATH and installs the server as a windows service. The NIRVA windows service is named “Nirva server” and can be found after the installation in the list of available windows services. The start-up mode is set to “Manual”. If necessary, change it to automatic in order to automatically start NIRVA in service mode when starting the computer.
If necessary, the installation program requires a computer restart in order to complete the installation.
On some windows OS the Microsoft redistributable package for Visual C++ 2015 should be installed before running Nirva. This package is delivered with the Nirva installation files or it can be found at:
https://www.microsoft.com/en-us/download/details.aspx?id=48145
For Nirva versions until 4.9.001 one must install the Visual C++ 2008 redistribuable package. This package can be found at:
http://www.microsoft.com/en-us/download/details.aspx?id=29 for x86
http://www.microsoft.com/en-us/download/details.aspx?id=15336 for x64
Under AIX, it is recommended to run the command “slibclean” at this step. This removes the unused shared libraries from memory.
Under HPUX, Nirva requires the use of the LD_PRELOAD_ONCE feature. This is available for HP-UX 11.11 (v1) on PA-RISC as a patch PHSS_26560. This patch is not needed for more recent versions than v1.
Under Linux, the libstdc++ version 6.0.17 (at least) must be installed. Nirva also requires glibc 2.11.3 minimum.
Run the command “sh nvinstall” from your temporary directory.
Follow the instructions. The installation program creates all necessary files and directories in the given target directory. It also detects if the installation is an update or a new installation. The target directory itself is created by the installation program but only at the lowest level. For example, if the target directory is “/usr/Myprgms/Nirva”, the installation program will fail if the directory “/usr/Myprgms” does not exist.
If necessary, the installation program requires you to update or create the environment variables NIRVA and PATH in the profile of the user that will run NIRVA.
The NIRVA environment variable must point to the NIRVA installation directory (for example “/usr/nirva”) and the Nirva\Bin directory must be added to the PATH variable (for example “/usr/nirva/Bin”).
The Nirva installation package also includes some shared libraries:
n libnvc.a for AIX, libnvc.so for LINUX, SOLARIS and HPUX Itanium, libnvc.sl for HPUX PA-RISC.
n libnvperlcore.a for AIX, libnvperlcore.so for LINUX SOLARIS and HPUX Itanium, libnvperlcore.sl for HPUX PA-RISC.
These library files can be found in the Nirva/Bin directory.
These libraries must be in the library path. Two options are available:
n Copy the libraries in a usual place where libraries can be found (/usr/lib for example).
n Modify the LD_LIBRARY_PATH (or LIBPATH under AIX) and SHLIB_PATH (for HPUX only) environment variables in the profile of the user in order to point this variable to the Nirva/Bin directory. This is the preferred solution since the philosophy of NIRVA is to keep everything in its own directories and nothing outside.
The procedure for completely removing a NIRVA installation is as follows:
n Stop the NIRVA server.
n Under Windows, go into the NIRVA Bin directory and run the command nvs –r from the command prompt.
n Remove the entire NIRVA installation directory.
n Remove the environment variable NIRVA and the optional path to the NIRVA Bin directory from the PATH environment variable.
Under Windows, NIRVA does not write anything into the registry since NIRVA has its own registry. A Windows registry cleanup is therefore unnecessary.
Once installation is complete, the NIRVA server can be started in console or service mode. The service mode is the standard way while the console mode can be used for debugging purposes.
If the environment variable “NIRVA” does not exist or does not point to the Nirva installation directory, NIRVA will fail to start.
|
! |
Important: only one instance of NIRVA can be started. It is therefore necessary to stop NIRVA in server mode if NIRVA needs to be started in console mode. |
For starting the Nirva server in console mode, go into the Nirva Bin directory and type “nvs –c” at the command prompt.
To stop a Nirva server started in console mode, just issue a ctrl+c from the console. This will properly stop the server.
Under Windows, NIRVA can be run as a Window service. In order to start or stop NIRVA as a Windows service, go to the control panel and select the “Nirva server” service. You can then start or stop it.
Under UNIX, just type the complete path of the NIRVA server (nvs) without any parameter (e.g. “\usr\nirva\Bin\nvs”).
For stopping the NIRVA server from UNIX, go into the Bin directory of Nirva and run the command “nvcc -i stop_server.txt”.
The server can be tested by typing the following URL from a web browser:
http://localhost:1081/nvs?Command&NV_CLASS=test&NV_COMMAND=test_browser&NV_CLOSE_SESSION=yes
This should give the GMT time of the NIRVA server. Press the refresh button of your browser if you have an error.
When the server is running, the NIRVA configuration is available by typing the following URL from a web browser:
http://localhost:1081/Config/login.htm
where localhost can optionally be replaced by the TCP/IP address (or name) of the server and 1081 by its TCP/IP port (1081 is the default).
It is important that the NIRVA server runs correctly since the configuration tool is using the built-in NIRVA web server.
The configuration tool first displays a login page. If you are using NIRVA for the first time, you can enter “nvadmin” as user name and “nirva” as password.
If no license has been installed, the configuration tool will display a warning message.
When the server is running, the NIRVA documentation is available by typing the following URL from the web browser:
http://localhost:1081/NV_DOC_/html/nirva.htm
where localhost can optionally be replaced by the TCP/IP address (or name) of the server and 1081 by its TCP/IP port (1081 is the default).
If the NIRVA server is not running, the documentation is available by opening the nirva.htm file from the NIRVA Docs/html directory or nirva.pdf from the NIRVA Docs directory.
Services can be installed from the NIRVA configuration tool.
Go to the main system configuration screen and then select "services" and "install". This tool requires the name of the service and its installation package file.
Select one of the service installation packages found on your NIRVA CDROM or sent by your NIRVA service provider.
Applications can be installed from the NIRVA configuration tool.
Go to the main system configuration screen and then select "applications" and "install". The tool requires the application installation package file.
Nirva Application Platform is free software: you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
Nirva Application Platform is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public License along with Nirva Application Platform. If not, see http://www.gnu.org/licenses.
|
! |
Only the Nirva application Platform is covered by the LPGL license. Applications, services or other external components have their licensing policy under the responsibility of their provider. Nirva application platform has itself some parts that are not covered by the Nirva LGPL license. These parts are: WebSphere MQ connector, virtual printer connector, license library (nvlc), licensing tool (nvl), contents of the Nirva Perl directory, contents of the Nirva Java directory, libxml, libxslt, openssl. Please consult these components’ documentations for their licensing policy. |
All brands or product names cited in this documentation are trademarks or registered trademarks of their respective companies or organizations.
Copyright (C) 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011 Nirva Systems.