Installing the CallAPI for NSK

The Automation Engine supplies a CallAPI for NSK. It enables calls in the Automation Engine from your own programs. This interface can be installed under the D4n.nn series of NSK.

UCXBNS1C is a CallAPI utility that can be called from the command line of the operating system, a script, or a job.

A three-character code is assigned for each supported NSK variant and it is used in some CallAPI file names (NS1 for HP NonStop Server Guardian NSK Version D40).

In Automic Automation Kubernetes Edition, CallAPIs establish a connection to a TCP load balancer. The address of the load balancer must be defined on both sides: the Automation Engine and the CallAPI. The only exceptions are the CallAPIs for Java and SAP, which must be upgraded to use TLS/SSL to connect to the Automation Engine. These two CallAPIs establish a connection with the Java communication process (JCP) through an HTTPS load balancer.

More information:

To Install the CallAPI for NSK

(Admin computer) Establish a connection to the HP NonStop Server using an FTP client and log on with the user ID that is required for the installation.
Transfer text and binary files to the corresponding sub-volume (Host).
(Host) Set up the system environment and adjust the INI file (UCXBNS1I.INI) of the NSK CallAPI, see Call API NSK INI file.

Tip: You can also adjust it on the Admin computer and transfer it to the host using FTP.

Note: You can keep your existing INI file even if there is a new Automation Engine version and adjust it as required.