Configure RMS for QA Testing

Previous  Top

Some companies have a policy to test a new version of RMS in a separate test environment before putting it into the production environment. Here are some things to consider when doing that.

1.	Backup your production RMS database and restore it to a test database; apply any database update scripts related to the new version

2.

Change the Flat File Directory in the test database to something other than the Flat File Directory in the production system. THIS MUST NOT BE DONE USING THE RMS APPLICATION. To change this setting directly in the database, open the T_USER_REFERENCE table and change the REFERENCE_VALUE to the test folder path where the REFERENCE_LABEL = Flat File Directory. Then make a copy of all of the files in the production folder to the test folder.

3.	Install the new RMS application version on a test computer

4.	Open the test RMS application and logon to the test database (referred to from now on as the test system)

5.

Turn off any downloading of data: If you are refreshing a test environment that has been established previously, check to be sure that the RMSAgent Windows Schedule Task job is disabled. Expand the Data Management branch on the Home window tree view control and double-click on the Import Properties branch. Be sure that for Billing Data and Sighting Data imports, only the Text File check box is checked, this will ensure that no production data will be downloaded into the test system.

6.

If you wish to test the import of Billing Data and Sighting Data, copy the files that are downloaded by the production system (these files are usually named cust417*, clm* or bill* and are located in the production system Flat File Directory) into test system Flat File Directory. Rename these files so that they will be imported by adding "NotImported" to the beginning of each filename.

7.	If you wish to test reports, copy all *.rpx files from the production system Flat File Directory in the test system Flat File Directory.