When updating the CAREWare test server using a backup from the production server, CAREWare administrators need to ensure that the settings for the test environment remain intact. CAREWare stores CAREWare Business Tier settings in the businesstiersettings.xml file and in the cw_common_storage table in the database. The businesstiersettings.xml file remains intact during the upgrade process, however if the database is restored from production, the cw_common_storage table is replaced with those settings from production.
Areas in CAREWare that may be impacted during the restoration:
-
The data tier update process may fail due to a failed connection to databases, that are not in use in the test environment. That may include cw_pdi, cw_user_changes, or cw_attachments. If the features associated with the databases are in use on the production server, CAREWare generates an error on the test server after the restoration due to the missing database connection strings for those databases in the businesstiersettings.xml file.
-
If Open ID Connect is setup on the production server, users would be unable to log into the test server until the Open ID Connect settings are restored matching the settings for the test environment.
-
HL7 import settings are based on file folder locations. Users may get errors if the drives on the production and test environment are different. If file folder locations in production are set for the E drive and that drive does not exist on the test server, users get errors when CAREWare attempts to create those folder and testing HL7 functions would fail.
-
Accessing the Provider Data Import feature in CAREWare would generate as error if the file folder location of the CAREWare Business Tier is different for the production server compared to the test server. The PDIFiles folder has to be set in a folder that CAREWare can read/write to in the common storage settings.
-
CAREWare may fail to generate client lists during initialization if the file folder location of the EURNGnerator.exe is different between the production and the test environment. This again has to do with the location the CAREWare Business Tier is installed on.
Follow these instructions in order to retain the test server cw_common_storage settings during a restoration of the CAREWare database using a backup from the production server:
-
Export a CSV copy of the cw_common_storage table from the test server cw_data database.
-
Stop the CAREWare Business Tier service on the test server.
-
Restart the CAREWare SQL Server instance.
-
Restore the test server CAREWare database using the production backup.
-
Copy the cw_common_storage values from the CSV file.
-
Paste them in the cw_common_storage table in the cw_data database replacing the values created by the production backup.
-
Run the query Exec sp_changedbowner 'cwbt'
-
Start the CAREWare Business Tier service on the test server or run the installation files (If CAREWare is to be upgraded on the test server)
By completing those steps, the test server settings are retained after the restoration.