Setting up Node.js support

Perform the basic setup tasks to support Node.js in your CICS® region.

Node.js profile validation and properties
Node.js profiles contain a set of options and environment variables that are passed to the Node.js runtime when it starts.
Controlling the location for NODEJSAPP output, logs, and trace
Output from Node.js applications, the Node.js runtime and CICS are written to z/OS® UNIX files. The z/OS UNIX files are specified using the STDOUT, STDERR, LOG, and TRACE options in the CICS Node.js profile.
Giving CICS regions access to z/OS UNIX directories and files
CICS requires access to directories and files in z/OS UNIX. During installation, each of your CICS regions is assigned a z/OS UNIX user identifier (UID). The regions are connected to an ESM group that is assigned a z/OS UNIX group identifier (GID). Use the UID and GID to grant permission for the CICS region to access the directories and files in z/OS UNIX.
Setting the memory limits for Node.js
Node.js applications typically require more memory than those written in compiled languages, in part due to the Node.js applications ability to service many client requests simultaneously. You must ensure that CICS and Node.js have enough storage and memory available to run Node.js applications.

Parent topic: Configuring