Setup

Once the necessary preparations have been made - for example, configuring the underlying operating system, the i-doit setup can begin.

Quick Start#

Extract the i-doit installation package in a directory that the Apache HTTP Server has access to. Then navigate to this directory with your browser and follow the setup instructions.

Download and Extract the installation Package#

The installation package of the pro variant is available to all customers in the customer portal, and the open variant at i-doit.org. This package is copied to the prepared server, extracted, and the files and directories are given the appropriate permissions. These instructions differ depending on the operating system.

Debian or Ubuntu#

The Apache HTTP Server runs with the permissions of the user www-data and the group of the same name www-data. The main directory of the Apache HTTP Server is /var/www/html/:

Create the i-doit folder and copy the files into it:

1
2
3
4

sudo cp i-doit.zip /var/www/html/
cd /var/www/html
sudo unzip idoit-xx.zip
sudo rm idoit-xx.zip

Now set the permissions so that the Apache HTTP Server user can read and write:

1
2
3

sudo chown www-data:www-data -R .
sudo find . -type d -name \* -exec chmod 775 {} \;
sudo find . -type f -exec chmod 664 {} \;

Red Hat Enterprise Linux (RHEL)#

The Apache HTTP Server runs with the permissions of the user apache and the group of the same name apache. The main directory of the Apache HTTP Server is /var/www/html/:

Create the i-doit folder and copy the files into it:

1
2
3
4

sudo cp i-doit.zip /var/www/html/
cd /var/www/html
sudo unzip idoit-xx.zip
sudo rm idoit-xx.zip

Now set the permissions so that the web server user can read and write:

1
2
3

sudo chown apache:apache -R .
sudo find . -type d -name \* -exec chmod 775 {} \;
sudo find . -type f -exec chmod 664 {} \;

Suse Linux Enterprise Server (SLES)#

The Apache HTTP Server runs with the permissions of the user wwwrun and the group www. The main directory of the Apache HTTP Server is /srv/www/htdocs/:

1
2
3
4

sudo cp i-doit.zip /var/www/html/
cd /var/www/html
sudo unzip idoit-xx.zip
sudo rm idoit-xx.zip

Now set the permissions so that the web server user can read and write:

1
2
3

sudo chown wwwrun:www -R .
sudo find . -type d -name \* -exec chmod 775 {} \;
sudo find . -type f -exec chmod 664 {} \;

Microsoft Windows Server#

Specific file and directory permissions typically do not need to be set if the Apache HTTP Server installed with XAMPP runs with the same user permissions.

Perform Setup#

i-doit can be installed in two ways: conveniently via the Web GUI (recommended for beginners) or via the console (e.g., for automated installation).

Web GUI#

The setup is automatically called when you access i-doit with the browser (example: http://i-doit-host/).

System Check#

In the first step, important system settings are checked. If something is not in order, the user is notified.

Directory Configuration#

Here, the paths are requested where installation- and user-specific files should be stored. The suggestions can be accepted.

Database Configuration#

Important credentials and settings need to be entered for the database connection. At least two databases and a special user are created for i-doit.

• Connection settings
  • Host: typically the host itself, i.e., localhost or 127.0.0.1
  • Port: typically the default port of MySQL/MariaDB, i.e., 3306
  • Username: username of the database system user, usually root
  • Password: password of the user
• MySQL user settings
  • Username: username of the owner of the i-doit databases, usually idoit
  • Password: password of the user
• Database settings
  • System Database Name: name of the system database, usually idoit_system
  • Mandator Database Name: name of the database for the first tenant, usually idoit_data
  • Mandator title: title of the tenant, usually the name of the organization in focus
  • Start value for object/configuration item IDs: usually 1

Framework Configuration#

There are separate credentials for accessing the Admin Center in i-doit, which can be set here. It is recommended to do so.

Config Check#

In this step, all previous steps are summarized and it is checked whether the setup can be completed.

installation#

In this step, the actual installation of i-doit on the system takes place. After successful installation, a summary follows. After that, i-doit can be accessed and used.

Console#

i-doit can be installed via the console using the included console.php: through a guided wizard or through a single line suitable for automated installations. Both methods are performed within the i-doit directory:

1

cd /var/www/html/

It is mandatory to execute the following commands with the user whose permissions the web server runs under. On Debian-based operating systems, this is www-data, on RHEL apache, and on SLES wwwrun.

The options are based on the setup via the Web GUI.

Guided installation via Console#

1

sudo -u www-data php console.php install

The wizard asks for some credentials and settings. Values shown in brackets are default values that are accepted by pressing Enter.

A tenant can then be created via the Admin Center or via the console.php.

1

sudo -u www-data php console.php create-tenant

Automated installation via Console#

1

sudo -u www-data php console.php install --root-user mysqlrootuser --root-password mysqlrootpassword --host localhost --port 3306 --database idoit_system --user mysqlidoituser --password mysqlidoitpassword --admin-password admincenterpw --no-interaction

i-doit is now installed. We still need a tenant. We also create this via the console.php:

1

sudo -u www-data php console.php tenant-create --root-user mysqlrootuser --root-password mysqlrootpassword --database idoit_system --user mysqlidoituser --password mysqlidoitpassword --no-interaction --title "CMDB"

Further Steps#

• Download and apply license
• Set up backup
• Set up cron jobs
• First login