Optim Data Privacy Providers
11.3.0
|
ODPP uses a number of shared libraries and uses the system-specific library search order to load these shared libraries. It is dependent on the PATH / LD_LIBRARY_PATH / LIBPATH / SHLIB_PATH environment variable to load its libraries.
This feature will enable ODPP to load its libraries without having a dependency on system environment variables such as PATH / LD_LIBRARY_PATH / LIBPATH / SHLIB_PATH. ODPP Loader must be invoked as the first activity even before ODPP framework initialization is done. This is an optional feature controlled by the user by means of a Loader API independent of the ODPP core API's and to use this feature the application must load and invoke all ODPP API's dynamically.
The primary interface is a Loader API exported by an ODPP shared library called "ODPPLoader" which is a stand-alone shared library that does not depend upon any other external library except system libraries
The following are the functions provided for ODPP Loader:
The following sequence diagram shows how an application would use the ODPP Loader along with ODPP core without setting the LD_LIBRARY_PATH or LIBPATH or SHLIB_PATH in a Unix environment.
This feature is supported on all ODPP supported platforms except HP PA-RISC.