Build Instructions

The following sections describe how to build the UVAPI example application and test application.

UNIX Platforms

To build the example UVAPI package and test utility, enter the following command in the directory where your files are located:

make -f uvapiunx.mak

This command produces the following files:

uvapi.so (the UVAPI package as a shared library)
tstuvapi (the test utility executable).
Note: TIBCO iProcess Engine 11.8.0 is built as a 64-bit application; therefore, the UVAPI package must be built as a 64-bit library as well as the test utility executable.
Note: The build environment requires modifications for different UNIX platforms. The uvapiunx.mak makefile contains a section that sets up the environment for the target platform. Edit this section as appropriate for your target platform.

To run the test utility, the UVAPI package must be locatable as a shared library. For the example UVAPI package, the SWDIR environment variable must also be set, and the file SWDIR/util/exuvapi.dat must exist (see the UVAPI developers documentation for details of the example UVAPI package).

The test utility only calls the Initialisation and Termination interfaces in the UVAPI package as all other interfaces require iProcess encrypted strings to be passed in or returned.

Windows Platforms

To build the example UVAPI package and test utility, set up the environment for the Microsoft Visual Studio 2017 compiler and enter the following command:

nmake -f uvapiw64.mak

This command produces the following files:

uvapi.dll (the UVAPI package as a Dynamic Link Library)
tstuvapi.exe (the test utility executable).

To run the test utility, the UVAPI package must be locatable as a DLL (on the PATH or in the current directory). For the example UVAPI package, the tstuvapi.exe utility and uvapi.dll components must be located in the util sub-directory of an iProcess installation. The file SWDIR\util\exuvapi.dat must exist.

The test utility only calls the Initialisation and Termination interfaces in the UVAPI package as all other interfaces require iProcess encrypted strings to be passed in or returned.