Migrating Schema Changes Between Systems
From SDU
Revision as of 09:57, 18 September 2008 by Kowy (Talk | contribs) (New page: == 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 product...)
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 1. Save all changes 1. Select File - Save and Publish in Schema Designer 1. 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 1. $NX_ROOT/site/mods/majic/wsp.altercol 1. $NX_ROOT/site/mods/majic/wsp.altertbl 1. $NX_ROOT/site/mods/majic/wsp_index.sch 1. $NX_ROOT/site/mods/majic/wsp_schema.sch 1. wsptbl.txt (extracts from previous step) 1. wspcol.txt (extracts from previous step)
1. On the destination server run
pdm_load -if wsptbl.txt pdm_load -if wspcol.txt
1. Stop Service Desk 1. Run pdm_publish
pdm_publish
1. Run Service Desk
