Overview
These are the instructions for enabling the use of the Geotab DVIR Defects to TMT Inspection Tickets feature. The first part of these instructions confirms in your settings that your DVIR feed is turned on and set to process defects, and the remaining instructions provide the SQL scripting needed for you to run for setting up the TMW/TMT database communication and ELEOS user creation in your TMT database.
After successfully completing the setup, your integration and databases should be configured to take advantage of the feature with default settings. However, note that with the individual configuration of each TMT system, if a client has a customized DVIR or wants to customize the Defects to Component Codes, special discussion is required. ASR will enable the default mappings and default configuration only.
Appsettings
You should first check within your appsettings.json file that the following settings are configured. Your appsettings.json file is in your active Eleos integration folder, which can be found by opening IIS on your web server, expanding the sites in the left pane, and locating the active site with Eleos in the name (usually called EleosIntegration). Then right click the site, select Explore, and open the appsettings file in the folder:
The following settings under the Geotab section within appsettings should either be “true” or configured to a value:
DVIRFeedEnabled - This should be set to true to enable the DVIR background service feed.
DVIRFeedIntervalSeconds - This should be configured to a value; our recommended default is 900 seconds or 15 minutes; however, this can be configured to an interval of your liking. The lower this value is, the more frequently your background service will pull new DVIR logs.
DVIRFeedMaxHistoryDays - This should also be configured to a value; our recommended default is 30 days; this can also be configured to a look back period of your liking. This day range will specify how far we look back when trying to pull new DVIR logs.
ProcessDVIRDefects - This should also be set to true to enable the processing of DVIR defects.
After ensuring those settings are properly configured, save the changes to the appsettings.json file.
For the settings changes to take effect, you will then want to recycle the application pool by opening IIS on your web server, selecting the Application Pools section in the left pane, and locating the active Eleos application pool that should already be running (it should show it as Started). Right click on the Eleos application pool and select Recycle:
Database And User Configuration
Next, you will want to run the attached ELEOS - Trustworthy Database.sql script in both your TMW and TMT databases to configure the cross-database permissions. This SQL script needs to be run by a user that has "sa" level permissions across both databases. Within this script you will need to configure the first line that indicates the database you want to update:
You will need to run the Trustworthy script within your TMW database and configure the first line to be your TMT database, then you would need to run the same script within your TMT database and configure the first line to be your TMW database. This allows the two to interact with each other.
Finally, you will want to run the below user creation SQL and configure the first line to be your TMT database to create the Eleos user and assign the proper role:
-- TFWUSER
;USE [YourTMTDatabaseNameHere]
;CREATE USER [ELEOS] FOR LOGIN [ELEOS]
;ALTER ROLE [TFWUSER] ADD MEMBER [ELEOS]
Note if the role TFWUSER is incorrect in the above SQL statement try TFW_USER instead.
This creates a SQL Login that has permissions to access the Transman database with the “TFWUser” role. You can add the TFWUSER role to the ELEOS user, as the TFWUSER role should have all the permissions necessary to execute SQL stored procedures on the TFW database.