Deployment of netxms should start from installation of NetXMS server which
does most of work and then distributing netxms agent all over the network
where it is possible and needed.

Basic NetXMS Installation
=========================

   These are generic installation instructions. For more detailed
installation instruction consult NetXMS Installation Guide (located in
doc/manuals, also available separately on NetXMS web site).

The simplest way to install netxms server is:

  1. Get current distribution from www.netxms.org using any of methods
     available. 
     For ex.: fetch http://www.netxms.org/download/netxms-0.1.20.tar.gz
     (do not just copy-paste line above, there might be newer version
     available).

  2. Unpack distribution.
     For ex. gunzip netxms-0.1.20.tar.gz; tar xf netxms-0.1.20.tar

  3. `cd' to the directory containing the package's source code and type
     `./configure' to configure the package for your system.  If you're
     using `csh' on an old version of System V, you might need to type
     `sh ./configure' instead to prevent `csh' from trying to execute
     `configure' itself.

     Running `configure' takes awhile.  While running, it prints some
     messages telling which features it is checking for.

     Please note: if You're willing to install netxms server - in most cases
     You should specify also --with-server and --with-[dbname] parameters
     for configure script where [dbname] is database driver name You're
     going to use. Try ./configure --help to see all possible
     parameters.
     
     For example:
     ./configure --with-server --with-agent --with-mysql=/opt/mysql \
                 --prefix=/opt/netxms
     Will configure distribution to build both server and agent and to build
     mysql driver for netxms using mysql libraries from mysql distribution 
     located in /opt/mysql. Distribution will be configured also to be
     installed in /opt/netxms.

  4. Type `make' to compile the package.

  5. Type `make install' to install the programs and any data files and
     documentation.
 
  6. Copy default netxms daemon configuration file ('netxmsd.conf-dist') to /etc
     directory with name 'netxmsd.conf' and edit it to match actual settings.
     You can do it like this: 
     cp ./contrib/netxmsd.conf-dist /etc/netxmsd.conf
     vi /etc/netxmsd.conf
  
  7. Use sql/dbinit_[dbname].sql script and Your database client
     program to initialize database for netxms. 
     For example if You're going to use mysql this could be like this:

     mysql> create database netxms;
     mysql> \q
     $> nxdbmgr init sql/dbinit_mysql.sql

  8. `cd' to netxms installation directory and try running bin/netxmsd.
     Check if netsmd process is running. If not try starting it again with
     --debug-all parameter and see log file for details.
 
  9. If You see netxmsd running - You have just successfuly installed netxms 
     monitoring server. Try connecting with netxms console. Default
     login/pass are admin/netxms.

 10. If You succeeded to connect - first action You should do is
     changing password (see netxms console docs for details).

 11. Repeat steps 1-5 on each server which needs to be monitored using just
     "./configure --with-agent --prefix=..." as parameters. You don't need
     server and database driver/libraries for agent. 
 12. Copy default netxms agent daemon configuration file ('nxagentd.conf-dist')
     to /etc directory with name 'nxagentd.conf' and edit it to match actual
     settings.
     You can do it like this:
     cp ./nxagentd.conf-dist /etc/nxagentd.conf
     vi /etc/nxagentd.conf
 13. Start nxagentd and check that it is running 
     (do it same way as netxms server).

Upgrading
=========
See UPGRADE file in root source directory for details of upgrade procedure.
Agent upgrades can be done automatically. New agent versions are distributed
to all servers by netxms server. This can be done from netxms console. So
You need to build agents only once - during initial installation.


Advanced installation/build details
===================================

   If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release.  If at some point `config.cache'
contains results you don't want to keep, you may remove or edit it.

   The file `configure.in' is used to create `configure' by a program
called `autoconf'.  You only need `configure.in' if you want to change
it or regenerate `configure' using a newer version of `autoconf'.

Compilers and Options
=====================

   Some systems require unusual options for compilation or linking that
the `configure' script does not know about.  You can give `configure'
initial values for variables by setting them in the environment.  Using
a Bourne-compatible shell, you can do that on the command line like
this:
     CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure

Or on systems that have the `env' program, you can do it like this:
     env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure

Compiling For Multiple Architectures
====================================

   You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory.  To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'.  `cd' to the
directory where you want the object files and executables to go and run
the `configure' script.  `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.

   If you have to use a `make' that does not supports the `VPATH'
variable, you have to compile the package for one architecture at a time
in the source code directory.  After you have installed the package for
one architecture, use `make distclean' before reconfiguring for another
architecture.

Installation Names
==================

   By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc.  You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PATH'.

   You can specify separate installation prefixes for
architecture-specific files and architecture-independent files.  If you
give `configure' the option `--exec-prefix=PATH', the package will use
PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.

   In addition, if you use an unusual directory layout you can give
options like `--bindir=PATH' to specify different values for particular
kinds of files.  Run `configure --help' for a list of the directories
you can set and what kinds of files go in them.

   If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.

Optional Features
=================

   Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System).  The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.

   For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.

Specifying the System Type
==========================

   There may be some features `configure' can not figure out
automatically, but needs to determine by the type of host the package
will run on.  Usually `configure' can figure that out, but if it prints
a message saying it can not guess the host type, give it the
`--host=TYPE' option.  TYPE can either be a short name for the system
type, such as `sun4', or a canonical name with three fields:
     CPU-COMPANY-SYSTEM

See the file `config.sub' for the possible values of each field.  If
`config.sub' isn't included in this package, then this package doesn't
need to know the host type.

   If you are building compiler tools for cross-compiling, you can also
use the `--target=TYPE' option to select the type of system they will
produce code for and the `--build=TYPE' option to select the type of
system on which you are compiling the package.

Sharing Defaults
================

   If you want to set default values for `configure' scripts to share,
you can create a site shell script called `config.site' that gives
default values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' if it exists.  Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.

Operation Controls
==================

   `configure' recognizes the following options to control how it
operates.

`--cache-file=FILE'
     Use and save the results of the tests in FILE instead of
     `./config.cache'.  Set FILE to `/dev/null' to disable caching, for
     debugging `configure'.

`--help'
     Print a summary of the options to `configure', and exit.

`--quiet'
`--silent'
`-q'
     Do not print messages saying which checks are being made.  To
     suppress all normal output, redirect it to `/dev/null' (any error
     messages will still be shown).

`--srcdir=DIR'
     Look for the package's source code in directory DIR.  Usually
     `configure' can determine that directory automatically.

`--version'
     Print the version of Autoconf used to generate the `configure'
     script, and exit.

`configure' also accepts some other, not widely useful, options.

