Professional Documents
Culture Documents
In this learning unit you will learn how T24 data is stored
when the database used is not jBASE. You will also learn how the architecture
changes to accommodate the use of Direct Connect Drivers.
1 Describe the way a Direct Connect Driver works and differentiate between the way
data is stored in T24 when jBASE or an external database is used.
2 Explain the use of the Direct Connect Driver and the changes it brings to the T24
architecture.
3 Understand what stub files are and how you can also do away with them if required
2 The other important concept that you will learn is the format in which the data is stored in the
external database and why T24 uses that format.
2. jBASE is more than a database to T24. It also acts as a run time environment. Code is
written in jBASE BASIC and compiled here as well.
3. T24’s data can be found in the bnk.data directory that is part of it’s directory structure. Data
is stored in J4 or JR files, both jBASE file types. Accessing data from these files are done
using jBASE commands within the source code.
4. So can this same code read and write into any other database? No. Rewriting T24 to make it
compatible with another database is close to impossible.
5. jBASE is an open database, which allows us to communicate with other databases using
Direct Connect Drivers. These drivers convert jBASE requests into a format that the external
database can understand, and then converts the data fetched into a format that T24 can
understand. Why data storage format is different you will learn a little later in the course.
6. One very important fact that you must never forget is that T24 cannot exist without jBASE.
Even if it uses an external database, T24 still requires the jBASE runtime environment.
2 Currently jBASE has 3 Direct Connect Drivers that allow it to connect to 3 different
databases namely Oracle, SQL and DB2. Depending on the choice of database, the
corresponding Direct Connect Driver must be installed.
1.2 Transform jBASE BASIC and jBASE commands to SQL statements as understood
by the underlying database
1.3 Transform the result returned by the database into a format that T24 and the
jBASE run time understand
3 Once the validations are through, the record is ready to be stored, but where is the
file FBNK.CUSTOMER located?
4 The VOC entry is referred to find out these details. The VOC holds the path to the
data and dict portion of every application’s file.
With a single application server, there is no need for a separate database server in the
T24 architecture. T24’s data will reside on the application server itself.
With multiple application servers, the only option you have is to NFS mount the
bnk.data directory and change the VOC entries accordingly.
2 To connect to any database other than jBASE, you will need to install the
corresponding Direct Connect Driver. This must be installed on each application
server.
T24’s data is now stored in another database - Oracle in this case. The data file in
bnk.data that the VOC entry points to will contain a pointer to the actual table in Oracle
where the data is stored. The files in bnk.data are referred to as stubs.
The illustration above shows the set up when a single application server is used and
when multiple application servers are used.
3 “JBC__SOB” and “XMLORACLEInit” strings tell the jBASE runtime that it needs to
locate a Shared OBject library containing the library initialisation function,
“XMLORACLEInit”.
So once the driver has information about the actual Oracle table name, it can access it
to retrieve or update the data as requested.
2 The VOC itself is now a table in Oracle. This is done during the driver installation
and data conversion process
3 The VOC is still present in jBASE as well, but instead of holding the path to the data
and dict files, it holds a pointer to the Oracle VOC table
4 The VOC in Oracle is the one that contains the actual pointer to the data stored in
Oracle tables
GEN7-Data Storage on
Module Code-Module an External Database-R10.01
Name-2008-H1-01 16
1 All T24 data tables in Oracle will have only two columns.
2 3 One to store the ID and the next to store the entire data record.
This is done because Oracle does not support the multi-value, sub-value concept that
T24 uses widely.
4 The naming conventions used for the table names in Oracle are similar to the ones
used in jBASE, the only difference being – dots are changes to underscore and $ are
changed to #.
In order for the driver to log details to the log file, the following variable must be set in
the .profile or the remote.cmd as the case may be
2. False
3. False
4. True
5. True
Describe how and where a Direct Connect Driver fits into the T24 architecture.
Explain how jBASE can be used as a database in a single / multi application server set
up