Administration Guide > Installation > New Installation > Installing the CallAPI for NSK

Installing the CallAPI for NSK

This document guides you through the new installation of a CallAPIA programming interface that processes a script in the Automation Engine system. It can be called directly from within the program itself or from a different program. for NSK.

A CallAPI for NSK is supplied with AE. This interface can be installed under the D4n.nn series of NSK. UCXBNS1C is a utility that can be called from the command line of the operating system, from a scriptA particular Automation Engine object type. or a jobAn Automation Engine object type for a process that runs on a target system.

A three-character code is assigned to each supported NSK variant. It is shown in some file names of the CallAPI and described in the terminology (NS1 for HP NonStop ServerYou can use nonstop processes (NWP) in order to increase your system reliability. A specific license is required for this purpose. In nonstop operation, only the WPs of one computer are active. The processes of a different computer (nonstop processes) are available upon request. If the primary computer that includes the active WPs fails, the nonstop processes take over their role. As opposed to a usual parallel operation, the system configuration NonStop Server does not use the WPs of all computers. The WPs of ony computer are always in the mode "hot standby." [Formerly called "UC4.Nonstop Server."] Guardian NSK Version D40).

Supplied Files

The files for the NSK CallAPI are included with the NSK agentA program that enables the de-centralized execution of processes (such as deployments) on target systems (computers or business solutions) or a service that provides connectivity to a target system (such as for databases or middleware). An agent is also an object type in the Automation Engine. [Formerly called "Executor."] See also: host found in IMAGE:Agent/nsk in a PAK archive.

File name

File

Description

UCXBNS1C

Binary

Utility for calling the CallAPI

UCXBNS1I

Text

INI file for the utility

scrsamp

Text

AE sample script

UCMSL

Text

Message library

 


Procedure

1.

Transferring the supplied file to the hostComputer, target system. and setting up the system environmentAn Environment consists of Deployment Targets which represent your endpoints. Different environments are used for different phases in the software delivery cycle, for example Development, QA, Staging, Production. An environment is typically set up once and used by several applications.

 

See also:

CallAPI for NSK

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2016 Automic Software GmbH