npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@apex-process-consultants/loopback-connector-ibmi

v1.0.0-beta.2

Published

LoopBack Connector for Db2 on the IBM i

Downloads

5

Readme

loopback-connector-ibmi

This is a database connectior for Db2 on IBM i intended for use with LoopBack 3 (LoopBack 4 testing soon). It uses the npm odbc package to connect to the database, so installing an ODBC driver manager and driver and setting up a datasource is required for use (see below).

Major differences from version 0.x of loopback-connector-ibmi

This version of the module is significantly different from version 0.x and constitutes a complete rewrite. This project is a derivative of loopback-connector-db2iseries and the v0.x loopback-connector-ibmi.

The main difference between this and the other packages for IBM i (including v0.x of this package) is that it uses ODBC to communicate to the database. Version 0.x of this package was built using the Db2 for i CLI API set, hence the need for important prerequisites (below).

Prerequisites

Before installing this package, you will need an ODBC driver and a driver manager (with development libraries). This package is primarily developed and tested with the IBM i Access ODBC driver, which is supported as part of IBM i software maintenance agreements (SWMA) and comes with no additional licensing fees.

On IBM i

On Linux

  • Install the unixODBC-devel package with your operating system's package manager (apt-get, zypper, yum, etc).
  • Install the "Linux Application Package" of IBM i Access Client Solutions. Consult this document for assistance.

On Windows

  • Install the "Windows Application Package" of IBM i Access Client Solutions. Consult this document for assistance.

Installation

Once the prerequisites are satisfied, enter the following in the top-level directory of your LoopBack application and install this package:

$ npm install loopback-connector-ibmi 

Configuration

In LoopBack, datasources are used to store the information about your database so it can be used by the program. Use the data source generator to add to your application:

lb datasource

The datasource generator will then walk you through the process of setting up a datasource:

  1. Enter the datasource name: Any name will do, such as the name of the schema you will use or the name of your system.
  2. Select connector for <name>: LoopBack 3 does not have knowledge of loopback-connector-ibmi, so just press up on the arrow key once and select other.
  3. Enter the connector's module name: Enter loopback-connector-ibmi.
  4. Install loopback-connector-ibmi: If you haven't installed it, enter Y. If you have already installed it, select n.

This will generate an entry in your server/datasources.json file. It should know have an entry similar to:

  "test": {
    "name": "test",
    "connector": "loopback-connector-ibmi"
  }

You should edit this entry to add information on how to connect to Db2. For loopback-connector-ibmi, you need to pass either a connectionString, or pass your username, password, and dsn (which will be the DSN name you set up for your ODBC driver).

"test": {
  "name": "test",
  "connector": "loopback-connector-ibmi",
  "connectionString": "DSN=MYDSN"
}

or

"test": {
  "name": "test",
  "connector": "loopback-connector-ibmi",
  "dsn": "MYDSN",
  "username": "FIRSTLAST",
  "password": "password123"
}

The following table describes the connector properties.

Property| Type | Description ---| --------| -------- connectionString | String | ODBC connection string for connecting to the database dsn | String | ODBC DSN to use for the connection username | String | Username on the IBM i password | String | Password on the IBM i schema | String | Specifies the default schema name that is used to qualify unqualified database objects in dynamically prepared SQL statements. The schema name is case-sensitive.

More connector properties will be added as requested by the community

Alternatively, you can create and configure the data source in JavaScript code. For example:

var DataSource = require('loopback-datasource-juggler').DataSource;
var DB2 = require('loopback-connector-ibmi');

var config = {
  dsn:      process.env.DSN
  username: process.env.DB2_USERNAME,
  password: process.env.DB2_PASSWORD,
};

var db = new DataSource(DB2, config);

var User = db.define('User', {
  name: { type: String },
  email: { type: String },
});

// Will make sure that 'User' table has the same format as the model
db.autoupdate('User', function(err) {
  if (err) {
    console.log(err);
    return;
  }

  User.create({
    name: 'Tony',
    email: '[email protected]',
  }, function(err, user) {
    console.log(err, user);
  });

  User.find({ where: { name: 'Tony' }}, function(err, users) {
    console.log(err, users);
  });

  User.destroyAll(function() {
    console.log('example complete');
  });
});