Menu

#1277 migrate from complex ITIL configuration to Simple Itil configuration

Documentation
closed
nobody
None
User Interface
Critical
2.3.1
defect
2016-07-20
2016-07-19
Dos Santos
No

Hello,

I want to migrate from complex ITIL configuration to Simple Itil configuration..
Could you need me a procedure for this action..

Thanks you
Michel

Discussion

  • Erwan Taloc

    Erwan Taloc - 2016-07-20

    Hello
    here is a small procedure for this migration:

    First update SQL database to change the installation options:

    UPDATE priv_module_install SET name='itop-request-mgmt' WHERE name='itop-request-mgmt-itil'; 
    
    DELETE from priv_module_install WHERE name='itop-incident-mgmt-itil';
    

    Then restart the setup procedure to update the setup option

    Once done, you have to migrate the data already loaded in iTop. For this execute the following SQL command to migrate the data stored in Incident (table ticket_incident) that has to be moved to
    UserRequest (table ticket_request)

    insert into ticket_request (id,status,impact,priority,urgency,request_type,origin,service_id,servicesubcategory_id,escalation_flag,escalation_reason,assignment_date,resolution_date,last_pending_date,cumulatedpending_timespent,cumulatedpending_started,cumulatedpending_laststart,cumulatedpending_stopped,tto_timespent,tto_started,tto_laststart,tto_stopped,tto_75_deadline,tto_75_passed,tto_75_triggered,tto_75_overrun,tto_100_deadline,tto_100_passed,tto_100_triggered,tto_100_overrun,ttr_timespent,ttr_started,ttr_laststart,ttr_stopped,ttr_75_deadline,ttr_75_passed,ttr_75_triggered,ttr_75_overrun,ttr_100_deadline,ttr_100_passed,ttr_100_triggered,ttr_100_overrun,time_spent,resolution_code,solution,pending_reason,parent_request_id,public_log,public_log_index,user_satisfaction,user_commment) 
    select id,status,impact,priority,urgency,'incident',origin,service_id,servicesubcategory_id,escalation_flag,escalation_reason,assignment_date,resolution_date,last_pending_date,cumulatedpending_timespent,cumulatedpending_started,cumulatedpending_laststart,cumulatedpending_stopped,tto_timespent,tto_started,tto_laststart,tto_stopped,tto_75_deadline,tto_75_passed,tto_75_triggered,tto_75_overrun,tto_100_deadline,tto_100_passed,tto_100_triggered,tto_100_overrun,ttr_timespent,ttr_started,ttr_laststart,ttr_stopped,ttr_75_deadline,ttr_75_passed,ttr_75_triggered,ttr_75_overrun,ttr_100_deadline,ttr_100_passed,ttr_100_triggered,ttr_100_overrun,time_spent,resolution_code,solution,pending_reason,parent_incident_id,public_log,public_log_index,user_satisfaction,user_commment from ticket_incident ;
    
    update ticket set finalclass = 'UserRequest' where finalclass='Incident' ;
    

    Last step you have to update as well history of changes and attachment if there is some:

    update priv_changeop as c, ticket as t set c.objclass='UserRequest' where c.objkey=t.id and c.objclass='Incident'; 
    update attachment as a, ticket as t set item_class='UserRequest' where a.item_id=t.id and a.item_class='Incident'; 
    

    Once done, you should see in User Request module all the incident that where track as a Incident before

     
  • Erwan Taloc

    Erwan Taloc - 2016-07-20
    • status: new --> closed
    • Milestone: Unassigned --> Documentation
     

Log in to post a comment.