iTop should be configured with strict class dictionary governance, profile permissions, and change process alignment.
¶ Core settings and files
conf/production/config-itop.php- database and web server tuning
- module enablement and extensions
Example baseline:
<?php
$MySettings['app_root_url'] = 'https://itop.example.com';
$MySettings['db_host'] = '127.0.0.1';
$MySettings['db_name'] = 'itop';
$MySettings['db_user'] = 'itop';
$MySettings['db_pwd'] = 'replace-with-strong-password';
¶ Process and role controls
- Align incident/change/problem workflows with your ITSM policy.
- Keep admin profiles limited and audited.
- Version-control custom datamodel extensions.
- Validate data import mappings in staging first.
- Use reconciliation keys to avoid duplicate CIs.
- Monitor sync jobs and reject invalid payloads.
¶ Backup and recovery
Back up:
- database
conf/ and module customizations- attachments/documents
Recovery test:
- Restore application and DB.
- Validate tickets, CIs, and linked relationships.
- Execute one scheduled import and verify reconciliation.
- HTTPS and admin protection enabled.
- Import job errors alerting enabled.
- DB backup tested.
- Extension compatibility checked before upgrades.
Squeezing every bit of performance from your Itop installation? Our experts help with:
- Memory and resource tuning
- Connection pool optimization
- Caching strategies
- Load balancing and clustering
Optimize your setup: office@linux-server-admin.com | Contact Us