Library files
Linux
When you install the AR System C and Java APIs on a supported Linux system, most library files are installed in a directory under the server directory, arInstallDir/api/lib.
Consider the following while using the Linux applications:
- The icu, xalan, and xerxes library files are installed in arInstalldir. To make sure your application can access these libraries, copy them to the lib directory.
- To load dynamic libraries on Linux, include the -ldl link flag in the link command. See the driver sample makefile.
- The JNI files and all C API library files are required when a Java API program connects to a pre-7.0.01 AR System server.
The following table lists the installed library files for Linux platform:
The C or Java API programs require the library files. In the library file names, the placeholder VerNum represents the version number of the release. In some cases, this includes a build number.
For example: In release 7.6.04, the AR System API file is named arapi7604jar or arapi7604_build001.jar.
Linux libraries
Operating system | Required for | Files |
|---|---|---|
Linux 64-bit | All | libar_lx64.a |
libar_lx64.so | ||
libicudatabmc_lx64.so.32.0 | ||
libicui18nbmc_lx64.so.32.0 | ||
libicuiobmc_lx64.so.32.0 | ||
libiculebmc_lx64.so.32.0 | ||
libiculxbmc_lx64.so.32.0 | ||
libicutubmc_lx64.so.32.0 | ||
libicuucbmc_lx64.so.32.0 | ||
XML functions | libarxmlutil_lx64.so | |
libxalan-cbmc_lx64.so.110.0 | ||
libxalanMsgbmc_lx64.so.110.0 | ||
libxerces-cbmc_lx64.so.28.0 | ||
libxerces-depdombmc_lx64.so.28.0 | ||
Java API | arapiVerNum.jar | |
arapiextVerNum.jar | ||
libarjniVerNum.so | ||
arlogger-9.1.11-SNAPSHOT.jar | ||
log4j2.xml | ||
arsys_sample.xml |
UNIX
When you install the AR System C and Java APIs on a supported UNIX system, most of the library files are installed in a directory under the server directory, arInstallDir/api/lib.
Consider the following while using the UNIX applications:
- The icu, xalan, and xerxes library files are installed in arInstallDir. To make sure your application can access these libraries, copy them to the lib directory.
- The name of each 64-bit library file includes a string that indicates its execution mode.
- The JNI files and all C API library files are required when a Java API program connects to a pre-7.0.01 AR System server.
The following table lists the installed library files for each UNIX platform:
The API programs require the library files. In the library file names, the placeholder VerNum represents the version number of the release. In some cases, this includes a build number.
For example: In release 7.6.02, the AR System API file is named arapi7602.jar or arapi7602_build001.jar.
UNIX library files
Operating system | Required for | Files |
|---|---|---|
Oracle Solaris* (64-bit) | All | libar_solsp64.a |
libar_solsp64.so | ||
libicudatabmc_solsp64.so.32.0 | ||
libicui18nbmc_solsp64.so.32.0 | ||
libicuiobmc_solsp64.so.32.0 | ||
libiculebmc_solsp64.so.32.0 | ||
libiculxbmc_solsp64.so.32.0 | ||
libicutubmc_solsp64.so.32.0 | ||
libicuucbmc_solsp64.so.32.0 | ||
XML functions | libarxmlutil_solsp64.so | |
libxalan-cbmc_solsp64.so.110.0 | ||
libxalanMsgbmc_solsp64.so.110.0 | ||
libxerces-cbmc_solsp64.so.28.0 | ||
libxerces-depdombmc_solsp64.so.28.0 | ||
Java API | libarjniVerNum.so | |
arapiVerNum.jar | ||
arapiextVerNum.jar | ||
arlogger-9.1.11-SNAPSHOT.jar | ||
log4j2.xml | ||
arsys_sample.xml | ||
*To load dynamic Solaris libraries, include the -ldl link flag in the link command. See the driver sample makefile. | ||
At run-time, all required library files must be in an accessible directory. Add the full path of the directory or directories to the environment variable listed in the following table:
Library path environment variables
Windows
When you install the AR System C and Java API on Windows, most library files are installed in a directory under the server directory, arInstalldir\serverName\ARServer\Api\lib.
Consider the following while using the Windows applications:
- The icu library files are installed in arInstalldir. To make sure your application can access these libraries, copy them to the lib directory.
- The JNI files and all C API library files are required when a Java API program connects to a pre-7.0.01 AR System server.
The following table lists the installed library files:
The API programs require the library files. In the library file names, the placeholder VerNum represents the version number of the release. In some cases, this includes a build number.
For example: In release 7.6.02, the AR System API .dll file is named arapi7602.dll or arapi7602_build001.dll.
Windows library files
Operating system | Required for: | Files |
|---|---|---|
Windows (64-bit) | All | icudt32.dll |
icuinbmc32_win64.dll | ||
icuucbmc32_win64.dll | ||
C | arapiVerNum_win64.dll | |
arapiVerNum_win64.lib | ||
arrpcVerNum_win64.dll | ||
arutlVerNum_win64.dll | ||
C XML functions | arxmlutilVerNum_win64.dll | |
Java API | arjniVerNum.dll | |
arapiVerNum.jar | ||
arapiextVerNum.jar | ||
jlicapiVerNum.jar | ||
arlogger-9.1.11-SNAPSHOT.jar | ||
log4j2.xml | ||
arsys_sample.xml |
In addition to these files, your program needs access to arcatalog_eng.dll or the message catalog for your locale. The message catalogs are installed in the server directory, C:\Program Files\BMC Software\ARSystem.
At run-time, all required library files must be in an accessible directory. Add the full path of the directory or directories to the Windows PATH environment variable.