This article is Part 2
Part 1 –
Using Node to Connect to … Almost Anything
18 Apr 2016
- Part 2 – This Article
I’m back, this time with a spin on the base application I established in the last post. This flavor of things will utilize JDBC to connect to a DB2 table on an IBM i. This should work with anything the
can connect to, and should you swap out the
for any other JDBC jar ( PostgreSQL
, etc.), the only changes you would need to make are to ensure your SQL queries/statements are valid for the data source.
As I break down the specifics for each implementation, you will find that I’m focusing on changing only a couple of files, the js files for the
module and for the
module are the biggest, with mere implementation concerns in the available
I recently stumbled across a long forgotten Facebook message (in the category of Facebook thought I didn’t want to see it)
regarding a comment I had made on a developerWorks article
, stemming from a micro-service I had written, to stand up a Node instance so I could consume data from our IBM i (iSeries/AS400/a power system by any other name) in a more RESTful/REST-like JSON API capacity.
The funny thing about the developerWorks article was that it eventually was refactored/updated to get around a dependency of a data server driver, which apparently is freely available for DB2 on other platforms than the IBM i (the strange things I had to learn at the time). In the end, I switched to using a jdbc package from npm, specifically the one titled ‘jdbc’ (at version 0.0.15), which subsequently underwent significant changes in their API format, meaning that I’m going to show a version with updated specifics using the ‘jdbc-pro’ package from npm.
The unique dependencies here are:
is set to ignore
files, so you’ll need to download and include your own copy of it; I’ m parking mine at the path of
the npm package
(which makes its main jdbc module accessible via a
statement); install via
npm i -S jdbc-pro
Part of why you’ll need to download and include your own copy is, while I know the project to be open sourced from IBM under the IBM Public License 1.0
, I’m just not familiar with that license. For those looking for one, the tldr legal page for IBMPL
does a good job summarizing the conditions of the license.
Specifics With IBM i and JT400
The core connection component here is
allowing for a JDBC connection
. When I first implemented my initial version, I tried using the
package, which I ended up not using in favor of the
package due to some issues
and preferences. Currently, the
package I used has moved on to a newer, major breaking API change, which I haven’t used, so the following will make use of the
from npm, which looks to be the one I would choose should I start it again, today (and is more consistent with my previous implementation).
Data Connection Config
For the config of connection, we’ll want to establish the url to the IBM i, the path to the
, driver name (provided), and a valid user name and password. This is exported as an object, making it directly usable in the data handling (
) module, it’s been pulled in via a
statement. You can see that I’m again using a number of environment variables to assign things like the url property, or username or password. My example has fail-over values, but it’s best to keep those separate from the code base.
Next, I defined a common connection closing function, then two functions for the actual SQL statement handling; that’s because this package has two separate methods. One is for queries (e.g.-
SELECT * FROM ...
) and one for updates (either
operations); per the npm package documentation.
I wrapped up those functions using a common function for both initializing a connection and for closing the jdbc connection. You’ll note that I’m approaching callback hell
, but I’ve deliberately avoided this as much as possible by separating out my functions to invoke the passed callback functions and handle any potential errors generated. This can seem tedious, but when it comes to event driven operations, it’s best to write code that matches the async nature.
Lastly, I export those two primary functions as a JS object (as methods) to be called via their require statement in my
Now that my connections are configured and my data handling is provisioned, all I need to do is invoke it in my various
. As you can see from my data
module, the exposed
method is simple enough to use:
- passing in the SQL query and
- a function, which has two parameters, error or data
This way, if the error handle is null, it will not execute the error block, and vice versa. At this point, I hope the up-front modularizing is starting to show off its utility, as the implementation is about as simple as you can get.
The other available
all get updated as well, but they’re virtually identical, save for the specifics of the SQL query.
You can find my source code for this version of the project, in full, in
the same GitHub repository as last time, just in the
As you can see, once we’ve configured and provisioned our connection, we can use it pretty easily. While wrapping up a bunch of queries to an RDBMS via JDBC can seem a bit silly, I have to say that the performance benchmarks I did at the time were quite impressive and the micro-service had the great benefit of being easily maintained outside my main production application, either by myself or another developer (who helped in setting up the SQL queries, due to their more intimate knowledge of the DB2 tables).
You can probably guess what’s coming up with the next post in this series. Once we connect, in a well structured way, to any data source, any data source becomes swappable by configuration. So tune in next time for an early, expanded example of the use and implementation of the domino-nsf
package for access to a Notes/Domino file.