Badger TraCS Guides
Task 3.14(b): Configure RMS Transmission Settings, Para-Virtualization Alternative
Task 3.14(b): Configure RMS Transmission Settings, Para-Virtualization Alternative
Different types of hardware virtualization include:
Full virtualization – Almost complete simulation of the actual hardware to allow software environments, including a guest operating system and its apps, to run unmodified.
Paravirtualization – The guest apps are executed in their own isolated domains, as if they are running on a separate system, but a hardware environment is not simulated. Guest programs need to be specifically modified to run in this environment.
Warning: although some agencies have chosen to run TraCS as a virtualized application, the Vendor for TraCS did not specifically design the application to be run in this manner. We have had reports that TraCS runs more slowly as a virtualized application. Data losses can occur if a session is dropped suddenly.
Purpose: Configure TraCS to extract and transmit data to your Records Management System (RMS). This task is optional.
Overview: TraCS is configured to export data for record management systems (RMS). These settings will also be adjusted to work in a virtualized environment. A communications folder is assigned to each user through a mapped networked drive instead of the local hard drive. Each user must have their own instance of the communications folder, but accessed through the same drive letter. The instructions below will refer to the “V:” drive, but you may use any drive letter mapping as long as it maps to a different physical path for each user.
Requirements: Master computer, RMS capable of importing TraCS data.
Consult the RMS vendor documentation to determine whether data should be exported in “7.3” format or “10” format. Either data format is support by TraCS.
Write the export format type here: _______
Double click the shortcut for the TraCS Configuration Manager, located on your desktop.
Sign in with account 00001.
Click Transmission tab.
Click the Import/Export Button.
Expand the Export Instructions.
Expand ExportRMS.
Expand one of the forms you want export
and enable and disable the export rules depending on what your agency wants to export to their RMS. XmlToRMS is the “10” export format. 73xmlToRMS is the “7.3” export format. ImageToRMS exports a PDF or TIFF of a report associated with the form.
The current version of the alcohol form is AlcoholV3.frm.exml. If you plan to export alcohol form data, this is the form you should choose. Alcohol.frm.exml is present only for backward compatibility and does not apply to new TraCS agencies.
Select xmlToRMS. If you want to export the form data in the “10” format, enable the Active check box. Otherwise, disable it and continue with step ii.
Change the Export Path by prefixing the user’s network folder and \tracs. For example, add V:\tracs to \Communications\Transmissions\RMS\elci to create V:\tracs\Communications\Transmission\RMS\elci.
Select 73xmlToRMS. If you want to export the form data in the “7.3” format, enable the Active check box. Otherwise, disable it and continue with step iii.
Change the Export Path by prefixing the user’s network folder and \tracs. For example, add V:\tracs to \Communications\Transmissions\RMS\elci to create V:\tracs\Communications\Transmission\RMS\elci.
Select imageToRMS. If you want to export an image of one of the forms reports, enable the Active check box. Otherwise, disable it and continue with step 4c-iv. By default the report image export is configured with the most commonly used report and the TIFF image type. These may be changed if you prefer another format:
Click the Reports button.
Select the report you want to export in the the File Name field.
Select the export format for the image in the File Type field. Most popular are PDF or TIFF-LZW (MultiPage).
Click the File Name button.
Change the File Extension to match the the image type, typically tif or pdf.
Click the OK button to close the File Name dialog.
Click the OK button to close the Edit Report dialog.
Change the Export Path by prefixing the user’s network folder and \tracs. For example, add V:\tracs to \Communications\Transmissions\RMS\elci to create V:\tracs\Communications\Transmission\RMS\elci.
repeat steps as needed
Click Apply to save your changes.
Click OK to exit the Import/Export Editor.
Did You Know? Custom data exports from TraCS are possible. This requires creating and installing a custom XSLT style sheet file to transform the native TraCS data and then configuring the xmlToRMS rule to use it.
See the Badger TraCS Integration Package for more information on integrating Record Management Systems with TraCS.
You may also contact Badger TraCS for assistance setting up custom data exports. |
---|
Set Up Communications
Click the Communications button to configure the destinations for your RMS data exports.
Expand the Communication Instructions item.
Expand the TransComm item.
Select the “ToRMS” setting (for example: elciToRMS) for each form to be transmitted to your RMS.
Enable the communication rule by checking the active check box.
On the File Options tab, change the From Folder field by prefixing the user’s network folder and \tracs. For example, add V:\tracs to \Communications\Transmission\RMS\ELCI to create V:\tracs\Communications\Transmission\RMS\ELCI.
If you are exporting TIFF or PDF files, you will need to add the file type in the Filename(s) to Process field. Add a comma after *.xml and then add *.pdf or *.tif
Example: *.xml,*.pdf
Change the Communication Type as needed by your RMS. File Copy is the most common option here.
Select the Communication Options tab.
Enter the location required by your RMS for the data files in the Destination Folder.
If you have chosen a Communication Type other than File Copy, configure the remainder of the panel as specified by your RMS vendor.
Repeat steps for the remaining forms that you want to transmit to your RMS.
Click Apply to save your changes.
Click OK to exit the Communications Editor.
Close the Configuration Manager.
email badgertracs@dot.wi.gov or call 608-267-2096