Migrating Schema Changes Between Systems - Revision history

Gityerfix: Reverted edits by Agegeleruvy (Talk); changed back to last version by Kowy

2010-11-30T05:25:16Z

Reverted edits by Agegeleruvy (Talk); changed back to last version by Kowy

Agegeleruvy at 03:28, 24 November 2010

2010-11-24T03:28:15Z

Kowy at 14:05, 23 April 2009

2009-04-23T14:05:22Z

Kowy: Add "Save and Publish"

2008-09-19T07:40:58Z

Add "Save and Publish"

Gityerfix: /* Overview */

2008-09-18T19:44:58Z

‎Overview

Gityerfix at 19:44, 18 September 2008

2008-09-18T19:44:10Z

Gityerfix: Schema Changes moved to Migrating Schema Changes Between Systems: Already had a Schema Changes Category. The basis for this document is to detail the procedures for migrating schema changes.

2008-09-18T19:20:41Z

Schema Changes moved to Migrating Schema Changes Between Systems: Already had a Schema Changes Category. The basis for this document is to detail the procedures for migrating schema changes.

Kowy at 14:04, 18 September 2008

2008-09-18T14:04:26Z

Kowy: 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...

2008-09-18T09:57:57Z

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...

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 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

@@ Line 1: / Line 1: @@
 __NOTOC__
 [[Category:Customizations]]
@@ Line 24: / Line 16: @@
 === Step 2. Extract WSP Tables ===
-&lt;source lang=&quot;text&quot;&gt;pdm_extract wsptbl &gt; wsptbl.txt
+<source lang="text">pdm_extract wsptbl > wsptbl.txt
-pdm_extract -f &quot;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&quot; &gt; wspcol.txt&lt;/source&gt;
+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</source>
 === Step 3. Copy Files ===
@@ Line 39: / Line 31: @@
 === Step 4. Load Extracts ===
 On the destination server run the following commands:
-&lt;source lang=&quot;text&quot;&gt;pdm_userload -f wsptbl.txt
+<source lang="text">pdm_userload -f wsptbl.txt
-pdm_userload -f wspcol.txt&lt;/source&gt;
+pdm_userload -f wspcol.txt</source>
 === Step 5. Publish Schema changes ===
@@ Line 56: / Line 48: @@
 Because content of wsptbl and wspcol tables on destination server is pointless from now, we can purify these tables using this two commands:
-&lt;source lang=&quot;text&quot;&gt;pdm_load -rf wsptbl.txt
+<source lang="text">pdm_load -rf wsptbl.txt
-pdm_load -rf wspcol.txt&lt;/source&gt;
+pdm_load -rf wspcol.txt</source>

@@ Line 1: / Line 1: @@
 __NOTOC__
 [[Category:Customizations]]
@@ Line 16: / Line 24: @@
 === Step 2. Extract WSP Tables ===
-<source lang="text">pdm_extract wsptbl > wsptbl.txt
+&lt;source lang=&quot;text&quot;&gt;pdm_extract wsptbl &gt; 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</source>
+pdm_extract -f &quot;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&quot; &gt; wspcol.txt&lt;/source&gt;
 === Step 3. Copy Files ===
@@ Line 31: / Line 39: @@
 === Step 4. Load Extracts ===
 On the destination server run the following commands:
-<source lang="text">pdm_userload -f wsptbl.txt
+&lt;source lang=&quot;text&quot;&gt;pdm_userload -f wsptbl.txt
-pdm_userload -f wspcol.txt</source>
+pdm_userload -f wspcol.txt&lt;/source&gt;
 === Step 5. Publish Schema changes ===
@@ Line 48: / Line 56: @@
 Because content of wsptbl and wspcol tables on destination server is pointless from now, we can purify these tables using this two commands:
-<source lang="text">pdm_load -rf wsptbl.txt
+&lt;source lang=&quot;text&quot;&gt;pdm_load -rf wsptbl.txt
-pdm_load -rf wspcol.txt</source>
+pdm_load -rf wspcol.txt&lt;/source&gt;

@@ Line 31: / Line 31: @@
 === Step 4. Load Extracts ===
 On the destination server run the following commands:
-<source lang="text">pdm_load -if wsptbl.txt
+<source lang="text">pdm_userload -f wsptbl.txt
-pdm_load -if wspcol.txt</source>
+pdm_userload -f wspcol.txt</source>
 === Step 5. Publish Schema changes ===
-{{R11 Publish Schema Change}}
+On destination server follow these steps for publishing the schema changes:
 == Optional Steps ==
@@ Line 43: / Line 46: @@
 # Copy content of wsp_index.sch file to some *.sch in [[$NX_ROOT]]/site/mods
 # Delete wsp.mods, wsp_index.sch and wsp_schema files

@@ Line 11: / Line 11: @@
 == Procedures ==
 === Step 1. Make Schema Changes ===
 From your source environment make the desired schema changes via the [[Schema Designer]]. Be sure to follow the proper protocol for publishing your schema changes.
 === Step 2. Extract WSP Tables ===

@@ Line 7: / Line 7: @@
 == Overview ==
-This article provides instructions for setting up an unattended replications.
+This article provides instructions for easily moving schema changes from one environment to another.
 == Procedures ==

@@ Line 1: / Line 1: @@
-== Migrate from development to test/production environment ==
+__NOTOC__
-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:
+[[Category:Customizations]]
-# On devel environment open Web Screen Painter and using Schema Designer make your required changes
+== Overview ==
-# Save all changes
+This article provides instructions for setting up an unattended replications.
-# Select File - Save and Publish in Schema Designer
-# 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
-# Copy these files from source to destination environment ''(can be done in unattended patch)''
-## [[$NX_ROOT]]/site/mods/majic/wsp.mods
-## [[$NX_ROOT]]/site/mods/wsp.altercol
-## [[$NX_ROOT]]/site/mods/wsp.altertbl
-## [[$NX_ROOT]]/site/mods/wsp_index.sch
-## [[$NX_ROOT]]/site/mods/wsp_schema.sch
-## wsptbl.txt ''(extracts from previous step)''
-## wspcol.txt ''(extracts from previous step)''
-# On the destination server run
- pdm_load -if wsptbl.txt
- pdm_load -if wspcol.txt
-# Stop Service Desk
-# Run pdm_publish
-# Run Service Desk
-=== Optional Steps ===
+== Procedures ==
 If you want to save SCH and MOD changes in your own file with better name, follow these steps:
 # Copy content of wsp.mods file to some *.mod in [[$NX_ROOT]]/site/mods/majic

← Older revision	Revision as of 19:20, 18 September 2008
(No difference)