- Find out what Node.js is, and its value in CICS
- Answer your questions on how to set up, and run Node.js in CICS as well as all the prerequisites for doing so
- Learn the useful links that can assist you with the education and process of Node.js in CICS
What is Node.js?
When is Node.js the best choice to use with CICS?
There is a large community of full-stack developers able to design and code the UI, APIs and server components, and Node.js is their preferred runtime. The Node.js Foundation claim there are 9 million instances of Node.js.
CICS already supports applications in several languages. Why do I need Node.js?
CICS has always been unique in providing developers the choice to use the language most appropriate to tackle the business and technical requirements – be it with Java, COBOL, PL/I, C/C++, or Assembler. CICS TS V5.5 is extending this choice by adding support for Node.js.
How does Node.js differ from other languages supported by CICS?
The integration of Node.js with CICS brings two diverse user communities together; the ecosystem of CICS products and tools can be used to manage a collection of Node.js applications, and the power and flexibility of a modern language is brought to CICS.
Although Node.js application can call CICS programs using network services, for improved response times they can also use a locally optimized memory transport provided by the ibm-cics-api module.
Which type of IBM Z processors does the Node.js application run on?
Node.js applications are run on general purpose CPs, and some operations use the Integrated Cryptographic Services Facility (ICSF). See Installing and configuring IBM SDK for Node.js – z/OS.
How do I run my Node.js application in CICS?
Node.js application typically consists of a .js file that is the initial script, a package.json file that describes the modules the script requires, and other scripts, modules, and web site files.
First create a CICS bundle using CICS Explorer V5.5, copy the Node.js application into the bundle, then start the CICS bundle editor. Select New > Node.js Application and the wizard will guide you through selecting the Node.js application start script and creating a profile. The profile is used to configure the environment for Node.js and the environment variables the application requires, such as a TCP/IP port and working directory for log files.
Next export the CICS bundle to zFS. If your application requires modules that are not already installed in zFS, use the utility Node Package Manager (npm) that is provided with IBM SDK for Node.js – z/OS to install them into either a global location or the CICS bundle.
Finally define and install a BUNDLE resource in CICS. The Node.js application will be started.
Like with any CICS bundle, you can automate the build and deployment using the CICS build toolkit and DFHDPLOY utility.
I don’t have a Node.js application – is there a sample?
How do I monitor Node.js applications in CICS?
CICS provides a new NODEJSAPP resource when the CICS bundle is installed to provide you with basic information about the Node.js application. In this open beta you can view NODEJSAPP resources with the CEMT INQUIRE NODEJSAPP command.
What do I need to try running Node.js applications on my system?
- Download and install CICS TS V5.5 and CICS Explorer V5.5.
- Download and install IBM SDK for Node.js – z/OS, V8 or later.
- Install sample Node.js application as described in Verifying the installation of the Node.js runtime.
Can I try this out without installing anything?
Yes – sign up at the page “Join our CICS early access program” and the beta team will provide a system you can access via your browser to try this out.