Steps to building a R11.2 Test System - Revision history

Gityerfix at 12:42, 29 October 2008

2008-10-29T12:42:03Z

Gityerfix at 00:55, 27 July 2008

2008-07-27T00:55:54Z

Gityerfix at 05:35, 26 July 2008

2008-07-26T05:35:26Z

Gityerfix at 05:34, 26 July 2008

2008-07-26T05:34:54Z

Gityerfix at 14:16, 18 July 2008

2008-07-18T14:16:41Z

Gityerfix at 14:14, 18 July 2008

2008-07-18T14:14:34Z

Eziril at 17:02, 15 July 2008

2008-07-15T17:02:00Z

Gityerfix at 13:02, 5 July 2008

2008-07-05T13:02:42Z

Revans at 13:37, 12 June 2008

2008-06-12T13:37:32Z

Gityerfix at 04:20, 10 June 2008

2008-06-10T04:20:30Z

← Older revision		Revision as of 12:42, 29 October 2008
Line 53:		Line 53:
	#apply patches		#apply patches

−	~~If any questions on this please email me, danegrey~~	+	== See Also ==
		+	[[Migrating Schema Changes Between Systems]]

@@ Line 1: / Line 1: @@
 __NOTOC__
 [[Category:Installation]]
-<div align='center'><font color="green">To make corrections or additions to this article, select the ''edit'' tab above.<br>
+{{Global Header}}
-To discuss or ask questions about this article, select the ''discussion'' tab above.</font></div>
+{{Global Announcement}}
 == Overview ==

@@ Line 12: / Line 12: @@
 Steps to go from migrated R11.x system to a R11 test system
 #install the base product
 #run the [[pdm_configure]] to setup and ensure the environment is correct.

@@ Line 1: / Line 1: @@
 [[Category:Installation]]
 The following are the steps I have used to build several test systems.
@@ Line 6: / Line 11: @@
 Steps to go from migrated R11.x system to a R11 test system
 #install the base product
@@ Line 49: / Line 53: @@
 If any questions on this please email me, danegrey

@@ Line 9: / Line 9: @@
 #install the base product
-#run the pdm_configure to setup and ensure the environment is correct.
+#run the [[pdm_configure]] to setup and ensure the environment is correct.
-#backup $nx_root/site/mods  on the production system
+#backup [[$NX_Root]]/site/mods  on the production system
 #do the following extract on production
 #*pdm_extract wspcol > wspcol.txt
@@ Line 17: / Line 17: @@
 #*pdm_load -f wspcol.txt
 #*pdm_load -f wsptbl.txt
-#delete the file $nx_root/site/mods/wsp_schema.log  (may not be present)
+#delete the file  [[$NX_Root]]/site/mods/wsp_schema.log  (may not be present)
-#log on to the wsp
+#log on to the [[Web Screen Painter]]
-##open the schema designer
+##open the [[Schema Designer]]
 ##open any table and make a dummy update (e.g. the description some place)
 ##choose 'File' -> 'Save and Publish'
 ##shutdown the Unicenter Service Desk services
-##run pdm_publish
+##run [[pdm_publish]]
 ##start the Unicenter Service Desk services
 ##check for any errors
@@ Line 30: / Line 30: @@
 ##*verify that any schema changes are in place
 ##check the ddict.sch found in $nxroot\site	verify fields are in the ddict
-#copy $nx_root/site/mods to the test system  (see step 3)
+#copy [[$NX_Root]]/site/mods to the test system  (see step 3)
-#run the pdm_configure to setup and ensure the environment is correct.
+#run the [[pdm_configure]] to setup and ensure the environment is correct.
-#*check ddict.sch found in $nxroot/site, to make sure that the fields were added correctly
+#*check ddict.sch found in [[$NX_Root]]/site, to make sure that the fields were added correctly
 #restore the database using SQL
 #change the database name in the following table
@@ Line 43: / Line 43: @@
 #*SQL Command is update dbo.usp_contact SET c_cm_idx = 1801
 #reboot the server
-#before running pdm_configure, check the following
+#before running [[pdm_configure]], check the following
 #*User ServiceDesk is active and available
 #*Update ServiceDesk in the SQL database

@@ Line 13: / Line 13: @@
 #do the following extract on production
 #*pdm_extract wspcol > wspcol.txt
-#*pdm_extract wsptab > wsptbl.txt
+#*pdm_extract wsptbl > wsptbl.txt
 #restore the wspcol / wsptab to the test system
 #*pdm_load -f wspcol.txt

← Older revision		Revision as of 13:02, 5 July 2008
Line 1:		Line 1:
		+	[[Category:Installation]]
	The following are the steps I have used to build several test systems.		The following are the steps I have used to build several test systems.

@@ Line 4: / Line 4: @@
 The existing mdb is copied over using the SQL restore.
-	Steps to go from migrated R11.x system to a R11 test system
+#install the base product
+#run the pdm_configure to setup and ensure the environment is correct.
+#backup $nx_root/site/mods  on the production system
+#do the following extract on production
-	install the base product		<br>
+#*pdm_extract wspcol > wspcol.txt
-	run the pdm_configure to setup and ensure the environment is correct.		<br>
+#*pdm_extract wsptab > wsptab.txt
-	backup $nxroot/site/mods  on the production system			<br>
+#restore the wspcol / wsptab to the test system
-	 do the following extract on production					<br>
+#*pdm_load -f wspcol.txt
-.1	 pdm_extract wspcol > wspcol.txt				<br>
+#*pdm_load -f wsptbl.txt
-.2	 pdm_extract wsptab > wsptab.txt				<br>
+#delete the file $nx_root/site/mods/wsp_schema.log  (may not be present)
-	restore the wspcol / wsptab to the test system			<br>
+#log on to the wsp
-.1	 pdm_load -f wspcol.txt					<br>
+##open the schema designer
-.2	 pdm_load -f wsptbl.txt					<br>
+##open any table and make a dummy update (e.g. the description some place)
-	delete the file $nxroot/site/mods/wsp_schema.log  (maybe not present)		<br>
+##choose 'File' -> 'Save and Publish'
-	 log on to the wsp			<br>
+##shutdown the Unicenter Service Desk services
-.1	 open the schema designer	<br>
+##run pdm_publish
-.2	 open any table and make a dummy update (e.g. the description some place)	<br>
+##start the Unicenter Service Desk services
-.3	 choose 'File' -> 'Save and Publish'					<br>
+##check for any errors
-.4	 shutdown the Unicenter Service Desk services		<br>
+##sign on to Service Desk
-.5	 run pdm_publish					<br>
+##sign on to sql visual studio
-.6	 start the Unicenter Service Desk services		<br>
+##*verify that any schema changes are in place
-.7	 check for any errors					<br>
+##check the ddict.sch found in $nxroot\site	verify fields are in the ddict
-.8	 sign on to Service Desk				<br>
+#copy $nx_root/site/mods to the test system  (see step 3)
-.9	 sign on to sql visual studio				<br>
+#run the pdm_configure to setup and ensure the environment is correct.
-.9.1	verify that any schema changes are in place	<br>
+#*check ddict.sch found in $nxroot/site, to make sure that the fields were added correctly
-.10	 check the ddict.sch found in $nxroot\site	verify fields are in the ddict		<br>
+#restore the database using SQL
-	copy $nxroot/site/mods to the test system  (see step 3)			<br>
+#change the database name in the following table
-	run the pdm_configure to setup and ensure the environment is correct.	<br>
+#*dlgtsrv table
-.1	 check ddict.sch found in $nxroot/site, to make sure that the fields were added correctly	<br>
+#*#change the primary server name to the test server name
-	 restore the database using SQL			<br>
+#*#*sym	from production name  to test name
-	 change the database name in the following table	<br>
+#*#*server from production name  to test name
-.1	 dlgtsrv table				<br>
+#change all the notifications in the usp_contact record to 'Notification'
-.1.2	change the primary server name to the test server name		<br>
+#*c_cm_id1, c_cm_id2, c_cm_id3, c_cm_id4
-.1.2.1	sym	from production name  to test name	<br>
+#*SQL Command is update dbo.usp_contact SET c_cm_idx = 1801
-.1.2.2	server	from production name  to test name	<br>
+#reboot the server
-	 change all the notifications in the usp_contact record to 'Notification'	<br>
+#before running pdm_configure, check the following
-.1  c_cm_id1, c_cm_id2, c_cm_id3, c_cm_id4		<br>
+#*User ServiceDesk is active and available
-.2	SQL Command is update dbo.usp_contact SET c_cm_idx = 1801		<br>
+#*Update ServiceDesk in the SQL database
-	 reboot the server	<br>
+#apply patches
-	 before running pdm_configure, check the following	<br>
-.1	 User ServiceDesk is active and available		<br>
-.2	 Update ServiceDesk in the SQL database			<br>
-								<br>
-	Patches		apply patches			<br>
-				<br>
-−
 If any questions on this please email me, danegrey