|The 2.x toolkit is available here: iTopDataModelToolkit-2.3.zip|
iTop is built on top of an ORM (Object Relational Mapper) abstraction layer that relies on the definition of a “Meta Data Model” made of PHP classes. Starting with iTop 2.0 the Meta Data Model can be described in XML which is then “compiled” into PHP classes during the setup of the application.
The iTop architecture can be depicted as the schema below:
The orange boxes on the schema above are the parts of the application that can be customized.
|Type of customization||Mean||Documentation||Intended audience|
|Extending or modifying the data model and adjusting the behavior of the console||XML files||XML reference||iTop consultants, ITIL specialists|
|Extending the generic user-interface via a plug-in||PHP files||Extensions API||PHP developers|
|Creating new user interface pages to implement new web services, specialized exports or a specific task oriented user interface||PHP files||ORM API||PHP developers|
|Creating your own security scheme||PHP files||User Rights API||PHP developers|
|Change the customer portal or develop a new portal||XML files||Customize the Customer Portal||iTop consultants, ITIL specialists, Web designers, PHP developpers|
Understanding the iTop file structure
The layout of the iTop files and folders can be depicted as below:
The following folders have a special usage in iTop:
conf: contains the configuration files, with one sub-folder per environment (see Environments below).
data: contains application generated data, like the image for the object life-cycle (if graphviz is available on the system)
datamodels: contains the meta data model definitions, with one sub-folder per major version of iTop.
env-xxxx: these folders (one per environment) contain the “compiled ” data model. The env-production folder is completely re-created each time the application is re-installed or upgraded. If you edit its content, be aware that your modifications will be lost upon re-install or upgrade.
extensions: this folder is the place where to copy extensions modules that are not part of the standard distribution of iTop.
log: contains the log files of the application:
All the other folders should be considered as part of the source code of the application and should generally not be modified. The application never writes to these folders, they can be marked as read-only for the web server process.
A new concept introduced by iTop 2.0 is the notion of “environment”. An environment is an instance of iTop running the same code base but with potentially its own data model and configuration file. An environment is made of:
A configuration file stored in
A data model runtime, stored in
The toolkit automatically creates a separate environment (named toolkit) in order to compile the XML data model and test its consistency without affecting the “production” environment. When the changes are Ok, you can instruct the toolkit to apply the validated changes to the “production” environment.
Extensions versus Modules
The basic unit of data model definition in iTop is called a module. The installation process of iTop considers each module as a whole.
A module groups together all the files needed to deliver a given
CSS files, PHP pages,
images, etc… A module contains at least one file: the module
definition file, always named
Though you can always patch the source code, the best way to customize iTop consists in writing your own module. This creates a clean packaging of the customization and allow an easy (re)installation for your deployment or in case of upgrade.
The concept of extension is introduced with iTop 2.4. An extension is an assembly of one or more module. The installation options proposed to the end-user during the setup are based on the extensions found in the “extensions” folder of iTop; For backward compatibility, if a module is found outside of an extension, this module will be directly listed as an installation option.
Extensions are identified by the
found in the root folder of each extension.
When an extension is made of one single module, the expected
structure is one single folder with all the files
datamodel.xxxx.xml, etc. at the same level.
When an extension is made of several modules, the expected
structure is one single root folder containing only the
extension.xml file, with one subfolder per module
If several extensions contain the same module (identified by its code), the installation process will install only one copy of the module: the highest version.
PHP versus XML data model definitions
In iTop versions 1.x, the data model definition was written as a plain PHP classes. iTop version 2.0 support both PHP and XML definitions for the data model.
XML definitions have one major advantage over PHP definitions: the XML definition in one module can alter the data model defined in another module. For example, it is possible to create an extension module that will - when installed - add an attribute to the standard class “Server”, which is defined in the standard iTop data model. The extension module does not need to replace the whole “itop-config-management” module (where the Server class is defined), it can just alter the definition of a classe defines elsewhere.
In order to achieve the same effect in PHP, the only solution consists in cloning the whole itop-config-mgmt module and replacing it with your own patched version. When a new version of the module is released, you have to redo this diff & patch work again to produce a new version of your own module. Since an XML definition is directly defined as a difference, the upgrade is automatic.
Content of a module
If my-module is the name of your module, the module folder will contain the following files:
|extension.xml||New in iTop 2.4: An XML
definition file, used by iTop 2.4 and above. This file contains
some information similar to the module PHP file, but enables the
support of extensions containing several modules. If the module is
located inside a folder already containing an
|module.my-module.php||The module definition file. Mandatory. Contains the description of the module (name version, dependencies on other modules, etc.) and its components.|
|datamodel.my-module.xml||Data Model in XML. Upon installation the “compilation” will produce the model.xxxxx.php file based on the XML definitions. The XML file can contain the definition of classes, menus and profiles|
|model.my-module.php||If you choose to define the data model directly in PHP, then this file is the place to put such definitions|
|main.my-module.php||PHP code and utilities. For some modules that contain a lot of PHP code, it is easier to extract the PHP code and edit it in this separate file than letting the code embedded in the XML.|
|images||It is a good practice to store the images (classes icons, etc…) in their own sub folder|
|en.dict.my-module.php||Dictionnary file, if you need some localized strings|
Creating a module
Fill the form below and click on “Generate” to generate an empty module as the starting point for your customization:
Installing the Toolkit
Download the toolkit zip file: iTopDataModelToolkit-2.3.zip
Expand the content of the zip file to create a directory “toolkit” at the root of the your developement iTop instance.
Point your browser to http://<your_itop>/toolkit
Create an empty module
Install a development instance of iTop, including your empty module in the “extensions” folder
Install the toolkit on your developement instance
Edit your extension module and validate it with the toolkit
Apply the changes made to your extension module to the “production” environment
Test your module with some sample data. In case of troubles, fix them by iterating at point 4.
When your extension is completed you can deploy it on your production system by:
Copying the folder containing your extension module to the “extensions” folder on the production system
Marking the configuration file as read/write
Running the setup again and selecting your module in the list of “extensions” at the end of the interactive setup
Using the Toolkit
Once the toolkit is installed, point your browser to: http://<your_itop>/toolkit.
The first tab performs some basic consistency checks and validation of the data model definition. You can use the “Refresh” button to perform the validation again each time the data model definition has changed. The checks performed in this tab work on the specific “toolkit” environment and thus have no effect on the actual iTop instance that uses the “production” environment.
If you get an error like:
XML datamodel loader: could not find node for
This probably means that your module lacks a dependency on the module where the class XXXX is defined.
When the setup runs the loading order is computed and the resulting order is written in the configuration file. Be aware that the toolkit does not recompute this loading order. Therefore if you miss a dependency, you need to modify the module definition file to add this dependency and run the setup again in order to recompute the whole configuration file
When the first tab does not show any error, you can move to the second tab to:
check the change to the database schema
apply the changes of the database schema and data model definitions to the “production” iTop environment by clicking on “Udpate iTop Code”
The third tab of the toolkit can be used to update the Data Synchronization sources (if there are any that was impacted by the changes to the data model), and to check if there are any discrepencies in the internal data maintained for hierachical keys. This tab directly operates on the “production” environment.
A graphical representation of the object's life-cycle is displayed in the “Data Model” page of iTop (tab “Life-cycle”). If you modify an object's life-cycle, then you'll need to have Graphviz installed on the web server to get this images re-computed. See Installing iTop for more information about installing Graphviz.
In iTop, a language is identified by two things:
The ISO 639-1 language code. Example:
The ISO country code. Example:
Localization relies on dictionary files, which names are
prefixed with the iTop language code in lowercase:
Those files will be found in the following directories:
The setup or the toolkit must be run to make sure that a change in the dictionaries will take effect.
A dictionary is in fact a PHP file. It must be encoded in the utf-8 character set (this is a MUST). We recommend that the PHP closing tag be omitted as in the example given below.
<?php /** * Localized data * * @copyright Copyright (C) 2015 John Foo Ltd * @author John Foo (email@example.com) * @license http://opensource.org/licenses/AGPL-3.0 */ Dict::Add('PT BR', 'Brazilian', 'Portuguese', array( 'Menu:ChangeManagement' => 'Gerenciamento Mudanças', 'Menu:Change:Overview' => 'Visão geral', 'Menu:NewChange' => 'New Change~~', ));
The first parameter of the function call is the iTop language code in uppercase.
The second parameter of the function call is the language name in english.
The third parameter of the function call is the language name in the target language.
The line Dict::Add must be the same amongst all the dictionnary files for the same language (yes, there are redundant information here).
~~at the end of some strings. This suffix is not displayed to the end-user. It has been automatically added by Combodo when releasing a new version of iTop, revealing which new strings require a translation.
How to contribute to improve an existing language
Look for (grep) the
~~ and translate them in
Create a zip with the updated files and create a ticket with the zip attached, and we will integrate the changes for the next release of iTop.
find -name "de*dict*.php" | grep -v "env-" | xargs grep "~~"
de* in the command above by the
language code you want to process (fr, it, sp…) and launch this
command from the directory where you installed iTop.
How to contribute to add a new language
Find out your language code and country code.
Copy the english files (either dictionary.*.php or
en.dict.*.php) into their respective directory, with the relevant
prefix (like in
Translate them, create a zip package, attach it to a ticket and we will integrate that translation for the next release of iTop.
Dict::Addfunction calls. Failing to do so will overwrite (at runtime) the english texts with yours.