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.
CA Service Desk Manger
Please review the following first:
To copy WSP/Schema Designer changes:
1. At a Administrator command prompt, run the following commands:
pdm_extract wspcol > wspcol.dat
pdm_extract wsptbl > wsptbl.dat
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:
Any optional custom table extracts (i.e. ztbl1.dat)
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
Please load any optional table extracts you may have (i.e. pdm_load -f ztbl1.dat)