InTime Server

How to install License Server and InTime Server separately?

272 views February 15, 2019 July 8, 2019 pohheng 0

Introduction

For a private cloud installation involving multiple computers running the same job, both the InTime Server and License Server are required.

1) The InTime Server is a component that distributes, schedules jobs and files.
2) The License Server is a component to enable InTime to use floating licenses.

The default installation installs both the Server and License components on the same machine with a single script. However, there are situations where the License Server must be a separate server.  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.

Deployment Scenarios

Scenario A) InTime Client and InTime License Server Only

Scenario A: InTime & License Only

In this scenario, multiple InTime clients connect to the License server directly. Each job runs on individually on the InTime client locally.  Note that there is no need for an InTime Server since the job doesn’t get distributed to other clients.

Scenario B) InTime Client, InTime Server and License Server 

Scenario B: Client, Server and License

In this scenario, all clients are connected to the InTime Server. Each additional client is called a worker and can be used on the same job. The InTime Server is responsible for handling and copying the files across to multiple InTime workers.

Installation

As of v2.6.10, users can choose the type of InTime Server installation.

  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.

For Windows, the 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]

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

2. Specify the log files’ directories for both the InTime Server and the License Server with the -wd <directory location> option when starting either InTime Server or the License Server

Example: Step-by-Step Deployment

In this example, Server B is 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.

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: July 8 2019 – Revision: 1.2

Leave a Reply