We are currently using r12.7 in our environment and planning to upgrade to 17.1, few queries regarding the same:
1. Is the latest version stable? What are the common issues faced?
2. Can we follow the swing box approach to upgrade directly from r12.7 to r17.1? or should the upgrade be like r12.7 to r14.1 then r14.1 to r17.1
The latest SDM version is 17.0. SDM 17.1 is expected to be released during the first half of this calendar year.
Yes, you can use the SWING BOX approach to upgrade to 17.0 from 12.7.
Here is the documentation that outline the steps: Use the Swing Box Method to Upgrade/Migrate to CA SDM 17.0 - CA Service Management - 17.0 - CA Technologies Documentatio…
Had few more queries:
As of now below is the environment of the current production system:
App : CA SDM r12.7
DB : MS SQL 2008 Standard Edition(SP3)
OS : Windows 2008 R2
Since we have to create Swing system, I was wondering if we can use MS SQL 2012 for r12.7 CA SDM version?
https://support.ca.com/phpdocs/0/8165/8165_r127_CertMatrix.pdf says that a patch needs to be installed if we are using 2012. Can you please confirm on this?
As per the Supportability matrix of r17.0 MS SQL 2008 is not supported hence the query!
As far as OS is concerned we are planning to install Windows 2012 as both versions support the same.
Also, please let me know if there are any other compatibility checks that needs to be considered before proceeding with the upgrade.
Thanks a lot of the document Paul! I'll go through the same.
Use the Swing Box Method to Upgrade/Migrate to CA SDM 17.0 - CA Service Management - 17.0 - CA Technologies Documentatio…
Refer steps 6,7 & 22,23 from the above link, this seems to be repeated. When are we supposed to place both the back up in the Swing system? if we are placing the same during step 6 & 7, then I believe the contents of the customized table wont be deleted/truncated as the required .sch and wsp.mods files are already available.
One way to install SDM r12.7 against SQL 2012 without resorting to patching would be to install 'SQL Connectivity' on the swing server from SQL 2008 media before installing r12.7. You should end up with the MDB on your SQL 2012 server but with database compatibility set at SQL 2008. You can then upgrade SQL Connectivity on Swing to SQL 2012 and set the MDB compatibility to SQL 2012 before starting the r17 upgrade.
With regard to SQL 2008 compatibility, I have a swing system, originally r12.7, that upgraded in-place to r17 on SQL 2008 SP4 with no issues. However, given that SQL2008 is not in the supportability matrix for r17 then you would clearly be better advised (and supported) to go with SQL2012.
Hope that helps :-)
Just to add that each Service Management product has their own upgrade requirements. If you're only using SDM then you're OK. If you're using Catalog or other pieces be sure to check their upgrade requirements
No problem Pushpith.
Let us know if you have any additional questions after reviewing the documentation.
I agree with you regarding steps 17 and 18. The customised tables should remain intact, and pdm_publish should not try to re-create their columns, as long as you have copied wsp_schema.log, wsp_schema.sch and wsp.mods, all of which will be copied along with the other contents of site\mods. I am logging a comment against those steps in 'docops' as the statements there seem to be incorrect.
To avoid losing other options on 'pdm_configure', ensure you edit the templates for web.cfg and pdm_startup - noting that their templates are in the folder samples\pdmconf rather than in bopcfg\www and pdmconf. It might also be advisable to carefully review your NX.env and prepare a script with 'pdm_options_mgr' commands, to re-apply any updates that you can see that are not done through Options Manager. Remember to duplicate the commands, with one copy sending the '-t' flag to apply the update to the NX.env template.
It is not clear to me either why you would copy attachments and site\mods twice, in steps 6/7 and 22/23. The first copy (steps 6 & 7) should be enough.
Paul_Coccimiglio Can you please check the below query and revert