Вы находитесь на странице: 1из 49

CTAS Reefer 7.4.

9
Installation Manual
Version 5.11
CTAS Reefer Installation Manual | October 09, 2018

Content

1. Version history ......................................................................................................................................................... 4


2. System overview...................................................................................................................................................... 6
3. Requirements .......................................................................................................................................................... 8
3.1 System Requirements ...................................................................................................................................... 8
3.1.1 Application Server Requirements ....................................................................................................... 8
3.1.2 Database Server Requirements .......................................................................................................... 8
3.2 Software Requirements ................................................................................................................................... 8
4. Server Installation ..................................................................................................................................................10
4.1 Pre-Requisites ...............................................................................................................................................10
4.1.1 Windows Server 2012 pre-requisites ................................................................................................10
4.2 Migrating from an installed 32-bit to 64-bit version ........................................................................................12
4.3 Software installation .......................................................................................................................................13
4.3.1 i-SHARE Installation..........................................................................................................................13
4.3.2 Installation packages.........................................................................................................................13
4.3.3 Database Setup ................................................................................................................................13
4.3.4 CTAS Reefer Module Installation ......................................................................................................13
5. Configuration .........................................................................................................................................................14
5.1 I-SHARE.........................................................................................................................................................14
5.1.1 TRAILBLAZER Data Interface configuration.....................................................................................14
5.1.2 TRAILBLAZER Data Interface failover configuration ........................................................................15
5.2 SQL Server Reporting Services .....................................................................................................................16
5.3 CTAS Reefer Configuration ...........................................................................................................................22
5.3.1 Configuration File Summary .............................................................................................................22
5.3.2 Configuration Parameters .................................................................................................................23
5.3.3 Interface Configuration ......................................................................................................................31
5.3.4 Failover configuration ........................................................................................................................40
5.3.5 I-Share failover configuration ............................................................................................................41
5.3.6 Self-updating client deployment ........................................................................................................41
5.3.7 Email Server ......................................................................................................................................42
5.3.8 E-mail message templates ................................................................................................................43
5.3.9 Other config values ...........................................................................................................................45
5.4 Customization OPTIONS ...............................................................................................................................46
5.4.1 Locale & Time zone ..........................................................................................................................46
5.4.2 Active directory user ..........................................................................................................................46
6. Client Installation ...................................................................................................................................................47
6.1 Pre Requisites ................................................................................................................................................47
6.2 Software Installation .......................................................................................................................................47
6.3 Configuration and Customozation .................................................................................................................47
7. Troubleshooting .....................................................................................................................................................47
7.1 WCF Trace logs .............................................................................................................................................47
7.2 NLog logs .......................................................................................................................................................48

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 2


CTAS Reefer Installation Manual | October 09, 2018

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 3


CTAS Reefer Installation Manual | October 09, 2018

1. Version history

No. Filename Version Author Date Status


31 CTAS Reefer Module – Installation 7.4.7.docx 4.4 BAD 14.10.2016

Configuration parameters adjusted

32 CTAS Reefer Module – Installation 7.4.7.docx 4.5 ERK 28.10.2016

Added description of TerminalRowViewEnabled in SettingsServiceConfig

33 CTAS Reefer Module – Installation 7.4.7.docx 4.6 KLW 31.01.2017

Added description of e-mail message templates

34 CTAS Reefer Module – Installation 7.4.7.docx 4.7 ERK 02.02.2017

Added description of CTAS Reefer Data API interface configuration

35 CTAS Reefer Module – Installation 7.4.7.docx 4.8 ERK 20.02.2017

Updated description of CTAS Reefer Data API interface configuration

36 CTAS Reefer Module – Installation 7.4.8.docx 4.9 KLW 16.03.2017

Added description of DefrostOperatingModes, DefrostOperatingModeAlarmInterval,


SupposedDefrostControllerTypes, SupposedDefrostInterval in SettingsServiceConfig
37 CTAS Reefer Module – Installation 7.4.8.docx 4.10 ERK 24.03.2017

Updated description of CTAS Reefer Data API interface configuration

38 CTAS Reefer Module – Installation 7.4.8.docx 4.11 KLW 05.04.2017

Added description of EnergyCalculationDefaultVoltage and EnergyCalculationDefaultCurrentCorrection in


SettingsServiceConfig
39 CTAS Reefer Module – Installation 7.4.8.docx 4.12 ERK 05.04.2017

Updates description of CTAS Reefer Data API interface configuration

40 CTAS Reefer Module – Installation 7.4.8.docx 4.13 ERK 03.11.2017

Updates description of CTAS Reefer failover configuration

41 CTAS Reefer Module – Installation 7.4.9.docx 4.14 ERK 18.01.2018

Added description of Signal-R configuration (used port and configuration parameters)

42 CTAS Reefer Module – Installation 7.4.9.docx 5.0 BAD 25.01.2018

New Document Template

43 CTAS Reefer Module – Installation 7.4.9.docx 5.1 KLW 06.02.2018

Added description of SendMonitoredReeferDataInterval and NavisN4UpdateIsPowerForMonitoredReefers


in TOSIntegrationServiceConfig
44 CTAS Reefer Module – Installation 7.4.9.docx 5.2 ERK 28.03.2018

Updated failover and database connection description

45 CTAS Reefer Module – Installation 7.4.9.docx 5.3 PIW 28.05.2018

Added description of PropertyDisplayNameConfigurations in SettingsServiceConfig

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 4


CTAS Reefer Installation Manual | October 09, 2018

46 CTAS Reefer Module – Installation 7.4.9.docx 5.4 PIW 07.06.2018

Added description of CarrierTypes in SettingsServiceConfig

47 CTAS Reefer Module – Installation 7.4.9.docx 5.5 PIW 12.07.2018

Extend description of TerminalRowViewEnabled in SettingsServiceConfig

48 CTAS Reefer Module – Installation 7.4.9.docx 5.6 KLW 16.07.2018

Added description of SendChangedSetpoint in DataAPIServiceConfig

49 CTAS Reefer Module – Installation 7.4.9.docx 5.7 ERK 03.08.2018

Added description of ColdTreatmentLogsFolderPath in SettingsServiceConfig

50 CTAS Reefer Module – Installation 7.4.9.docx 5.8 KLW 09.10.2018

Added description of EnableEmailEscalationAlarms in SettingsServiceConfig

51 CTAS Reefer Module – Installation 7.4.9.docx 5.9 PIW 23.10.2018

Added description of PreTripTabEnabled in SettingsServiceConfig

52 CTAS Reefer Module – Installation 7.4.9.docx 5.10 PIW 16.11.2018

Added description of EnableAutoTemperatureExport in SettingsServiceConfig

53 CTAS Reefer Module – Installation 7.4.9.docx 5.11 PIW 03.12.2018

Added description of ArrivalTemperatureVariation in SettingsServiceConfig

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 5


CTAS Reefer Installation Manual | October 09, 2018

2. System overview

Reefer Mechanic
Reefer Application
Tablet

CTAS Reefer TOS

Terminal Network (LAN or WLAN)

i-PORT M350 ETM Reader Network

Wireless Communication (UHF)

iQ350 RMU iQ350 RMU iQ350 RMU iQ350 RMU iQ350 RMU iQ350 RMU

Reefer Reefer Reefer Reefer Reefer Reefer


Container Container Container Container Container Container

Figure 1: CTAS Reefer system overview

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 6


CTAS Reefer Installation Manual | October 09, 2018

CTAS Reefer CTAS Reefer CTAS Reefer


Client Client Client

CTAS Reefer
TOS Database
Service

RFID Hardware i-SHARE Service

Application Server Database Server


Figure 2: Server, services and communication channels

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 7


CTAS Reefer Installation Manual | October 09, 2018

3. Requirements

3.1 System Requirements

3.1.1 Application Server Requirements

The values below are typical values for installations with 500-1000 reefer points.

CPU Dual Core Server CPU


Memory 12 GB RAM
Disk Raid System – min. 100 GB
Operating System Windows 2008 Server R2
Network Interfaces min. 2 Ethernet interfaces

3.1.2 Database Server Requirements

CPU Dual Core Server CPU


Memory 12 GB RAM
Disk Raid System – min. 500 GB
Operating System Windows Server 2008 R2
Database Server SQL Server 2008 R2
Edition Standard1

3.2 Software Requirements

CTAS Reefer supports the following operating systems


Server:
• Windows Server 2003
• Windows Server 2008 R2
• Windows Server 2012
• Windows 7
• Windows 8
• Windows 8.1
• Windows 10

Client:
• Windows Server 2003
• Windows Server 2008 R2
• Windows Server 2012
• Windows 7
• Windows 8
• Windows 8.1
• Windows 10
Please note that CTAS Reefer does not support the RT version of Windows 8!

1
Operational requirements for archiving, backup or high availability may require different editions of the
database.

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 8


CTAS Reefer Installation Manual | October 09, 2018

Supported Database Versions


• SQL Server 2008 R2 Standard
• SQL Server 2008 R2 Enterprise
• SQL Server 20012 Standard
• SQL Server 20012 Enterprise
• SQL Server 20014 Standard
• SQL Server 20014 Enterprise

Networking Requirements
CTAS Reefer requires several connections to external systems to operate. The system diagram below shows the
interfaces, protocols and the direction of the communication relative to the “Application Server”.

CTAS Reefer
Client
Reefer Client Communication:
Port 9201 (SSL) incoming

Web-Service Communication
Port 9200 (HTTPS)

CTAS Reefer
TOS MS SQL-Server
Service

SQL-Server Communication:
RFID Hardware i-SHARE Service Port 1433 (TCP/IP) outgoing

RFID Reader Communication


Port 2101 (TCP) outgoing for
ethernet readers
Application Server Database Server

Figure 3: Communication ports and protocols (direction as seen from the Application Server).

Port Direction Protocol Purpose


9201 Outgoing SSL Communication from the client to the server.
9200 Incoming HTTPS Web-Service based TOS interface based on IDENTEC
standard
9203 Incoming HTTPS Two-way communication channel between the client and the
server
1433 Outgoing SQL Server Connection from CTAS Reefer to the SQL Server database
(TCP)
2101 Outgoing TCP Connection from CTAS Reefer (i-SHARE) to rfid readers with
Ethernet (or WiFi) interface.

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 9


CTAS Reefer Installation Manual | October 09, 2018

4. Server Installation

4.1 Pre-Requisites

CTAS Reefer server requires some operating system features to be present prior to the installation.
Server
• Message Queuing (MSMQ)
• .NET 4.6
• Windows installer 4.5
• Microsoft WSE 3.0
• SQL Server access
• Internet Information Services (IIS)

4.1.1 Windows Server 2012 pre-requisites

Server roles need to be installed as below (Server roles -> Web Server (IIS) -> Web Server -> Application
Development):

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 10


CTAS Reefer Installation Manual | October 09, 2018

Features need to be installed as below (Features -> .NET Framework 4.5 Features -> WCF Services):

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 11


CTAS Reefer Installation Manual | October 09, 2018

4.2 Migrating from an installed 32-bit to 64-bit version

If a previously installed 32 bit version of CTAS Reefer server gets updated to a 64 bit version, the installer will not
be able to migrate automatically. In order to make the migration work the following manual steps are required
before the installation:

The existing files are located in C:\Program Files (x86)\IDENTEC SOLUTIONS\CTAS Reefer\Service

Copying of the configuration files


• Create the application folder: C:\Program Files\IDENTEC SOLUTIONS\CTAS Reefer\Service
• Copy CTASReeferService.exe.config, Services.config and Custom.config (if it is present)

Copying the license file


• Create folder: C:\Program Files\IDENTEC SOLUTIONS\CTAS Reefer\Service\ Licenses
• Copy Licenses\License.xml file

To complete the manual steps, please uninstall the previously installed 32 bit version of CTAS Reefer.

A migration from 64 bit back to 32 bit work the same way, only by exchanging the folder names.

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 12


CTAS Reefer Installation Manual | October 09, 2018

4.3 Software installation

4.3.1 i-SHARE Installation

For the installation of i-SHARE please consult the “Installation and Quick start” manual distributed together with the
i-SHARE installation package.

4.3.2 Installation packages

CTAS Reefer installation suite comes in four packages (archives). Each of those consists of separate .exe file
which initiates the installation process, and .msi, which the installer content.

Installer package Description


IS.CTASReefer.Installer-[platform]-[version].zip CTAS Reefer Service installation package. Please
note, that it already includes CTAS Reefer Client
application.
IS.CTASReefer.Database.Utility-[version].zip Database utility used to configure database.
IS.CTASReefer.Client.Installer-[platform]-[version].zip CTAS Reefer Client installation package.
Dedicated only for UI client machines.
IS.CTASReefer.Client.Mobile.Installer-[platform]-[version].zip Installer of mobile version of CTAS Reefer Client.
Dedicated for machines used in the field (tablets,
handhelds)
IS.CTASReefer.Client.ClickOnceInstaller-[version].zip Installation package for sefl-updating CTAS
Reefer Client
IS.CTASReefer.Client.ClickOnceInstaller.Mobile-[version].zip Installation package for sefl-updating CTAS
Reefer Mobile Client
IS.CTASReefer.Client.ClickOnceInstaller.WalkBy-[version].zip Installation package for sefl-updating CTAS
Reefer WalkBy Client

platform is either x86 or x64, version is number of version to be installed

4.3.3 Database Setup

CTAS Reefer Database Utility (IS.CTASReefer.Database.Utility.bat) will take care of database creation during the
setup process. To enable this process the available database needs to have “mixed mode authentication” enabled.
Please be prepared to give administrative permissions to the installation process.
If configuration of the database is not default and port was changed there is a way to configure connection to a
database server using custom port. In that case, instead of using only db server name you need to provide port
using template below:
[db_server], [port]
where db_server is name or ip address of SQL Server and [port] is a custom SQL Server port.

4.3.4 CTAS Reefer Module Installation

After successfully completing the installation of all pre-requisites and CTAS Reefer Database Installer, start the
actual CTAS Reefer installation process by executing the IS.CTASReefer.Installer-[platform]-[version]-
setup.exe file of the installation package. Please be prepared to give administrative permissions to the installation
process.

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 13


CTAS Reefer Installation Manual | October 09, 2018

5. Configuration

5.1 I-SHARE

In order to capture and forward reefer data in i-SHARE the following things need to be configured:
• Device connections to all involved readers
• Creation of a new “Site” for reefer monitoring
• Creation of a new “Filter Chain” for reefer data filtering
• Adding a “Duplicate Filter” to the filter chain (for RCM tags)
• Creation of a “TRAILBLAZER Data Interface”.

Outgoing commands from CTAS Reefer to the container require a user of the group “system_rw” to be active. Create
and configure the user and note the credentials down in order to add the user to the CTAS Reefer configuration.

5.1.1 TRAILBLAZER Data Interface configuration

TRAILBLAZER Data Interface is needed for forwarding reefer data from i-SAHRE to CTAS Reefer. Create new data
interface, choose type TRAILBLAIZER Data Interface.

Provide correct URL to CTAS Reefer service:


net.tcp://[host]:9100/ILREventService
replacing [host] with the FQDN or IP address of the CTAS Reefer machine. Connection to interface can be tested by
clicking Test interface button.

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 14


CTAS Reefer Installation Manual | October 09, 2018

5.1.2 TRAILBLAZER Data Interface failover configuration

There is a way to configure failover for TRAILBLAZER Data Interface by checking Failover URL checkbox.

Provide both URL to CTAS Reefer master server:


net.tcp://[master_host]:9100/ILREventService
and Failover URL to CTAS Reefer slave server:
net.tcp://[slave_host]:9100/ILREventService
replacing [master_host] with the FQDN or IP address of the CTAS Reefer master machine and [slave_host] with the
FQDN or IP address of the CTAS Reefer slave machine. Connection to interface can be tested by clicking Test
interface button.

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 15


CTAS Reefer Installation Manual | October 09, 2018

5.2 SQL Server Reporting Services

In order to install SQL Server Reporting Services the database server needs to have Reporting Services feature
installed. The minimal edition which contains this feature is SQL Server Express with Advanced Services. Feature
is not included in SQL Server Express edition. SQL Server Express 2008 with Advanced Services can be
downloaded from: http://www.microsoft.com/en-us/download/details.aspx?id=1842. Before installing it the system
requirements have to be fulfilled. Above version does not support Windows 8 operating system. Report Server can
be installed using “Add features…” option or “Perform a new installation…” option. The report server should be
installed as a NETWORK SERVICE. The process of installation is presented on the screens below:

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 16


CTAS Reefer Installation Manual | October 09, 2018

The next step is to create user for reporting services. User has to be created under manage user accounts in the
control panel:

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 17


CTAS Reefer Installation Manual | October 09, 2018

When the user is created and the report server feature is installed the report server has to be configured under
Reporting Services Configuration Manager which is installed along with the report server:

After connecting to the instance of the database where the report server is installed 3 values has to be checked:
• Web Service URL – the url with listings of all reports and data sources uploaded to the Report Server
(the default value is http://localhost/ReportServer)
• Database – to check if there is a connection to the database
• Report Manager URL - the url to the manager in which the access to report server objects can be defined
(the default value is http://localhost/Reports/Pages/Folder.aspx)

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 18


CTAS Reefer Installation Manual | October 09, 2018

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 19


CTAS Reefer Installation Manual | October 09, 2018

The next step is to assign roles to the reporting services user created previously. To open report manager the
default link (http://localhost/Reports/Pages/Folder.aspx) can be entered in the browser.

Important notes:

• Browser has to run under administrative privileges.


• When reporting services are configured reporting feature can be selected and marked for installation in
CTAS Reefer setup. Credentials used by the installer are the same as for previously created user for
reporting services (described at the beginning of this section).

Using report manager the following changes have to be applied:

• In Folder settings new role assignment has to be defined for previously created user for reporting services.
All roles have to be selected in combo boxes:

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 20


CTAS Reefer Installation Manual | October 09, 2018

Once it is done the user should have an access to the report server. More detailed description of parameters used
by the report server is presented in the next section in Interfaces subsection of this document.

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 21


CTAS Reefer Installation Manual | October 09, 2018

5.3 CTAS Reefer Configuration

After installing CTAS Reefer server from -setup.exe file, service configuration can be customized by modifying the
CTASReeferService.exe.config file which can be found in the installation folder in the service directory. The config
file nodes structure is summarized in the CTASReeferService.exe.config table.

5.3.1 Configuration File Summary

CTASReeferService.exe.config file summary

XmlNode Description
configSections Contains configuration section and namespace declarations (ex.
WindowsService)
microsoft.web.services3 Controls the configuration options defined by the Web Services
Enhancements for Microsoft .NET (WSE)
WindowsService Defines services which starts with the CTAS system
common Contains entries used for logging
connectionStrings Specifies connection strings to the database, filled in by the installer
appSettings Contains additional configuration elements used by the application
(TOS server client user and password, CTAS Interface username and
passowrd
system.serviceModel Contains all the Windows Communication Foundation (WCF)
ServiceModel configuration elements (ex. service behaviours, service
endpoints, client endpoints, bindings)
runtime Specifies how the common language runtime handles garbage collection
and the version of an assembly to use in configuration files
system.net Contains settings that specify how the .NET Framework connects to the
network; empty by default
system.runtime.serialization Defines known types for the serialisation

In Other config values section the common and appSettings nodes are described in more details.

During the installation two other configs should be created in the service directory: Services.config and
Custom.config. The summary of the elements from these config files is presented in the tables below.

Services.config file summary

XmlNode Description
ReeferBrokerServiceConfig Used to configure access to iShare
AlarmServiceConfig Used to configure parameters for alarm checkers
ContainerServiceConfig Used to configure parameters for container checkers
SettingsServiceConfig Defines settings for the system
MessageFilterServiceConfig Used to configure message dispatcher

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 22


CTAS Reefer Installation Manual | October 09, 2018

Custom.config file summary


XmlNode Description
TOSIntegrationServiceConfig Contains configuration for TOS client – url, username, password, flag
which indicates if the extended TOS interface is used, flag which indicates
if the Navis N4 interface is used; the subelement of this config is ActiveMQ
config which defines Inbound and Outbound queue names, broker
address, username, password and default terminal, message time to live,
delivery mode and priority for ActiveMQ
ReportingServiceConfig Config used for reporting services, filled in by the installer, defines url,
username, password and domain for the Report Server
DataAPIServiceConfig Configuration used for CTAS Reefer Data API interface.

In the Behavior section, Interfaces section and Email section of this document the Services.config and
Custom.config files are described in more details.

5.3.2 Configuration Parameters

The following settings allow changing the system behavior


• Time zone
The time zone settings in CTAS reefer are based on two settings. A server wide setting which is being
applied to all clients by default and a user setting allowing a certain user to change the time zone he uses
to view the data.
Both settings can be adjusted by using the user interface.
• Reefer Container Tags vs. Temperature Tags
The two versions of CTAS Reefer are differing by the supported hardware. One supports the RCM tags
integrating to the controller of a reefer container, the other one uses the temperature tags to report direct
temperature readings.
• Required Set points.
• Alarm time for sending Tag Events.

Behaviours can be configured in the AlarmServiceConfig, CheckContainerStateServiceConfig,


SettingsServiceConfig and MessageFilterServiceConfig sections from the Services.config file. The
SettingsServiceConfig will be described first, then AlarmServiceConfig, CheckContainerStateServiceConfig and
MessageFilterServiceConfig.

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 23


CTAS Reefer Installation Manual | October 09, 2018

SettingsServiceConfig:
• RequiredContainerParameters - to define which parameters are obligatory for a container, if one of
those parameters is not set up, the missing parameter alert is raised.
• TOSIntegrationServiceEnabled - flag indicating if the integration with the TOS is enabled.
• IdentificationValidatorName - to configure which container identification checker is used.
• SupportedTagTypes - tag types supported by the server.
• DefaultContainerMonitoringInterval - if the container for which new work order is created does not
have its own monitoring interval then this parameter defines DueDate for a work order.
• IsCommodityForAutomaticStateTransitionChecked – defines whether commodity field needs to be set in
order to move container to the monitored state, if true means that only containers with commodity will be
automatically moved from connected to monitored state (when other requirements like no active alarms, no
missing parameters and no setpoint conflict are fulfilled)
• CheckCommodityHumiditySetPointConflict - flag indicating whether system checks for commodity humidity
set-point conflicts.
• CheckCommodityTemperatureSetPointConflict- flag indicating whether system checks for commodity
temperature set-point conflicts.
• ShowAllContainersOnMobile – flag indicating whether all containers are shown on mobile client
• IsUserRoleTabVisible – flag indicating whether user role tab is visible in user detail view, true by default
• IsUserSettingsVisible – flag indicating whether user can change setting, true by default
• IncludeAlarmInfoLevelInStatistics – flag indicating whether alarms with severity of info will be included in
alarms statistics and shown on dashboard, false by default
• TerminalRowViewEnabled – flag indicating whether graphical representation for terminals is enabled in the
UI

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 24


CTAS Reefer Installation Manual | October 09, 2018

<SettingsServiceConfig>
<EmailConfig>
...
</EmailConfig>
<AlarmNotificationEmailAddress>ctas@company.com</AlarmNotificationEmailAddress>
<RequiredContainerParameters>
<ContainerParameter>TemperatureExpSetPoint</ContainerParameter>
<ContainerParameter>TemperatureSetPoint</ContainerParameter>
</RequiredContainerParameters>
<SetpointsRestrictions>
<SetpointRestrictions ContainerAction="5" Brand="1" ReeferType="*"
Minimum="-30" Maximum="30" Precision="0.01" />
...
</SetpointsRestrictions>
<DefrostOperatingModes>
<OperatingMode>Defrost</OperatingMode>
</DefrostOperatingModes>
<DefrostOperatingModeAlarmInterval>40</DefrostOperatingModeAlarmInterval>
<SupposedDefrostControllerTypes>
<ControllerType>ML3</ControllerType>
<ControllerType>MP3000</ControllerType>
</SupposedDefrostControllerTypes>
<SupposedDefrostInterval>30</SupposedDefrostInterval>
<SensorDataParameters>
<ArrivalTemperatureVariation>6.0</ArrivalTemperatureVariation>
<TemperatureVariation>5.0</TemperatureVariation>
<TemperaturePrecision>0.1</TemperaturePrecision>
<CO2Variation>5.0</CO2Variation>
<CO2Precision>0.1</CO2Precision>
<HumidityVariation>5.0</HumidityVariation>
<HumidityPrecision>1.0</HumidityPrecision>
<O2Variation>5.0</O2Variation>
<O2Precision>1.0</O2Precision>
<VentilationVariation>5.0</VentilationVariation>
<VentilationPrecision>1.0</VentilationPrecision>
</SensorDataParameters>
<TOSIntegrationServiceEnabled>true</TOSIntegrationServiceEnabled>
<IdentificationValidatorName>ISOContainerValidator</IdentificationValidatorName>
<SupportedTagTypes><TagType> iQ350RMU </TagType></SupportedTagTypes>
<DefaultContainerMonitoringInterval>240</DefaultContainerMonitoringInterval>
<WorkOrderDefaultDueDateInterval>45</WorkOrderDefaultDueDateInterval>
<PretripDueDateInterval>45</PretripDueDateInterval>
<AddMonitoringEventOnWorkOrderClosing>true</AddMonitoringEventOnWorkOrderClosing>
<IsCommodityForAutomaticStateTransitionChecked>true
</IsCommodityForAutomaticStateTransitionChecked>
<CheckCommodityHumiditySetPointConflict>true</CheckCommodityHumiditySetPointConflict>
<CheckCommodityTemperatureSetPointConflict>true
</CheckCommodityTemperatureSetPointConflict>
<EnergyCalculationDefaultVoltage>400</EnergyCalculationDefaultVoltage>
<EnergyCalculationDefaultCurrentCorrection>0.25
</EnergyCalculationDefaultCurrentCorrection>

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 25


CTAS Reefer Installation Manual | October 09, 2018

<PropertyDisplayNameConfigurations>
<PropertyDisplayNameConfiguration PropertyName="Block"
DisplayName="BlockDisplayName"/>
...
</PropertyDisplayNameConfigurations>
<CarrierTypes>
<CarrierType>VESSEL<CarrierType/>
<CarrierType>TRAIN<CarrierType/>
<CarrierType>TRUCK<CarrierType/>
...
</CarrierTypes>
<ColdTreatmentLogsFolderPath>C:\ColdTreatmentStorage\</ColdTreatmentLogsFolderPath>
<EnableEmailEscalationAlarms>true</EnableEmailEscalationAlarms>
<PreTripTabEnabled>true</PreTripTabEnabled>
<EnableAutoTemperatureExport>true</EnableAutoTemperatureExport>
</SettingsServiceConfig>
SettingServiceConfig entry summary

Fields Type Definition Sample Values


EmailConfig config Described in a separate section
AlarmNotificationEmailAddress string E-mail address to which will be ctas@company.com
sent alarm notifications
SensorDataParameters config Parameters used to check if please check example
measured value is within defined
range (setpoint +/- variation) and
if setpoints difference is less
than precision of the data
RequiredContainerParameters list Specifies container parameters <ContainerParameter>
which must be filled in, if some TemperatureExpSetPoint
of those parameters are missing
</ContainerParameter>
for a container, the parameter
missing alert is raised
SetpointsRestrictions list Specifies set-point restrictions please check example
for container brands or particular
controller types
DefrostOperatingModes list Specifies defrost operating please check example
modes, which prevent of
temperature alarms raising
DefrostOperatingModeAlarmInterval int The time interval after defrost 40
operating mode in which the
temperature alarm won’t be
raised. It’s expressed in
minutes.
SupposedDefrostControllerTypes list Controller types, which don’t please check example
report defrost mode correctly
SupposedDefrostInterval int The time interval in which the 30
temperature alarm won’t be
raised when temperature is
above the limits and controller
type is on the list:
SupposedDefrostControllerType
. It’s expressed in minutes.

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 26


CTAS Reefer Installation Manual | October 09, 2018

TOSIntegrationServiceEnabled bool Flag indicating whether the true, false


integration with the TOS service
is enabled or not
IdentificationValidatorName string Specifies which validator for NonISOContainerValidator,
container identification should ISOContainerValidator
be used
SupportedTagTypes list Specifies which tag types are <TagType>
supported by the application iQ350RMU
(RMU Tags, Temperature tags)
</TagType>,
<TagType>
iQ350T
</TagType>
DeafultContainerMonitoringInterval int If the container for which work 240
order is created does not have
its own monitoring interval then
this parameter defines DueDate
for a work order, it is expressed
in minutes
WorkOrderDefaultDueDateInterval int Due date interval expressed in 45
minutes
PretripDueDateInterval int The time interval in which the 45
pretrip process should be
started. It’s expressed in
minutes.
AddMonitoringEventOnWorkOrderCl bool Flag indicating whether manual true, false
monitoring event should be
osing
added after connect work order
is closed
IsCommodityForAutomaticStateTrans bool Flag indicating wheather true, false
automatic state transition
itionChecked
(connected -> monitored)
checks the commodity of a
container.
CheckCommodityHumiditySetPointC bool Flag indicating whether system true, false
checks for commodity humidity
onflict
set-point conflicts.

CheckCommodityTemperatureSetPoi bool Flag indicating whether system true, false


checks for commodity
ntConflict
temperature set-point conflicts.
InboundContainerStates list List of container states that are <InboundContainerStates>
visible on Inbound list
<State>IncomingState</State>

<State>ConnectionPendingState</State>

</InboundContainerStates>

InventoryContainerStates list List of container states that are <InventoryContainerStates>


visible on Inventory list
<State>ConnectedState</State>

<State>MonitoredState</State>

<State>DisconnectionPendingState</State>

</InventoryContainerStates>

OutboundContainerStates list List of container states that are <OutboundContainerStates>


visible on Outbound list
<State>DisconnectedState</State>

</OutboundContainerStates>

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 27


CTAS Reefer Installation Manual | October 09, 2018

ManualContainerStates list List of container states that are <ManualContainerStates>


visible on Manual data entry list
(only on mobile clinet) <State>IncomingState</State>

<State>ConnectionPendingState</State>

<State>ConnectedState</State>

<State>MonitoredState</State>

<State>DisconnectionPendingState</State>

<State>DisconnectedState</State>

</ManualContainerStates>

EnergyCalculationDefaultVoltage double Specifies a default voltage 400


value, if it’s not read from the
sensor, used in the energy
calculation.
EnergyCalculationDefaultCurrentCorr double Specifies a default current 0.25
correction used in the energy
ection
calculation.
<PropertyDisplayNameConfigurations>
PropertyDisplayNameConfigurations list List of display names for
<PropertyDisplayNameConfiguration
properties (PropertyName PropertyName="Block"
DisplayName="BlockDisplayName"/>
attribute must be unique).
</PropertyDisplayNameConfigurations>
Display names for Block, Row
and Column property names can
be provided.
<CarrierTypes>
CarrierTypes list List of inbound or outbound
<CarrierType>VESSEL<CarrierType/>
carrier types available in <CarrierType>TRAIN<CarrierType/>
container edit and column filters. <CarrierType>TRUCK<CarrierType/>
</ CarrierTypes >

TerminalRowViewEnabled bool Flag indicating whether true, false


graphical representation for
terminals is enabled in the UI

ColdTreatmentLogsFolderPath string Path to a folder storing C:\ColdTreatmentStorage\


downloaded 556 cold treatment
reports in year/month/day folder
structure
EnableEmailEscalationAlarms bool (optional node) A value true, false
indicating whether alarms
should be escalated via e-mail.
Default value in case of missing
node: true.
PreTripTabEnabled bool (optional node) A value true, false
indicating whether pre trip tab is
enabled. Default value in case of
missing node: false.
EnableAutoTemperatureExport bool (optional node) A value true, false
indicating whether automatic
temperature export when closing
container visit enabled. Default
value in case of missing node:
false.
ArrivalTemperatureVariation double (optional node) Specifies a 6.0
accepted difference between
temperature setpoint and return
temperature when container
arrives. Default value is 6.

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 28


CTAS Reefer Installation Manual | October 09, 2018

AlarmServiceConfig:

Alarms can be configured in the AlarmServiceConfigSection. There are four alarm checkers:
NoTagUpdateAlarmChecker, NotConnectedContainerAlarmChecker, JobNotExecutedAlarmChecker,
NotLeftContainerAlarmChecker. Each of them has TimeInterval entry and TimeLimitInMinutes entry.
TimeLimitInMinutes defines the minimum frequency of the alarm checker timer. Frequency cannot be lower than
once per TimeLimitInMinutes. Frequency cannot be greater than once per one minute and this value cannot be
configured. TimeInterval is used in four cases. For NoTagUpdateAlarmChecker it defines how often events from
the tag should be generated and if the last event is older than this interval the NoTagUpdate alarm should be
raised. For NotConnectedContainerAlarmChecker it defines how often the tag should be checked for connectivity
and if the enter terminal time for the alarm checker is older than this interval the NotConnected alarm should be
raised. For JobNotExecutedAlarmChecker it defines how often a container should be checked for work order and if
the work order time is older than this time the JobNotExecuted alarm should be raised. For
NotLeftContainerAlarmChecker it defines how often a disconnected container should be checked for moving to the
left state and if the state change time is older than this time the JobNotLeftContainer alarm should be raised.

<AlarmServiceConfig>
<AlarmCheckers>
<NoTagUpdateAlarmChecker>
<TimeInterval>60</TimeInterval>
<TimeLimitInMinutes>5</TimeLimitInMinutes>
</NoTagUpdateAlarmChecker>
<NotConnectedContainerAlarmChecker>
<TimeInterval>4</TimeInterval>
<TimeLimitInMinutes>5</TimeLimitInMinutes>
</NotConnectedContainerAlarmChecker>
<JobNotExecutedAlarmChecker/>
<NotLeftContainerAlarmChecker>
<TimeInterval>5</TimeInterval>
<TimeLimitInMinutes>5</TimeLimitInMinutes>
</NotLeftContainerAlarmChecker>
</AlarmCheckers>
</AlarmServiceConfig>

AlarmServiceConfig entry summary

Fields Min [minute] Max [minute] Sample Value


NoTagUpdateAlarmChecker 1 TimeLimitInMinutes 60
NotConnectedContainerAlarmChecker 1 TimeLimitInMinutes 4
JobNotExecutedAlarmChecker 1 TimeLimitInMinutes 1
NotLeftContainerAlarmChecker 1 TimeLimitInMinutes 5

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 29


CTAS Reefer Installation Manual | October 09, 2018

ContainerServiceConfig:

Defines how often the container state should be checked. It is used for disconnected containers. If container is in
disconnected state for longer than DefaultTime it should be moved to the left state. Default time is expressed in
hours.
Container checkers can be configured in the ContainerServiceConfig section. There are two container checkers:
MoveToLeftStateContainerChecker and ExecutePreTripPlaningContainerChecker. Each of them has TimeInterval
entry and TimeLimitInMinutes entry. TimeLimitInMinutes defines the minimum frequency of the alarm checker
timer. Frequency cannot be lower than once per TimeLimitInMinutes. Frequency cannot be greater than once per
one minute and this value cannot be configured. TimeInterval is used in four cases.

<ContainerServiceConfig>
<ContainerCheckers>
<MoveToLeftStateContainerChecker>
<CheckerTimeLimit>300</CheckerTimeLimit>
<TimerInterval>1</TimerInterval>
</MoveToLeftStateContainerChecker>
<ExecutePreTripPlaningContainerChecker/>
</ContainerCheckers>
</ContainerServiceConfig>

ContainerServiceConfig entry summary

Fields Min [minute] Max [minute] Sample Value


MoveToLeftStateContainerChecker 1 TimeLimitInMinutes 300
ExecutePreTripPlaningContainerChecker 1 TimeLimitInMinutes 1

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 30


CTAS Reefer Installation Manual | October 09, 2018

MessageFilterServiceConfig:

Used to configure message dispatcher.

<MessageFilterServiceConfig>
<UseJsonChannel>false</UseJsonChannel>
</MessageFilterServiceConfig>

MessageFilterServiceConfig entry summary

Fields Type Definition Sample Values


UseJsonChannel bool Flag indicating whether json channel (Signal-R) true/false
for two-way communication between the server
and the client

5.3.3 Interface Configuration

The following communication interfaces are present


• CTAS Reefer to i-SHARE communication
• CTAS Reefer to TOS communication
• CTAS Reefer to client or handheld communication
• CTAS Reefer Data API to communicate with 3rd party systems

Interfaces can be configured in ReeferBrokerServiceConfig from Services.config file, TosIntegrationServiceConfig,


ReportingServiceConfig and DataAPIServiceConfig from Custom.config file. TOSIntegrationService and
DataAPIServiceConfig configs are not used for all clients, for that reason it was moved to the Custom.config file.
ReportingServiceConfig will be visible for the user which installed reporting services feature.

ReeferBrokerServiceConfig:

FakeIShare flag equals true is used when the connection to the iShare is not configured and system uses fake one
which means that all forward commands are faked. QueueName defines the name of the queue which stores
iShare events. IShareUserName and ISharePassword are used for not faked system.

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 31


CTAS Reefer Installation Manual | October 09, 2018

<ReeferBrokerServiceConfig>
<MachineName>.</MachineName>
<FakeiShare>true</FakeiShare>
<QueueName>private$\ctasreefer_ilr_queue</QueueName>
<DeviceName></DeviceName>
<IShareHostName>.</IShareHostName>
<IShareUserName>system_rw</IShareUserName>
<ISharePassword>******</ISharePassword>
<!-- A validity period for tag connection events in minutes. -->
<ConnectionEventValidityPeriod>2</ConnectionEventValidityPeriod>
<!-- Definition of queues for processing tag events -->
<TaskPoolDefinitions>
<TaskPoolDefinition Name="BrokerTaskPool-Slow" TaskPoolSize="2">
<TypePairs>
<TypePair EventType="*" ReeferType="7"/>
<TypePair EventType="Connected-InitialInfo" ReeferType="7"/>
<TypePair EventType="Connected-InitialInfo-UpdateSetup" ReeferType="7"/>
<TypePair EventType="Connected-UpdateSetup" ReeferType="7"/>
</TypePairs>
<OutboundCommands>true</OutboundCommands>
</TaskPoolDefinition>
<TaskPoolDefinition Name="BrokerTaskPool-Normal" TaskPoolSize="4">
<TypePairs>
<TypePair EventType="Connected" ReeferType="7"/>
<TypePair EventType="Disconnected" ReeferType="7"/>
</TypePairs>
</TaskPoolDefinition>
<TaskPoolDefinition Name="BrokerTaskPool-Fast" TaskPoolSize="4">
<TypePairs>
<TypePair EventType="PowerChanged" ReeferType="7"/>
<TypePair EventType="MonitoredDataChange" ReeferType="0"/>
<TypePair EventType="MonitoredDataChange" ReeferType="1"/>
<TypePair EventType="MonitoredDataChange" ReeferType="2"/>
<TypePair EventType="MonitoredDataChange" ReeferType="3"/>
<TypePair EventType="MonitoredDataChange" ReeferType="5"/>
</TypePairs>
</TaskPoolDefinition>
</TaskPoolDefinitions>
<IShareLocksEnabled>false</IShareLocksEnabled>
</ReeferBrokerServiceConfig>

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 32


CTAS Reefer Installation Manual | October 09, 2018

ReeferBrokerServiceConfig entry summary

Fields Description Sample Value


MachineName The name of the computer should be valid for the local machine
FakeiShare Indicates if faked iShare true, false
should be used. Should be
enabled for testing purposes
only
QueueName The name of the queue private$\ctasreefer_ilr_queue
where iShare stores events
DeviceName The name of the device Empty by deafult
IShareHostName The name of the host where should be valid for the local machine
iShare runs
IShareUserName User for iShare system_rw
ISharePassword Password for iShare some password
ConnectionEventValidityPeriod A validity period for tag 2
connection events in minutes.
TaskPoolDefinitions Configuration of seperate
queues for tag events
processing. Each kind of
reefer tag (and each reefer
type) event may be
configured to be processed in
seperate queue, depending
on it’s complexity. Not to be
changed unless performance
issues are seen.
UnpoweredAsDisconnected Indicates if Upowered reefers True, false. Default is false
should be treated as
disconnected

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 33


CTAS Reefer Installation Manual | October 09, 2018

TOSIntegrationServiceConfig:

FakeTOSClient flag equals true is used when the TOS system is faked. Besides that TOSClientUrl,
TOSClientUserName, TOSClientPassword can be configured. PollM1MessageTimeInterval is expressed in
minutes and defines how often polling message is executed; HeartbeatMessageTimeInterval is expressed in
minutes and defines how often the heartbeat message is executed.

<TOSIntegrationServiceConfig>
<FakeTOSClient>true</FakeTOSClient>
<TOSClientUrl>http://localhost:8088/ArgobasicService</TOSClientUrl>
<TOSClientUserName>admin</TOSClientUserName>
<TOSClientPassword>******</TOSClientPassword>
<TOSScopeCoordinateIds>CTW/DEWVN/CTW/CTW1</TOSScopeCoordinateIds>
<!-- A time interval for polling M1 message expressed in minutes. -->
<PollM1MessageTimeInterval>15</PollM1MessageTimeInterval>
<!-- A time interval for sending heartbeat message expressed in minutes. -->
<HeartbeatMessageTimeInterval>1</HeartbeatMessageTimeInterval>
<UseExtendedTOSInterface>false</UseExtendedTOSInterface>
<UseTOSNavisN4Interface>false</UseTOSNavisN4Interface>
<!-- A flag indicating whether work orders should be generated
from N4 interface messages. -->
<GenerateWorkOrdersFromN4Messages>false</GenerateWorkOrdersFromN4Messages>
<NavisN4UpdateManuallyMonitoredReefers>false</NavisN4UpdateManuallyMonitoredReefers
>
<!-- Possible excluded location types: VESSEL, TRUCK, RAILCAR, TRAIN-->
<ExcludedLocationTypes>
<LocationType>VESSEL</LocationType>
<LocationType>RAILCAR</LocationType>
</ExcludedLocationTypes>
<!-- Navis 3.7 configuration -->
<UseTOSNavis37Interface>true</UseTOSNavis37Interface>
<TOSListeningPort>5555</TOSListeningPort>
<!-- The maximum number of items (ex. messages) sent in one package. -->
<MaximumItemCountPerPackage>100</MaximumItemCountPerPackage>
<!-- Settings for ActiveMQ interface. -->
<!-- Is ActiveMQ interface enabled. -->
<UseActiveMQInterface>true</UseActiveMQInterface>
<!-- Configuration for ActiveMQ TOS interface-->
<ActiveMQConfig>
<!-- ActiveMQ Inbound queue name. -->
<InboundQueueName>LBCT.IDENTEC.RAMS.INBOUND</InboundQueueName>
<!-- ActiveMQ Outbound queue name. -->
<OutboundQueueName>LBCT.IDENTEC.RAMS.OUTBOUND</OutboundQueueName>
<!-- ActiveMQ broker address. -->
<BrokerAddress>tcp://localhost:61616</BrokerAddress>
<!-- ActiveMQ user name. -->
<UserName>ActiveMQUserName</UserName>
<!-- ActiveMQ password. -->
<Password>ActiveMQPassword</Password>
<!-- Default value for terminal field for ActiveMQ interface -->
<DefaultTerminal>LBCT</DefaultTerminal>

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 34


CTAS Reefer Installation Manual | October 09, 2018

<!-- Time to live for all messages in minutes -->


<MessageTimeToLive>30</MessageTimeToLive>
<!-- Message delivery mode -->
<DeliveryMode>Persistent</DeliveryMode>
<!-- Message priority -->
<Priority>Normal</Priority>
<!—Sender identification -->
<Sender>IDENTEC.CTAS</Sender>
<!-- Ping message interval in minutes -->
<PingInterval>2</PingInterval>
</ActiveMQConfig>
</TOSIntegrationServiceConfig>

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 35


CTAS Reefer Installation Manual | October 09, 2018

TosIntegrationServiceConfig entry summary

Fields Description Sample Value


FakeTOSClient Switch between fake TOS and TOS true, false

TOSClientUrl The url for the TOS client http://localhost:8088/ArgobasicService

TOSClientUserName User name for TOS admin


TOSClientPassword Password for TOS Some password

TOSScopeCoordinateIds Scope coordinates for TOS CTW/DEWVN/CTW/CTW1

PollM1MessageTimeInterval Time frequency for poll message in 1


minutes
HeartbeatMessageTimeInterval Time frequency for heartbeat 1
message in minutes
SendMonitoredReeferDataInterval Time frequency for sending null (default value), 240
monitored data to N4 interface in
minutes. By default the sending
data is switched off (no XML node)
UseExtendedTOSInterface A flag indicates, if the extended false
interface should be used
MaximumItemCountPerPackage The maximum number of items 100
(ex. messages) sent in one
package
UseTOSNavisN4Interface A flag which indicates if NavisN4 true, false
interface is enabled. If false it
means that the heartbeat message
and the poll message will not be
executed and TOS client will be
inactive
UseTOSNavis37Interface A flag which indicates if Navis 3.7 true, false
interface is enabled.
TOSListeningPort Port used to exchange 5555
communication with Navis 3.7
interface.
UseActiveMQInterface A flag which indicates if the true, false
ActiveMQ interface should be used
Navis37RemoveContainersWhenEmp Controls whether empty container true, false
list in Navis 3.7 results in moving
tyList
containers to Left
GenerateWorkOrdersFromN4Messag A flag indicating whether work true, false
orders should be generated from
es
N4 interface messages.
NavisN4UpdateManuallyMonitoredRe A flag indicating whether system true, false
should propagate updates of
efers
manually monitored reefers to N4
interface.
NavisN4UpdateIsPowerForMonitored A flag indicating whether system true (default value), false
should update ‘is-power’ flag in N4
Reefers
interface. By default it’s true (no
XML node)
ExcludedLocationTypes A list of location types, for which VESSEL, TRUCK, RAILCAR, TRAIN
reefers are considered as left.

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 36


CTAS Reefer Installation Manual | October 09, 2018

ActiveMQConfig subentry summary

Fields Description Sample Value


InboundQueueName Name of a queue to which TOS LBCT.IDENTEC.RAMS.INBOUND
send data
OutboundQueueName Name of a queue from which TOS LBCT.IDENTEC.RAMS.OUTBOUND
reads data
BrokerAddress Address of ActiveMQ broker tcp://localhost:61616
UserName User name used to authorize to Some user name
use ActiveMQ
Password Password used to authorize to use Some password
ActiveMQ
DefaultTerminal Dafault value for location field LBCT

MessageTimeToLive Message time to live in minutes 30

DeliveryMode Message delivery mode NonPersistant, Persistant

Priority Message priority Lowest, VeryLow, Low, AboveLow,


BelowNormal, Normal, AboveNormal,
High, VeryHigh, Highest
Sender Sender identification IDENTEC.CTAS

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 37


CTAS Reefer Installation Manual | October 09, 2018

ReportingServiceConfig:

Defines url, username, password and domain for the Report Server. Installer enables Reporting Services feature by
setting enabled="false" in CTASReeferService.exe.config in <service name="ReportingService"…>
Entry. To setup remote connection to the Reporting Service SSRSClientUrl should contain machine name instead
of localhost.

<ReportingServiceConfig>
<ReportingConfig>
<SSRSClientUrl>http://localhost/ReportServer</SSRSClientUrl>
<SSRSUser>SSRSUser</SSRSUser>
<SSRSPassword>******</SSRSPassword>
<SSRSDomain>.</SSRSDomain>
<ReportsFolder>Identec</ReportsFolder>
</ReportingConfig>
</ReportingServiceConfig>

ReportingServiceConfig entry summary

Fields Description Sample Value


SSRSClientUrl The url of the report server http://localhost/ReportServer
SSRSUser The name of the reporting SSRSUser
service
SSRSPassword The password for the ******
reporting service user
SSRSDomain The name of the domain (ex. .
Computer name)
ReportsFolder A root folder for CTAS Reefer Identec
reports.

DataAPIServiceConfig:

Allows to enable CTAS Reefer Data API interface to be used with 3rd party system to exchange visit data.

<DataAPIServiceConfig>
<IsDataAPIEnabled>true</IsDataAPIEnabled>
<UserName>ctas</UserName>
<Password>ctas</Password>
<DataAPIServiceUrl>http://localhost:9205/DataAPIService</DataAPIServiceUrl>
<SendVisitDataInterval>60</SendVisitDataInterval>
<SendAllMonitoringsWithinInterval>false</SendAllMonitoringsWithinInterval>
<DataTypes>
<DataType>Monitoring</DataType>
<DataType>Event</DataType>
<DataType>Alarm</DataType>
</DataTypes>
</DataAPIServiceConfig>

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 38


CTAS Reefer Installation Manual | October 09, 2018

DataAPIServiceConfig entry summary

Fields Description Sample Value


IsDataAPIEnabled Indicated whether CTAS Reefer Data true
API is enabled
UserName User name used for communication ctas
with external system
Password Password used for communication ctas
with external system
DataAPIServiceUrl Address to external system http://localhost:9205/DataAPIService
SendVisitDataInterval Interval for sending visit data to 60
external system, in minutes, by
default set to 60 minutes
SendAllMonitoringsWithinInte Indicate whether all monitoring false
events from defined interval for each
rval
visit are send, if set to false only last
event is send, by default set to false
SendChangedSetpoint Indicate whether data is sent false
immediately when any setpoint is
changed, by default: false
DataTypes Definition of data types that CTAS <DataTypes>
Reefer sends to external system. <DataType>Monitoring</DataType>
There is a possibility to configure <DataType>Event</DataType>
combination of Monitoring, Event and <DataType>Alarm</DataType>
Alarm data type.
</DataTypes>

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 39


CTAS Reefer Installation Manual | October 09, 2018

5.3.4 Failover configuration

In order to use CTAS Reefer with failover mechanism you must select Failover feature during CTAS Service
installation on two machines that will be used as master and slave nodes. CTAS Reefer service installed on both
machines should be configured to use the same database. Make sure that those machines are on the same LAN
network are available for each other.
After installation FailoverCTASReeferService.exe.config file has to be adjusted on both machines accordingly so
that each Failover service could communicate with each other. IP addresses or hostnames have to be match on
both machines.

First, FailoverServiceConfig configuration section in the .config file has to be edited.

FailoverServiceConfig entry summary

Fields Type Definition Sample Values


Host string FQDN or IP address used to access fialover service
from remote host
FailoverTimeoutSec int Time after failover service will start CTAS service 20
WindowsServiceName string Name of the windows CTAS Service that would be CTASReeferService
started by Failover service
SenderID int Unique id of the failover node, Master should be always 1
lower than slave node
IsMaster bool Indicates if the current failover service should act as a true
master node

After filling out FailoverServiceConfig section, find section that defines connection to the other failover
node. Please look for url net.tcp://[remote_host]:5999/FailoverService . Replace [remote_host] with the
FQDN or IP address of the other machine that will be failover node.

Those modifications of FailoverCTASReeferService.exe.config has to be performed on both machines accordingly.

Please note, that before starting failover windows services on both machines, you should first stop CTASReefer
windows services on both machines – as it will normally be after successful installation of CTAS Reefer.

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 40


CTAS Reefer Installation Manual | October 09, 2018

5.3.5 I-Share failover configuration

In order to use CTAS Reefer with i-Share configured with failover additional configuration needs to be done on
CTAS Reefer side. ReeferBrokerEngineServiceConfig configuration section in Services config has to be edited,
nodes below need to be added:

<Url>https://[master_host]:9220/i-SHARE/iShare.asmx</Url>
<Failover>
<Url>https://[slave_host]:9220/i-SHARE/iShare.asmx</Url>
</Failover>

Replace [master_host] with the FQDN or IP address of the other machine that will be a master node of
i-Share failover and [slave_host] with the FQDN or IP address of the other machine that will be a slave node
of i-Share failover.

5.3.6 Self-updating client deployment

In order to use CTAS Reefer with self-updating client deployment you must select Self-updating client feature
during CTAS Service installation and client installation should be performed with dedicated installation packages.
Self-updating client deployment enables automatic updates of CTAS Reefer Clients (both standard and mobile)
without the need to uninstall previous client version.

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 41


CTAS Reefer Installation Manual | October 09, 2018

5.3.7 Email Server

CTAS Reefer can forward alarms and alarm escalations to certain users. To enable this functionality email settings
are required in the server configuration. The configuration can be found in the Services.config file in
SettingsServiceConfig section and EmailConfig subsection.

<SettingsServiceConfig>
<EmailConfig>
<Host>smtpx17.msoutlookonline.net</Host>
<EnableSsl>true</EnableSsl>
<DeliveryMethod>Network</DeliveryMethod>
<UseDefaultCredentials>false</UseDefaultCredentials>
<ServerPort>465</ServerPort>
<EmailAddress>ctas@identecsolutions.com</EmailAddress>
<EmailDisplayName>CTAS Reefer</EmailDisplayName>
<EmailPassword>******</EmailPassword>
</EmailConfig>

</SettingsServiceConfig>

EmailConfig summary

Fields Type Definition Sample Values


Host string The name or IP address of the host smtpx17.msoutlookonline.net
used for SMTP transactions
EnableSsl bool Specifies whether the email true, false
client uses Secure Sockets Layer
(SSL) to encrypt the connection
DeliveryMethod enum Specifies how outgoing email Network, PickupDirectoryFromIis,
messages will be handled SpecifiedPickupDirectory
UseDefaultCredentials bool Controls whether the Default true, false
Credentials are sent with requests
ServerPort int The port used for SMTP 465
transactions.
EmailAddress string The address of the email ctas@identecsolutions.com

EmailDisplayName string Specifies the name displayed in the CTAS Admin


header of the message
EmailPassword string The password for the email some password

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 42


CTAS Reefer Installation Manual | October 09, 2018

5.3.8 E-mail message templates

All the e-mail messages can be customized using EmailMessageTemplates.xml file (in the
Service\EmailMessageTemplates folder). After the installation there is only a file with default e-mail templates
(DefaultEmailMessageTemplates.xml file) and the file with custom templates will be created from the default file
before the first e-mail creation. You can also create such file by copying and renaming the default file.

Structure of the file:

<EmailMessageTemplateSettings>
<MissingValue>n/a</MissingValue>
<EmailMessageTemplates>
...
<EmailMessageTemplate>
<Name>DispatchAlarm</Name>
<SubjectTemplate>{alarm.ShortDescription}</SubjectTemplate>
<BodyTemplate>{message}
{alarm.LongDescription}</BodyTemplate>
</EmailMessageTemplate>
...
</EmailMessageTemplates>
</EmailMessageTemplateSettings>

Field Type Definition Sample Values


MissingValue string A string used as a placeholder n/a
when a value in curly brackets
cannot be evaluated (null
reference, missing property etc.)
EmailMessageTemplate enum A unique template identification DispatchAlarm, EscalateAlarm,
NotifyAlarm, SendReminder,
Name SendReport, ResetPassword,
RemindUsername
EmailMessageTemplate string A subject template which can {alarm.ShortDescription}
contain values (in curly brackets) to
SubjectTemplate
be evaluated
EmailMessageTemplate string A body template which can contain {message}
values (in curly brackets) to be {alarm.LongDescription}
BodyTemplate
evaluated

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 43


CTAS Reefer Installation Manual | October 09, 2018

Source objects used in the templates:

Source Object Type Definition Used In Templates


alarm Alarm Represents a container alarm. DispatchAlarm,
Sample values: EscalateAlarm, NotifyAlarm
{alarm.ShortDescription}
{alarm.LongDescription}
message string A comment provided by user, DispatchAlarm
who dispatched the alarm
preTripPlanning PreTripPlanning Represents a pre-trip planning SendReminder
with a list of containers, schedule
and action to be performed.
Sample values:
{preTripPlanning.Name}
scheduleDateString string A pre-trip planning schedule date SendReminder
formatted using system settings
containerList string A list of container identifications SendReminder
in separated lines
reportToGenerate ScheduledReport A definition of the report, which SendReport
will be automatically generated
and sent to assigned users.
Sample values:
{reportToGenerate.ReportName}
dateFromString string A report start date formatted SendReport
using system settings
dateToString string A report end date formatted SendReport
using system settings
password string A generated password ResetPassword
person Person Represents a CTAS Reefer user. RemindUsername
Sample values:
{person.UserName}

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 44


CTAS Reefer Installation Manual | October 09, 2018

5.3.9 Other config values

Other values which can be configured in the CTASReeferService.exe.config file. It contains logging and appSettings
entries:

Logging entry:

The name of the log file is defined in configFile arg key. For nlog configFile ( value="~/NLog.config") file value
(value="FILE") in configType should be used. For log4net configFile ( value="~/log4net.config") file watch value
(value="FILE-WATCH") in configType should be used.

<logging>
<factoryAdapter
type="IS.CTASReefer.Common.Logging.ExtendedNLogLoggerFactoryAdapter,
IS.CTASReefer.Common">
<arg key="configType" value="FILE" />
<arg key="configFile" value="~/NLog.config"/>
</factoryAdapter>
</logging>

AppSettings entry:
In AppSettings TOSServerClientUser and TOSServerClientPassword (credentials used for the TOSClient) and also
CTASInterfaceUsername and CTASInterfaceInterfacePassword parameters (credentials used for the
IdentecInterface) should be provided.

<appSettings>
<add key="TOSServerClientUser" value="interfaceTestUser" />
<add key="TOSServerClientPassword" value="interfaceTestPassword" />
<add key="CTASInterfaceUsername" value="interfaceTestUser" />
<add key="CTASInterfacePassword" value="interfaceTestPassword" />
<add key="DataAPIUser" value="interfaceTestUser"/>
<add key="DataAPIPassword" value="interfaceTestPassword"/>
<add key="Version" value="7.0.21"/>
</appSettings>

AppSettings entry summary

Fields Description Sample Value


TOSServerClientUser TOSClient user interfaceTestUser

TOSServerClientPassword TOSClient password interfaceTestPassword

CTASInterfaceUsername IdentecInterface user interfaceTestUser

CTASInterfacePassword IdentecInterface password interfaceTestPassword

DataAPIUser CTAS Reefer Data API user interfaceTestUser

DataAPIPassword CTAS Reefer Data API password interfaceTestPassword

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 45


CTAS Reefer Installation Manual | October 09, 2018

5.4 Customization OPTIONS

5.4.1 Locale & Time zone

5.4.2 Active directory user

To configure new active directory user the following should be fulfilled:


• user should be permitted for remote access
• group: domain- user, identec-user, zzisa_all
• user should be NOT permitted for RAS (VPN)
• remote surveillance should be active

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 46


CTAS Reefer Installation Manual | October 09, 2018

6. Client Installation

6.1 Pre Requisites

For the installation of CTAS Reefer client, please make sure the following components are available.
• Message Queuing (MSMQ)
• .NET 4.6
• Windows installer 4.5

6.2 Software Installation

6.3 Configuration and Customozation

7. Troubleshooting

In case of problems, IDENTEC support will assist you. In order to prepare all requested information please
collected the following information:
• Description of the problem with steps to reproduce
• Service Configuration
• Service Log Files
• Client Log Files

7.1 WCF Trace logs

You can switch on the WCF Trace logs in the CTASReeferService.exe.config file.
Please find a section:

<!--
<system.diagnostics>
<trace autoflush="true" />
<sources>
<source name="System.ServiceModel" switchValue="Information, ActivityTracing"
propagateActivity="true">
<listeners>
<add name="wcfTraceListener" type="System.Diagnostics.XmlWriterTraceListener"
initializeData="Logs\WcfTrace.svclog" />
</listeners>
</source>
</sources>
</system.diagnostics>
-->

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 47


CTAS Reefer Installation Manual | October 09, 2018

and uncomment it:

<system.diagnostics>
<trace autoflush="true" />
<sources>
<source name="System.ServiceModel" switchValue="Information, ActivityTracing"
propagateActivity="true">
<listeners>
<add name="wcfTraceListener" type="System.Diagnostics.XmlWriterTraceListener"
initializeData="Logs\WcfTrace.svclog" />
</listeners>
</source>
</sources>
</system.diagnostics>

Save the configuration file and restart the service.

You can switch off WCF Trace logs by commenting the section and restarting the service.

You can also switch on and off WCF Trace logs on the client side. In this case you need to edit
IS.CTASReefer.Client.exe.config or IS.CTASReefer.Client.Mobile.exe.config file (depends on client type).

7.2 NLog logs

You can define minimum levels of logging in the NLog.config files.

Please find a section:

<rules>
...
<logger name="*" minlevel="Info" writeTo="logfile" />
...
</rules>

and set the minimum levels (Trace, Debug, Info, Warn, Error or Fatal) for particular loggers.

Copyright © 2018 IDENTEC SOLUTIONS. All rights reserved. 48