Linking C API Programs With the AppConn Shared Library

In order to link a C API program with an AppConn shared library, you must declare the library in the PATH variable. Declaring the PATH variable is handled differently on each platform. The following topics explain the differences between using a Windows platform and using a Linux, AIX, or Solaris platform for development.

Using a Windows-based Platform for Development

Programs that use the AppConn C API must also link with appconn.lib. The AppConn C API functions are implemented in appconn.dll (AppConn COM is also implemented in appconn.dll). Appconn.lib contains the linkage definitions necessary to use the AppConn C API functions in appconn.dll. Appconn.lib is installed in your <install directory>\lib directory and appconn.dll and xerces-c_1_4.dll are installed in your \Winnt\system32 directory.

Using a Linux, AIX, or Solaris Platform for Development

Programs that use the AppConn C API must also link with the libappconn.so, and with libxerces-c1_4.so for Linux and Solaris, and libxerces-c1_4.a for AIX. The actual AppConn C API functions are implemented in libappconn.

Note: When using the AppConn C API, the directory where the libappconn and libxerces-c1_4 are located must be declared in the library variable. For example:

 LD_LIBRARY_PATH={/usr/local<install directory>/lib} (Linux and Solaris)
  LIBPATH={/usr/local<install directory>/lib} (AIX)

  export LD_LIBRARY_PATH  (Linux and Solaris)
  export LIBPATH (AIX)

Notes:

The library files associated with the AppConn C API are installed in your /lib directory.
The AppConnXML interface has been deprecated.