BOI Software Entwicklung und Vertrieb GmbH

Phone: +43 (0) 732 / 736423 - 0

Spazgasse 4


4040 Linz, Austria




TABEX/4 JAVA APPLICATION ENGINE is a supplement to the TABEX/4 installation.

JAE is a Java application programming interface for easy implementation of distributed and audit-proof Java applications for the maintenance of TABEX tables using the TABEX/4 functionality.

The comfortable Java interface extents the functionality of TABEX/4 for read and write access to table data via TCP/IP on distributed platforms.

By using TABEX/4 JAVA APPLICATION ENGINE, read and write access to table data is possible from any Java environment, such as

  • web applications (Java/JSP)
  • GUI applications
  • server batch applications.

Your Advantages

  • Distributed and audit-proof maintenance of central table data (e.g. on the mainframe) using Java applications.
  • Easy implementation of web applications and GUI applications by using the BOI Java classes of the JAE.
  • Possibility of automation of table maintenance by distributed Java programs on all system platforms.
  • User authentification of JAE ensures that only authorized users are allowed to run JAE Java applications.
  • Moving applications from the mainframe to distributed platforms and therefore saving on hardware and software costs.

In addition to these advantages JAE offers the same advantages which are offered by the TABEX/4 web frontend - the TABEX/4 Table Manager:

  • Secure login to TABEX/4: The password is encrypted.
  • Authorized access to table data: A user can have read and/or write access to tables. The TABEX/4 authorization system checks these access rights.
  • The processing of the table is transaction oriented. Multiple update operations can be performed and stored together. During the transaction, tables are locked for other applications.
  • Data checks can be implemented by check routines stored in TABEX/4 tables. This does not require to write a single line of Java code. The check logic of TABEX/4 prevents that invalid data is stored in the database. The definition of the check tables is done with the TABEX/4 Table Manager.
  • Audit-proof table maintenance: All data changes made by Java applications are automatically logged in the central TABEX/4 revision log. This also does not require to write a single line of Java code. Thus, it is possible to obtain a complete revision log of all changes for each table. The following data are saved in the revision log:
    • Who made the change?
    • What kind of changes were made (insert, change, delete)?
    • Which data records were changed?
    • Additional information if needed


The following figure shows the sequence of a JAE Java program:

  • At first the session must be initialized: the connection is established and the encrypted login to TABEX/4 is executed.
  • Open transaction and close transaction surround a transaction.
  • Before the table maintenance the table must be loaded in memory.
  • Now the loaded tables can be maintained.
  • Store saves the changes in the table. Here also the revision log is automatically written.
  • Remove is used to roll back the changes.
  • Unlock removes the lock of the table.
  • At the end of the session the session is cleaned and a disconnect from TCP/IP is executed.



Changes in ESA data spaces, efficient migration and a new success story: Learn more in our newsletter!


Migration Packages

BOI GmbH offers migration packages for the table management systems SPITAB, TABSYS and VTAS.


» Migration Packages

Success Stories

GDIS and BOI: Carrying on the Success

With TABEX4 JTC, GDIS has introduced the world's fastest Java interface for table access on customer and control data. Learn the details in our new Success Story.


» read this Success Story

» read more Success Stories