The PS service is an active – passive component and layer between the TM components and the DB. The PS Service should be installed on all TM application servers.

Installation

  1. Run the  PS.Setup.msi
  2. On the  Luware-TM-PS Configuration Settings   screen of the TM.PS.Setup.msi pay attention to fill the
    1. Instance Name
    2. Port Number
    3. SQL Server
    4. SQL Instance
    5. Database

  3. Configure Certificate Security
    (info) When you select the ‘Configure Certificate Security’ check box and press ‘Next’ button to open a page with server certificate settings. Also see prepare certificate thumbprint

    PS Setup - Configure Server and DB Settings

  4. If ‘Configure Certificate Security’ check box was set to true, configure the server certificate settings as the next step.The server settings are used to validate clients during connection to PS.

    PS Setup - Configure certificate security
    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

  5. Complete the installation

Post installation 

Open Services and start the Luware-TM-PS service

Check if PS service in Windows Services is started

Check that PS service is successfully started without any errors in Event Viewer or in the log file. 
c:\Program Files\Luware AG\TM-PS\log\regularLog.txt

The Persistence Service is vital point to TM operation as all other components communicate via PS. 

A first check of Logs is always recommended, even when the service appears as "running". 

Configuration

It is not necessary to add the PS Component to the Luware-TM-Configurator application. However it is highly recommended to do so because it allows you to see the status of further added services later down the line.

In the Luware-TM-Configurator application:

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

  2. Add PS component as it is shown in the example

    Example of an PS Entry in the TM Configurator

    (lightbulb) There are no properties for PS to configure.

Special Case when using Fallback / Failover Servers

In case you are using more than 1 TM server (each with their installation of the PS), the fail-over-partner(s) need to be configured in the respective config file: 

  1. Locate and open "C:\Program Files\Luware AG\TM-PS\TM.PS.Service.exe.config "
  2. Find the "<connectionStrings" entry
  3. Locate the entry that goes like ";Data Source=<yourSQL Server>\TM;"

  4. Add the following entry so it looks as follows:

    Failover partner connections tring

    ;Data Source=<YourSQLServer>\TM;Failover Partner= <YourFallbackServer>\TM;
    TEXT
  5. Repeat this step for every additional server running the PS-component (with "<YourSQLserver>" and "<YourFallBackServer>" adapted accordingly)