The CI service is an active – active component and is responsible for the opening hours and standby duty feature. This service has to be installed on all TM machines.

Installation

  1. Run the  CI.Setup.msi
  2. On the  Luware-TM-CI Configuration Settings   screen of the setup pay attention to fill the
    1. Instance Name
    2. Port number
    3. Configure Certificate Security

  3. For security reason TM provides possibility to use certificate-based encryption and verification during the components communication. To configure certificate based authentication, select ‘Configure Certificate Security’ check box and press ‘Next’ button to open a page with server certificate settings.

    Example of filled Luware-TM-CI Configuration Settings screen

  4. If ‘Configure Certificate Security’ check box was set to true, configure the server and client certificate settings as the next step. The client settings specify which settings CI will use while connecting to PS. The server settings are used to validate another services when they try to connect to CI.

    Example of filled Luware-TM-CI Server Certificate Settings screen
    SettingsDescriptionValue

    Mode

    Transfer security modes offered by WCF to ensure a secured communication between a client and a server.

    • None : This mode ensures that no security is applied while communication between server and client.
    • Transport:  As the name suggests, it is concerned with security of communication between a client and a service over a network protocol. It guarantees the confidentiality and integrity of messages at transport level since transport security secures the entire communication channel.

    Validation Mode

    The mode that specifies how incoming certificate is validated and how trust is determined .

    • None: In this mode no validation is perfomed.
    • ChainTrust: :  In this mode WCF simply validates the certificate against the issuer of a certificate known as a root authority (the expiration time is checked too).
    • PeerTrust:  In this mode WCF simply checks if the incoming certificate is installed in the  Trusted People  folder in the certificate store (the expiration time is checked too).
    • PeerOrChainTrust:  Mixed mode.

     

    Is Dedicated

    The flag that defins which certificate is used for encryption.

    • False: Encryption is done with default certificate. It means that certificate with the hostname of the machinefrom the Personal Store is used on server side.
    • True : Encryption is done with a dedicated certificate. It means there is  possibility to configure identifier (thumbprint) of the certificate.

    Thumbprint

    The thumbprint is a hash value computed over the complete certificate, which includes all its fields, including the signature.

    (info) The system reports all errors related to  connection or certificate issues to a log file ‘C:\Program Files\Luware AG\TM-ICH\log \connectionIssues.log’.

    See →  prepare certificate thumbprint

Note: The system reports all errors related to  connection or certificate issues to a log file ‘C:\Program Files\Luware AG\TM-ICH\log\connectionIssues.log’.

Open  Services  and start the installed service.

  • Check that service is successfully started without any errors in Event Viewer or in the log file

c:\Program Files\Luware AG\TM-CI\log\regularLog.txt

Configuration


Support for Exchange Web Service (EWS) APIs for Exchange Online is being phased out by Microsoft1 in favor of OAuth 2.0 (via O365 credentials). TeamManager features already use Graph API and can be reconfigured. Check in your configuration that "O365" settings are used instead of "Exchange".

(tick) AREAS TO CHECK: Mailboxes, Calendars, Voicemail, Topology Settings. Note that "Mail Manager" as an exception will not get further Graph support.

1 https://techcommunity.microsoft.com/t5/exchange-team-blog/upcoming-api-deprecations-in-exchange-web-services-for-exchange/ba-p/2813925

In the TM-Configurator application:

  1. Open TM Configurator -> Topology -> Components (Server)

  2. Add CI component as it is shown in the example (select the CI Server Type, System Instance, Activity Order and fill the service’s Settings according to the table below):

    Example of filled CI properties
KeyDescription
CallbackCategoryNameDefines the name of category which will be taken as callback.


Example : callback

ClosedCategoryNameDefines the name of category which will be taken as closed.


Example : closed

FlexibleTimeCategoryNameDefines the name of category which will be taken as flexible.


Example : flexible

InternationalHolidayCategoryNameDefines the name of category which will be taken as international holiday.


Example : international

LocalHolidayCategoryNameDefines the name of category which will be taken as local holiday.


Example : local

NationalHolidayCategoryNameDefines the name of category which will be taken as national holiday.


Example: national

O365PollingTimeInSecThe polling time in seconds to check for updated opening hours or standby duty calendar entries.


Example : 30

OpenCategoryNameDefines the name of category which will be taken as open.


Example : open

PreHolidayCategoryNameDefines the name of category which will be taken as pre-holiday.


Example : preholiday

Special1CategoryNameDefines the name of category which will be taken as special 1.
Special2CategoryNameDefines the name of category which will be taken as special 2.
Special3CategoryNameDefines the name of category which will be taken as special 3.
Special4CategoryNameDefines the name of category which will be taken as special 4.
StandByDutyCategoryNameDefines the name of category which will be taken as standby duty.


Example : standbyDuty

SynchronizationTimeThe time in 24 hours format when the CI will synchronize the calendar changes. This time is important if the streaming notifications mechanism cannot be used to access a calendar.


 

Note :  It’s strongly recommended to set synchronization time outside 02:00 – 03:00 o’clock.

 

Example   01:00:00

UpdateDelayWith the usage of streaming notifications to access the exchange calendar, an update will be received multiple times. To avoid unnecessary operations, the CI waits for a specified delay in seconds to update the memory.


Example : 30