Databases and MapForce

www.altova.com Print this Topic Previous Page Up One Level Next page

Home >  Data Sources and Targets >

Databases and MapForce

Altova website: _ic_link Database mapping

 

MapForce 2019 provides powerful support for mapping databases to XML, flat files, and other database formats. With MapForce Enterprise edition, you can additionally map databases to EDI formats, Excel 2007+, JSON, XBRL, and Web services.

 

The following databases are supported. While Altova endeavors to support other databases, successful connection and data processing have only been tested with the databases listed below. If your Altova application is a 64-bit version, ensure that you have access to the 64-bit database drivers needed for the specific database you are connecting to.

 

Database

Notes

Firebird 2.5.4, 3.0


IBM DB2 8.x, 9.1, 9.5, 9.7, 10.1, 10.5


IBM Db2 for i 6.1, 7.1, 7.2, 7.3

Logical files are supported and shown as views.

IBM Informix 11.70, 12.10

Informix supports connections via ADO, JDBC and ODBC. The implementation does not support large object data types in any of the code generation languages. MapForce will generate an error message (during code generation) if any of these data types are used.

MariaDB 10.2, 10.3


Microsoft Access 2003, 2007, 2010, 2013


Microsoft Azure SQL Database

SQL Server 2016 codebase

Microsoft SQL Server 2005, 2008, 2012, 2014, 2016, 2017,

Microsoft SQL Server on Linux


MySQL 5.0, 5.1, 5.5, 5.6, 5.7, 8.0


Oracle 9i, 10g, 11g, 12c


PostgreSQL 8.0, 8.1, 8.2, 8.3, 9.0.10, 9.1.6, 9.2.1, 9.4, 9.5, 9.6, 10, 11

PostgreSQL connections are supported both as native connections and driver-based connections through interfaces (drivers) such as ODBC or JDBC. Native connections do not require any drivers.

Progress OpenEdge 11.6

 

SQLite 3.x

SQLite connections are supported as native, direct connections to the SQLite database file. No separate drivers are required.

Sybase ASE 15, 16


Teradata 16

Connections are supported through ADO.NET, JDBC, and ODBC.

 

When a mapping inserts data into a database table, database-generated identity fields are not supported.

 

Database mappings in various execution environments

When you generate program code from a mapping, or when you compile a mapping to MapForce Server execution files, or when you deploy a mapping to FlowForce Server, the database connection details saved with the generated files are adapted to drivers applicable or supported for the chosen target environment, as shown in the table below. For example, if the mapping transformation language is set to Java, ADO connections are converted to JDBC when Java code is generated from the mapping.

 

When the mapping is executed in an environment other than MapForce, you will need to make sure that the database connection details are meaningful on the machine which executes the mapping (for example, the database driver is installed, the database path is correct, the database server is accessible, etc.).

 

Some database connection types are not supported in some target environments, as shown in the table below.

 

Connection type/Execution Environment

C#

C++

Java

MapForce Server on Windows

MapForce Server on Linux/Mac

ADO

ADO bridge

As is

Converted to JDBC

As is

Converted to JDBC

ADO.NET

As is

User defined

Converted to JDBC

As is

Converted to JDBC

JDBC

User defined

User defined

As is

As is

As is

ODBC

ODBC bridge

ODBC bridge

Converted to JDBC

As is

Converted to JDBC

Native PostgreSQL

Not supported

Not supported

Not supported

As is

As is

Native SQLite

Not supported

Not supported

Not supported

As is

As is

 

Table legend:

 

"As is" means that the database connection type (for example, JDBC, ODBC) remains as defined in MapForce.
"Converted to JDBC" means that the database connection will be converted into a JDBC-like database connection URL.
"ADO bridge" or "ODBC bridge" means that the connection string remains as defined in MapForce, but the generated code will use a suitable class which acts as an ADO bridge (or ODBC bridge, respectively), for example, System.Data.OleDb.OleDbConnection or System.Data.Odbc.OdbcConnection.
"User defined" means that, in order for the connection to work in generated code, you will need to manually enter the connection details into the Database Component Settings dialog box. Depending on the case, these connection details must be entered under ADO/OLE-DB-specific settings or under JDBC-specific settings.

 

See also:

 

Preparing Mappings for Server Execution
Compiling Mappings to MapForce Server Execution Files
Deploying Mappings to FlowForce Server
Code Generator

© 2019 Altova GmbH