InTime Server

How to install License Server and InTime Server separately?

215 views February 15, 2019 February 20, 2019 pohheng 0

Introduction

The License Server is a service to enable InTime to use floating licenses. The InTime Server is a service that schedules jobs, and manages files and other operations. These two services are by default built into a single start_server.sh/bat script. In some environments, the IT administrator needs to run the License Server on Server A and the InTime Server on Server B. The License Server generally uses very little CPU and memory resources whereas the InTime Server requires more storage space for data files generated by each InTime client/worker.

Update 31st Jan 2019

As of v2.6.10, users can choose the type of InTime Server installation. Windows users are also able to specify an InTime Server installation directory. The types of installation are listed below. See the screenshots for the different installation types on Windows and Linux

  1. Full installation – Both InTime Server and License Server will be installed.
  2. License Server Only – Only License Server will be installed.
  3. InTime Server Only – Only InTime Server will be installed.

Windows installation wizard will display the different installation options available. Check the appropriate checkbox and click next to continue.

 

For a Linux installation, the installation options will be presented on the command line. Select the appropriate option and hit <Enter> to continue.

Verifying archive integrity... All good.
Uncompressing Plunify InTime Server version 2.6.10 (Build 3e011a2)....
Installation selection ('1' Full installation of InTime Server/License Server, '2' for License Server only, '3' for InTime Server only) [1]

For a less verbose installation process in Linux, set the environment variable DEFAULT_INSTALL=X where X is either 1, 2 or 3.

Example

In this example, Server B runs the License Server (IP: 10.8.0.7) and Server A runs the InTime Server (IP: 10.8.0.5). The InTime Client has access to the InTime Server but not to the License Server. It is also possible to have the License Server running in Linux and the InTime Server running in Windows, and vice versa.

Update 31st Jan 2019

As of v2.6.10, users can specify the log files’ directories for both the InTime Server and the License Server. Use the -wd <directory location> option when starting either InTime Server or the License Server to set the “working directory”. The “working directory” is a location to keep log files and some application-specific files.

In Server B, launch a terminal console and go to /home/edaadmin/plunify/licenseserver/ directory and perform a quiet installation. When installation is done, make sure to copy server.lic to /home/edaadmin/plunify/licenseserver/.

[admin@10.8.0.7 licenseserver]$ cd /home/edaadmin/plunify/licenseserver
[admin@10.8.0.7 licenseserver]$ DEFAULT_INSTALL=2 sh intimeserver_v2.6.10_64bit_linux.sh 
Verifying archive integrity... All good. 
Uncompressing Plunify InTime Server version 2.6.10 (Build 3e011a2).... 
Installing License Server
License Server installation OK.

[admin@10.8.0.7 licenseserver]$ ./license_server.sh
----- SHELL SCRIPT VARIABLES -----
SERVERIP 1 = 10.8.0.7

Starting License Server       [ OK ]
License server.lic            [ OK ]
License has started?          [ OK ]
License not expired?          [ OK ]
License Mac 00:0D:3A:40:75:1D [ OK ]
License features              [ OK ]

Server A, on the other hand, is a server that is going to run InTime Server service to schedule and submit jobs. Launch a terminal console. Navigate to the installation directory, for example, /home/edaadmin/plunify/intimeserver/.

[admin@10.8.0.5 intimeserver]$ cd /home/edaadmin/plunify/intimeserver 
[admin@10.8.0.5 intimeserver]$ DEFAULT_INSTALL=3 sh intimeserver_v2.6.10_64bit_linux.sh 
Verifying archive integrity... All good. 
Uncompressing Plunify InTime Server version 2.6.10 (Build 3e011a2).... 
Installing InTime Server 
Install support for SQLite
InTime Server installation OK. 

[admin@10.8.0.5 intimeserver]$ ./start_server.sh -licenseip 10.8.0.7 -licenseport 39940 -nolicense
----- SHELL SCRIPT VARIABLES -----
SERVERIP 1 = 10.8.0.5

$---- START OF LOG FILE 2.6.10-5834a4e ----
UTC DATE/TIME: 2019-01-12 02:06:08.120

$---- START OF LOG FILE 2.6.10-5834a4e ----
UTC DATE/TIME: 2019-01-12 02:06:08.120
JDBC (plunify.db)             [  OK  ]
JDBC (intimeruns.h2.db)       [  OK  ]
Starting InTime Server        [  OK  ]
Starting License Server       [FAILED]
Starting ACL Server           [  OK  ]
License server.lic            [FAILED]
License has started?          [  OK  ]
License not expired?          [  OK  ]
License Mac 00:0D:3A:40:75:1D [  OK  ]
License features              [  OK  ]

In the InTime Client, under File->Settings, key in the InTime Server IP address, click on the “Test and Configure button” to test the communications (includes licensing) flow.

Applies to:

  • Linux Operating System
  • Windows Operating System

Knowledge Base ID: 201902123 – Last Review: Feb 12 2019 – Revision: 1.1

Leave a Reply