DBPronto - Frequently Asked Questions

What platforms is DBPronto compatible with?

Please refer to the DBPronto Current Releases page for current availability.

Contact Transoft Customer Services to request DBPronto for a different platform.

Is DBPronto compatible with my RDBMS?

DBPronto provides compatibility with a number of Relationsal Database Management System (RDBMS) types, including:

Microsoft SQL Server
Oracle
MySQL
PostgreSQL
Sybase ADS
DB2

Please contact Transoft Customer Services if you are would like to be able to use DBPronto with a different RDBMS type.

Is DBPronto compatible with my data access code

The types of data access code that are currently supported by DBpronto include:

ACUCOBOL
Micro Focus COBOL
RM/COBOL
C-ISAM
D-ISAM
U/FOS
isCOBOL
Fujitsu COBOL
BB-ISAM (currently in beta test)

Please contact Customer Services to request DBPronto for additional data access types.

What is the typical deployment architecture of DBPronto

The DBpronto architecture can be logically divided into three tiers:

DBPronto Client;
DBPronto Server (and Metadata);
RDBMS.

The diagram below shows the logical DBPronto deployment architecture:

There are a number of ways in which DBPronto can be deployed, meaning that the architecture is flexible depending on each user's specific requirements. The deployment "rules" only require that the DBPronto client is installed on the same device as your legacy COBOL program, and that the client can communicate with the DBPronto Server via a simple TCP/IP link. The DBPronto Metadata must be accessible to the DBPronto Server, which in turn must be able to communicate with the RDBMS via a JDBC link.

With the above rules in mind, DBPronto will typically be deployed physically in one of three ways:

All components installed on the same physical device (Client, Server and RDBMS);
Seperate physical devices for each component ;
Client installed on a one machine, Server and RDBMS on another.

Although the default configuration is 3-tier as described above, DBPronto can also be deployed in a 2-tier architecture in order to optimise performance for specific processes, for example, large batch processes. Most sites will either use the 3-tier architecture or a mixed, 2-tier and 3-tier, architecture. This is a relatively recent enhancement to DBPronto, please refer to the DBPronto product documentation or contact Customer Services for more information.

What version of Java do I need in order to run DBPronto?

The DBPronto Server requires Java version 1.5 or later in order to run correctly.

Does DBPronto provide record locking?

DBPronto features an integrated Lock Server which provides a full emulation of legacy (e.g. COBOL) application locks. The Lock Server API is available for both Java and .NET environments to facilitate WRITE access to the RDBMS from new applications. This allows deployment of new application development in .NET and Java alongside existing legacy application code because the same locking methodology and lock server is used by both.

Record locks can be viewed in the "Monitor" tab in the DBPronto Administrator.

The Modernization Experts