The 5-T Presentation

1. The 5-T Presentation TCJIUG April 13, 2010

2. TLETS Technical Talk on Tuesday by Tena TCJIUG April 13, 2010

3. Agenda • Question & Answer Period • TLETS Architecture • Connectivity Options for Local Agencies • Message Processing • Omnixx Trainer and TLETS Certifications • Troubleshooting

4. TLETS Architecture

5. Introduction to TLETS TLETS is a fairly complex system. TLETS is made up of many components that work together to get the information needed / requested by the end user.

6. Network & Network Components Application Servers Database Servers Web Servers System Interfaces / Databases Clients Interface Systems Software TLETS Architecture

11. Physical Connectivity Physical Connectivity is achieved by connecting agency computing equipment to the LAN 1 Ethernet port on the back of the HN7700. The local agency is responsible for any internal networking at their site.

12. Connectivity Options DPS satellite network is set up so that each site has a range of IP addresses (a subnet). The number of IP addresses in the subnet varies depending on anticipated growth of the location. Therefore whether or not the local agency has one or multiple TLETS devices, each site is a subnet off the satellite network.

13. Connectivity Because each site has a subnet associated with it, typically: • DPS assigns the first address in the subnet to the HN7700 (the indoor unit). • The next sequential address is reserved for use by the local agency • The remaining addresses are used for the devices that communicate with TLETS.

14. Connectivity Although the subnet will typically have “extra addresses, the agency cannot randomly add another device. • The agency must obtain approval from the CJIS Security Team. • The TLETS Order Center must assign a mnemonic and ORI to the device. • Configurations must be made in the TLETS system

15. Options for ConnectivitySingle Device When a single TLETS device does not reside on a local agency network, this is considered a standalone device. This is typically the easiest way to connect and exchange information with the TLETS system. The Agency will simply configure the TLETS device with the IP address provided on the TCR and make connectivity between the Ethernet port on the PC and the Ethernet port on the HN7700 using a standard Ethernet CAT5 cable. The single device may be either an Omnixx workstation or an interface system.

16. Options for Connectivity • Most agencies have multiple TLETS devices. • Each device must • Present a unique IP address to the system. • Have a unique station identifier (mnemonic)

19. Connectivity Use of Dual NIC Cards or a single NIC Card configured with two TCP/IP addresses and route statements are often used as an alternative.

20. New Hardware • Replacement of hardware requires the agency to install Software on a new client and to configure the client TCP/IP address of PC the same as the previous client. • Contact DPS to add new devices, so that configurations can be made.

21. Message Processing in TLETS

22. Message Processing • TLETS supports hundreds of message keys / transactions to multiple data sources. • Typically the data source works with DPS to come up with a message format that will work for them. • A device connected directly to TLETS must know the format of the data TLETS is expecting. • DPS publishes the formats for the message keys on the TCIC2000 website.

23. Types of messages • There are two classifications of messages: • Unsolicited – typically delivered based on ORI or mnemonic • Administrative Type message • Hit Confirmation • Dollar Message • Solicited – a request from a data source

24. Solicited Message

25. 1) End User Formulates a message and submits it to TLETS 5) The repository processes the message and sends the response to the broker 6) The broker logs the message then uses the tracking number and/or the ORI to determine where the response is supposed to be routed. (7) The message is reformatted and logged before being sent to the requestor. 2) Message arrives at the broker where it is logged and a special tracking number is assigned to the message. 3) The broker determines, based on the message key and other factors, what data source(s) will process the message. 4)The broker reformats the message (including the special tracking number) , logs it, and sends it to the appropriate data source (s).

26. <OFML> <HDR> <ID>02WD000008</ID> <DAC>TWFX</DAC> <DAT>20100415121743</DAT> <REF>02WD000008</REF> <MKE>DQ</MKE> <ORI>TX0000052</ORI> <SUM>DQ: 02982031</SUM> <DST EID="DRI">TX</DST> </HDR> <TRN> <OLN>02982031</OLN> </TRN> </OFML>

27. POST /DLSWeb/services/TLETS HTTP/1.1 soapaction: http://dl.txdps.com/axis/services/TLETS/ user-agent: CPI Client Content-Type: text/xml; charset="utf-8" Content-Length: 765 Host: ndlstest.tx.gov Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 Connection: keep-alive <?xml version="1.0" encoding="utf-8"?> <SOAP-ENV:Envelope      xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"      xmlns:dmv="http://dl.txdps.com/axis/services/TLETS"      xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/"      xmlns:xsd="http://www.w3.org/2001/XMLSchema"      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">      <SOAP-ENV:Header>           <Deconfliction xmlns="http://dl.txdps.com/axis/services/TLETS">               <RequestorOri>TXDPS00B2</RequestorOri>               <RequestorUserId>TW00125</RequestorUserId>               <RequestorEmailAddress/>               <ReasonCode/>           </Deconfliction>       </SOAP-ENV:Header>       <SOAP-ENV:Body>       <StatusInquiryRequest xmlns="http://dl.txdps.com/axis/services/TLETS">           <firstName/>           <lastName/>           <sex/>           <dlIdUnlNumber>02982031</dlIdUnlNumber>       </StatusInquiryRequest>       </SOAP-ENV:Body> </SOAP-ENV:Envelope>  Message Broker

28. HTTP/1.1 200 OK Date: Thu, 17 Dec 2009 22:55:05 GMT Server: Apache/2.0.52 (Red Hat) X-Powered-By: Servlet/2.5 JSP/2.1 Keep-Alive: timeout=15, max=100 Connection: Keep-Alive Transfer-Encoding: chunked Content-Type: text/xml; charset=utf-8 <?xml version="1.0" encoding="utf-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"    xmlns:xsd="http://www.w3.org/2001/XMLSchema"    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">    <soapenv:Body>    <StatusInquiryResponse xmlns="http://dl.txdps.com/axis/services/TLETS">       <error xsi:nil="true"/>       <ns1:DriverHistory xmlns:ns1="http://www.nlets.org">       <ns1:StandardResponse>       <ns2:Person xmlns:ns2="http://www.it.ojp.gov/jxdm/3.0.2">          <ns2:PersonName xsi:type="ns2:PersonNameType">              <ns2:PersonGivenName>TENA</ns2:PersonGivenName>              <ns2:PersonMiddleName xsi:type="ns2:PersonNameTextType">ANN</ns2:PersonMiddleName>              <ns2:PersonSurName>WATSON</ns2:PersonSurName>              <ns2:PersonSuffixName xsi:type="ns2:TextType"></ns2:PersonSuffixName>          </ns2:PersonName>          <ns2:Residence xsi:type="ns2:ResidenceType">             <ns2:LocationAddress xsi:type="ns2:AddressType">                <ns2:LocationStreet ns2:commentText="street address 1" xsi:type="ns2:StreetType">                   <ns2:StreetFullText>6310 CLAIRMONT DR</ns2:StreetFullText>                 </ns2:LocationStreet>                 <ns2:LocationCityName>AUSTIN</ns2:LocationCityName>                 <ns2:LocationCountyName>TRAVIS</ns2:LocationCountyName>                 <ns2:LocationStateName>TEXAS</ns2:LocationStateName> …

29. <OFML> <HDR> <ID>02WD000008</ID> <DAC>TWFX</DAC> <SRC>NDLS</SRC> <DAT>20100415121745</DAT> <REF>02WD000008</REF> <MKE>DR</MKE> <ORI>TXOLN0000</ORI> <DST>TWFX</DST> <SUM>DQ: 02982031</SUM> </HDR> <RSP> <TXT> SEARCH ON 02982031 NAME: WATSON, TENA, ANN DESCRIPTION: WHITE\FEMALE\08231957\5-04\145\BROWN\HAZEL SEX OFF: COMM IMPED: ORGAN DONOR: VISA EXP: PHYSICAL ADD: 6310 CLAIRMONT DR CI/CO/ST/ZIP: AUSTIN,TRAVIS,TEXAS,78749-3424 MAILING ADD: 6310 CLAIRMONT DR CI/ST/ZIP: AUSTIN,TEXAS,78749-3424 REC STATUS: ELIGIBLE ADMIN STATUS: CARD STATUS: HME THR ASMT: EXP: CARD TYPE: DL #: 02982031 CLASS: C TYPE: DL EXPIR DATE: 08232011 RESTRICTIONS: ENDORSEMENTS: ********** END OF RECORD********** MRI: 66920013 IN: NDLS 56790 AT 15APR2010 12:17:44 OUT: TWFX 7 AT 15APR2010 12:17:45 </TXT> </RSP> </OFML> Message Broker

31. Message Processing • The key difference between an unsolicited message and a solicited message is that the unsolicited message does not contain the special tracking number, so they are routed by mnemonic or ORI.

33. Certifications and Omnixx Trainer

34. Certifications • Access to system resources occur through certifications. • Certifications can have 3 Statuses: • ACT (Active ) • PRO (Probationary) • EXP (Expired) • All Operators have at least 3 certifications: • Some sort of TLETS Certification (LE and/or MOBILE) • Some sort of TCIC Certification (FA and/or LTFA) • Interpol Certification

35. Interpol Certification • A new certification in TLETS • Access to the Interpol Message Keys • Optional but recommended

36. TCIC Certifications • Correlate to Full Access or Less than Full Access TCIC training. • Provide Access to TCIC/NCIC and CCH/III message Keys • Some agencies choose not to allow operators to have access to CCH, so DPS has added additional Certifications to prevent access to CCH for those operators at the request of the agency.

37. TLETS Certifications • TLETS Mobile is a subset of TLETS LE. • TLETS LE allows access to Vehicle Registration, Boat Registration, Driver License, other states, NICB, Canada, LoJack, NOAA, LESC, DEA, Financial Responsibility etc. • TLETS Mobile allows access to Texas and other states’ Driver License, Vehicle Registration, Boat Registration, LoJack and Financial Responsibility.

38. Maintenance of Certifications Certifications have expiration dates. If the certifcation expires, then the access to the associated message keys / transactions is suspended. To extend the certification date, navigate to http://tlets.txdps.state.tx.us/omnixx/desktop

39. Maintenance of Certifications • Log in using your DPS credentials • If you don’t know your DPS Credentials Contact DPS OIC at 1-888-377-6420.

40. Omnixx Trainer Select the “Trainer” icon from the Omnixx Desktop

41. Use the Menu to Navigate. Select TESTS to take a test. Only the tests you are authorized to take are available to the operator If a Certification is underlined, that means a “Course” is available.

42. Tests • Tests are compiled from a pool of questions that may change from time to time to keep up with current policy and functionality. • Typically a person will have to make a 75% or higher to pass the test. • Tests are comprised of multiple choice, true false, or fill-in-the-blank questions. • Tests are open book.

43. Tests • The top of the screen shows you the Certification, how much time you have to complete the question, how many questions are on the test, and how many you’ve answered so far.

44. Tests • When all questions have been completed, click on • The operator will be presented with a summary. • The operator must acknowledge the test results for the certification date to get extended.

45. Trainer – Common issues • Operator does not acknowledge test results • Operator does not have full control over the TLETS & Java folders on the PC he is running • Operator has a slow internet connection and the system times out during a submission. • Operator does not have Java 1.5.x installed on his equipment.

46. Troubleshooting

47. HN7700

48. Omnixx Common Problems • Full control over the TLETS folder and the Java Folders as specified. • Use of the correct mnemonic at login time • Popup • No Force Icon • Cannot connect to the switch

49. Login Problems • 1400 The user ID submitted is unknown • 1402 The password submitted for a valid user ID does not match. • 1406 The current password has expired

50. Problems Changing Password • A password is composed of 8 to 15 characters • A password must contain one letter, one number and one special character • A password cannot be re-used until the password has already been changed 10 times.