Re: What forum is best for a Tope and Node question? -- WEB400

*>this then means you have to run your NodeJs server on the IBM i and can't
develop it locally and get all the benefits you get on the PC, like a
reloading development server when the code changes and a nice debugger*

Note I do all of my Node.js development in VSCode on my laptop and have the
source automatically sync'd to the IFS. And I have an ssh session open to
the directory of the application on the server.

Also, Node.js v8.x on IBM i supports server-side debugging through Chrome's
dev tools (and also through VSCode).

Here's a slide deck I gave at WMCPA a few days ago that details some useful
Node.js things the community can make use of:
http://krengel.tech/litmis-nodejs-all-the-things-slides

Aaron Bartell
IBM i hosting, starting at $157/month. litmis.com/spaces

On Fri, Mar 16, 2018 at 10:45 AM, Tim Fathers <X700-IX2J@xxxxxxxxxxx> wrote:

Well, let's say you want to target DB2 (not just on the i) then there are
a number of DB2 drivers, none of which appear to be officially supported,
the most popular one seems to be "ibm_db", however, this doesn't support
the retrieval of metadata from a stored procedure call, which is necessary
if you wish to communicate back to the webservice caller the types and
sizes of the parameters and result set columns. IBM do have a native driver
I think, which I suspect does allow metadata retrieval, but this then means
you have to run your NodeJs server on the IBM i and can't develop it
locally and get all the benefits you get on the PC, like a reloading
development server when the code changes and a nice debugger (I've not
tried using a remote debugger on IBM Node, which might make debugging a bit
less painful). In Java EE, I can develop on my PC in the IDE, run a Tomcat
instance locally and use a local copy of DB2, MySQL or whatever, or even
point to my IBM i just by providing th
e right JDBC driver and connection options - my code stays exactly the
same. This also means that simply by providing different DB connection
resources in TomEE the same webservice can execute SPs on completely
different databases seamlessly.

Coming back to Node, if you look up drivers for SQL Server, for example,
there don't seem to be any officially supported ones. Furthermore, the APIs
for each driver are often completely different so you have to write
specific code for each database, or worse still, driver that you wish to
use. Also, TomEE has a build in database connection pooling facility, in
Node on the other hand, some drivers have it, some not, then you have to
find your own pooling solution.

If anyone knows better or I've missed something obvious I'd love to know,
as I said, I'd prefer to rewrite my framework in Typescript and run it
under Node then I have all the code under one roof as it were, but it just
doesn't seem that straightforward.