Files
iTop/setup/unattended-install
odain 77626f8159 N°8760 - Audit uninstall of extensions that declare final classes
N°8760 - be able to list modules based on extension choices
refactoring: move some classes in a moduleinstallation folder (coming
namespace)

N°8760 - module dependency check applied before audit

N°8760 - make dependency check work during audit

N°8760 - fix ci

N°8760 - fix ci

N°8760 - add GetCreatedIn to get module name based on DBObject class - everything stored in MetaModel during compilation and autoload

N°8760 - be able to describe from which module a datamodel class comes via MetaModel created_in field

N°8760 - rename GetCreatedIn <- GetModuleName + compute module name live instead having complex stuff in MetaModel/compilation

temp review 1

review: renaming InstallationChoicesToModuleConverter

review: renaming InstallationChoicesToModuleConverter

review: ModuleDiscovery:GetModulesOrderedByDependencies replacing deprecated GetAvailableModules method

ci: fix typo

cleanup

review: rework InstallationChoicesToModuleConverter

N°8760 - review tests
2026-02-06 16:48:00 +01:00
..

Unattended-install

This script allows to install and update iTop via CLI.

For more information, see the official Wiki : Automated installation [iTop Documentation]

unattended-install.php

Usage

Execution of the unattended installation

Note: Because the installation runs from the command line, make sure that the current user has enough rights to access the different locations and that the web server will be able to access the files and directories created during the scripted installation. In order to exactly emulate the behavior of the interactive installation it may be a good practice to run this installation from the user account used for running the web server process.

Launch the script with the following command: bash php unattended_install.php --param-file=fresh-install.xml

Where: fresh-install.xml is the response file containing your desired settings for the installation (there are 4 models available in the folder xml_setup: fresh-install.xml, itil-fresh-install.xml, itil-upgrade.xml, upgrade.xml)

Fresh installation parameters

Important: In the case of a fresh installation (install), do not forget to complete below mandatory parameters before:

<database>
    <server></server>
    <user></user>
    <pwd></pwd>
    <name></name>
    <db_tls_enabled></db_tls_enabled>
    <db_tls_ca></db_tls_ca>
    <prefix></prefix>
</database>
<url>
</url>
<graphviz_path>/usr/bin/dot</graphviz_path>
<admin_account>
<user></user>
<pwd></pwd>
<language></language>
</admin_account>
<language></language>

Options

To get all available options of the script, you can perform the following command : php unattended-install.php --help

install-itop.sh

Usage

You can install your iTop by only using config-itop.php settings and run either

  • a non-ITIL iTop fresh installation (use itil-fresh-install.xml to have ITIL modules instead)
./install-itop.sh ./xml_setup/fresh-install.xml
  • a non-ITIL iTop upgrade (use itil-upgrade.xml to have ITIL modules instead)
./install-itop.sh ./xml_setup/upgrade.xml
  • a specific iTop installation by providing both xml setup file in below example file provided is the one generated by iTop during last setup.
./install-itop.sh ../../log/install-2024-04-03.xml