Oracle® Content Database Administrator's Guide for Oracle WebCenter Suite 10g (10.1.3.2) Part Number B32191-01 |
|
|
View PDF |
An Oracle Content DB service comprises a Java runtime environment for the protocol servers and agents that it supports. A service also manages connections to the database through JDBC. There are three default service configuration objects you can use to create new services on nodes:
SmallServiceConfiguration
MediumServiceConfiguration
LargeServiceConfiguration
The differences among the three configuration templates are in the number of connections and sessions supported.
This appendix lists the service configuration properties and their default values.
Note: Do not use spaces to separate alternate values of a property. Instead, use a comma as a delimiter. |
Table D-1 IFS.SERVICE.*
Properties
Property | Description and Usage Notes | Default | Required? |
---|---|---|---|
|
The cache size, in ACLs, at which the service ACL cache performs an immediate purge of data that has not been recently used. Must be greater than |
600 - Small 2400 - Medium 6000 - Large |
No |
|
The cache size, in ACLs, at which the service ACL cache schedules a low-priority purge of data that has not been recently used. |
500 - Small 2000 - Medium 5000 - Large |
No |
|
The target cache size, in ACLs, on completion of a purge cycle. Must be less than |
400 - Small 1600 - Medium 4000 - Large |
No |
|
The absolute maximum size of the service's ACL cache, in ACLs. The service ACL cache holds resolved access levels of ACLs. |
750 - Small 3000 - Medium 7500 - Large |
No |
|
The cache size, in ACLs, at which the service ACL cache schedules a high-priority purge of data that has not been recently used. Must be greater than |
550 - Small 2200 - Medium 5500 - Large |
No |
|
Whether, in performing Cleartext authentication, passwords are case-sensitive. |
false |
No |
|
Number of seconds between checks for orphan sessions. (Active sessions generate heartbeats. An orphan session is one that no longer generates session heartbeats. When the service detects an orphan session, it disconnects the session and releases the resources for the session.) Default is 60 seconds between checks. Set to 0 to disable the checking. |
60 |
No |
|
The absolute maximum number of database connections in the read-only connection pool. Must be greater than or equal to |
20 - Small 40 - Medium 60 - Large |
No |
|
The maximum period, in milliseconds, that a service will postpone a connection allocation request when there are no unallocated connections, if the current size of the read-only connection pool is equal to its maximum size. If a database connection does not become available within this period, the allocation request will fail and an exception will occur. |
10000 |
No |
|
The initial number of database connections in the read-only connection pool. |
2 - Small 4 - Medium 6 - Large |
No |
|
The cache size, in number of statements, at which the statement cache schedules a purge. |
150 |
No |
|
The target cache size, in number of statements, for the statement cache upon completion of a purge cycle. Must be less than |
120 |
No |
|
The target maximum number of database connections in the read-only connection pool. Must be greater than or equal to |
10 - Small 20 - Medium 30 - Large |
No |
|
The maximum period, in milliseconds, that the service will postpone a connection allocation request when there are no unallocated connections, if the current size of the read-only connection pool is greater than or equal to its target size, but less than the maximum size. If a database connection does not become available within this period, a new connection will be created. |
1000 |
No |
|
The absolute maximum number of database connections in the writeable connection pool. Must be greater than or equal to |
20 - Small 40 - Medium 60 - Large |
No |
|
The maximum period, in milliseconds, that a service will postpone a connection allocation request when there are no unallocated connections, if the current size of the writeable connection pool is equal to its maximum size. If a database connection does not become available within this period, the allocation request will fail and an exception will occur. |
10000 |
No |
|
The initial number of database connections in the writeable connection pool. |
2 - Small 4 - Medium 6 - Large |
No |
|
The cache size, in number of statements, at which the statement cache schedules a purge. |
200 |
No |
|
The target cache size, in number of statements, for the statement cache upon completion of a purge cycle. Must be less than |
160 |
No |
|
The target maximum number of database connections in the writeable connection pool. Must be greater than or equal to |
10 - Small 20 - Medium 30 - Large |
No |
|
The maximum period, in milliseconds, that the service will postpone a connection allocation request when there are no unallocated connections, if the current size of the writeable connection pool is greater than or equal to its target size, but less than the maximum size. If a database connection does not become available within this period, a new connection will be created. |
1000 |
No |
|
The configuration of credential managers for the service. These properties are set during installation. Do not change these values. |
Not applicable |
Not applicable |
|
The absolute maximum size of the service's data cache, in LibraryObjects. The service data cache holds the attribute values of recently used LibraryObjects. |
7500 - Small 30000 - Medium 75000 - Large |
No |
|
The cache size, in LibraryObjects, at which the service data cache schedules a low-priority purge of data that has not been recently used. |
5000 - Small 20000 - Medium 50000 - Large |
No |
|
The cache size, in LibraryObjects, at which the service data cache schedules a high-priority purge of data that has not been recently used. Must be greater than |
5500 - Small 22000 - Medium 55000 - Large |
No |
|
The cache size, in LibraryObjects, at which the service data cache performs an immediate purge of data that has not been recently used. Must be greater than |
6000 - Small 24000 - Medium 60000 - Large |
No |
|
The target cache size, in LibraryObjects, on completion of a purge cycle. Must be less than |
4000 - Small 16000 - Medium 40000 - Large |
No |
|
This property is not used. |
Not applicable |
No |
|
This property is not used. |
Not applicable |
No |
|
This property is not used. |
Not applicable |
Not applicable |
|
Number of result set rows prefetched. If set to null or 0, prefetches 10 rows. Do not change. |
0 |
No |
Specifies the JDBC driver type. Do not change. |
oci8 |
No |
|
|
Sends JDBC debugging information to the standard output. Do not change. |
false |
No |
The maximum number of nested transactions by the session. |
100 |
No |
|
|
The time period (in seconds) for a session to wait when attempting to lock database resources when performing an update operation. If unable to lock the required database resources within the time period indicated, the update operation will time out, and an exception will occur. |
10 |
No |
|
Maximum number of Library sessions the service can support concurrently. Default of 0 means unlimited. This value determines how many Library sessions are available for outstanding user requests, across all users. It does not limit the number of users who can log in. |
40 - Small 70 - Medium 200 - Large |
No |
|
Number of seconds after which a session that no longer generates a heartbeat becomes an orphan. Set to 0 to disable orphan session timeout. |
600 |
No |
|
Seconds between checks for incoming events from other services. Set to 0 to disable interservice event polling. |
2 |
No |
|
Seconds between service heartbeats. The Service Watchdog Agent detects services that cease to have a heartbeat, and cleans up information associated with the failed service in the Oracle Content DB repository. Set to 0 to disable the heartbeat. |
60 |
No |
|
The event poller used by a session to generate the heartbeat of the session. Must be either |
|
No |
|
The period, in milliseconds, of the session's heartbeat. In addition to indicating the health of the session to the service, the heartbeat allows an idle session to process events generated by other sessions or services. |
2500 |
No |
|
The period, in seconds, after which a search API call is terminated, even if incomplete. If a search times out in this manner, it is terminated and an exception occurs. The session performing the search remains valid. A value of 0 disables search timeouts. |
60 |
No |
|
The target maximum size of the bean-side session object cache, in LibraryObjects. The bean-side session object cache holds instances of |
750 |
No |
|
Whether the session caches the resolution of folder paths. |
true |
No |
|
The absolute maximum size of the folder path cache of the session, in cached folder paths. |
150 |
No |
|
The cache size, in folder paths, at which the session's folder path cache schedules a low-priority purge of data that has not been recently used. |
100 |
No |
|
The cache size, in folder paths, at which the folder path cache of the session schedules a high-priority purge of data that has not been recently used. Must be greater than |
110 |
No |
|
The target cache size, in folder paths, on completion of a purge cycle. Must be less than |
80 |
No |
|
The absolute maximum size of the server-side session object cache, in LibraryObjects. The server-side session object cache holds instances of |
750 |
No |
|
The cache size, in LibraryObjects, at which the session data caches schedule a low-priority purge of data that has not been recently used. |
500 |
No |
|
The cache size, in LibraryObjects, at which the session data caches schedule a high-priority purge of data that has not been recently used. Must be greater than |
550 |
No |
|
The cache size, in LibraryObjects, at which the session data caches perform an immediate purge of data that has not been recently used. Must be greater than |
600 |
No |
|
The target cache size, in LibraryObjects, on completion of a purge cycle. Must be less than |
400 |
No |
|
Number of seconds after which certain Oracle Content DB API calls are terminated, even if incomplete. If an operation times out in this manner, it is terminated, its transaction is terminated, and an exception occurs. The session performing the operation remains valid. Set to 0 to disable session operation timeout. |
300 |
No |
|
The number of trace logger channels. Oracle reserves channels 0 to |
50 |
No |
|
The destination of trace data generated by a service. Must be |
|
No |
|
The destination of trace data generated by a server-side session. Must be |
|
No |
|
The destination of trace data generated by a bean-side session. Must be |
|
No |
|
Tracing verbosity for trace channel n. Refer to the Javadoc for class |
None |
No |
|
Default tracing verbosity for all trace channels. See |
None |
No |
|
Maximum length of time (seconds) that outgoing events are buffered before sending. Set to 0 to disable outgoing event buffer. |
2 |
No |