IBM_RobPublished on January 15, 2019
There are two recent changes to App Connect Enterprise which now enable users of the cloud service to connect directly (without any need for an additional software installation) to JDBC based endpoints.
Below is an example configuration showing how to achieve this.
Download the attached Project Interchange file, which you can import into your App Connect Enterprise Toolkit. This file contains two projects:
3 comments on"Connecting integrations to JDBC endpoints on App Connect"
Hi, I found this small tutorial about JDBC drivers to connect to DB2. Is it to connect to DB2 Databases on-premises? I am trying to connect from APP Connect to a DB2 database on-premises and I only found this one. I was also searching a way to do it through API Connect and IBM Cloud Functions, but can’t find anything :/ (just found a way on API Connect through a connector, but I realized is using ODBC instead :/). If this is really for the purpose I mentioned above, is there a way to configure it without having to install the toolkit on my local machine?
Thanks! I figured this out by myself just today:| Is it necessary to use always DefaultPolicies in ACE on Cloud as a default PolicyProject?
Glad to hear that you have been using this new feature. Regarding your question about “DefaultPolicies” … I guess the original article should have been clearer: No, you can choose any name you like when defining the name of your Policy Project in the App Connect Enterprise Toolkit, it is just this example happened to use a project interchange file which had a policy project of this name. This Policy Project, and the policy it contains, are placed entirely under your control because you can choose in your Application and Flow which Policy / Policy Project you wish to refer to, and deployment of both the Policy Project and the Application and Flow are all handled in the BAR file itself.
In the Cloud service, you can also use the menus to define policies – this part of the cloud service was available when we were still branded as IBM Integration Bus on Cloud, and actually pre-dates the ACEv11 software capabilities in the area of policies. These policies, which are defined exclusively through the UI (web browser) of the cloud service, result in additional definitions being placed into the ACE containers which the service starts up on your behalf when you deploy your BAR files.
This means that as a user, you now have two separate ways available to get configuration information into your running containers – both the very controlled way through our web browser UI, and a much more free-form method (discussed in this JDBC example) of using policies inside policy projects which are carried inside the BAR files which you upload. For scenarios like this one, where you also want to carry a JDBC driver into the service as well, the more free-form method gives you many more functional opportunities!