JDEBase Database Middleware

Different database management systems (DBMS) have their own version of Structured Query Language (SQL). For example, this demonstrates how Microsoft SQL Server, Oracle, and DB2 for i handle the same SQL statement:

DBMS	SQL Statement
Microsoft SQL Server	SELECT * FROM PRODDTA.F0101
Oracle	SELECT * FROM PRODDTA.F0101;
DB2 for i	SELECT * FROM PRODDTA/F0101

The purpose of a database middleware layer is to provide a common interface to interpret the various versions of SQL. EnterpriseOne has a database middleware product called JDEBase, which is a common set of application programming interfaces (APIs) that programmers can call to request data and perform data manipulation logic. JDEBase interprets the generic APIs and converts the SQL into the appropriate statements for EnterpriseOne to access the database.

Multiple databases in a distributed environment require a monitoring program to ensure database integrity. This monitoring program is referred to as a transaction monitor. The JDEBase database middleware has an embedded transaction monitor.

JDEBase provides:

• The ability to insulate developers from platform-specific SQL coding.

• Rapid development of native drivers.

• Server-to-server communication.

• Transaction processing.

JDEBase provides a set of APIs to the developer and a set of translation programs to EnterpriseOne. The translation programs are embedded in the data source definitions.

For example, suppose a data request for Address Master is made. The Object Configuration Manager (OCM) determines which data source contains the requested table. The Data Source Master table (F98611) provides the database information.