Migrating Schema Changes Between Systems

Migrate from development to test/production environment

This is deeply described in Modification Guide, but it that routine you must run Web Screen Painter on the destination production server. Here is step by step manual how to do unattended replication:

1. On devel environment open Web Screen Painter and using Schema Designer make your required changes
2. Save all changes
3. Select File - Save and Publish in Schema Designer
4. Extract wspcol and wsptbl tables

pdm_extract wsptbl > wsptbl.txt
pdm_extract -f "SELECT column_name,dbms_name,description,display_name,is_cluster,is_descending,is_indexed, is_local,is_not_null,is_order_by,is_required,is_skey,is_unique,is_write_new,is_wsp,last_mod_dt,on_ci_set,on_new_default, schema_name,status,string_len,table_name,type,xrel_table FROM wspcol" > wspcol.txt

1. Copy these files from source to destination environment (can be done in unattended patch)
   1. $NX_ROOT/site/mods/majic/wsp.mods
   2. $NX_ROOT/site/mods/wsp.altercol
   3. $NX_ROOT/site/mods/wsp.altertbl
   4. $NX_ROOT/site/mods/wsp_index.sch
   5. $NX_ROOT/site/mods/wsp_schema.sch
   6. wsptbl.txt (extracts from previous step)
   7. wspcol.txt (extracts from previous step)
2. On the destination server run

pdm_load -if wsptbl.txt
pdm_load -if wspcol.txt

1. Stop Service Desk
2. Run pdm_publish
3. Run Service Desk

Optional Steps

If you want to save SCH and MOD changes in your own file with better name, follow these steps:

1. Copy content of wsp.mods file to some *.mod in $NX_ROOT/site/mods/majic
2. Copy content of wsp_schema.sch file to some *.sch in $NX_ROOT/site/mods
3. Copy content of wsp_index.sch file to some *.sch in $NX_ROOT/site/mods
4. Delete wsp.mods, wsp_index.sch and wsp_schema files