Source-derived document; reported behaviour, inference and evidence gaps are identified in the text.
Return to: 08. Integration Catalogue — topic detail
database and SQL
In this document
Interface: database and SQL
The application uses JDBC through Application.getDB and targets an Informix database. The supplied configuration names the Informix JDBC driver, a localhost connection on port 9088, database stores_demo, and Informix server informix. Other evidence describes initialization against the stores7 schema, while the repository instructions describe installing the demo database with dbaccessdemo7 stores7. These names occur in different configuration or descriptive contexts; the supplied evidence does not resolve whether they represent aliases, environment differences, or inconsistent documentation. E0011 E0013 E0014
The configuration identifies the database user as informix and the password as [credential redacted], and enables statement caching with STMT_CACHE set to 1. These configuration values describe connection settings but do not by themselves establish component placement or deployment topology. E0013
The database schema for orders, items, stock, and customer is inferred from SQL queries and record definitions rather than explicitly defined by the supplied Java source. SQLCA captures SQL status, error text, error program names, diagnostic values, and warning flags, but the framework’s interpretation of status values is not established. E0011 E0013
Harten documentation of the Informix 4GL and Java source repository, from the retained 17 October 2026 export. The exact upstream revision analysed is not established. Source findings do not establish runtime behaviour or equivalence between the implementations.
Evidence identifiers are retained for traceability. The underlying analysis records are not included in this public edition; credential values are redacted. About this case study.