When you insert a database component into a Transformation Map you must have the necessary ADO, ODBC, or JDBC database connectivity components installed on your client workstation. You define the map through the mapping tool, and if you do a trial execute of the map in the mapping tool, you will use the selected ADO, ODBC, or JDBC database connector for the database connectivity.
For maps prepared as Java executable files (.JAR), when you execute the map in a LANSA Composer Processing Sequence, the map will use JDBC database connectivity components installed on your LANSA Composer server computer. The details for the JDBC database connection are provided by means of a Database Configuration.
LANSA Composer supplies neither the ADO, ODBC, nor the JDBC database connectivity components. You must obtain and install these components yourself for use with LANSA Composer – usually, these components are supplied by your database software vendor.
Most vendors will provide the requisite drivers on their installation CDs and allow you to download them from their website. In many cases, these drivers will be available at no charge. Most databases will need you to use a driver that is of exactly the same version as the database. Therefore, ensure that you have access to the correct driver for the version and type of database that you wish to connect to. Vendor websites are the best source for this information.
Refer to the appropriate one of the following headings for more information, links, and suggestions relating to your particular database:
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
Note: For many databases, drivers can also be obtained from third-party sources.
For executing maps prepared as Java executable files (.JAR), JDBC driver components need to be installed either into the jar directory of the LANSA Integrator instance or into a location that is accessible through the classpath.