Embedded Files
The Dekalb Marshals office was a Strategic RFID (SRP) version 1 roll-out. It consists of multiple fixed readers, along with handheld barcode scanners. The system tracks the documents (warrants) as they are served by Marshals to the public. This Wiki only covers the Server side portion of the application. Their is a mobile side in which the officers interface with the application.
Current POC:
Steven N. Taylor
I.T. Manager
O: 404-687-2763
C: 404-788-6881
Notes:
FX Devices are running on Device code that has them report to the server (not like version 2 SRP)
Websites use a SQL back end
Application was converted to new 2016 servers in 2019
There is a test environment on sstwebapptest01 in the default website (Dekalb)
Problem during the last upgrade were due to some missing Stored Procedures in SQL, don't forget them!
Remoting into Dekalbs Environment:
Click on the 'Terminal Session' to the server. This server name may change over time but they should add it to our terminal session list when it does.
Install any appropriate plugins that the session requests (IE: Pulse at the time of this documentation)
Username may need to have DCG\ before it and fail login without it.
Application support for Dekalb consists of three .Net applications, all under Default website:
DocumentTracker (Not DocumentTracking, Not DTS, Not DocTrack)
OdysseySync (Integrates with their odyssey system, url in web.config file.
RFIDPortal (Fixed Reader communication integrated directly with DocumentTracking
All applications are mapped to the database via entries in the web.config
*Most issues with Dekalb (along with other old .Net apps) are due to the following:
Incorrect SQL User/Passwd
Possibly recreate username even if it appears to be correct. Test by having DBA hit the database with that user and passwd in sql management studio
Other SQL Issues:
Missing stored procedures
Connectivity issues to database
Changing from SQL authentication to Active Directory Authentication
Incorrect Prerequisites
Need .Net installed (currently v4.0, may be further compatible with other version)
Web Deploy not installed correctly (need it to import websites onto server)
Fixed Reader issues:
Readers are statically mapped, so changing something such as DNS server will break them as they point to the hostname of the server
Readers going bad ? (Some are offline, they don't monitor or care about the fixed reads so its hard to get a grasp on which ones are actually offline)
OdysseySync change:
URL Change, application integration change, etc. We only point to their URL with our existing code. If they change the format in which they send it then we will stop functioning on the integration piece.
Large infrastructure changes without letting us know:
Server OS Change
SQL OS Change
Network Change
Unplugging fixed readers
Page updated
Report abuse