iTop Administrator's Guide

This document is targeted towards system administrators in charge of configuring and operating the iTop application. For the basic usage of the application, from the end-user point of view, refer to the iTop User Manual.

This document assumes that you have at least a basic knowledge about MySQL or the SQL language in general.

A few pages which can be useful:

• Managing Organizations: During Implementation, you have defined the tree structure of organizations for your iTop. Later you may need to add or modify some organizations.
• Scheduling background tasks: This should have been set during iTop installation
• Tuning iTop Performance: if you encounter such issue, that could help.
• Object Query Langage: for reference
• HTML formatting limitations: what HTML syntax is supported within iTop Notes documents and Template HTML fields, Ticket's Description and AttributeCaseLog fields

This part explains all the actions available on the Admin Tools menu:

• User Accounts & Profiles: What are the possible profiles? What do they mean? How to create a user account? … User forgets its password?
• Notifications: Based on trigger, emails are sent automatically. Define those triggers and the email templates. See this step by step example.
• Auditing the CMDB: Define audit rules, using OQL, to control the completeness of the data stored in iTop.
• Run Object Queries: Get a set of objects compliant with some criteria.
• Query Phrasebook: Prepare your OQL queries and saved them for re-use.
• Export: Command line interface which can be used within a script. There is an interactive version and a CLI legacy version since iTop 2.2.x
• Browsing the Data Model: Not sure about the internal name of an object field, while writing an OQL, check here.
• Universal Search: Allow to search for any iTop objects even if no menu exist for them.
• Synchronize Data Sources: Allow to align iTop objects to an external data source. If you are not familiar with this, check the Overview first.
• Data Backup: Backup your database in a zip file, on demand or on schedule (requires Background tasks to be set).
• Configuration Editor: allow to change any configuration parameter on the fly. See the details of all configuration parameters and their usage. Examples of possible actions based on parameters: Setting iTop in read-only and Preventing concurrent modifications