ITOP2.7-install

 

Installation wizard

1. Make sure that you have a properly configured instance of Apache/PHP running
2. Unpack the content of the “web” directory in a directory served by your web server (for example /var/www/html/itop on Linux or C:\inetpub\wwwroot\itop on Windows/IIS).
3. Point your web browser to the URL corresponding to the directory where the files have been unpacked (for example http://localhost/itop) and follow the indications on the screen.

iTop provides a step by step wizard to install the application.

The first step of the installation consists in checking the consistency of the configuration, user rights for web server user and the prerequisites for MySQL, PHP and optional PHP extensions.

The second step of the installation offers the choice to either upgrade an existing iTop or to install the application from scratch.

If you select to install a new instance then third step of the wizard will prompt you to accept the license agreement.

The fourth step of the wizard prompts you for the credentials to connect to MySQL and the database to use for installing iTop. Make sure that you supply an account with enough rights for installing and running iTop. This account needs to create tables, triggers and views in the database, as well as drop views in case of upgrade. If you choose to let the setup create a new database for you, this account needs to have enought rights to do it.

You can also specify a prefix to be added to the names of all tables and views created by iTop in the database. Useful if you want to install several iTop inside the same MySQL database, but avoid otherwise. It's better to create multiple databases.

Note that the database server does not need to be on the same physical server as the PHP/web server it can be a remote host if you prefer to have a two-tier architecture, or connect to an already installed MySQL server.

If your database is located on a shared server, you can specify the port after the Server Name: my_server:3309

If your database is running on Windows, it is recommended to not use the following specific characters in password: !,%,“. In such a case, the setup will inform you to during the setup phase that the iTop backup mechanism won't work '

The next step of the wizard prompts you for the information about the administrator account. iTop authentication can rely on external mechanisms (LDAP, Active Directory or JASIG-CAS) but the installation requires that at least one administrator account be created with a local password.

The next screen prompts your for several miscellaneous information:

• default language: this is the language of the login screen and the default language for newly created user accounts.
• URL to access iTop: change this value if users will be accessing iTop using a different URL (thanks to a DNS alias, a different IP adress, etc.)
• sample data: install sample data if you want to quickly experiment with iTop. Sample data provide some sample configuration items (servers, applications, contacts) and default settings for the service catalog in order to ensure a quick deployment of the application. Do not select this option if you are deploying a production instance of iTop and want a “clean” installation.

In case you have multiple virtual hosts pointing to iTop or if you are using a test system with a dynamic IP address (DHCP) and you want to connect anyway from another system, the “address” of the iTop server cannot be fixed at installation time. In this case you can use the placeholder $_SERVER_NAME_$ in the URL parameter. For example you can type: http://$_SERVER_NAME_$/itop as the URL to access the application. At runtime this value will be substituted by the value of the PHP variable SERVER_NAME for the current connection.

The following steps of the installation wizard will help you tailor the “data model” of iTop in order to best suit your needs.

Configuring the CMDB

The CMDB is made of 5 modules:

• The Configuration Management Core module which is always installed. This module provides the basic objects that must always be present in iTop: Organizations, Locations, Contacts and a few common CIs like Servers, Groups, Applications, etc…
• The Data Center Management module provides configurations items for managing the logistics of a data center: racks, enclosures, power (PDUs, power sources…). You probably don't need this module if you don't manage a data center.
• The End-Users Devices modules defines the devices related to end-users: phones, PCs, tablets… if you don't plan to manage such devices in iTop, you may uncheck this option.
• The Advanced Storage Management module defines configuration items related to the management of storage devices: SAN switches, NAS, Tape libraries and tapes, etc… It is optional.
• The Virtualization Management module defines Virtual Machines, hypervisors, farms, etc. You may uncheck it if you don”t plan to manage virtual devices in iTop.

Configuring Service Management

Service management comes in two flavors in iTop. Choose the option that best represents your situation:

• Service Management for Enterprises is best suited for describing a situation where the same infrastructure is used to deliver services to a set of customers. Customers can be internal entities of a common organization or external customers.
• Service Management for Service Providers is best suited if the infrastructure used for delivering/supporting a customer is specific to each customer with little overlap (sharing) between customers.

The documentation for these two modules is grouped in: Service Management (services, SLAs, contracts) Module.

Configuring Tickets Management

If you plan to manage tickets in iTop, there are basically two options:

• Simple Ticketing is best suited for implementing simple processes where little difference is made between the incidents and user requests. All tickets share the same life cycle and you can change the characterization of a ticket at any time. This choice is probably appropriate if you plan to let end-users create tickets directly through the portal either to place service requests or to report incidents.
• ITIL Compliant Tickets is best suited for implementing strict ITIL compliant processes. A clear distinction is made between User Request and Incident tickets. (You may choose to deploy only one of theses processes or both)

Of course you can also select not to manage such tickets in iTop at all. In this case, select the third option.

Configuring Change Management

If you plan to implement Change Management in iTop there are also two options:

• Simple Change Management provides one single type of all purposes Change Request tickets.
• ITIL Compliant Change Management provides the complete set of ITIL compliant change processes with Normal, Routine and Emergency Change tickets.

You can also completely deactivate the Change Management in iTop by selecting the third choice.

Additional ITIL processes

In addition to change and incident management, two other type of ITIL compliant processes can be deployed by selecting the corresponding type of tickets:

• Problem Management
• Known Errors and FAQs

Launching the installation

Once all the choices are made, a summary is displayed. You can drill down to check your choices by clicking on the “plus” button for each section.

To start the actual installation of iTop, click on the “Install !” button.

The progress of the installation is displayed with a moving progress bar.

Once the installation is done, you can: Review the instructions about setting up the background tasks, by clicking the link “Manual instructions for Tickets Management”. Or enter iTop immediately by clicking on the “Enter iTop” button.

Instructions to setup the background tasks are also available and potentially more up to date here

Congratulation, you’ve successfully installed iTop!

Automated installation

The installation of iTop is generally performed interactively using the “setup” page. However once information about the desired configuration has been collected by the setup page, the actual installation process is fully unattended and therefore can be automated.