System requirements
For an overview of hardware requirements, supported platforms, databases and browsers, and Java considerations, see hardware and software requirements.
License information
LuciadFusion makes use of a number of third-party libraries and components. A list of those libraries and their respective licenses is available below.
This distribution of LuciadFusion includes the third-party build and deployment tool Apache Ant, licensed under the Apache 2.0 license. Documentation and source code can be found on http://ant.apache.org/. This third-party tool is supplied with the LuciadFusion distribution because of its convenience for building applications with LuciadFusion. It is not needed to run LuciadFusion-based applications, nor does it need to be distributed with such applications.
In addition, the OGC implementations in your Luciad software include and make use of the following resources:
- The OGC Symbology Encoding functionality in LuciadLightspeed uses XML code from the Spring framework, which is licensed under the Apache License Version 2.0.
- All libraries containing implementations of XML Schema-based OGC specifications include the relevant XML Schemas for caching purposes. These XML Schemas are licensed under the OGC Software Notice.
The Earth repository implementation in LuciadLightspeed uses JDBM which is licensed under the JDBM LICENSE 1.0.
The NetCDF implementation uses a modified version of the NetCDF-Java library, which is licensed under the NetCDF-Java license. The NetCDF implementation also includes the google protobuf library, which is licensed under the google protobuf license.
The 3D icons implementation includes code ported from libsquish, an open source DXT compression library which is licensed under the Squish MIT license.
The BlackLimeLookAndFeel (used in the map centric version of Lucy) uses the Noto font. This font is licensed under the SIL Open Font License.
The XML implementation includes code ported from stax-utils, an open source library which is licensed under the BSD License.
The IFC implementation uses the EXPRESS grammar developed by Ribose Inc. which is licensed under a BSD-2 License.
Component integrations
Database Connectors requires or offer specific integrations with the following components:
- LuciadFusion integrates with Defense Standards. Fusion Client can use the GeoSym symbology to style vector data when available.
- LuciadFusion integrates with Maritime Standards. Fusion Client can use ECDIS when available.
- LuciadFusion integrates with Database Connectors. The Fusion Engine can fuse this format.
- LuciadFusion integrates with S-63. The Fusion Engine can fuse this format, if the LuciadFusion license includes this component.
- LuciadFusion integrates with Infrastructure Standards. The Fusion Engine can fuse this format.
- LuciadFusion integrates with Aviation Standards. The Fusion Engine can fuse this format.
- LuciadFusion integrates with Weather & Environment Standards. The Fusion Engine can fuse this format.
- Additionally, LuciadFusion integrates with Advanced GIS Engine, Advanced Raster Services, Defense Standards, Maritime Standards, Database Connectors, S-63, Infrastructure Standards, Aviation Standards and Weather & Environment Standards.
- Additionally, Data Connectivity Manager integrates with Aviation Standards, Radar Connectors, Infrastructure Standards, Advanced Raster Services, Defense Standards, Maritime Standards, S-63, Weather & Environment Standards, Database Connectors, Defense Symbology, Real-time Engine, Terrain Analysis Engine and Google Earth Enterprise.
- Radar Connectors requires Real-time Engine. The Realtime option is required to display live tracks at best performance and to be able to replay trajectories.
- S-63 requires Maritime Standards. This package contains an encryption scheme designed specifically for S-57 data.
The licenses of third-party libraries used in the Fusion Studio front-end can be found in your LuciadFusion installation,
under docs/platform-licenses.
Libraries
Database Connectors depends on the following additional or third-party libraries:
| Name | Version | License(s) | |
|---|---|---|---|
| Checker Qual | 3.42.0 | O | MIT License |
| DB2 JDBC drivers | 3.64 | C | International Program License Agreement |
| Informix JDBC drivers | 3.00JC1 | C | International Program License Agreement |
| Microsoft JDBC Driver for SQL Server | 7.2.1.jre8 | O | MIT License |
| Oracle Database JDBC Driver | 19.12.0.0 | C | Oracle Free Use Terms and Conditions (FUTC) |
| Oracle Spatial Java API | 12.2.0.1 | C | Oracle Free Use Terms and Conditions (FUTC) |
| PostgreSQL JDBC Driver - JDBC 4.2 | 42.7.3 | O | BSD 4 Clause |
| SAP Hana JDBC Connector | 1.00.68 | C | SAP Hana Driver License Agreement |
Sample libraries
Database Connectors doesn't require any additional or third-party libraries to run the samples.
Jar files
Database Connectors includes the following jars:
| File | Description |
|---|---|
| lcd_db2.jar | Contains the java classes to support DB2 databases. |
| lcd_informix.jar | Contains the java classes to support Informix Geodetic databases. |
| lcd_informix_spatial.jar | Contains the java classes to support Informix Spatial databases. |
| lcd_mssql.jar | Contains the java classes to support Microsoft SQL databases. |
| lcd_oracle.jar | Contains the java classes to support Oracle Locator databases. |
| lcd_oracle_georaster.jar | Contains the java classes to support Oracle Spatial databases. |
| lcd_postgresql.jar | Contains the java classes to support PostgreSQL databases. |
| lcd_saphana.jar | Contains the classes necessary to connect to a SAP Hana database. |