Deploying Adapter for JDBC Assets
To deploy Adapter for JDBC assets such as driver jars and TypeMapping configurations to Integration Cloud, perform the following steps:
1. Create the below folder structure inside any package which needs to be deployed apart from the core product package:
<
package_Name>\adapters\WmJDBCAdapter\config
2. Copy the database specific driver jar files from on-premises installation, <webM_Home>\Integration Server\instances\<instance_Name>\packages\WmJDBCAdapter\code\jars to <package_Name>\code\jars\static. Also, copy the Adapter for JDBC configurations (TypeMapping.xml files) from <webM_Home>\Integration Server\instances\<instance_Name>\packages\WmJDBCAdapter\config to <package_Name>\adapters\WmJDBCAdapter\config folder.
3. To enable the assets (Adapter Connections, Polling Notifications) on cloud, ensure to enable the State After Deployment option during deployment from Software AG Designer. The state of the assets (Adapter Connections, Polling Notifications) should be disabled on-premises before deploying to Integration Cloud. To deploy Adapter for JDBC to Integration Cloud, see Deploying Packages and Configuration Assets to
Integration Cloud. To connect to an on-premises database using VPN, you must variable substitute the serverName to IP address of the server as the hostname of the server cannot be resolved.
Segregate the driver jars and solutions such as
Adapter for JDBC's services, notifications into separate test packages.
Set the proper package dependency between the jar package and the
Adapter for JDBC's solutions package.
Limitations
You can use only Type 4 JDBC drivers for
Integration Cloud deployment.
Kerberos authentication is not supported.
Data type configuration file editing is not supported.