Management server is made up of 4 main components: Database server, which stores inventory information Communication server, which handles HTTP communications between database server and agents. Administration console, which allows administrators to query the database server using their favorite browser. These 4 components can be hosted on a single computer or on different computers to allow load balancing.
If you want to use multiple computers to host OCS inventory NG management server, we recommend that you set it up on Linux servers. Database server currently can only be MySQL 4. Communication server needs Apache Web Server 1. This is better performance-wise. Communication server may require some additional PERL modules, according to your distribution.
Administration console is written in PHP 4. Under Linux Operating System. We assume that you have: Apache Web server installed and running for Communication server and Administration server. Perl module DBI version 1. Make utility such as GNU make. The Web communication server requires Apache web server and Perl 5 scripting language and some additional modules for Perl 5 see Requirements.
You must have root privileges to set required perl modules up. It is better for system integrity to use your distribution's precompiled packages when they are available. Some of these packages are only avalaible in EPEL. Entities On Gentoo like Linux, you can use "emerge" to get required modules set up: Entities If a precompiled package is not available for your distribution, you can download the package source from http: PL make make test make install You can also install the missing modules using the cpan script.
You must have root privileges to install Administration console. For later Fedora installations 7. Install it php devel package is required: You must have root privileges to set management server up. During the installer, default choice is presented between . If you encounter any error, please refer to this log for detailed error messag Warning: Then, setup checks for MySQL client binary files version 4. If not present, you will be prompted to continue or abort setup. It will be used to find Apache configuration files.
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. 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. Validate or enter directory path. If it does not exist, this directory will be created. If any of these modules is missing, setup will abort. If all is OK, setup will install Communication server: 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. Do not add content to apache main configuration file if it is not a fresh install! You must manually copy content of the ocsinventory. Please refer to the General Public Licence http: External modules PerlModule Apache:: Simple Ocs PerlModule Apache:: Duplicate Options PerlModule Apache:: Download This module guides you through the module creation PerlModule Apache:: Example This module adds some rules to filter some request sent to ocs server in the prolog and inventory stages PerlModule Apache:: Filter Virtual directory for handling OCS Inventory NG agents communications Be carefull, do not create such directory into your web server root document!
Apache configuration sample file Communication server installation is now finished. You will be prompted to set Administration console up. Configure PERL script ipdiscover-util. Now, you can restart Apache web server for changes to take effect httpd is usually for apache2. We recommend you to check your php.