Configuring Sterling B2B Integrator maps that use SQL

To run Sterling B2B Integrator maps that use SQL through the Transform() API, you must configure a database property to describe the names and types of data sources referred to in the map.

To transform a map that uses SQL, the JVM from the host application that invokes SPE must be provided with a system property named databaseProps. The databaseProps property describes the names and types of data sources referred to in the map.

This property file is required whether the Sterling B2B Integrator map uses SQL on the input side, output side, or both sides.

If SQL is present in the input side, you must provide a valid file for an input stream. This input stream file is used to satisfy the Transform() API method signature only, and is not processed.

In the host application, define JDBC connections properties in a system property file named databaseProps. The format looks like an Sterling B2B Integrator database properties files.
Example:
```
mysqlPool.driver=com.mysql.jdbc.Driver
mysqlPool.url=jdbc:mysql://hostURL:13003/database_name?useUnicode=true&characterEncoding=UTF-8&useOldAliasMetadataBehavior=true&useCursorFetch=true&defaultFetchSize=1024 mysqlPool.user=si mysqlPool.password=database_password mysqlPool.maxconn=20 mysqlPool.catalog=catalog.name mysqlPool.maxRetries=100
```
where

mySQLPool is the name of an ODBC data source that is used in a Sterling B2B Integrator map.

Important: The translator code expects the exact name databaseProps. The system property file must have this name to be recognized.
Configure your invoking application to call the databaseProps file with this statement:
```
-DdatabaseProps=c:/_dev/spe2/jdbc.properties
```
Add the target database JDBC driver to the classpath of the invoking application.
If SQL is used on the input side, provide a valid text or binary marker file to pass in the input stream to the transform call.
This file is required, even though the input file is ignored during processing.