Calling a Shared Library in UNIX from eScript
(Doc ID 476274.1)
Last updated on NOVEMBER 22, 2019
Applies to:Siebel Tools - Version 7.0.4  and later
V8 (Enterprise), V8 (MidMarket), V8 (Professional), V7 (Enterprise), V7 (MidMarket), V7 (Professional)
Database(s):All Supported Databases
App Server OS(s):AIX, Solaris, HP-UX
Latest release tested against:V8 (Enterprise)
Keywords:eScript, shared library, SElib.dynamicLink
This document was previously published as Siebel Technical Note 291.
””Checked for Relevance on 17-Nov-2015””
This technical note provides information about creating a shared library on UNIX, and accessing it from Siebel eScript using the SElib.dynamicLink() method. Shared libraries on UNIX are similar to DLLs on Windows. By implication, the eScript must run within a Siebel Server on UNIX, for example, a business service called by a workflow process.
For additional guidelines regarding calling external DLLs and shared libraries via the SElib Object, refer to "Stability Guidelines When Calling External DLLs/Shared Libraries via SELib Object (eScript) (Doc ID 477418.1)", which is available on the support portal.
If you are running Siebel applications version 126.96.36.199 or earlier, please review "eScript, SElib.dynamicLink : assumes length of string parameter returned from an external library - (Doc ID 477091.1)"on the support portal regarding a potential Object Manager crash and the necessary Maintenance Release to avoid this issue.
This document is informational and intended for any user.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Appropriate usage for SElib.dynamicLink|
|Definition of a Shared Library|
|How to Create a Shared Library on UNIX|
|The LD_LIBRARY_PATH Environment Variable|
|Use of a Shared Library in eScript|
|Known Issues with SElib.dynamiclink on UNIX platforms|