Deployment of Adapter for JDBC Assets
To deploy Adapter for JDBC assets to Integration Cloud, do the following:
1. Create a separate package, <package_Name>, for deploying the database specific driver jar files that are part of the on-premises installation.
2. Copy the jar files from the on-premises installation <webM_Home>\Integration Server\instances\<instance_Name>\packages\WmJDBCAdapter\code\jars, and place the driver jar files in the <package_Name>/code/jars/static folder.
3. Add the package dependency of the asset package to the package <package_Name>, where database specific driver jar files are placed.
Note: Maintain the package dependency for assets scattered across packages. For more information on package dependency, see the webMethods Adapter for JDBC Installation and User’s Guide .
4. To enable the asset (connection, polling notification) on cloud, ensure that the State After Deployment is enabled during deployment from Software AG Designer. The state of the asset (connection, polling notifications) should be disabled on-premises before deploying to cloud. To deploy Adapter for JDBC to Integration Cloud, see Deploying Packages and Configuration Assets to
Integration Cloud. 
When using VPN and connecting to an on-premises database, you have to variable substitute the serverName to IP address of the server, as the host name of the server cannot be resolved.
Limitations
You can use only Type 4 JDBC drivers for cloud deployment.
Kerberos authentication is not supported.
Data type configuration file editing is not supported.