How to Configure Verity Isolation in Content Server 7.x and 10.1.3.3.x (10gR3)
(Doc ID 445339.1)
Last updated on MAY 21, 2021
Applies to:Oracle WebCenter Content - Version 7.0.0 and later
Information in this document applies to any platform.
Content Server 7.01, 7.1, 7.1.1, 10.1.3.3.0, 10.1.3.3.1, 10.1.3.3.2 for Windows, UNIX (Solaris, AIX) and Linux
Internal Only currency check Nov 5, 2012
How can you configure Verity isolation on Stellent Content Server (SCS)?
In a standard installation, when a Verity search is performed, the code runs in the same Java process as the Content Server. This design has the advantage that a single interface is used to manage the Content Server and Verity searches.
In some situations, because Verity and Content Server are run together, resources limits may be exceeded and problems can occur. For example, UNIX systems may encounter file descriptor limitations that result in the error “too many open files”. In these cases, Verity isolation can be set so the SCS Java process invokes the SearchVdk4ApiProcess.exe and passes the search command to this executable.
When isolating Verity searches, spawning a new process to do a search may have a slight impact on performance. The configuration setting for SearchExeTimeout (default 40) can be used to set the number of seconds to wait until the executable should be timed out.
In pre-7x versions of Content Server, a custom component was used to isolate the Verity process. With 7.01, 7.1 and 7.1.1 of the Content Server, Verity isolation is no longer a component, but a config variable.
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