This documentation applies to the 8.1 version of Remedy IT Service Management Suite, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

Updating fields in forms for delta data

This section deals with data transformation changes that you need to apply to the migrated data.

The upgrade process applies the data transformation changes to all of the data that is present during the upgrade. However, you need to perform this step to apply those changes to data that was created after the delta data migration so that all of the data has these updates.

There is a batch file for each application, which also generates a log file to help you verify the results of the update after after you run it. The .arx and .def files that are extracted are imported into the system and you do not have to do anything manually with the def or arx files.   Apply these packages to your destination server.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments

  1. Andrej Kajzer

    Hi! Could you please explain why this is needed? And what is output of this action actually?

    Nov 24, 2014 06:47
    1. Bruce Cane

      Hi Adrej, ... I updated the explanation at the top of the page. Does this make it more clear?

      Nov 25, 2014 10:59
      1. Andrej Kajzer

        Bruce,

        in summary for each module described above we need to run command:

        setup.bat "<destinationServer>" "<user>" "<password>" <port>

        and should be fine if logs file are ok. If i am not wrong this command also creates arx files. Do we need to do something about those files?

        Thanks!

        Nov 26, 2014 05:23
        1. Bruce Cane

          Hi Andrej,

          For this part of your question, I'll need to follow up with a subject matter expert.

          I'll get back to you.

          -Bruce.

           

           

          Dec 02, 2014 03:46
        1. Murali Viswanathan

          Hello Andrej,

          This section deals with "data transformation changes" that needs to be applied to the data migrated.

          Upgrade takes care of these "data transformation changes" for all the data in the forms that are available during upgrade and this above step is required to re-trigger those changes to be updated post DDM so all data is now covered with these updates.

          There is a batch file for each product and logs to verify after it is executed. The arx and def files extracted are imported into the system and you do not have to do anything manually with the def or arx files. We do not document what not to do but we document what to execute and how to verify.

           

          HTH

          Thanks

          Murali V

          Dec 02, 2014 05:36
          1. Andrej Kajzer

            Murali V: many thanks. all clear.

            Dec 03, 2014 03:35
            1. Bruce Cane

              Andrej, I updated the introduction to this topic, based on Murali's response. Do the changes make this topic more clear for you, now? Would you recommend any changes?

               

              Thanks.

              Dec 03, 2014 09:33
              1. Andrej Kajzer

                For me it is clear now (smile)

                Dec 03, 2014 09:40
                1. Bruce Cane

                  Good! Thanks Andrej.

                  Dec 04, 2014 10:35
          1. Bruce Cane

            Yes, thanks Murali!

            Dec 03, 2014 09:32
  2. Rakesh Jajper

    Do we have to run this Post DDM batch files after each DDM process? Or only during final DDM process. We have to run DDM process almost every week until we go live.

    Feb 07, 2017 09:32
    1. Murali Viswanathan

       The staged upgrade process requires a new DB backup taken form your current production server 5-6 days before your go live date to be used for upgrading in your production staging server and DDM is only needed for that 5-6 days data, so not understanding why you are running DDM for weeks.

       

      Post DDM tasks has to be performed after final DDM run.

      You will also need to perform these tasks if you have a requirement to perform testing on the production staging server in-between DDM runs. You have to take a back up then perform post ddm tasks and testing THEN REVERT back to the DB backup taken and continue DDM.

      Feb 07, 2017 09:51
  3. Rakesh Jajper

    How all kind of testing can be done in 5-6 days? if we take DB backup from current prod and put it onto staging server and then upgrade it within this 5-6 days and perform testing as well before going live. I suspect this period is not enough even for the best case.

    We have to do thorough testing before Go live and not possible to do everything in 5-6 days.

    As remedy always trouble us upgrading to new version. Also we have integrations. So we have to do this frequent DDMs.

    So If I understood you correctly, we have to run this tasks after each DDM run, but before that take DB backup of staging server and then run DDM tasks, do testing and then revert back to DB backup stage. Is this just because we are doing multiple DDM run?

    And you really want this DDM tasks to be part of Final DDM run? Do we have to take backup at final run as well?

     

    Thanks Murali for your time

     

    Feb 07, 2017 10:09
    1. Murali Viswanathan

      I was commenting on production staging server activities in my reply for which you only need 5-6 days and by this time you should have all customizations and UAT test result fixes packaged and ready to be deployed before you start this prod server upgrade activity.

      Dev and QA staging server activities can start any time and can go for any time (weeks) you need, but no freeze or restrictions are needed as they will be performing the upgrade again with a fresh DB backup on the prod staging. This is the process and the only best practice process we document and support.

       

      Post DDM tasks have to be only run once if you are only doing upgrade and DDM in that server (which is what we expect you do on the prod staging server).

      If you have a requirement to test on the Prod staging server after upgrade OR after upgrade and between DDM runs then you need to run the post DDM scripts before you can start testing, and once your testing is complete then you need to restore to a stage before the post DDM scripts were run.

       

      Feb 07, 2017 10:54