jBASE Distributed Lock Service

This section provides a user guide for the deployment and configuration of the jBASE Distributed lock service for a Multiple Application Server environment.

Overview

Although Temenos Transact has been successfully deployed over Multiple Applications Servers, certain peculiarities related to operating systems, performance and recovery of file locks over networked file systems have prompted the requirement to provide an alternative lock strategy for Multiple Application Server deployment. As such, the jBASE Distributed lock service is used as an alternative mechanism to the networked file system, by which locks can be propagated between servers.

Deploying Distributed Lock Service

This section describes the jDLS options, examples of server deployment and how to install jDLS as a Window service.

Deploying Client Distributed Lock

It is possible to configure the client system to use the Distributed Lock Service.

jBASE Distributed Lock Service Process Flow

This section shows the flow diagram of jDLS process.

Lock Mechanisms

There are two types of lock mechanism that can be implemented on the lock server used for the jDLS. This section describes the two lock mechanisms.

Distributed Lock Information

Although the lock mechanisms keeps track of outstanding locks taken by processes or even threads in case of the shared memory lock table, this information is relatively limited and usually insufficient to easily determine lock ownership. This section details about the lock information in jDLS.

Utilities

This section explains about the SHOW-ITEM-LOCKS utility. It can be referenced by other program names to display record lock information.

Resilience

This section explains about the Client lock resilience and Server lock resilience.

Recovery

This section shows how to recover the system when the system fails.