TIBURON (FORMERLY COMPUDYNE - PUBLIC SAFETY - SOFTWARE LICENSE) 2006

Home Browse Search

r1 Ir�J 24SEVEN Version 2.6 Telestaff Interface Configuration CompuDyne Proprietary 3. CONFIGURATION 3.1 DATABASE CONFIGURATION In short, the codes that are used in both the TeleStaff database and the 24SEVEN database must be configured identically. Here is a summary of the applicable codes: • All personnel must be entered in both systems. This is determined by the Personnel ID. If a person is entered into TeleStaff and not into 24Seven, the interface will not import any data for that person at all until this is fixed. When this occurs, an error event is written to the event log. • Station codes must be set up the same in both systems — The system will not function if they are configured as 1, 2, etc. in TeleStaff, but as STI, ST2, etc. in 24SEVEN. • The TeleStaff Organization must be the same as the 24Seven Department Setup. For example, if TeleStaff uses District codes (Di, D2, etc), but these are Battalions in 24Seven (B 1, B2, etc.), the system will not function correctly. Again, the codes must be configured to be the same in both systems. • Units must be configured the same in both systems. For example, if Engine 4 is E -4 in TeleStaff, it cannot be E4 in 24SEVEN. • TeleStaff Work Status codes must be configured the same as the 24SEVEN Pay codes. • TeleStaff Job Title codes must be configured the same as the 24SEVEN Job Role codes. The codes that are exported from TeleStaff correspond to their Abbreviation in the TeleStaff system. 3.2 24SEVEN TELESTAFF INTERFACE CONFIGURATION FILES The two configuration files for the two windows services are very simple XML files. You will only need to modify one or two settings in each file. You can go into a simple text editor such as Notepad to make the necessary changes. 3.2.1 24SEVEN TELESTAFF POLLER There are three settings that are available in the configuration file for the 24SEVEN TeleStaff Poller. They are listed and explained here. interval - this is the time, in milliseconds, that determines how long the Poller will wait between polling the directory for XML files. tsdirectory - this is the absolute directory where the PDSI Gateway Manager catcher will place the generated files. No trailing backslash is required. tsfilename - this is if you are using a static filename with the catcher, and it will only look for an XML file with this filename. If you have set up your pitcher to pitch Rosters for a multiple date range, then you cannot use a specific filename (see the TeleStaff Configuration section for an explanation). CompuDyne Proprietary uompuuyne December 29, 2005 Page 4