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).

Important! The communication between the Java Communication Process (JCP) and the Proxy uses TLS/SSL exclusively. Because the CallAPI does not natively support TLS/SSL and still connects to the Communication Process (CP), it cannot connect directly to the Proxy nor the JCP). However, you can route CallAPI connections through the TLS Gateway to secure them. For more information, see TLS Gateway. The exceptions are the Java and SAP CallAPIs which already use TLS/SSL to connect to the Automation Engine. They communicate directly with the JCP and use trusted certificates to authenticate their identity to other communication partners.

More information:

For additional information about the different certificate types and examples of how they could be created and used, see What Kind of Certificates Should I Use for Automic Automation v21.

Important! Please note that these are only examples, not a requirement for Automic Automation and they are not meant to replace the product documentation.

In Automic Automation Kubernetes Edition, CallAPIs establish a connection to a TCP load balancer. The address of this load balancer must be configured on both ends—the Automation Engine and the CallAPI. The only exceptions are the Java and SAP CallAPIs, which must be updated to use TLS/SSL when connecting to the Automation Engine. These two CallAPIs establish a direct connection to the Java Communication Process (JCP) through an HTTPS load balancer. In this setup, you can also route the connections of the other CallAPIs through the TLS Gateway to securely reach the HTTPS load balancer.

More information:

To Install the CallAPI for NSK

  1. (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.

  2. Transfer text and binary files to the corresponding sub-volume (Host).

  3. (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.

See also: