Menu

Lesson 20 · Node.js on IBM i — From RPG Developer to Modern IBM i Developer

Complete the Tools Rental Project

Review the finished application, verify every layer, and identify sensible next improvements without losing the working baseline.

IBM iNode.jsTools RentalProject ReviewModernization

The project began with one JavaScript object representing a cordless drill. It now has a database, business transactions, an API, tests, a browser interface, and a production operating plan.

That progression is the point of the course. Node.js is not useful because it can print Hello World. It is useful because it can provide a maintainable modern interface while Db2 for i and established IBM i practices continue to protect the business data.

What you built

The completed application includes:

Browser interface
       ↓
Fastify routes and validation
       ↓
Node.js database module
       ↓
Db2 procedures, constraints, and tables
       ↓
IBM i authority, jobs, storage, and operations

It can:

Verify the repository

A finished repository should have a recognizable shape:

tool-rental/
├── public/
│   ├── app.js
│   ├── index.html
│   └── styles.css
├── sql/
│   ├── README.md
│   ├── 001-create-tables.sql
│   ├── 002-seed-development-data.sql
│   └── 003-rental-procedures.sql
├── src/
│   ├── db.js
│   └── server.js
├── test/
│   └── server.test.js
├── .env.example
├── .gitignore
├── package.json
└── package-lock.json

Your exact structure may differ, but another developer should be able to find the source, database changes, tests, configuration definition, and operating instructions without guessing.

Run the final checklist

Before calling version 1 complete:

If one of these items is missing, record it as work rather than quietly accepting it as a production assumption.

Sensible next improvements

Build on the working baseline one feature at a time:

Each improvement should begin with a business requirement, a data decision, and a test. Avoid adding a framework or package simply because it is popular.

The larger lesson

You did not replace RPG, move Db2, or abandon IBM i. You added a modern application layer using the same habits that make traditional IBM i systems dependable: explicit data rules, controlled authority, repeatable deployment, traceable source, and operational ownership.

That is a practical modernization path—small enough to begin, but complete enough to operate.

The application is complete at this point. The next lesson is an optional extension that keeps the same project and replaces only its Db2 connector with Mapepire.

References

Documentation and references used for this lesson.

← Return to Node.js on IBM i

Comments

Share your thoughts, questions, or real-world IBM i experiences related to this article.