This document assumes you have a full PMAPS WebPro Test environment successfully certified.

Transcription

1

2 Overview This document outlines the steps for updating a development or test environment with your current production data. This is allows further testing with the most recent production content. This document assumes you have a full PMAPS WebPro Test environment successfully certified. To expedite any troubleshooting support, we require you to complete a table at the end of each section and throughout this document. Fill in the columns: Assigned To: Comments: Date Completed: Name of the person responsible for that section of the installation Any notes or comments that will be helpful for troubleshooting Date the task is completed. Please have available the completed PMAPS WebPro On-Premises Installed Technical Checklist.PDF prepared for the initial installation as reference will be made to this document. PMAPS WebPro Updating Dev Environment with Production Data 1

3 Step 1: Create a Backup of the Production PMAPS WebPro SQL Database Create a full backup (.bak) of the PMAPS SQL database and save it to a location on the Test environment SQL server. Example: c:\sqlfiles\webpro.bak Create Backup of Production WebPro Database Step 2: Configure for Test Environment Prior to restoring the WebPro SQL Database, make sure you export to Excel the dbo.applicationsetting table from the Test WebPro SQL server which contains the current test WebPro settings. The following fields will then need to be updated once the bak file is successfully restored. (Ref: A1-A56). Export Test SQL dbo.applicationsetting table to Excel PMAPS WebPro Updating Dev Environment with Production Data 2

4 Step 3: Restore SQL.BAK Database in Test 1. All the following steps are performed in the Test environment. 2. Open SQL Server Management Studio and login as the user who has been granted dbo rights to the database. 3. Make sure you have exclusive access to the database before restoring. You can use the Activity Monitor tool to confirm. 4. Right click the Database folder and select Restore Database 5. Type in the field To Database the new database to create. In this example we are creating a PMAPSWEBPRO_Clientname (this should be the same as Test WebPro SQL Database which you are replacing with the Production copy). PMAPS WebPro Updating Dev Environment with Production Data 3

5 6. Click the From device ellipse box. 7. Locate the SQL.bak file and select it. PMAPS WebPro Updating Dev Environment with Production Data 4

6 8. Manually change the location where you want to create the WebPro SQL Database 9. Click OK to create the WebPro database. Restore.Bak File PMAPS WebPro Updating Dev Environment with Production Data 5

7 Step 4: Security for SQL Database Under Security->Logins, make sure to reassign access to the WebPro database. Map them a data_owner. Updated Security to SQL Database Step 5: Update SQL Settings Open the WebPro SQL table dbo.applicationsetting and overwrite the field settings with your current environment configuration EXCEPT for the value in the DocumentCache field. Refer to (Ref: A1-A56). Update SQL dbo.applicationsetting table PMAPS WebPro Updating Dev Environment with Production Data 6

8 Step 6: Re-run the.net Framework.exe Open up a DOS window and run the following command to register ASP.NET. You may need administrative privileges to do this. This procedure will register the PMAPS database with the application server. C:\WINDOWS\Microsoft.NET\Framework\v \aspnet_regsql.exe Optional: SuperAdmin setup Step 7: Purge Training/Test Document Folders 1. Locate the root folder where the WebPro documents are stored (Ref: D1). This should be the same as the field DocumentCache located in the dbo.applicationsetting table as a reference. 2. Delete all files in the folders. Example: delete \\servername\webpro\documents\*.* Purge Training/Test Data Folders PMAPS WebPro Updating Dev Environment with Production Data 7

9 Step 8: Restore New Documents 1. Locate the Documents folder from the Production environment and copy them to the root of the Test WebPro location. You can find the location of these files by referring to the production SQL dbo.applicationsetting table and the documentcache value. You will need the full path up to the \documentcache path: Example: DocumentCache = \\productionservername\webpro\documents\documentcache You will need to copy all the files from the \\productionservername\webpro\documents (not just the documentcache folder) which should include \\productionservername\webpro\documents\documentcache \\productionservername\webpro\documents\newdocs \\productionservername\webpro\documents\proposals \\productionservername\webpro\documents\smartcart \\productionservername\webpro\temp Restore New Data Files PMAPS WebPro Updating Dev Environment with Production Data 8

10 Step 9: Update Data UNC Path for your Server Environment 1: SQL Tables The database table dbo.documents contains a field UNCPath which holds the full UNC Path for the data files. (These will be automatically updated). The database table dbo.applicationsetting table will require changes. Open the dbo.applicationsetting table Setting Name Details Example DocumentCache Leave the \\servername\documents\documentcache\ original value in this field except make sure there is a backslash at the end of the line. The SQL script will automatically update this value. DocumentTempDir Update this to \\servername\newlocation\documents\temp the new location Proposal Directory Update this to \\servername\newlocation\documents\proposals the new location SmartCartDirectory Update this to \\servername\newlocation\documents\smartcartdirectory the new location Temporary Files Update this to the new location \\servername\newlocation\temp 2: Download SQL Scripts Download the following ZIP file which contains two SQL scripts. Scripts/Change Document UNCPath.zip PMAPS WebPro Updating Dev Environment with Production Data 9

11 3: Extract SQL Scripts Extract the files to the SQL server. You should have the following two files: - Change Document UNCPath Setup.sql - Change Document UNCPath Execute.sql 4: Run Change Document UNCPath Setup Script If this stored procedure already exists you can skip this step. Open the Change Document UNCPath Setup.sql. Search for PMAPS_DATABASE_NAME and replace it with the name of your PMAPS WebPro database. Run the script which creates a stored procedure in the database. 5: Run Change Document UNCPath Execute in Test mode Open the Change Document UNCPath Execute.sql. Search for PMAPS_DATABASE_NAME and replace it with the name of your PMAPS WebPro database. This procedure requires two parameters: The first is the name of the new location for the documentcache. This would be the new location on the Test environment. Replace the \\newdir\\' with the location where the new documentcache folder will be moved. The second parameter is either the value test or execute. The test value will show a preview of the changes. 6: Run Change Document UNCPath Execute in Execute mode The execute value will perform the actual update. Updated UNC Path PMAPS WebPro Updating Dev Environment with Production Data 10

12 For questions please contact our technical support team at: Ext. 2 Or us at: support@proposalsoftware.com PMAPS WebPro Updating Dev Environment with Production Data 11

13