Badger TraCS Guides
Task 4.5: Create Test Environment
Task 4.5: Create Test Environment
Purpose: Creates an entirely separate TraCS environment in which to test TraCS. This task is optional.
Requirements: Non-production computers to be used for test master, test field units, and test workstations.
Contact badgertracs@dot.wi.gov and request an additional serial number from Badger TraCS to be used for testing purposes only.
Decide on a network folder for the test environment, for example, \\myserver\sharename\tracstest\tracs.
TraCS Test Network Folder: _________________________________________________
Designate one of the test computers to be your master test computer and complete the tasks in chapter 1 of the installation guide, adding the following modifications.
Substitute the test network folder location above when prompted for the TraCS network folder throughout all tasks.
Perform task 1.1. Task 1.1: Prepare for TraCS Installationarchived
Perform Task 1.2: Task 1.2(c): Install TraCS on Master Computer, Web Server Alternative
Use the test serial number instead of the production serial number
When prompted for agency name, be sure to add the word test, for example, OUR TOWN TEST POLICE DEPARTMENT.
For network destination, use the test network folder location from step 2.
Perform task 1.4: Task 1.4(c): Set up Databases, E-Mail, and Proxy Server Connections, SQL Server Alternative Name the databases tst_tracs_support, tst_tracs_custom, tst_tracs_data, tst_tracs_users, and tst_tracs_log.
Before task 1.5 copy support and user tables from production.
SQL Server: Use the SQL Server Management Studio import/export wizard to copy the tables in
tracs_support to tst_tracs_support and
copy the tables in tracs_custom to tst_tracs_custom.
copy the tables in tracs_users to tst_tracs_users.
DO NOT copy tables or data from tracs_data or tracs_log. Empty table structures will be created in step 3h.
Perform task 1.5. Task 1.5: Master Computer Auto-update Be sure to acknowledge that you are setting up a test environment, not production, when you request master computer authorization in step 12c.
Perform Task 1.6 Task 1.6(c): Complete Database Setup, SQL Server Alternative
Edit data “delta” SQL script in step 2 to change the target database to the test version: USE [tst_tracs_data]
Edit the log SQL script in step 3 to change the target database to test version: USE [tst_tracs_log]
Complete chapter 3, adding the following modifications.
Task 3.1: Configure Master Computer Settings Substitute the test network folder location from step 2 when prompted for the TraCS network folder throughout all the tasks.
After completing task 3.1, add the following settings manually:
Open the file c:\programdata\tracs\settings\formpreferences.ini in notepad and add the following setting:
[Mode]
Training=True
Open the file c:\programdata\tracs\settings\autonumbers.ini in notepad and add the following setting under the
[ELCI]
EARS=fake
Open the file c:\programdata\tracs\settings\splash.ini in notepad and edit the the Organization setting to read ******TEST******:
[TraCS]
Logo=\Graphics\TraCS Splash.png
SoftwareTitle=TraCS
SoftwareSubTitle=Traffic and Criminal Software
Organization=******TEST******
ServicePack=
Task 3.2: Task 3.2: Create ELCI Citation Number Inventory Order exactly 5000 citation numbers. Regardless of the quantity ordered, the test environment will be assigned citation A100001 through A105000. No receipt will be sent to the e-mail address entered, since these are special test citation numbers.
Perform task 3.13.1. Task 3.13.1: Manually Installing ELCI Citation Numbers
Copy communications files from the production environment to the test environment.
Copy \settings\ImportExport.set.loc.exml from the production TraCS network folder to the same location in the test TraCS network folder. Be careful; there are many similarly named files in the settings folder.
Copy \settings\Communications.set.loc.exml from the production TraCS network folder to the same location in the test TraCS network folder. Be careful; there are many similarly named files in the settings folder.
Perform task 3.14 Task 3.14(a): Configure RMS Transmission Settings, Standard Alternative if applicable to your agency. Change any references to network paths to the equivalent test location. Be careful! You imported production settings in step f. If you miss any file paths you could have test data showing up in the production environment.
Perform task 3.16, Task 3.16: Active Directory Integration step 3 only, to configure the LDAP connection if you use active directory.
Skip task 3.22. If you modified the list of available diagramming tools in the production environment, copy \settings\ExternalInformation.set.loc.exml from the production TraCS network folder to the same location in the test TraCS network folder. Be careful; there are many similarly named files in the settings folder.
Skip task 3.23. If your agency created custom symbol palettes follow this procedure:
Copy the .tdp files in the Symbol Palettes folder in the production TraCS network folder to the equivalent folder in the test environment.
Also copy the .tdp files to the c:\programdata\tracs\Symbol Palettes\ folder on the test master computer.
set up batch transmission Setting up a TraCS Windows Services “Batch” Server Machine
Perform task 4.1, Task 4.1(a): Create Custom Installation Files, Standard Alternative but add the following settings after completing step 9d.
Add the training mode setting.
Click the add button.
Enter TrainingMode and click OK.
Select the training mode setting that you just created and then edit the panel on the right to match the screenshot below.
Add the EARS setting.
Click the add button.
Enter EARS and click OK.
Select the EARS setting that you just created and then edit the panel on the right to match the screenshot below.
Add the SplashOrganization setting.
Click the add button.
Enter SplashOrganization and click OK.
Select the SplashOrganization setting that you just created and then edit the panel on the right to match the screenshot below.
Continue task 4.1, picking up at step 9e.
Perform tasks 4.3, substituting the test network folder as needed, to set up additional Web client units. Your test environment should include at least one field unit.
Your test environment is now complete.
Related content
email badgertracs@dot.wi.gov or call 608-267-2096