Run Guidelines

Before running your compiled application, consider the following guidelines for the messaging API that you are using.

Java RTO API

  • For applications running on UNIX or Linux systems, set the LD_LIBRARY_PATH environment variable to specify the run-time path needed to find the appropriate RTO API library files.
  • For applications running on Windows systems, the lib directory in the API distribution archive includes a dynamic link library. When running clients built with these libraries, make sure to copy the dynamic-link library (DLL) to the directory that contains your client or copy it to a location where the DLL can be found by the operating system.

C API

  • For an application running on a UNIX or Linux system, set the LD_LIBRARY_PATH environment variable that specifies the run-time path needed to find the appropriate SolClient library files.
  • For an application running on Windows systems, the lib directory in the API distribution archive includes a dynamic link library. When running clients built with these libraries, make sure to copy the DLL to the directory that contains your client or copy it to a location where the DLL can be found by the operating system.
  • For an iOS application, always statically link against libsolclient. libsolclient includes libssl.a and libcrypto.a, so an iOS application does not need any extra steps to create secure connections.
    For specific instructions on running the SecureSession sample for iOS, see the README file in the ex/certs directory in the location where the iOS API is installed.

.NET API

  • Ensure that the corresponding .NET API assembly can be located and loaded by the .NET runtime.

    • The .NET API requires Microsoft .NET 2.0 or above framework.