Source-derived document; reported behaviour, inference and evidence gaps are identified in the text.
Return to: Deployment evidence
Deployment evidence
In this document
What is deployed where, and is that known from repository declarations or a verified runtime observation?
This view separates repository-described application artifacts from configured database endpoints; neither category is treated as proof of deployment. E0008 The supplied material reports configuration files and source artifacts, but does not provide a runtime observation or a declaration assigning a component to a host or environment. E0008 Therefore, the view identifies deployment candidates and preserves the deployment assignment as unknown rather than adding unsupported deployed_to relationships. E0008
The configuration evidence is also conflicting: demo/bin/default.properties names a localhost Informix endpoint, while demo/source/demo.properties names [internal hostname redacted] with different connection settings. E0008 The evidence does not establish precedence, deployment context, or whether both configurations are used. E0008
Elements
Demo application
Kind: component
Basis: reported
Description: The supplied assessment characterizes the source as a legacy Informix-4GL demonstration application with customer management, order entry, lookup, and reporting functionality. E0008
Evidence: E0008
Generated Java record artifacts
Kind: component
Basis: reported
Description: Generated or version-control-base Java artifacts model customer and state records under the com.ais.demo.record.stores7 package, but the evidence does not prove that these classes are loaded at runtime. E0007 E0008
Evidence: E0007, E0008
Local stores7 Informix endpoint
Kind: target
Basis: reported
Description: demo/bin/default.properties configures the stores7 database with an Informix JDBC URL using localhost, port 9088, database stores7, and server name informix. E0007 This is a configured endpoint, not an evidenced deployment assignment. E0008
Evidence: E0007, E0008
Project Informix endpoint
Kind: target
Basis: reported
Description: demo/source/demo.properties configures an Informix database target with host [internal hostname redacted], port 1526, server ol_informix, and database name settings. E0007 This is a project configuration target, not an evidenced deployment assignment. E0008
Evidence: E0007, E0008
Translation project
Kind: component
Basis: reported
Description: The project configuration identifies the translation project as demo, with source, work, and target paths configured as .\\source, .\\work, and .\\target; it also configures package prefix com.ais.demo and server port 7082. E0007 These settings do not establish where the resulting artifacts are deployed. E0008
Evidence: E0007
Relationships
No deployed_to relationship is supported. The supplied evidence reports configuration endpoints and generated artifacts but does not declare or observe an assignment from any component to either endpoint. E0008
Gaps
- No repository declaration assigns the Demo application, generated Java artifacts, or translation project to a host, environment, or runtime target. E0008
- No runtime observation verifies deployment to the localhost Informix endpoint or the project Informix endpoint. E0008
- The two database configurations conflict in host, port, server name, and credentials; precedence and usage are unresolved. E0008
- The evidence does not establish whether generated Java artifacts are loaded at runtime. E0008
- Follow-up requires deployment manifests, launch configuration, packaging or installation declarations, and a verified runtime observation identifying the actual application host and database target. E0008
Recovery limitations
- No supported relationships reconstructed.
- Some identified concepts have no supported connection.
Sources
- E0007 — SHA256
ce6dd2b00b79f008ecb98935db9ed709c044218bcdd4143008d56d06a04cff97 - E0008 — SHA256
1713f4e3d42ac5e2af28387ac6ff649f06bbe1683b11869af71326929d6a5f32
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.