Difference between revisions of "Steps to building a R11.2 Test System"
From SDU
(New page: The following are the steps I have used to build several test systems. It involves getting a sql backup of mdb, with all login's in the backup and then restoring is to a test system that...) |
m |
||
| (11 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| + | __NOTOC__ | ||
| + | [[Category:Installation]] | ||
| + | {{Global Header}} | ||
| + | {{Global Announcement}} | ||
| + | |||
| + | == Overview == | ||
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 10: | ||
The existing mdb is copied over using the SQL restore. | The existing mdb is copied over using the SQL restore. | ||
| + | Steps to go from migrated R11.x system to a R11 test system | ||
| − | + | == Procedures == | |
| − | + | #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 | |
| − | + | #*pdm_extract wspcol > wspcol.txt | |
| − | + | #*pdm_extract wsptbl > wsptbl.txt | |
| − | + | #restore the wspcol / wsptab to the test system | |
| − | + | #*pdm_load -f wspcol.txt | |
| − | + | #*pdm_load -f wsptbl.txt | |
| − | + | #delete the file [[$NX_Root]]/site/mods/wsp_schema.log (may not be present) | |
| − | + | #log on to the [[Web Screen Painter]] | |
| − | + | ##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]] | |
| − | + | ##start the Unicenter Service Desk services | |
| − | + | ##check for any errors | |
| − | + | ##sign on to Service Desk | |
| − | + | ##sign on to sql visual studio | |
| − | + | ##*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) | |
| − | + | #run the [[pdm_configure]] to setup and ensure the environment is correct. | |
| − | + | #*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 | |
| − | + | #*dlgtsrv table | |
| − | + | #*#change the primary server name to the test server name | |
| − | + | #*#*sym from production name to test name | |
| − | + | #*#*server from production name to test name | |
| − | + | #change all the notifications in the usp_contact record to 'Notification' | |
| − | + | #*c_cm_id1, c_cm_id2, c_cm_id3, c_cm_id4 | |
| − | + | #*SQL Command is update dbo.usp_contact SET c_cm_idx = 1801 | |
| − | + | #reboot the server | |
| − | + | #before running [[pdm_configure]], check the following | |
| − | + | #*User ServiceDesk is active and available | |
| − | + | #*Update ServiceDesk in the SQL database | |
| − | + | #apply patches | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | == See Also == | |
| + | [[Migrating Schema Changes Between Systems]] | ||
Latest revision as of 12:42, 29 October 2008
To make corrections or additions to this article, select the edit tab above.
To discuss or ask questions about this article, select the discussion tab above.
To discuss or ask questions about this article, select the discussion tab above.
Overview
The following are the steps I have used to build several test systems.
It involves getting a sql backup of mdb, with all login's in the backup and then restoring is to a test system that has been setup and have an existing mdb built. The existing mdb is copied over using the SQL restore.
Steps to go from migrated R11.x system to a R11 test system
Procedures
- 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
- pdm_extract wspcol > wspcol.txt
- pdm_extract wsptbl > wsptbl.txt
- restore the wspcol / wsptab to the test system
- pdm_load -f wspcol.txt
- pdm_load -f wsptbl.txt
- delete the file $NX_Root/site/mods/wsp_schema.log (may not be present)
- log on to the Web Screen Painter
- 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
- start the Unicenter Service Desk services
- check for any errors
- sign on to Service Desk
- sign on to sql visual studio
- 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)
- run the pdm_configure to setup and ensure the environment is correct.
- 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
- dlgtsrv table
- change the primary server name to the test server name
- sym from production name to test name
- server from production name to test name
- change the primary server name to the test server name
- dlgtsrv table
- change all the notifications in the usp_contact record to 'Notification'
- c_cm_id1, c_cm_id2, c_cm_id3, c_cm_id4
- SQL Command is update dbo.usp_contact SET c_cm_idx = 1801
- reboot the server
- before running pdm_configure, check the following
- User ServiceDesk is active and available
- Update ServiceDesk in the SQL database
- apply patches
