CA Service Management

Expand all | Collapse all

Migrate change categories from one system to another

  • 1.  Migrate change categories from one system to another

    Posted 09-18-2014 06:03 PM

    I have ran the following to extract all the change categories and associated properties and workflow tasks.

     

    pdm_extract Task_Type > task_type.txt

     

    pdm_extract Property_Validation_Rule > prp_val_rule.txt

     

    pdm_extract Workflow_Task_Template > wftpl.txt

     

    pdm_deref -s wftpl_deref.txt < wftpl.txt > wftpl1.txt

     

    pdm_extract Property_Value > prpval.txt

     

    pdm_deref -s prp_val_deref1.txt < prpval.txt > prpval1.txt

     

    pdm_extract Change_Category > chgcat.txt

     

    pdm_deref -s chgcat_deref1.txt < chgcat.txt > chgcat.1.txt

     

    pdm_extract Property_Template > prptpl.txt

     

    pdm_deref -s prptpl_deref.txt < prptpl.txt > prptpl1.txt

     

    I then copied the text files to the new system and ran the corresponding pdm_load and pdm_derefs but the workflow tasks do not show up on the change category until I Edit the category and then click the Use Classic Workflow button and cancel the create new task.  Then when I save the category, all the tasks are there.  Anyone attempted this before and know if there is any way to get the tasks to show up without have to go into each change category and edit it?  There are over 390 categories.

    Regards,

    Kevin



  • 2.  Re: Migrate change categories from one system to another

    Posted 09-18-2014 06:58 PM

    Hi Kevin,

     

    I saw strange things happen when we copied the prod environment over to test, then upgraded test to 12.7.  I didn’t see the problem on prod after it was upgraded, so it had to have something to do with the data moving from prod to test.  I was able to show this to support, but a few weeks later it stopped happening on its own.

    I’m sure this won’t help you any, but here’s what I saw:

     

     

     

    - If I added a task that was created prior to the upgrade, there were no problems.  But if I added a task that I created after the upgrade, and I put something in the task description, then it hung with an hourglass when saved.  If I clicked ‘close window’ and refreshed the screen, it showed that the task was added ok though. 

    - If I added a task that I created after the upgrade, and left the description empty, there were no problems. But if I tried editing the task to add a description, it would hang when saved.

    There was one error detected, only on one occasion:  AHD03075: Required attribute sequence is missing from object Workflow task template when save.

    Tammy



  • 3.  Re: Migrate change categories from one system to another

    Posted 09-18-2014 09:31 PM

    Hi Kevin,

     

    From the list, I dont see some tables such as behavior_template etc. If you would like to copy the change categories from one machine to another, then ensure that you copy all the associated tables are copied. Run the below command to get the list of associated tables:

     

    bop_sinfo -dq chgcat

     

    bop_sinfo -dq wftpl

     

    bop_sinfo -dq bhvtpl

     

    Thanks,

    Naveen



  • 4.  Re: Migrate change categories from one system to another

    Posted 09-19-2014 02:18 AM

    Hi Kevin

    I use the below extracts for categoris and workflows. I also extract macros and behaviors data as they may also be associated with the Workflow Tasks

     

    Let us consider you have 2 servers.

    Server 1 : New Server where you want to load the data

    Server 2 : Old Server where you have your entire Categories and Workflow Data

     

    1. ON SERVER 2 RUN THE BELOW EXTRACT STATEMENTS TO GET YOUR DATA.

    Its better you move them to a folder called "Server2_Data"

     

    pdm_extract Change_Category > chgcat.txt

    pdm_extract usp_change_type > chgtype.txt

    pdm_extract Service_Desc > sdsc.txt

    pdm_extract Workflow_Task_Template > wftpl.txt

    pdm_extract Behavior_Template > bhvtpl.txt

    pdm_extract Property_Template > prptpl.txt

    pdm_extract Property_Validation_Rule > prpvalrule.txt

    pdm_extract Property_Validation_Type > prpvaltype.txt

    pdm_extract Property > prp.txt

    pdm_extract Workflow_Task > wf.txt

    pdm_extract Task_Type > tsktyp.txt

    pdm_extract Task_Status > tskstat.txt

    pdm_extract usp_lrel_status_codes_tsktypes > lrel_status_codes_tsktypes.txt

    pdm_extract Active_Boolean_Table > actbool.txt

    pdm_extract Spell_Macro > macro.txt

    pdm_extract usp_lrel_true_bhv_true > lrel_true_bhv_true.txt

    pdm_extract usp_lrel_false_bhv_false > lrel_false_bhv_false.txt

    pdm_extract usp_lrel_att_ctplist_macro_ntf > lrel_att_ctplist_macro_ntf.txt

    pdm_extract usp_lrel_att_cntlist_macro_ntf > lrel_att_cntlist_macro_ntf.txt

    pdm_extract usp_lrel_att_ntflist_macro_ntf > lrel_att_ntflist_macro_ntf.txt

    pdm_extract usp_lrel_false_action_act_f > lrel_false_action_act_f.txt

    pdm_extract usp_lrel_true_action_act_t > lrel_true_action_act_t.tt

    pdm_extract usp_lrel_ntfr_macrolist_att_ntfrlist > lrel_ntfr_macrolist_att_ntfrlist.txt

    pdm_extract usp_lrel_svc_grps_svc_wftpl > lrel_svc_grps_svc_wftpl.txt

     

    2. RUN THE ABOVE EXTRACT STATEMENTS ON SERVER 1 AS WELL. Its better you extract the files into a folder called "server1_data"


    3.  NOW ON SERVER 1 REMOVE THE EXISTING DATA


    From the command prompt change the directory to "server1_data" and run the below commands to clear the data


    pdm_load -r -f chgcat.txt

    pdm_load -r -f chgtype.txt

    pdm_load -r -f sdsc.txt

    pdm_load -r -f wftpl.txt

    pdm_load -r -f bhvtpl.txt

    pdm_load -r -f prptpl.txt

    pdm_load -r -f prpvalrule.txt

    pdm_load -r -f prpvaltype.txt

    pdm_load -r -f prp.txt

    pdm_load -r -f wf.txt

    pdm_load -r -f tsktyp.txt

    pdm_load -r -f tskstat.txt

    pdm_load -r -f lrel_status_codes_tsktypes.txt

    pdm_load -r -f actbool.txt

    pdm_load -r -f macro.txt

    pdm_load -r -f lrel_true_bhv_true.txt

    pdm_load -r -f lrel_false_bhv_false.txt

    pdm_load -r -f lrel_att_ctplist_macro_ntf.txt

    pdm_load -r -f lrel_att_cntlist_macro_ntf.txt

    pdm_load -r -f lrel_att_ntflist_macro_ntf.txt

    pdm_load -r -f lrel_false_action_act_f.txt

    pdm_load -r -f lrel_true_action_act_t.tt

    pdm_load -r -f lrel_ntfr_macrolist_att_ntfrlist.txt

    pdm_load -r -f lrel_svc_grps_svc_wftpl.txt


    4. Now you will have to move the folder "server2_data" that you created in Step1 to "Server1" and then

    from server1 command prompt change the directory to "Server2_data" and run the below commands to load the data

     

    pdm_load -f chgcat.txt

    pdm_load -f chgtype.txt

    pdm_load -f sdsc.txt

    pdm_load -f wftpl.txt

    pdm_load -f bhvtpl.txt

    pdm_load -f prptpl.txt

    pdm_load -f prpvalrule.txt

    pdm_load -f prpvaltype.txt

    pdm_load -f prp.txt

    pdm_load -f wf.txt

    pdm_load -f tsktyp.txt

    pdm_load -f tskstat.txt

    pdm_load -f lrel_status_codes_tsktypes.txt

    pdm_load -f actbool.txt

    pdm_load -f macro.txt

    pdm_load -f lrel_true_bhv_true.txt

    pdm_load -f lrel_false_bhv_false.txt

    pdm_load -f lrel_att_ctplist_macro_ntf.txt

    pdm_load -f lrel_att_cntlist_macro_ntf.txt

    pdm_load -f lrel_att_ntflist_macro_ntf.txt

    pdm_load -f lrel_false_action_act_f.txt

    pdm_load -f lrel_true_action_act_t.tt

    pdm_load -f lrel_ntfr_macrolist_att_ntfrlist.txt

    pdm_load -f lrel_svc_grps_svc_wftpl.txt

     

    Hope the above helps

    Regards

    Nas



  • 5.  Re: Migrate change categories from one system to another

    Posted 09-19-2014 08:49 AM

    Nas,

    Thanks for this, however, I forgot to mention that the source server is 12.1 and the destination is 12.9, so the tables are slightly different.  Any suggestions on how to get this to work for the two different versions?

     

    Thanks,

    Kevin



  • 6.  Re: Migrate change categories from one system to another

    Posted 09-19-2014 11:08 AM

    Hi Kevin,

    I would like to know if there are any macros associated? Are you just interested in category names, workflows, properties? If its the second case it should be much simpler.

    Regards

    Nas



  • 7.  Re: Migrate change categories from one system to another

    Posted 09-19-2014 11:19 AM

    There are macros associated.  I actually have an upgraded environment to get the data from now, so it will be 12.9 - 12.9.

     

    Thanks,

    Kevin



  • 8.  Re: Migrate change categories from one system to another

    Posted 10-20-2014 06:40 AM

    Hello Kevin Gerber

     

    Do you have enough to be getting on with for this thread?

     

    If possible, please mark a thread as Correct Answer if it got you over the line. See Communities: Responding to Replies.

     

    I'm flagging the overall thread as "Assumed Answered" based on the above responses, but you may edit that flag if it isn't correct.

     

    Thanks, Kyle_R.

    Admin.



  • 9.  Re: Migrate change categories from one system to another

    Posted 02-12-2015 04:51 PM

    Hi Kevin,

    I've accidentally red this post. I'm pretty sure you already solved this somehow, but it should be helpful for someone in the future.

     

    I had exactly the same issue some time ago and the only problem was that the change category didn't have flow_flag attribute set to 0.

     

    Jakub



  • 10.  Re: Migrate change categories from one system to another

    Posted 06-05-2015 12:25 AM

    Hi Kevin,

     

    We use a new installation SDM 14.1.with CUM1 but I have same problem.

     

    I loaded some WF task templates for Category and Area but until the Edit button not used the loaded tasks templates doesn't appear.

    I loaded 0 to relevant flags in the chgcat and pcat object too.

     

    Restarted the server but nothing helped me.

     

     

    Gábor



  • 11.  Re: Migrate change categories from one system to another

    Posted 06-05-2015 02:39 AM

    I have created some new test that Jakub said and now it is working.

     

    The problem was when I loaded first round the area, category I didn't set the flow_flag, flow_flag_in attributes to 0.

    Just set these attributes to 0 after I loaded the tasks. And it didn't worked.

     

    But if the first loading file already including for Area these: flow_flag, flow_flag_in flow_flag_pr and the values are "0" then will work.

    Category: flow_flag.

     

    After the Area, Category loading process you can load the tasks too.

     

    Gábor