Migrate WSP changes to a new server
Article ID: 32106
Updated On:
Products
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. Conversely, there may be a need to clone an existing environment, to establish a testing instance.
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 Environment is defined here as the CA SDM Environment whose customizations you wish to copy over
- The Target Environment is defined here as the CA SDM Environment that will be receiving the customizations.
- Please make sure you have made a backup of all Target Environment servers before running through the steps, including the CA SDM installs and the backend MDB database. A snapshot of the given servers is recommended.
- The Target Environment will need to have its CA SDM services stopped and 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, such as copying changes between CA SDM 17.1 and CA SDM 17.3. Copying of table or form 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 Environment
The following commands should be performed on the Primary server for Conventional or the active Background server for Advance Availability.
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 Environment
For Conventional environments, the following commands should be performed on the Primary server for Conventional. Stop all Secondary Servers before proceeding.
For Advance Availability environments, the following commands should be performed on the active Background server unless otherwise indicated. Stop all Application servers and Standby servers before proceeding. The instructions provided are not compatible with rolling maintenance methodologies.
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 and access Schema Designer
5. Perform a Save and Publish action.
6. Rename the file NX_ROOT/site/mods/wsp_schema.log to wsp_schema_log.old (skip this step if the Target environment is a new SDM install instance, which would lack this file)
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 Environment.
For Conventional environments, copy the site-mods.zip content to all secondary servers.
For Advance Availability environments, copy the site-mods.zip content to all standby and application servers.
9. Restart CA SDM Services
OPTIONAL:
Please load any optional table extracts you may have (i.e. pdm_load -f ztbl1.dat)
Additional Information
We recommend testing the above instructions in a non-production instance to familiarise yourself. The simplest way to understand the process is to try with a Target environment that is comprised of a new single Conventional SDM Server instance connected to a new database instance with only default data loaded.
Feedback
