jBASE 5.5.0 Windows Installation Guide

Table of Contents

Contents

  1. Starting the Installation
    1. Starting the Installation
    2. Installation
    3. Setting Up jBASE
      1. System Requirements
      2. License Key
  2. Installation
    1. Download the jBASE software
  3. Run the jBASE Installer
    1. Installation Mode
    2. jBASE Installation Wizard
      1. The installation begins with a Welcome page:
      2. Choose your company location:
      3. Review and accept the software license agreement:
      4. Choose an installation mode:
      5. Select the destination folder:
      6. Select the Start Menu folder:
      7. Select optional tasks to preform:
      8. User name for jBASE Administrator:
      9. Password for jBASE Administrator user:
      10. Directory for jBASE SYSTEM file:
      11. Directory for jBASE Administrator account:t
      12. Directory for the jBASE Spooler:
      13. jBASE License Keys:
      14. Installation summary:
      15. Pre-install tasks:
      16. Installing jBASE:
      17. Post-install tasks:
    3. Installing a compiler for jBASE 5
      1. Compiler Wizard welcome page:
      2. Compiler information:
      3. Install the Windows SDK:
      4. Environment variable information:
      5. Update system environment variables:
      6. Compiler installation finished:
    4. Upgrading from a Previous Version
    5. License Key Installation
      1. Using jshmd instead of jDLS
    6. Install jBASE telnet service for remote connections
    7. Install jBASE Remote Connectivity Server
  4. jBASE Users and Accounts
    1. jBASE Users
    2. jBASE Accounts
      1. Using CREATE-ACCOUNT to create a new account
    3. Setting up the jBASE environment for users
      1. Using IJU to set up the jBASE environment for users
  5. Further Reading
  6. Glossary of Terms
    1. jBASE
    2. jBASE Distributed Locking Service (jDLS)
    3. jBASIC
    4. jCL
    5. jED
    6. jEDI
    7. jLP
    8. jPLUS
    9. jQL
    10. jRCS
    11. jServControl
    12. JSH.exe
    13. jshmd
    14. jSHELL
    15. Environment Variables
    16. HOME
    17. Multisession
    18. System.Properties
    19. Websession

1. Starting the Installation

The contents of this guide are designed to allow the installation and initial configuration activities of the jBASE 5.5.0 product.

It is intended primarily for users who do not have a detailed knowledge of jBASE but will also be a useful reference for all users.

A summary of each chapter follows:

1.1. Starting the Installation

This section describes the tasks that need to have been completed before the install of jBASE 5.5.0 as well as what information is needed to complete the installation.

1.2. Installation

This section describes the installation process, including how to obtain the jBASE software, installing a license key and the minimum environmental settings required to run a jBASE shell.

1.3. Setting Up jBASE

This section describes the optional steps required in order for the jBASE installation to be configured to behave like other 'MultiValue database' flavours.

1.3.1. System Requirements

jBASE 5.5.0 is a 64-bit release and must be installed onto a 64-bit operating system. jBASE 5.5.0 is supported on: Windows 7 Windows 8 Windows 8.1 Windows 10 Windows Server 2008 R2 Windows Server 2012 Windows Server 2012 R2 Ensure the volume in which you are installing jBASE 5.5.0 has sufficient free disk space, approximately 500MB is required, plus additional space for any temporary files.

1.3.2. License Key

In order to complete the installation you will need to enter your jBASE license key. jBASE cannot be installed without either a permanent or evaluation license key.

2. Installation

2.1. Download the jBASE software

Download the jBASE 5.5.0 software via the link provided.

3. Run the jBASE Installer

Navigate to the folder to which you downloaded the jBASE installer and run the executable. Installation requires administrator privileges.

3.1. Installation Mode

The jBASE installer provides three installation modes: Express, Advanced and Minimal:

Express: install jBASE with typical options and services. Select this option if you are new to jBASE and wish to get started quickly. Express mode installs jBASE, creates a jBASE Administrator user and account, creates a SYSTEM file to organize jBASE accounts, initializes the spooler, installs and starts jBASE services.

Advanced: allows you to select which features and services to install. Select this option if you need to customize the location of the SYSTEM file, administrator account, or jBASE spooler, or if you do not want some of these features installed. Also select this option to select which optional services to install (telnet and jRCS).

Minimal: install the jBASE system files only. Select this option if you are comfortable with configuring jBASE manually. Most wizard pages are skipped when performing a minimal install. Note: Minimal installs do not require the jBASE license key during installation. You will need to manually enter the license key after installing jBASE.

3.2. jBASE Installation Wizard

The jBASE installer is a wizard-based installer which will guide you through the installation process. In this guide, above each wizard page is a legend showing which of the installation modes the page applies to. Navigation buttons are provided at the bottom of each wizard page. All but the first page have a 'Back' button to navigate to the previous page. All but the last have a 'Next' button to proceed to the next page. On the last page, click the 'Finish' button to close the wizard. The installation can be cancelled at any time by clicking the 'Cancel' button.

3.2.1. The installation begins with a Welcome page:

Installing_jBASE_5_fig01.png

3.2.2. Choose your company location:

Installing_jBASE_5_fig02.png

3.2.3. Review and accept the software license agreement:

Installing_jBASE_5_fig03.png

Read through the License Agreement and confirm that you agree to the terms and conditions by selecting 'I accept the agreement'.

3.2.4. Choose an installation mode:

Installing_jBASE_5_fig04.png

3.2.5. Select the destination folder:

Installing_jBASE_5_fig05.png

Choose the location to which jBASE will be installed then click 'Next'. If you are performing an Express mode install, the parent of the installation folder will be used as the location for the SYSTEM file, the JBASEADM account and jBASE spooler. Using the path shown above, the destination parent is 'C:\jBASE', so the SYSTEM file will be created as 'C:\jBASE\SYSTEM'.

3.2.6. Select the Start Menu folder:

Installing_jBASE_5_fig06.png

Enter a Start Menu folder for jBASE shortcuts, or check the 'Don't create a Start Menu folder' option. The installer will create jShell, jBase Administrator and jBase Help shortcuts in the Start Menu folder.

3.2.7. Select optional tasks to preform:

Installing_jBASE_5_fig07.png

Create jBASE administrator user The installer can create a new Windows user to perform jBASE administrative functions such as creating new jBASE accounts. The jBASE administrator also owns the jBASE system files. If you select this option you will be prompted for the user name and password. An existing user name is acceptable, for example, when performing an upgrade of jBASE.

Create SYSTEM file to organize jBASE accounts In jBASE, the SYSTEM file is optional. However, using a SYSTEM file provides a convenient way to organize your jBASE accounts, and is required for using Q-pointers and the LOGTO command in your jBASE applications.

Create JBASEADM account for administrative functions The JBASEADM account can be used to perform jBASE administrative tasks such as creating or deleting other jBASE accounts.

Initialize the print spooler Select this option to initialize the default print spooler configuration after a new installation. Note: this option is not available for upgrade installations.

Start telnet server The jBASE telnet server is required to support remote connections to jBASE over telnet. The telnet server runs as a Windows service. By default, the telnet server listens on TCP port 23. See jBASE knowledgebase article www.jbase.com/r5/knowledgebase/manuals/3.0/30manpages/man/telnet1.htm for information on configuring the jBASE telnet server.

Start jRCS service The jBASE Remote Connectivity Server (jRCS) provides remote access to your jBASE system. jBASE System Manager uses this service to perform management tasks on your jBASE system. By default, the jRCS server listens on TCP port 8236. See the jBASE knowledgebase article JRCS for more information regarding jRCS.

3.2.8. User name for jBASE Administrator:

Installing_jBASE_5_fig08.png

Enter a user name for the jBASE Administrator. This is the Windows user who will "own" the jBASE system files, and can be used to perform jBASE administrative tasks such as creating new jBASE accounts. The name you specify here is a local system user name. If the user does not exist, the installer will create the user for you.

3.2.9. Password for jBASE Administrator user:

Installing_jBASE_5_fig09.png

If the user name specified in the previous screen does not exist, you need to specify a password for this user. The installer will not create a new user without a password. Because security policies vary widely, it is not possible for the jBASE installer to validate that the password you enter conforms to the local security policy of the computer. Be sure to follow your local security policy regarding passwords. Otherwise the installer will not be able to create the jBASE Administrator user, and you will need to do this manually after the installation.

3.2.10. Directory for jBASE SYSTEM file:

Installing_jBASE_5_fig10.png

Enter the directory where you want the jBASE SYSTEM file to be created. By default, the SYSTEM file is created in the parent of the jBASE release directory.

3.2.11. Directory for jBASE Administrator account:t

Installing_jBASE_5_fig11.png

Enter the directory where you want the JBASEADM account to be created. By default, the JBASEADM account directory is created in the parent of the jBASE release directory.

3.2.12. Directory for the jBASE Spooler:

Installing_jBASE_5_fig12.png

Enter the directory where you want the jBASE spooler to be created. By default, the jBASE spooler directory is created in the parent of the jBASE release directory.

3.2.13. jBASE License Keys:

Installing_jBASE_5_fig13.png

jBASE requires a valid license key in order to operate. Either a permanent or evaluation key may be used. Enter this key in the 'jBASE License Key' field. If your license key is an evaluation key, check the 'Evaluation License' check-box. If you have been issued a Multisession or Websession license key, enter these keys in the respective fields. If you are upgrading from a previous version of jBASE, the installer will attempt to locate your existing license keys and use them to populate the license key fields on this page. Note: the installer will not continue unless you enter a license key.

3.2.14. Installation summary:

Installing_jBASE_5_fig14.png

Click the 'Install' button to proceed with the installation.

3.2.15. Pre-install tasks:

Installing_jBASE_5_fig15.png

Before installing jBASE, all jBASE services are stopped, and a check is made to see if any processes are using any jBASE system files. If any files are in-use, the installer will display a page allowing you to shut down processes that are using jBASE. If any jBASE files are still in-use when the installation continues, a system reboot may be required.

When performing an upgrade installation, a backup copy of the current 'config' directory is made as 'config_pre_<new release>'. For example, if upgrading from release 5.2 to 5.5.0, the old 'config' directory (C:\jBASE5\5.2\config) is copied to the new release directory as 'config_pre_5.5.0'.

3.2.16. Installing jBASE:

Installing_jBASE_5_fig16.png

The jBASE release files are copied to the destination folder, replacing any existing files if installing over an existing installation.

After copying the jBASE release files, the installer will install the Microsoft Visual C++ runtime.

Finally, optional configuration tasks are performed, such as creating the jBASE Administrator user, creating the SYSTEM file, the JBASEADM account, initializing the spooler, and installing and starting the jBASE services.

3.2.17. Post-install tasks:

Installing_jBASE_5_fig17.png

If jBASE installation was successful, two additional options are available: install the compiler (see next section) and open a jShell command prompt.

If the installation was not successful, for example, an invalid license key was entered, an error message will be displayed.

3.3. Installing a compiler for jBASE 5

In order to compile and catalog programs and subroutines in jBASE, a 'C' compiler must be installed on the system where jBASE is installed. After completing the jBASE installation, one of the optional tasks you can select is to install and configure the compiler.

If you need to run the compiler configuration wizard separately from the jBASE installer, open a command prompt, change to the directory where you saved the jBASE installer, and enter the name of the installer executable file, followed by /COMPILER (leave a space between the file name and the slash).

For example: jbase_5.5.0.18121_rel_64bit.exe /COMPILER

3.3.1. Compiler Wizard welcome page:

Installing_jBASE_5_fig18.png

The jBASE compiler configuration wizard will guide you through the process of installing an appropriate 'C' compiler. The wizard will examine your system to determine if a suitable compiler is already installed, and verify that the correct environment variables are set for using the compiler with jBASE.

3.3.2. Compiler information:

Installing_jBASE_5_fig19.png

Because the actual compiler installation is performed by Microsoft's web-based SDK installer, an Internet connection is required to complete the installation.

If any pre-requisites are required, you will be provided with instructions on installing them. Prerequisites may include .NET 3.5 Framework feature on Windows Server 2012 and SP1 for Visual Studio 2008.

3.3.3. Install the Windows SDK:

Installing_jBASE_5_fig20.png

Once the prerequisites are installed, click the 'Launch the SDK Installer' button to start the web-based SDK installer.

jBASE does not require many of the SDK components, so a screen shot displaying which components you need will be displayed to aid in the SDK installation process. You can install additional components if you desire - the minimum components are shown in the screen shot.

3.3.4. Environment variable information:

Installing_jBASE_5_fig21.png

After the SDK is installed, the wizard will examine the system environment variables which jBASE requires for invoking the compiler. Click 'Next' to examine the environment variables.

3.3.5. Update system environment variables:

Installing_jBASE_5_fig22.png

If any environment variables require updating, the new contents will be displayed. Click the 'Update Environment Variables' button to update the environment. Then click 'Next' to validate the compiler configuration. If a problem is detected, a notice will be displayed.

3.3.6. Compiler installation finished:

Installing_jBASE_5_fig23.png

Click the 'Finish' button to close the wizard.

3.4. Upgrading from a Previous Version

The jBASE installer will examine the directory pointed to by the JBCRELEASEDIR environment variable for a previous jBASE installation. If a 'config' directory is found in the previous jBASE release directory, the current contents of the previous 'config' directory will be backed up to 'config_pre_<new version> in the destination directory. For example, if, prior to installing this release of jBASE, JBCRELEAESEDIR points to 'C:\jBASE5\5.2' and the new installation destination directory is C:\jBASE\5.5.0, then the contents of 'C:\jBASE5\5.2\config' will be backed up as 'C:\jBASE\5.5.0\config_pre_5.5.0'.

If you have modified any of the configuration files in the previous release 'config' directory, you will need to apply your modifications to the corresponding files in the new installation 'config' directory. Such files may include:

When upgrading a previous release of jBASE, the installer will not overwrite any existing JBASEADM account, SYSTEM file, jBASE Spooler configuration or jbaseadm user.

3.5. License Key Installation

License keys for jBASE 5.5.0 need to be added to the 'system.properties' file which is located in the 'config' directory under your jBASE release directory. The jBASE installer will update the license keys during Express and Advanced mode install. If you need to change the keys, for example , to enter a permanent key instead of an evaluation key, or if you performed a Minimal install, you can use any text editor (Notepad, for example) to enter the keys in the 'system.properties' file.

You should have either a permanent system license key, or an evaluation license key. You may also have a 'Multisession' and/or 'Websession' key. Each key must be added as a separate entry in the 'system.properties' file. New keys should be added at the end of the file, after the 'jruntime.license' line, which should be left in the file without modification. When the keys have been added, the last few lines of your 'system.properties' file will look something like this:

#################################################################
jruntime.license = qP2XhdjqbdbiqzvfDBgPisP3ITiDfhyT
jruntime.azeroth= 5FLY3q6e4P6I1qdZLr2q4wadhM06VQvzoOGDVX0KZSs=
jruntime.multisession=5FLY3q6e4P6vTff9AETIQYwyjTnxDVK6sS1uFVfPeFQ=


For further information on jBASE licensing see the jBASE Knowledgebase article jBASE 5 Licensing.

3.5.1 Install jDLS service to initialize shared memory


jBASE on Windows uses 'shared memory which must be initialised prior to using many jBASE functions, such as jShell. Typically, this function is performed by the 'jBASE Distributed Locking Service' (jDLS). 'jDLS' is designed to be run as a Windows Service.

When jBASE is installed using Express and Advanced install mode, the 'jDLS' service is installed and started automatically. The service is started using default options (background operation, process-based locks).

If you need to manually install the service (for example, when using the Minimal install mode) the 'jServControl' command can be used. From an elevated Windows Command (DOS) prompt:

jServControl -s auto -p %JBCRELEASEDIR%\bin\jdls.exe jDLS install start
 

Note: The command prompt must be started using the 'Run as Administrator' option.

jDLS can now be managed as a normal Windows service.

For further information on jBASE Distributed Locking Service see the jBASE Knowledgebase: jBASE Distributed Locking User Guide

3.5.2 Using jshmd instead of jDLS

For those customers that do not wish to take advantage of 'jDLS', the 'jshmd' service is provided which will also initialize the required shared memory. jDLS' is the recommended option.

Use this command to install and start 'jshmd' as a Windows Service. From an elevated Windows Command (DOS) prompt:

jServControl jshmd install start

Note: The command prompt must be started using the 'Run as Administrator' option.

The 'jshmd' service can now be managed as a normal Windows service.

Once either of the above services is installed and started, you should be able to start the jShell and compile and catalog jBASE programs.

3.6. Install jBASE telnet service for remote connections

The jBASE telnet server provides support for remote connections to jBASE.

When jBASE is installed using Express mode, the jBASE telnet service is installed and started automatically. For Advanced mode, installing the telnet service is optional. The service is started using default options (listen on TCP port 23, run remote.cmd after logging in).

If you need to manually install the service (for example, when using the Minimal install mode) the 'jServControl' command can be used. From an elevated Windows Command (DOS) prompt:

jServControl -s auto -p %JBCRELEASEDIR%\bin\telnetd.exe telnet install start

Note: The command prompt must be started using the 'Run as Administrator' option.

jBASE telnetd server can now be managed as a normal Windows service.

For further information about the jBASE telnetd service see the jBASE Knowledgebase: Windows Telnet

3.7. Install jBASE Remote Connectivity Server

The jBASE Remote Connectivity Server ('jRCS') provides a method for external clients to access jBASE services. In particular, the jBASE System Manager utilizes 'jRCS' to perform its management functions.

When jBASE is installed using Express mode, the 'jRCS' service is installed and started automatically. For Advanced mode, installing the 'jRCS' service is optional. The service is started using default options (listen on TCP port 8236,data encryption enabled, password encryption enabled.)

If you need to manually install the service (for example, when using the Minimal install mode) the 'jServControl' command can be used. From an elevated Windows Command (DOS) prompt:

jServControl -s auto -p %JBCRELEASEDIR%\bin\jrcs.exe jrcs install start

Note: The command prompt must be started using the 'Run as Administrator' option.

jRCS service can now be managed as a normal Windows service.

For further information about the jBASE Remote Connectivity Service see the jBASE Knowledgebase: jBASE Remote Connectivity Service

4. jBASE Users and Accounts

This section describes the jBASE concepts of users and accounts.

4.1. jBASE Users

jBASE users are normal Windows users. Both local and domain users are supported. As with any Windows application, the user must have the correct privileges to access jBASE programs and data files.

User creation in Windows is done using the 'Computer Management' screen, which can be accessed via the 'Administrative Tools' section of the 'Control Panel'.

Installing_jBASE_5_fig24.png

Select 'Computer Management' then select 'Local Users and Groups' and choose the option to add a new user.

Installing_jBASE_5_fig25.png

The following screen will be displayed.

Installing_jBASE_5_fig26.png

Enter the user details and select 'Create'.

Next, select the user you have just created and select the 'Properties' option, then choose the 'Profile' tab.

Installing_jBASE_5_fig27.png

Add an entry for the 'Home folder', then click OK and save your settings.

The jBASE user login has now been created and you should now be able to connect to your jBASE system via telnet using this user.

If the jBASE user should log in to a particular jBASE account, you can set the 'Home folder' to the path of that account.

4.2. jBASE Accounts

A jBASE account is a directory that contains jBASE data and executable files. An account can optionally have a "master dictionary" (MD) which may contain file pointers, PROCs (JPQ), and definitions used by the jBASE query processor (jQL).

Use of a SYSTEM file in jBASE is optional. However, a SYSTEM file is a useful place to organize your jBASE accounts. By adding a record in the SYSTEM file for an account, it is possible to use the LOGTO command to log to the account from another jBASE account. The SYSTEM file record also enables Q-pointers to files in that account. See SYSTEM File in the jBASE knowledgebase for details on the content of SYSTEM file records.

4.2.1. Using CREATE-ACCOUNT to create a new account

The CREATE-ACCOUNT command can be used to create a new jBASE account. The command is normally executed from the JBASEADM account. The CREATE-ACCOUNT command creates a directory for the new account, creates an MD for the account, updates the SYSTEM file (a SYSTEM file is required when using the CREATE-ACCOUNT command) and optionally creates a remote.cmd script for the account.

The basic syntax is:

CREATE-ACCOUNT {-n} {-r} path

where path is the full or relative path for the new account; the final directory name in the path is used as the account name and that name is registered in the SYSTEM FILE. The -r option creates a remote.cmd file for the account. The -n option inhibits creation of a MD for the account. Use the -h option to see a full list of options and examples.

4.3. Setting up the jBASE environment for users

jBASE is defined by its environment. The 'remote.cmd' file in the user's home folder will define the jBASE environment for a user.

Defining a 'Home folder' in the user's profile, and placing a proper 'remote.cmd' file in this folder, should be all that is necessary to set up the jBASE environment for the user. Using the CREATE-ACCOUNT command to create the account and 'remote.cmd' file is an easy way to accomplish this. After creating the account, update the 'Home folder' in the user's profile to point to the account directory. If you do not set a 'Home folder', Windows will set the HOMEDRIVE and HOMEPATH environment variables to the user's "profile" - typically C:\Users\<username>.

4.3.1. Using IJU to set up the jBASE environment for users

The IJU utility (Initialise Jbase User) can be used to initialize an account directory for a user and create a suitable remote.cmd file to set up the jBASE environment.

Log into the jBASE system via telnet using your jBASE user login. Once connected, run the command IJU.

This command will prompt you to supply details for a number of environment variables which will be used to populate the remote.cmd file in order for it to properly interact with jBASE.

In most cases the default options will be fine. However, make sure to answer 'Y' to the prompt asking 'Do you wish to use the jsh' as this will ensure that you access a 'jsh' session after logging in.

5. Further Reading

Further reading relating to jBASE and it's component technologies is available from the jBASE Knowledgebase.

jBASE Agent

Accepts and Processes incoming client requests

jEDI Development Kit

Provides access to RDBMS from jBASE applications

jBASE jDBC Driver

Provides jDBC access to jBASE data files

jBASE ODBC Driver

Provides ODBC access to jBASE data files

Transaction Journaling

Logs jBASE database updates

jBASE Dataguard

Database Resilience within jBASE

jRCS

jBASE Remote Connectivity Service

jBASE Spooler

The jBASE Spooler

mv.NET

Visual Studio development for MultiValue Data

The ODBC driver requires MSCV runtime for VS2005, downloads available here:

Microsoft Visual C++ 2005 SP1 Redistributable Package (x86)

Microsoft Visual C++ 2005 SP1 Redistributable Package (x64)

For support related queries, please email Support

6. Glossary of Terms

6.1. jBASE

An open database product that brings the strengths of MultiValue technology into the mainstream computing market; providing a multidimensional database, a development environment including a development language, and a middleware component allowing other mainstream and standards-based products to communicate with the jBASE products.

6.2. jBASE Distributed Locking Service (jDLS)

jDLS is responsible for resolving all record locking conflicts for jBASE processes. It runs in the background on your system and is commonly referred to as the lock daemon.

If jDLS is not running, jBASE will use the normal operating system locks. This is acceptable for small user populations, but the operating system locking mechanism has limits on the number of locks available, and on performance.

6.3. jBASIC

The language built in to jBASE, jBASE BASIC (jBC) is a dialect of BASIC that combines the power of stored procedure languages with a fully-fledged development language.

6.4. jCL

The jBASE Command Language is an implementation of the PROC processor found in other multivalue offerings. The jCL processor stores a complex series of commands that can be executed later by a single word or command, but does not require any compilation.

6.5. jED

The jBASE Editor. jED is a fully featured screen editor, which can be used for creating, modifying, or deleting records.

6.6. jEDI

The jBASE External Device Interface(jEDI). The jEDI enables applications to achieve seamless integration with foreign databases without changes to the jBASE MultiValue BASIC application code and logic. JEDIFILENAME_SYSTEM

6.7. jLP

The jBASE spooler program. This is the jBASE equivalent of the unix lp command.

6.8. jPLUS

jPLUS files provide large file support on 64 bit UNIX and Windows platforms, such that Hash files can extend beyond the normal 2GB operating system limit.

6.9. jQL

The jBASE Query Language (jQL) is a powerful and easy to use facility which allows you to retrieve data from the database in a structured manner and to present the data in a flexible and easily understood format.

6.10. jRCS

The jBASE Remote Connectivity Server. jRCS runs as a Windows service and provides jBASE functions to remote programs. jBASE System Manager uses jRCS to perform its management tasks.

6.11. jServControl

A jBASE command line utility allowing the install, configuration and removal of jBASE services

6.12. JSH.exe

A windows executable that initiates a jSHELL session.

6.13. jshmd

jBASE service that initiates the required areas of shared memory for systems which utilise operating system locking.

6.14. jSHELL

The jBASE shell. It can be invoked as your login shell by using the normal system administration software supplied with the platform. Either via .bat files (Windows) or .profiles (Unix ).

6.15. Environment Variables

jBASE uses a number of environment variables to modify jBASE behaviour

6.16. HOME

The 'HOME' environment variable. This stores the pathname of user home directory

6.17. Multisession

A Multisession license allows for up to ten concurrent sessions from a single IP address or system name to the database.

6.18. System.Properties

The 'system.properties' file resides in the %JBCRELEASEDIR%\config directory and stores jBASE license keys and compiler instructions.

6.19. Websession

A Websession license allows up to a ten sessions originating from a Web Server or Terminal Server (single IP address). For example with three of these licenses the Web Server would have 30 concurrent sessions available.