Connecting to databases in Transformation Maps

The mapping tool in LANSA Composer supports mapping data between the various forms in which you exchange, transport, store and process it - for example, between XML and CSV.

Because most corporate data is stored in relational databases, a common application of Transformation maps is to map data between one of those formats and an application database. For example, in an application that permits trading partners to submit sales orders in an agreed XML format, your application might need to:

• transform incoming sales order XML data received from your trading partner into your received-orders database;

• transform order acknowledgement information from your database into an agreed XML form to send back to the trading partner.

 

The mapping tool supports the use of database components as either the source or target (or both) of the transformation for the databases it supports. These include:

• MS SQL Server

• Oracle

• IBM DB2

• MySQL

• Firebird

 

Other databases may be used if they provide suitable connectivity. You should refer to MapForce documentation and Altova for details of database support in MapForce.

Database Connectivity

You may need to be able to establish two types of connectivity to a database for use with the mapping tool and the maps it generates:

• ODBC, ADO or JDBC connection from the LANSA Composer client and server computers

     While defining your map you need to be able to establish an ODBC, ADO or JDBC connection (depending on the specific database type). This connection is initiated from the client computer running MapForce. Refer to:

Connecting to databases while defining a Transformation Map using ODBC or ADO

Connecting to databases while defining a Transformation Map using JDBC

     If your maps will be prepared to execute as MapForce Server execution files (.MFX), then this same (ODBC, ADO or JDBC) connection will be used on the server computer when executing the map (subject to the use, or not, of MapForce's Global Resources feature).  Refer to:

Connecting to Databases while Executing a Transformation Map

• JDBC connection from the LANSA Composer server computer

     For Transformation Maps prepared as Java executable files (.JAR), when the map runs, it will use a JDBC connection to establish the connection to the database. This connection is initiated from the server computer on which the transformation map executes. Refer to:

Connecting to Databases while Executing a Transformation Map

The following topic provides additional information about connecting to databases in Transformation Maps:

Database Connectivity Components and Drivers

The following topics provide examples, sample screens and guidance for connecting to selected specific database types as well as driver version and download information and links:

Example Database Connections for IBM i DB2

Example Database Connections for Microsoft SQL Server

Example Database Connections for Oracle

Example Database Connections for MySQL

Example Database Connections for Firebird

Example Database Connections for Microsoft Access