Languages:

English  • Deutsch  • Español  • Français  • Polski

Aufsetzen des Managementservers.

Der Management Server besteht aus 4 Hauptkomponenten:

1. Database server, speichert die Inventory Informationen.
2. Communication server, steuert die HTTP-Kommunikation zwischen dem Database Server und den Agents.
3. Administration console, erlaubt den Administratoren die Datenbankabfrage mit dem Lieblingsbrowser.
4. Deployment server, speichert alle Konfigurationen der Paketverteilung (benötigt HTTPS!)

Diese 4 Komponenten können sich auf einem einzelnen Server befinden, sie können aber auch auf verschiedenen Servern untergebracht werden falls Load Balancing erwünscht wird. Bei mehr als 10000 inventorisierten Rechnern empfehlen wir mindestens 2 physikalische Server und zwar einen Server für die Datenbank und für die Kommunikation und einen zweiten Server als Datenbankreplikation, als Administrationsserver und als Deployementserver.

Database server darf aktuell nur MySQL 4.1 mit der InnoDB engine oder höhere Version sein.

Communication server benötigt Apache Web Server 1.3.X/2.X und ist in PERL als ein Apache Modul geschrieben. Der Grund? Weil PERL scripte beim Start des Apache kompiliert werden, und nicht bei jeder Anfrage. Dies erhöht die Performance. Der Communication server benötigt, je nach Distribution, zusätzliche PERL Module.

Deployment server benötigt einen beliebigen Web Server mit aktiviertem SSL.

Administration console läuft unter PHP 4.1 (oder höher) mit einem Apache Web Server 1.3.X/2.X. Die Administration console benötigt ZIP-Unterstützung und aktiviertem GD unter PHP zum ferngesteuerten Installieren von Softwarepaketen.

Mit Linux als Betriebssystem.

Voraussetzungen:

• MySQL zur Verfügung stehender Datenbank Server der auf den standard port 3306 über TCP/IP hört.
• installierter Apache Web Server als Communication Server und Administration Serve.
• PHP und Perl müssen für die Administrative Console auf dem Apache Web Server installiert und aktiv sein.
• Perl uns mod_perl müssen für den Communication Server auf dem Apache Web Server installiert und aktiv sein.

Requirements

• Apache Version 1.3.33 oder höher / Apache Version 2.0.46 oder höher.
  • Mod_perl Version 1.29 oder höher.
  • Mod_php Version 4.3.2 oder höher.
• PHP 4.3.2 oder höher, mit ZIP und GD support aktiviert.
• PERL 5.6 oder höher.
  • Perl module XML::Einfache Version 2.12 oder höher.
  • Perl module Compress::Zlib Version 1.33 oder höher.
  • Perl module DBI Version 1.40 oder höher.
  • Perl module DBD::Mysql Version 2.9004 oder höher.
  • Perl module Apache::DBI Version 0.93 oder höher.
  • Perl module Net::IP Version 1.21 oder höher.
  • Perl module SOAP::Lite Version 0.66 oder höher (optional)
• MySQL version 4.1.0 oder höher mit InnoDB engine aktiviert.
• Make utility wie z.B. GNU make.

Die Installation des Communication Server benötigt einige PERL Module.

Der Web Communication Server benötigt den Apache Web Server mit Perl 5 Scripting Language und einige zusätzliche Perl 5 Module(siehe Requirements). Diese funktionieren als Apache Module welche die Anfragen der HTTP OCS Inventory agents' zum virutellen Verzeichnis /ocsinventory umleiten.

Template:WArning

Unter Fedora/Redhat like Linux, können Sie “yum” benutzen um die benötigten Module zu installieren:

yum install perl-XML-Simple
yum install perl-Compress-Zlib
yum install perl-DBI
yum install perl-DBD-MySQL
yum install perl-Apache-DBI
yum install perl-Net-IP
yum install perl-SOAP-Lite

On Debian like Linux, können Sie “apt-get” benutzen um die benötigten Module zu installieren:

apt-get install libxml-simple-perl
apt-get install libcompress-zlib-perl
apt-get install libdbi-perl
apt-get install libdbd-mysql-perl
apt-get install libapache-dbi-perl
apt-get install libnet-ip-perl
apt-get install libsoap-lite-perl
cpan -i XML::Entities

On Gentoo like Linux, können Sie "emerge" benutzen um die benötigten Module zu installieren:

emerge dev-perl/XML-Simple
emerge perl-core/IO-Compress
emerge dev-perl/Apache-DBI
emerge dev-perl/Net-IP
emerge dev-perl/SOAP-Lite
emerge app-portage/g-cpan
g-cpan -i XML::Entities

Falls kein vorkompiliertes Paket für Ihre Distribution vorhanden ist, können Sie den Quellcode der Pakete unter http://search.cpan.org runterladen und diesem auf Ihrem System kompilieren (make und C Compiler sollten zur Verfügung stehen). Zum Beispiel:

tar –xvzf package_name.tar.gz
cd package_name
perl Makefile.PL
make
make test
make install

Sie können die fehlenden Module ebenfalls durch ein cpan Script installieren

z.B.

cpan -i Compress::Zlib 

/opt/lampp/bin/perl Makefile.PL

Die Installation der Administration Konsole benötigt PHP Module

Die Web Administration Konsole benötigt den Apache Web Server sowie PHP 4 Scripting und einige zusätzliche Module für PHP (siehe Requirements).

Unter Fedora/Redhat -ähnlichen Linuxdistributionen, können Sie “yum” benutzen um die ZIP Unterstützung für PHP zu installieren:

yum install php-pecl-zip

Unter RedHatEL, können Sie die RPM Pakete unter laden.

Für spätere Fedora Installationen 7.x+

yum install php-common

Unter Debianählichen Destributionen, Kônnen Sie “apt-get” nutzen:

apt-get install libphp-pclzip

Für die anderen Distributionen ist die bevorzugte Weg die PHP PECL ZIP Pakete zu nutzen. DAzu benötigen Sie die PHP development libraries (php-devel package unter RedHat oder Fedora Core, unter Linux Debian oder Ubuntu) damit Sie phpize Befehl nutzen können.

Nachdem Sie pear installiert haben,geben Sie Folgendes ein:

pear install zip

Falls Sie pear nicht installiert haben oder aber keine Verbindung ins Internet haben können Sie das Paket “zip-1.3.1.tgz” von der Webseite http://pecl.php.net/package/zipladen. In Debian/Ubuntu ähnlichen Systemen müssen die Pakete libpcre3 und libpcre3-dev vorher installiert sein, bevor das PECL_ZIP installiert wird..

Installieren Sie das Paket mit (php devel Paket wird benötigt):

tar –xvzf zip-1.3.1.tgz
cd zip-1.3.1
phpize
./configure
make
make install

Sie benötigen ebenfalls GD support für PHP.

Unter Fedora/Redhat ähnlichen Linux, installieren Sie mit “yum”:

yum install php-gd

Unter Debian ähnlichen Derivaten, installieren Sie mit “apt-get”:

apt-get install php5-gd

Installation des management server.

Sie benötigen Root Rechte zur Installation des Management Servers.

Laden Sie “OCSNG_LINUX_SERVER_1.01.tar.gz” von der OCS Inventory Web Site. (bzw die aktuellste Version)

Entpacken Sie das Paket. (Befehl ändert sich je nach Versionsnummer!)

tar –xvzf OCSNG_UNIX_SERVER-1.02.1.tar.gz
cd OCSNG_UNIX_SERVER-1.02.1

Führen sie per “setup.sh” den Installallierung durch. Während der Installation werden die Standardeinstellung in viereckigen Klammern [] dargestellt. Zum Beispiel bedeutet, [y]/n das “y” (yes) die Standardauswahl ist und “n” (no) die Alternative.

sh setup.sh

Geben sie “y” oder “enter” ein, um die Eingabe zu bestätigen und geben sie anschliessend die MySQL server host Adresse ein. In den meisten Fällen ist dies dann aber 'localhost'.

Then, setup checks for MySQL client binary files version 4.1 or higher. If not present, you will be prompted to continue or abort setup.

If all is OK, enter MySQL server port, generally 3306.

Enter or validate path to Apache daemon binary, generally “/usr/sbin/httpd”. It will be used to find Apache configuration files.

Enter or validate Apache main configuration file path, generally “/etc/apache/conf/apache.conf” or “/etc/httpd/conf/httpd.conf”.

Enter or validate Apache daemon running user account, generally “apache” or “www” (under Debian/Ubuntu is “www-data”).

Enter or validate Apache daemon user group, generally “apache” or “www” (under Debian/Ubuntu is “www-data”).

Next, setup checks for PERL interpreter binaries. Enter or validate path to PERL interpreter.

Common information for setting up Communication server or Administration console is now collected. Setup prompts you if you wish to set Communication server up on this computer. Enter “y” or validate to set Communication server up, “n” to skip Communication server installation.

Setup will then try to find make utility. If it fails, setup will stop.

Enter or validate path to Apache include configuration directory. This is the directory where is stored Apache configuration for specific modules. Generally, this directory is

/etc/httpd/conf.d

or

/etc/apache/conf.d

If you are not using configuration directory, but having all configurations into Apache main configuration file, enter no.

Setup will next try to determine your Apache mod_perl version. If it is not able to determine mod_perl version, it will ask you to enter it.

Next, it will prompt you to enter log directory where Communication server will store debugging/tuning logs. Validate or enter directory path. If it does not exist, this directory will be created.

Next, setup will check for required PERL modules (cf Requirements.):

• XML::Simple version 2.12 or higher
• Compress::Zlib version 1.33 or higher
• DBI version 1.40 or higher
• DBD::mysql version 2.9004 or higher
• Apache::DBI version 0.93 or higher
• Net::IP version 1.21 or higher
• SOAP::Lite version 0.66 or higher

If all is OK, setup will install Communication server:

• Configure Communication server PERL module.
• Build Communication server PERL module.
• Install Communication server PERL module into PERL standard library directories.
• Create Communication server log directory (/var/log/ocsinventory-NG by default).
• Configure daily log rotation for Communication server (file /etc/logrotate.d/ocsinventory-NG by default)
• Create Apache configuration file (ocsinventory.conf). If you are using Apache configuration directory, this file will be copied under this directory. Otherwise, you will be prompted to add content of this file to the end of Apache main configuration file.

################################################################################
#
# OCS Inventory NG Communication Server Perl Module Setup
#
# Copyleft 2006 Pascal DANEK
# Web: http://ocsinventory.sourceforge.net
#
# This code is open source and may be copied and modified as long as the source
# code is always made freely available.
# Please refer to the General Public Licence http://www.gnu.org/ or Licence.txt
################################################################################

# Which version of mod_perl we are using
# For mod_perl <= 1.999_21, replace VERSION_MP by 1
# For mod_perl > 1.999_21, replace VERSION_MP by 2
PerlSetEnv OCS_MODPERL_VERSION 1

# Where to write detailled logs
PerlSetEnv OCS_LOGPATH "/var/log/ocsinventory-NG"

# Database options
# Replace DATABASE_SERVER by hostname or ip of MySQL server, generally localhost
PerlSetEnv OCS_DB_HOST localhost
# Replace DATABASE_PORT by port where running MySQL server, generally 3306
PerlSetEnv OCS_DB_PORT 3306
# Name of database
PerlSetEnv OCS_DB_NAME ocsweb
PerlSetEnv OCS_DB_LOCAL ocsweb
# User allowed to connect to database
PerlSetEnv OCS_DB_USER ocs
# Password for user
PerlSetVar OCS_DB_PWD ocs

# The options below are overloaded if you are using ocs GUI
# Be careful: you must restart apache to have any effects
PerlSetEnv OCS_OPT_FREQUENCY 0
PerlSetEnv OCS_OPT_PROLOG_FREQ 24
PerlSetEnv OCS_OPT_DEPLOY 1
PerlSetEnv OCS_OPT_TRACE_DELETED 0
PerlSetEnv OCS_OPT_AUTO_DUPLICATE_LVL 7
PerlSetEnv OCS_OPT_LOGLEVEL 0
PerlSetEnv OCS_OPT_INVENTORY_DIFF 1
PerlSetEnv OCS_OPT_INVENTORY_TRANSACTION 1
PerlSetEnv OCS_OPT_PROXY_REVALIDATE_DELAY 3600

# Optional modules
PerlSetEnv OCS_OPT_IPDISCOVER 2
PerlSetEnv OCS_OPT_IPDISCOVER_MAX_ALIVE 7
PerlSetEnv OCS_OPT_IPDISCOVER_LATENCY 100
PerlSetEnv OCS_OPT_REGISTRY 0
PerlSetEnv OCS_OPT_UPDATE 0
PerlSetEnv OCS_OPT_DOWNLOAD 0
PerlSetEnv OCS_OPT_DOWNLOAD_FRAG_LATENCY 10
PerlSetEnv OCS_OPT_DOWNLOAD_CYCLE_LATENCY 0
PerlSetEnv OCS_OPT_DOWNLOAD_PERIOD_LATENCY 0
PerlSetEnv OCS_OPT_DOWNLOAD_TIMEOUT 30
PerlSetEnv OCS_OPT_WEB_SERVICE_ENABLED 0

############ DO NOT MODIFY BELOW ! #######################

# External modules
PerlModule Apache::DBI
PerlModule Compress::Zlib
PerlModule XML::Simple

# Ocs
PerlModule Apache::Ocsinventory
PerlModule Apache::Ocsinventory::Server::Constants
PerlModule Apache::Ocsinventory::Server::System
PerlModule Apache::Ocsinventory::Server::Communication
PerlModule Apache::Ocsinventory::Server::Inventory
PerlModule Apache::Ocsinventory::Server::Duplicate

# Options
PerlModule Apache::Ocsinventory::Server::Option::Registry
PerlModule Apache::Ocsinventory::Server::Option::Update
PerlModule Apache::Ocsinventory::Server::Option::Ipdiscover
PerlModule Apache::Ocsinventory::Server::Option::Download
# This module guides you through the module creation
# PerlModule Apache::Ocsinventory::Server::Option::Example
# This module adds some rules to filter some request sent to ocs server in the prolog and inventory stages
# PerlModule Apache::Ocsinventory::Server::Option::Filter

# Virtual directory for handling OCS Inventory NG agents communications
# Be carefull, do not create such directory into your web server root document !
#PerlTaintCheck On
<Location /ocsinventory>
order deny,allow
allow from all
Satisfy Any
SetHandler perl-script
PerlHandler Apache::Ocsinventory
</Location>

PerlModule Apache::Ocsinventory::SOAP;
<location /ocsinterface>
SetHandler perl-script
perlHandler "Apache::Ocsinventory::SOAP"
order deny,allow
allow from all
Satisfy any
</location>

Communication server installation is now finished. You will be prompted to set Administration console up. Enter “y” or validate to set Administration console up, enter “n” to skip Administration console installation.

Setup will ask you to enter Apache root document directory, usually “/var/www/html” or “/var/www-data”.

Next, setup will check for required PERL modules (cf Requirements.):

• XML::Simple version 2.12 or higher
• DBI version 1.40 or higher
• DBD::Mysql version 2.9004 or higher
• Net::IP version 1.21 or higher

If everything is OK, setup will install Administration console into the “ocsreports” subdirectory:

• Create /ocsreports directory structure.
• Create /download directory structure.
• Copy files into /ocsreports directory.
• Fix directories and files permissions to allow Apache daemon reading and writing to required directories (write access is required in /ocsreports, /ocsreports/ipd and /download, cf § 11.4 Files and directories permissions under Linux.).
• Configure PERL script ipdiscover-util.pl to access database and install it.

Now, you can restart Apache web server for changes to take effect (httpd is usually for apache2).

/etc/init.d/httpd restart 

or

/etc/init.d/apache restart

Configuring management server.

mysql -f -hlocalhost -uroot -p DBNAME < ocsbase.sql >log.log

Else, open your favorite web browser and point it on URL http://administration_console/ocsreports to connect the Administration server.

As database is not yet created, this will begin OCS Inventory setup process. Otherwise, you can rerun configuration process by browsing http://administration_console/ocsreports/install.php URL (this must be used when upgrading OCS Inventory management server).

Fill in information to connect to MySQL database server with a user who has the ability to create database, tables, indexes, etc (usually root):

• MySQL user name
• MySQL user password
• MySQL hostname

Setup actions :

• Create ocsweb database, and will add MySQL user ocs with password ocs.
• Grant to user ocs privileges Select | Insert | Update | Delete | Create | Drop | References | Index | Alter | Create temp | Lock on database ocsweb.

Refer to Secure your OCS Inventory NG Server documentation. If you don't want to secure your OCS Inventory Server, you have to desactivate Warning message in user profile. Procedure is in the same documentation page.

Finally, you may fill in a text describing the TAG, a string displayed at first launch of the agent to ask user to enter the TAG Value. It's a generic data which allows you to sort the new computers (geographical site, first floor, john room....). If you don't want this functionality, just let it blank.

Configuration of Management server is now finished.

Just point your browser to the URL http://administration_server/ocsreports and login in with admin as user and admin as password.

Upgrading management server.

When new versions of web communication server or web administration console are released, you must upgrade your installation.

To upgrade web communication server and administration console, you must follow instructions as described in Installing management server. You don’t need to update Perl modules if not required in the release notes.

Then, just point your favorite browser to URL “http://administration_server/ocsreports” and it will run the upgrade process to ensure that your database schema and default data are up to date. Upgrade process looks like configuration of management server as described in Configuring management server.

Fill in MySQL administrator name (usually root) and password, and MySQL database server address and click on [ Send ] button. Template:Notice

Finally, you may fill in a text describing the TAG if you wish to use it.

Under Windows Operating System.

We have chosen to package OCS inventory NG server for Windows as an integrated package containing all required components. As is, the 3 main components of Management server (database server, web communication server and web administration server) are installed on the same computer.

OCS Inventory NG server 1.0 for Windows is based on ApacheFriends XAMPP version 1.5.5 (ApacheFriends) which sets the following components up on a single computer:

• Apache 2.2.3
• MySQL 5.0.27
• PHP 5.2.0 + PHP 4.4.4 + PEAR
• PHP-Switch win32 1.0
• XAMPP Control Version 2.3 from www.nat32.com
• XAMPP Security 1.0
• SQLite 2.8.15
• OpenSSL 0.9.8d
• phpMyAdmin 2.9.1.1
• ADOdb 4.93
• Mercury Mail Transport System for Win32 and NetWare Systems v4.01b
• FileZilla FTP Server 0.9.20
• Webalizer 2.01-10
• Zend Optimizer 3.0.2
• eAccelerator 0.9.5 RC1 for PHP 5.1.6 (comment out in php.ini)
• Perl 5.8.8
• mod_perl 2.0.2

Installing management server.

Download OCSNG_WINDOWS_SERVER_1.02.1.zip from OCS Inventory Web Site, unpack it and launch OcsWin32ServerSetup.exe.

If XAMPP components (server and perl addon) are not already installed, Setup will prompt you that you have to set them up. Otherwise, Setup will automatically install OCS Inventory Server into XAMPP directories.

Click [ Next ] button to start installation wizard.

Click [ Next ] button and accept License agreement.

Choose installation directory, by default C:\Program Files\OCS Inventory NG. You need 400 MB of free hard disk space if XAMPP components are not installed, otherwise, only 10MB are required.

Then, you have to validate components to install. Only OCS Inventory NG Server is required, if XAMPP components are already installed.

Next, you have to choose the program group name in start menu, where OCS Inventory NG icons will be created and then click on [ Install ] button to start installation.

If XAMPP setup selected, Setup will first launch XAMPP 1.5.5 setup in silent mode. This will create a folder xampp under destination folder, and a program group Apache Friends in start menu.

You will be prompted to start XAMPP Control Panel. Please, answer No.

Then, it will launch XAMPP perl addon setup in silent mode.

Last, Setup will install OCS Inventory NG Server files, configure XAMPP Apache and MySQL servers for OCS Inventory NG Server, and automatically start MySQL and Apache servers.

At the end of the process, Setup will launch your default browser to start OCS Inventory NG Server configuration (see Configuring management server).

Setup is now finished and you can click [ Finished ] button.

Communication server files are now located into PERL standard libraries.

Apache logs (access.log, error.log, phperror.log) and communication server logs (ocsinventory-NG.log) are located in the sub-directory Apache\Logs”.

Configuring management server.

Open your favorite web browser on the server and point it on URL http://localhost/ocsreports to connect the Administration server.

You will be prompted for information to connect to MySQL database server with a user who has the ability to create database, tables, indexes, etc:

• MySQL user name, root by default
• MySQL user password (empty password by default)
• MySQL hostname, localhost

Setup actions :

• Create ocsweb database, and will add MySQL user ocs with password ocs.
• Grant to user ocs privileges Select | Insert | Update | Delete | Create | Drop | References | Index | Alter | Create temp | Lock on database ocsweb.

Refer to Secure your OCS Inventory NG Server documentation. If you don't want to secure your OCS Inventory Server, you have to desactivate Warning message in user profile. Procedure is in the same documentation page.

Finally, you may fill in a text describing the TAG, a string displayed at first launch of the agent to ask user to enter the TAG Value. It's a generic data which allows you to sort the new computers (geographical site, first floor, john room....). If you don't want this functionality, just let it blank.

Configuration of Management server is now finished.

Default Administrator login is admin as user and admin as password.

[[Image:|center]]

Updating security of XAMPP components.

Open your favorite web browser on the server and point it on URL http://localhost/xampp/splash.php to connect the XAMPP configuration GUI.

Click on the language you want to access the XAMPP main configuration menu.

Then, click [ Security ] on the left menu. As you will see, all is marked as unsecure or unknown for non started components.

You can change this by clicking the link http://localhost/security/xamppsecurity.php.

First of all, you must fill in MySQL root password and select phpMyAdmin authentication method.

Validate your changes by clicking Password changing button.

You can then protect the access to XAMPP configuration menu by filling in user and password for XAMPP DIRECTORY PROTECTION. As is, this user and password will be asked to connect to XAMPP configuration menu through a web browser.

Validate your changes by clicking Make safe the XAMPP directory button.

Finally, you must restart Apache and MySQL services for changes to take effect.

Open XAMPP Control Panel from system tray or from OCS Inventory NG start menu folder, click [ Stop ] button for Apache, then [ Start ] button and do the same for MySQL.

You can now reselect [ Security ] on left side menu to see that all started services are now secured.

Upgrading management server.

To upgrade web communication server and administration console, you must follow instructions as described in the section Installing management server. Just ensure that setup detects old installation folder correctly.

You don’t need to update XAMPP components. Setup, by default, will not select XAMPP components install. If you do so, backup your databases and web sites if you want to also upgrade XAMPP components ! See the section Backup/restore of OCS Inventory NG database.

At the end of the process, Setup will launch your default browser to run the upgrade process to ensure that your database schema and default data are up to date. Upgrade process looks like configuration of management server as described in the section Configuring management server.

Fill in MySQL administrator name (usually root) and password, and MySQL database server address and click “Send” button.

Finally, you may fill in a text describing the TAG if you wish to use it.