About Configuring the COM Daily Operations Interface
The COM Daily Operations (CDO) Interface allows Trapeze COM to read a flat file output from third party Operations and Dispatch systems.
This section is only applicable to sites that use third party Operations and Dispatch systems. For more information, contact your Trapeze representative.
The Operations and Dispatchsystem writes a flat file every X hours and the CDO Interface can be configured to read from the file also every X hours.
Initially, the CDO Interface is run manually in the Trapeze6 Client shell. The Client shell points to a Trapeze6 Service shell configured to run the CDO Interface Service. You must set up the source file, log file, and field map. An ini file is saved after you have completed the set up and successfully ran the interface as a manual operation.
You must then configure the TpNtService. The application (TpNtService.exe) registers the CDO Service as a Windows Service running in the Windows Service Manager. To configure the application, you must create an ini file to assist in the service installation. This ini file must have the same name as the exe file, for example, TpNtService.ini for the TpNtService.exe file.
After this ini file is created, install the Service from the command prompt.
The following text is an example of the required ini file:
[Settings]ServiceName = TpNTService The name appears in the Windows Service Management. This can be changed.
ProcCount = 1
CheckProcess = 30
[Process0]
CommandLine = C:\Trapeze\Bin\Win\CDOInterface.exe -login=RTO -pwd=RTO -dsn=RTOComplaints -setupfile=c:\Temp\CDO.ini
This file was generated by manually running the Exchange->CDOInterface. WorkingDir = C:\Trapeze\Bin\Win\ PauseStart = 1000
This refers to the waiting time between sessions. PauseEnd = 1000
UserInterface = No
Restart = Yes
NoEmployee = Yes This means the employee information is not imported into the Employees table and EmployeeStatus table.
NoVehicle = Yes This means the vehicle information is not imported into the Vehicles table.