How to migrate CA Service Desk Manager (CA SDM) changes made in Web Screen Painter (WSP)

Products

• CA Service Desk Manager
• CA Service Management - Service Desk Manager

Issue/Introduction

In many environments, it is customary to develop CA SDM changes in a test environment first, before moving the changes over to a production environment.

This document discusses the actions one would generally follow to copy a set of custom CA SDM changes between two different CA SDM environments.

Environment

CA Service Desk Manger

All Versions

Resolution

Please review the following first:

• The Originating Server is defined here as the CA SDM server whose customizations you wish to copy over
• The Target Server is defined here as the CA SDM server that will be receiving the customizations
• Please make sure you have made a backup of all affected CA SDM servers before running through the steps, including the CA SDM environment and the backend MDB database.
• The Target Server will need to have its CA SDM services recycled.  Please make sure you have scheduled any appropriate outages or downtime.
• These instructions are intended for WSP and Schema Designer specific changes ONLY.  Any custom changes made outside of WSP or Schema Designer are not warranted or guaranteed to be copied via the given instructions.
• Please do not use these instructions to move custom changes between dissimilar releases of CA SDM (i.e. copying changes between CA SDM 17.1 and CA SDM 17.3).  Copying of table data between two different versions of CA SDM is unsupported.
• All custom WSP/Schema Designer changes that exist on the Originating Server will be copied to the Target Server.  This includes any incomplete tables or forms that may exist in the Originating Server. 
• There is a risk that existing changes on the Target Server may be overwritten or corrupted if they contradict changes developed in the Originating Server.

To copy WSP/Schema Designer changes:

Originating Server

1.  At a Administrator command prompt, run the following commands:

pdm_extract wspcol > wspcol.dat
pdm_extract wsptbl > wsptbl.dat

OPTIONAL:

If you wish to also copy the data from the custom table(s), run pdm_extract against any custom tables whose content you also wish to bring over. 

For example, if you have a custom table called "zTestTable", run the command:

pdm_extract zTestTable > ztbl1.dat

2.  Acquire the NX_ROOT/site/mods directory in a zip file (i.e. site-mods.zip)

3.  Copy to the Target Server the following from the Originating Server:

wspcol.dat 
wsptbl.dat
site-mods.zip
Any optional custom table extracts (i.e.  ztbl1.dat)

Target Server

1.  Copy the existing NX_ROOT/site/mods directory to a backup location.

2.  With CA SDM Services running, run the following commands to backup the existing wspcol and wsptbl tables:

pdm_extract wspcol > wspcol-back.dat
pdm_extract wsptbl > wsptbl-back.dat

3.  Load in the new tables' content by using the files created from the Originating Server:

pdm_load -f wspcol.dat
pdm_load -f wsptbl.dat

4.  Login to Web Screen Painter, select any table and make a small "dummy" update to its description (such as adding a space at the end)

5.  Perform a Save and Publish action.

6.  Rename the file NX_ROOT/site/mods/wsp_schema.log to wsp_schema_log.old 

7.  Stop CA SDM Services and run pdm_publish to bring in the new table and field definitions.

8.  Copy the contents of the site-mods.zip to the corresponding NX_ROOT/site/mods location in the Target Server.

9.  Restart CA SDM Services

OPTIONAL:

Please load any optional table extracts you may have  (i.e. pdm_load -f ztbl1.dat)

Additional Information

How to Modify Schema Using Web Screen Painter