Installing the CallAPI for UNIX

The Automation Engine supplies a CallAPI for UNIX. It enables calls in the Automation Engine from your own procedures or programs , which can be written in programming languages such as C, C++, or COBOL.

UCXB???C is a CallAPI utility that can be used for command-line calls or in executable files.

A three-character code is assigned for each supported UNIX variant and is used in some CallAPI file names such as AP6 for AIX.

Note: In this document, the specific code is replaced by ???.

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:

• Securing Connections to the AE (TLS/SSL)

• TLS/SSL Certificate Considerations

• Types of Server Processes

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:

• Container-Based Installation - Automic Automation Kubernetes Edition

• Connecting to the AAKE Cluster

To Install the CallAPI for UNIX

1. (Admin computer) Transfer the tar file UCXB???C.tar.gz using FTP.

2. (Host) Unpack the tar file: gzip -d UCXB???C.tar.gz or gunzip UCXB???C.tar.gz

   tar xvf UCXB???C.tar

   Linux:tar -zxvf UCXB???C.tar.gz

   When unpacked, the actual files are automatically created in the directories /bin, /lib and /src, if they do not yet exist. The packed file can be deleted afterward.

3. Adjust the INI file (UCXBXXXC.ORI.INI) of the UNIX CallAPI to your system environment. For more information, see Call API Unix INI file.

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

4. Set the variable:

   • AIX:export LIBPATH=Paths of the installation directories

   • Solaris, Linux, zLinux:export LD_LIBRARY_PATH=Paths of the installation directories

See also:

Platforms for CallAPIs