1.1.5.4.2 Configuring Plug-in Libraries
A plug-in is a set of functions that are called when the
GWWS
server is running. SALT provides a plug-in
framework as a common interface for defining and implementing
plug-ins. Plug-in implementation is carried out through a dynamic
library that contains the actual function code. The implementation
library can be loaded dynamically during GWWS
server
start up. The functions are registered as the implementation of the
plug-in interface.
In order for the GWWS
server to load the library,
the library must be specified using the
<Plugin>/<Interface>
element in the
SALTDEPLOY
file.
The following example shows a SALTDEPLOY
file segment configuring multiple customized plug-in libraries to be loaded by the GWWS
servers.
Example 1-15 Configuring Plug-in Libraries In the SALTDEPLOY File
<Deployment ..>
...
<System>
<Certificates>
<PrivateKey>/home/user/gwws_cert.pem</PrivateKey>
<VerifyClient>true</VerifyClient>
<CertPath>/home/user/trusted_cert</CertPath>
</Certificates>
</System>
</Deployment
Note:
If the plug-in library is developed using the SALT 2.0 plug-in interface, the “id
” and “name
”attributes for the interface do not need to be specified. These values can be obtained through plug-in interfaces. For more information, see Using SALT Plug-Ins in Oracle SALT Programming with Web Services.
Parent topic: Configuring System-Level Resources