Vetting WebSphere shared libraries

A WebSphere® shared library must be created for WebSphere to find the user exits loaded by Vetting. The shared library must be associated with the Vetting_EJBEAR application by configuring the shared library reference of the application.

Note: To avoid .jar file dependency problems, use a different WebSphere Application Server shared library path for each component.

Table 1. Vetting engine WebSphere shared library properties
Property	Value or example	Description
Scope	Stand-alone server installation: Server Cluster installation: Node	Specifies the level at which the resource definition is visible. The resource needs to be configured at the server or node scope because the shared library references directories on the computer. For a stand-alone server installation, the shared library is to be configured at the server scope. For example, `Server=server1`. For a cluster installation, the shared library is to be configured at the node scope. For example, `Node=izhNode`.
Name	cvp_engine	The name of the shared library.
Description	Shared library for the Vetting engine	Describes the shared library.
Classpath	`install_directory`/shared/v3213/pfs/Vetting/engine/application/lib	Specify the class path used to locate the .jar files that are needed by this component. For example, the .jar files for user exits. Note: The value is an example. It shows how to create a unique class path directory for this component.
Native library path	`install_directory`/shared/v3213/pfs/Vetting/engine/application/bin	Specify the class path used to locate any platform-specific library files that are needed by the application or shared library. If any user written code requires more binary files, such as .dll or .so object files, the directory that contains those files must be specified in this property. Note: The value is an example. It shows how to create a unique native library path directory for this component.