CA Service Management

 View Only
Expand all | Collapse all

Swing Box Migration Method for CA Service Desk Manager

  • 1.  Swing Box Migration Method for CA Service Desk Manager

    Posted Jun 19, 2014 11:21 AM

    Are you planning your upgrade to Service Desk Manager 12.9?

    If so, then here is a great document to check out:

    https://comm.support.ca.com/?legacyid=TEC578669

     

    This is a Technical Document that I wrote which explains how to use the Swing Box Migration method!   It will save you a lot of time, and has many advantages.

     

    Take a look at the document and feel free to share your experiences with Upgrades/Migrations of CA Service Desk Manager here!



  • 2.  Re: Swing Box Migration Method for CA Service Desk Manager

    Posted Jun 20, 2014 10:58 AM

    Jon, have you or any of your peers created a document this thorough for swinging catalog implementations over?  Thanks  - fred



  • 3.  Re: Swing Box Migration Method for CA Service Desk Manager

    Posted Jun 20, 2014 09:38 PM

    Hi Fred,

    I dont believe the same method is recommended by the Catalog team at this time.  I would have to defer to someone from that team to confirm whether or not this can be done.  If no one responds here I will reach out ot them next week and find out for you


    Thanks,

    Jon Israel

    Principal Support Engineer

    CA Technologies



  • 4.  Re: Swing Box Migration Method for CA Service Desk Manager

    Broadcom Employee
    Posted Jun 23, 2014 12:12 AM

    Hi Fred/Jon,

     

    There is no similar swing box document for Catalog upgrades at this point. Note, however, that Catalog does support a migration model upgrade which uses a similar method to the one that the Service Desk swing box method uses. This means that you can do a clean install of Catalog on new hardware and use an existing mdb which will then be upgraded at configuration time. It's documented in the Implementation Guide.

     

    Implementation Guide Release 12.9.00

     

    Regards,

    Gordon Preston



  • 5.  Re: Swing Box Migration Method for CA Service Desk Manager

    Posted Nov 07, 2014 09:01 AM

    Thanks, Jon.

     

    If there are no changes for this document for r12.9, can the TEC doc be updated to include this in the 'Releases' notes line and body?

     

    JW



  • 6.  Re: Swing Box Migration Method for CA Service Desk Manager

    Posted Jan 18, 2016 06:35 AM

    Hi Jon,

     

    I have referred to your doc but facing issues while upgrading MDB. We are planning to upgrade from 12.5/Sql2005.

     

    I have followed the following steps till now. Please let me know whether we have missed out anything.

     

    We installed Windows Server 2008 R2 with SQL Server 2008>> Installed Service Desk 12.9>> Restored the MDB from 12.5

    While running pdm_configure, it says unable to connect MDB.

     

    Any help or suggestions would be appreciated.

     

    Thanks.



  • 7.  Re: Swing Box Migration Method for CA Service Desk Manager

    Posted Jan 18, 2016 08:11 AM

    Hi SSDCG,  This is because you cannot simply point a 12.9 system at a 12.5 MDB and run configure.  That will not work for two reasons.  First, the database structure is different, and you did not upgrade the database to the 12.9 structure, and second, your data never went through the migration process - which is the part that unfortunately takes the longest, but is the most important - its what takes your data, lays it out into XML files and loads it into the updated structure for 12.9.  Now, if you are currently on 12.5/SQL2005 on Windows 2003, you would first have to replicate your 12.5 environment onto Windows 2008 with SQL 2008, as that would be supported by both 12.5 and 12.9.  Then, you would run the MDB upgrade from the 12.9 install media on the SQL 2008 box.  This would upgrade the MDB to 12.9 format.  Then you would run the application upgrade on the app side, and that will upgrade the application, and then kick off the migration wizard which will migrate your data into the upgraded structure/schema.  Once that is complete, pdm_configure will kick off and you should be good to go.   As for the reasons for not connecting to the MDB, there could be several.  First, when you copy an MDB from one environment to another, you must fix the orphaned sql user (which is documented in the swing box document).  The other reason could be that you dont have the SQL client installed on the 12.9 application box.  However, without doing a proper upgrade/migration as the document states, none of this would work, so you have to go back and do this the proper way first.

    Lastly, as a side note, if you are in the testing phase you should think about going to 14.1 instead of 12.9.  There are a lot of improvements, and you would be on the latest version of the product at that point.

    Hope this helps,

    Thanks,

    Jon I.



  • 8.  Re: Swing Box Migration Method for CA Service Desk Manager

    Posted Jan 19, 2016 03:09 AM

    Jon,

    Thanks so much for your suggestions. Much appreciated.

     

    I had already tried 14.1 upgrade but that was also unsuccessful hence i thought of giving 12.9 a try.

    I guess the problem is i didn't  replicate my prod server on the swing environment.

     

    Please confirm the following -

    Can I upgrade to 14.1 directly once I replicate my prod server on Swing or do I need to upgrade step wise.

     

    Also, please note we have both BOXI and SDM on same box as it is a small set up. Will it support on the same box??

     

    Thanks in adv.



  • 9.  Re: Swing Box Migration Method for CA Service Desk Manager

    Posted Jan 19, 2016 08:41 AM

    Correct, you can upgrade directly to 14.1 without a problem.  As for BOXI, we never recommend using BOXI on the same box as service desk just due to the shear size and resources that BOXI uses.  BOXI really should be installed on its own sever for optimal performance of both SDM and BOXI.

    Thanks,

    Jon I.



  • 10.  Re: Swing Box Migration Method for CA Service Desk Manager

    Posted Jan 23, 2016 03:43 AM

    Hi Jon,

    Can you please elaborate more on Step 13.- "After pdm_publish is completed, all data on custom tables will be removed.
    When running pdm_publish, it drops ta custom tables and recreate them. As a result, the data on the tables will be removed.
    You need to load the data from the original MDB to the new one by running pdm_extract/pdm_load commands. "

     

    Thanks



  • 11.  Re: Swing Box Migration Method for CA Service Desk Manager

    Broadcom Employee
    Posted Jan 24, 2016 11:17 PM

    Hi SSDCG,

     

    The pdm_publish will drop and re-create  your custom z tables as part of the publish process. This leaves you with those z tables, but with no data in them.

     

    In order to re-load the data, you'll need copy it from the mdb that you used to create the swing box mdb. (from production for example). Simply run a pdm_extract on the production mdb (e.g. pdm_extract ztest > ztest.dat) and copy the extracted file (ztest.dat) over to the new server where the pdm_publish was run and load it into the new mdb using pdm_load (pdm_load -f ztest.dat) as described in this tec doc.

     

    Hope this clarifies for you.

     

    Gordon.



  • 12.  Re: Swing Box Migration Method for CA Service Desk Manager

    Posted Jan 25, 2016 03:09 AM

    Hi Gordon/Jon,

     

    I am not very sure of the custom tables as it was done  by a third party vendor for us.

    How do I check the custom tables in order to extract data from them.

     

    Thanks.



  • 13.  Re: Swing Box Migration Method for CA Service Desk Manager

    Posted Jan 30, 2016 03:25 AM

    Hi Jon,

    As I am unsure of the tables, Can I take a backup of wspcol.dat and wsptbl.dat and update in the target server? Will that work?

    Please suggest.



  • 14.  Re: Swing Box Migration Method for CA Service Desk Manager

    Broadcom Employee
    Posted Jan 31, 2016 05:42 PM

    Hi SSDCG

     

    Check the wsp_schema.log file in the NX_ROOT\site\mods folder. It lists the custom tables and columns that are added via a pdm_publish.

     

    Hope that this helps.

    Gordon



  • 15.  Re: Swing Box Migration Method for CA Service Desk Manager

    Posted Feb 05, 2016 03:19 AM

    Hi Gordon,

     

    I found few tables listed in wsp_schema.log. When I run the pdm_extract command, it gave an error" it is not a recognizable table"

    Please see the screen shot attached

     

    zsla.JPG

    Can I proceed with copying site/mods folder?



  • 16.  Re: Swing Box Migration Method for CA Service Desk Manager

    Posted Feb 05, 2016 12:26 PM

    Please show us your wsp_schema.log



  • 17.  Re: Swing Box Migration Method for CA Service Desk Manager

    Posted Feb 06, 2016 12:01 AM

    2013.02.07 17:59:21 created column Call_Req.zcomments_sla

    2013.02.07 17:59:24 created column Call_Req.zhold_comments

    2013.02.07 17:59:26 created column Call_Req.zproblem_review_comments

    2013.02.07 17:59:29 created column Call_Req.zreopen_comments

    2013.02.07 17:59:32 created column Call_Req.zresolution_comments

    2013.02.07 17:59:35 created column Call_Req.ztime_sec

    2013.02.07 17:59:37 created column Call_Req.zwait_flag

    2013.02.07 17:59:40 created column Call_Req.zwait_time

    2013.02.11 16:58:25 created column Call_Req.zSecurity_incident

    2013.02.18 14:05:13 created column Call_Req.zsecurity_in



  • 18.  Re: Swing Box Migration Method for CA Service Desk Manager

    Posted Feb 07, 2016 11:38 PM

    Those wsp_schema.log records are for the creation of custom columns rather than custom tables.  It may be that there are not in fact any custom tables. 
    Can you run this command to check that?
    pdm_extract wsptbl
    If that returns nothing then you probably don't have to worry about tables.
    As an extra check please run this:
    bop_sinfo -d cr | find /I "z"
    Look at the definitions of the 'z' columns that are extracted.  Are any of them are shown as 'SREL' to another table with a 'z' leading its name?  Again, if not then you are in the clear...
    Regards, James



  • 19.  Re: Swing Box Migration Method for CA Service Desk Manager

    Posted Feb 08, 2016 02:02 AM

    Thanks James for your reply.

    Please see the attachment after running the command.wsptbl.JPG



  • 20.  Re: Swing Box Migration Method for CA Service Desk Manager

    Posted Feb 08, 2016 03:52 AM

    OK, you have no custom tables relating to the Call_Req table ('cr' object).
    However, there seems to be a table called 'act_type_assoc' which was not created using Web Screen Painter. 
    (If it was created with WSP its name would start with a 'z'.) 
    So I'd suggest do this as well:
    pdm_extract wspcol
    and this:
    pdm_extract act_type_assoc
    And also look up act_type_assoc in Web Screen Painter / Tools / Schema Designer just in case there are any helpful comments associated with it, so we can work out what its purpose is.



  • 21.  Re: Swing Box Migration Method for CA Service Desk Manager

    Posted Feb 08, 2016 05:00 AM

    Thanks James for prompt response.

    When i run pdm_extract act_type_assoc it says "it is not recognizable table"

    however wspcol gave me lots of details which is attached for your reference

     

     

    :\> pdm_extract wspcol

    ABLE wspcol

           addl_info column_name dbms_name description display_name id is_cluster i

    _descending

           is_indexed is_local is_not_null is_order_by is_required is_serv_prov is_

    key

           is_unique is_write_new is_wsp last_mod_by last_mod_dt on_ci_set on_new_d

    fault

           persid schema_name serv_prov_code status string_len table_name type ui_i

    fo

           xrel_table

           { "" ,"zcomments_sla" ,"" ,"" ,"zcomments_sla" ,"400001" ,"0" ,"0" ,"0",

     

           "0" ,"0" ,"0" ,"0" ,"0" ,"0" ,"0" ,"0" ,"1",

           "3F49B2692D87C44E9AD749AF33CDB62D" ,"02/07/2013 17:54:30" ,"" ,"",

           "wspcol:400001" ,"zcomments_sla" ,"0" ,"3" ,"1000" ,"cr" ,"2" ,"" ,"" }

           { "" ,"zhold_comments" ,"" ,"" ,"zhold_comments" ,"400002" ,"0" ,"0" ,"0

    ,

           "0" ,"0" ,"0" ,"0" ,"0" ,"0" ,"0" ,"0" ,"1",

           "3F49B2692D87C44E9AD749AF33CDB62D" ,"02/07/2013 17:54:30" ,"" ,"",

           "wspcol:400002" ,"zhold_comments" ,"0" ,"3" ,"1000" ,"cr" ,"2" ,"" ,"" }

     

           { "" ,"zproblem_review_comments" ,"" ,"" ,"zproblem_review_comments",

           "400003" ,"0" ,"0" ,"0" ,"0" ,"0" ,"0" ,"0" ,"0" ,"0" ,"0" ,"0" ,"1",

           "3F49B2692D87C44E9AD749AF33CDB62D" ,"02/07/2013 17:54:30" ,"" ,"",

           "wspcol:400003" ,"zproblem_review_comments" ,"0" ,"3" ,"1000" ,"cr" ,"2"

    ,"" ,"" }

           { "" ,"zreopen_comments" ,"" ,"" ,"zreopen_comments" ,"400004" ,"0" ,"0"

     

           "0" ,"0" ,"0" ,"0" ,"0" ,"0" ,"0" ,"0" ,"0" ,"1",

           "3F49B2692D87C44E9AD749AF33CDB62D" ,"02/07/2013 17:54:30" ,"" ,"",

           "wspcol:400004" ,"zreopen_comments" ,"0" ,"3" ,"1000" ,"cr" ,"2" ,"" ,""

    }

           { "" ,"zresolution_comments" ,"" ,"" ,"zresolution_comments" ,"400005",

           "0" ,"0" ,"0" ,"0" ,"0" ,"0" ,"0" ,"0" ,"0" ,"0" ,"0" ,"1",

           "3F49B2692D87C44E9AD749AF33CDB62D" ,"02/07/2013 17:54:30" ,"" ,"",

           "wspcol:400005" ,"zresolution_comments" ,"0" ,"3" ,"1000" ,"cr" ,"2" ,""

    ,"" }

           { "" ,"ztime_sec" ,"" ,"" ,"ztime_sec" ,"400006" ,"0" ,"0" ,"0" ,"0" ,"0

    ,

           "0" ,"0" ,"0" ,"0" ,"0" ,"0" ,"1" ,"3F49B2692D87C44E9AD749AF33CDB62D",

           "02/07/2013 17:54:30" ,"" ,"0" ,"wspcol:400006" ,"ztime_sec" ,"0" ,"3" ,

    0",

           "cr" ,"1" ,"" ,"" }

           { "" ,"zwait_flag" ,"" ,"" ,"zwait_flag" ,"400007" ,"0" ,"0" ,"0" ,"0",

           "0" ,"0" ,"0" ,"0" ,"0" ,"0" ,"0" ,"1" ,"3F49B2692D87C44E9AD749AF33CDB62

    ",

           "02/07/2013 17:54:30" ,"" ,"" ,"wspcol:400007" ,"zwait_flag" ,"0" ,"3" ,

    0",

           "cr" ,"1" ,"" ,"" }

           { "" ,"zwait_time" ,"" ,"" ,"zwait_time" ,"400008" ,"0" ,"0" ,"0" ,"0",

           "0" ,"0" ,"0" ,"0" ,"0" ,"0" ,"0" ,"1" ,"3F49B2692D87C44E9AD749AF33CDB62

    ",

           "02/07/2013 17:54:30" ,"" ,"" ,"wspcol:400008" ,"zwait_time" ,"0" ,"3" ,

    0",

           "cr" ,"4" ,"" ,"" }

           { "" ,"zSecurity_incident" ,"" ,"" ,"zSecurity_incident" ,"400009" ,"0",

     

           "0" ,"0" ,"0" ,"0" ,"0" ,"0" ,"0" ,"0" ,"0" ,"0" ,"1",

           "3F49B2692D87C44E9AD749AF33CDB62D" ,"02/11/2013 16:52:41" ,"" ,"0",

           "wspcol:400009" ,"zSecurity_incident" ,"0" ,"3" ,"0" ,"cr" ,"3" ,"" ,"bo

    l" }

           { "" ,"zsecurity_in" ,"" ,"" ,"zsecurity_in" ,"400010" ,"0" ,"0" ,"0",

           "0" ,"0" ,"0" ,"0" ,"0" ,"0" ,"0" ,"0" ,"1",

           "3F49B2692D87C44E9AD749AF33CDB62D" ,"02/18/2013 14:03:14" ,"" ,"0",

           "wspcol:400010" ,"zsecurity_in" ,"0" ,"3" ,"0" ,"cr" ,"3" ,"" ,"bool" }

    spcol

           rows:10

     

    Please suggest.

     

    Thanks!!



  • 22.  Re: Swing Box Migration Method for CA Service Desk Manager

    Posted Feb 08, 2016 08:35 PM

    OK, based on that information I think we can safely say that you have no custom tables, only some columns added to the Call_Req table / 'cr' object.  You should (says he, hopefully) not need to worry about losing data from custom tables.
    Good luck with the rest of your migration, please keep the community posted about how it goes and if you hit any further snags.
    Regards,
    James



  • 23.  Re: Swing Box Migration Method for CA Service Desk Manager

    Posted Feb 10, 2016 06:28 AM

    Thanks James,

    I have replicated my prod swing successfully.

    Now I am ready to upgrade to 14.1. Please confirm me the following -- Should CABI be installed before 14.1 installation ? In my prod we had 12.5 with CABI in the same box.



  • 24.  Re: Swing Box Migration Method for CA Service Desk Manager

    Broadcom Employee
    Posted Feb 10, 2016 06:38 AM

    CABI needs to be installed on its own server for performance reasons.

     

    You can install CABI anytime but you won't be able to integrate with SDM until you upgrade to 14.1.

     

    Paul

     

    Principal Support Engineer



  • 25.  Re: Swing Box Migration Method for CA Service Desk Manager

    Posted Apr 09, 2018 09:36 AM

    Dear Jon,

     

    I have the following scenario: I have to migrate a CA SDM 12.5 installation to the last version (17.1). The database is currently SQL Server 2008 (remote). The problem is that CA SDM 17.1 only supports SQL Server 2012 or newer. So my question is: what version of SQL server must I install in the SWING box?
    As I can see:
    - If I install SQL 2008 it will not be supported for 17.1.
    - If I install SQL 2012 or newer it will not be supported for 12.5 (initial clone installation), and there would be issues for migrating mdb from a SQL 2008 to SQL 2012 or never.
    So what is the right way to perform the swing migration?



  • 26.  Re: Swing Box Migration Method for CA Service Desk Manager

    Broadcom Employee
    Posted Apr 09, 2018 01:05 PM

    Pablo,

     

    If you need to change Database versions or Operating Systems, it adds an extra step to the process for each major change. For a scenario like yours, you would need to do a multi-step migration like the following:

    1. Make a copy of the current SDM 12.5 on SQL 2008, then upgrade that to...
    2. SDM 14.1 on SQL 2008. This is a good 'stepping stone' release as it supports SQL 2008 and 2012. Upgrade from here to...
    3. SDM 14.1 on SQL 2012. This gets your database up to SQL 2012, which is compatible with 17.1. From here, do the last upgrade to...
    4. SDM 17.1 on SQL 2012. This is your final 'swing' system that can be copied over to your new fresh production environment, with SDM 17.1 on SQL 2012.

    Please keep in mind that this doesn't account for any incompatibilities in Operating Systems as well; if you need to change the OS too, then that will add another swing step. It's generally recommended to only change one aspect of the environment at once to minimize the number of confounding factors. If you're not sure if a version is supported with a particular OS or Database system, you can consult the Supportability Matrix, or the certification document that came with releases prior to 14.1.

    Supportability Matrix - SDM 14.1

    Supportability Matrix - SDM 17.1



  • 27.  Re: Swing Box Migration Method for CA Service Desk Manager

    Posted Feb 08, 2016 10:38 AM

    Jon and the Community,

     

    What is best practice or common wisdom when you want to combine a migration with a change in architecture from Conventional to Advanced Availability (AA)?

    Using the existing TECDOC, but making these changes:

     

    1. Build NEW PROD systems first as the AA systems Background, Standby, and Applications as core 14.1.02. Validate core functions.

    2. Set the Standby, and App servers to inactive in the Configuration.

    3. Change the Background to Primary (I don't need Secondary servers to complete migration)

    4. Complete the SWINGBOX migration on NEW PROD Primary as the target as defined in the TECDOC..

    3. Change Primary to Background. Test migrated functions

    4. Reactivate AA Configuration servers.  (Run pdm_configure and have Version Control set to Update to pick up changes. OR manually copy site/mods the same as PROD. ??)

     

    This is to eliminate the need to build AA servers as part of the GO-LIVE day.

     

    Afterwards, do an Environment Promotion from NEW PROD to NEW DEV and NEW QA. (Not part of SWINGBOX).

     

    J.W.



  • 28.  Re: Swing Box Migration Method for CA Service Desk Manager

    Posted Feb 11, 2016 07:02 AM

    I upgraded to 14.1 and there were no error during the upgrade process. However when I am trying to open SDM web client it shows a blank page.

    What could be the problem? All the services are running fine.



  • 29.  Re: Swing Box Migration Method for CA Service Desk Manager

    Broadcom Employee
    Posted Feb 11, 2016 07:31 AM

    SSDCG,

    Maybe the SDM URL needs to be added to the Trusted Sites list on the browser?

    _R



  • 30.  Re: Swing Box Migration Method for CA Service Desk Manager

    Posted Feb 11, 2016 12:13 PM

    Double check the IIS Service.  There are notes for post-installation checks and one is about restarting IIS.  (It seems to keep moving in the Wiki)

     

    J.W.



  • 31.  Re: Swing Box Migration Method for CA Service Desk Manager

    Posted Feb 12, 2016 02:35 AM

    Hi All,

     

    I checked the services and trusted zone as well.

    It was working before the upgrade when I had replicated the prod swing. Once I upgraded to 14.1 and ran pdm_configure, it gave me errors.