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. Alternatively, one may consider developing a "mirror" of an existing CA SDM environment's custom changes for testing purposes. This document discusses the actions one would generally follow to copy a set of custom CA SDM changes between two different CA SDM installations
Please review the following before running through the steps:
- 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.
- Ideally, the Target Server should not have any custom changes in place or its changes are purely a subset of changes in place in the Originating Server, with no unique changes of its own.
- 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 to have its CA SDM services cycled. Please make sure you have scheduled any appropriate outages or downtime to perform these steps.
- 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 12.7 to CA SDM 14.1). 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:
- At a command prompt, run the following commands:
pdm_extract wspcol > wspcol.dat
pdm_extract wsptbl > wsptbl.dat
OPTIONAL: Please run pdm_extract against any custom tables whose content you also wish to bring over.
Example: if you have a table called "zTestTable", run
pdm_extract zTestTable > ztbl1.dat
- Acquire the NX_ROOT/site/mods directory in a zip file (site-mods.zip)
- Copy to the Target Server the following from Originating Server:
Any optional custom table extracts (i.e. ztbl1.dat)
- Copy the existing NX_ROOT/site/mods directory to a backup location.
- 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
- 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
- Go into WSP and Schema Designer and perform a Save/Publish action.
Note: In older releases of CA SDM (12.6 or earlier), you may need to make a small change in Schema Designer to obtain the Publish action. Simply adding text to a description field in a given attribute should suffice
- Stop CA SDM Services and run pdm_publish to bring in the new table and field definitions.
- Copy the contents of the site-mods.zip to the corresponding NX_ROOT/site/mods location in the Target Server.
- Start CA SDM Services
- OPTIONAL: Please load any optional table extracts you may have, ie:
pdm_load -f ztbl1.dat