threadpoolworker.properties

This configuration sets the threadpoolworker configuration for global and individual threadpoolworkers. As with submitters there are global defaults as well as individual threadpoolworker configurations.

Note:

Some settings in this file are shared with the submitbatch.properties file but these settings apply to the threadpoolworker JVM's rather than submitter JVM's.

Note:

This section is the default set of configuration parameters. Adding Custom JMX Information to Jobs can be done through Implementing Custom Templates.

com.oracle.ouaf.batch.scriptDir - Base Scripts Directory for Infrastructure Job

Parameter	com.oracle.ouaf.batch.scriptDir
Description	The base directory in which the scripts have to be placed for the generic infrastructure job to execute them.
Ordinality	Optional
Valid Values	Directory path.
Source	Defaulted by configureEnv.
Applicability	Background Processing
Example:	com.oracle.ouaf.batch.scriptDir=$SPLEBASE/scripts/generic/batch/exposed/$OWNER $OWNER would be the owner flag of the batch control thereby allowing restrictions on which scripts might be executed. Additional owners can be provided access by creating symbolic links in those owners’ directories .

com.ouaf.batch.disableAutoFlush – Auto Flush Batch L2 Cache

Parameter	com.ouaf.batch.disableAutoFlush
Description	Disables the auto flushing of batch L2 cache. If this value is set to true, the L2 cache auto flush will be disabled.
Ordinality	Mandatory
Valid Values	[true|false]
Source	Generated by template. Use Configuring Batch Using Bedit to implement a different value.
Applicability	Business Application Server
Example:	com.ouaf.batch.disableAutoFlush=true

com.ouaf.batch.flushIntervalInSeconds – Batch L2 Cache Auto Flush Interval

Parameter	com.ouaf.batch.flushIntervalInSeconds
Description	Sets the time interval between batch L2 cache auto flushes. The time interval should be specified in seconds.
Ordinality	Optional
Valid Values	Value in seconds. Default is 60.
Source	Generated by template. Use Configuring Batch Using Bedit to implement a different value.
Applicability	Business Application Server
Example	com.ouaf.batch.flushIntervalInSeconds=90

com.ouaf.batch.jvmoptions - Threadpool JVM Options

Parameter	com.ouaf.batch.jvmoptions
Description	Custom JVM Options for threadpool. Note: This setting can be overridden using the -z option on the threadpoolworker.sh - Manage Threadpools command line.
Ordinality	Mandatory
Valid Values	Valid JVM Options for the Java version used
Source	Maintained by product templates. Use Configuring Batch Using Bedit to implement a different value.
Applicability	Background Processing
Example	com.ouaf.batch.jvmoptions=-Xms1024k -Xmx2048k -XX:MaxPermSize=512m

com.splwg.grid.executionMode - Threadpool Mode of Execution

Parameter	com.splwg.grid.executionMode
Description	Execution Mode used by this threadpool.
Ordinality	Mandatory
Valid Values	[CLUSTERED]
Source	Maintained by product templates.
Applicability	Background Processing
Example	com.splwg.grid.executionMode=CLUSTERED

com.splwg.grid.distThreadPool.threads - Threadpool Thread Limit

Parameter	com.splwg.grid.distThreadPool.threads
Description	Maximum number of threads for a particular threadpool. The format of the setting is:  com.splwg.grid.distThreadPool.threads.<poolname>=<limit> where: <poolname> is the Name of the threadpool <limit> is the thread limit supported by each instance of the threadpool. Note: This setting can be overridden using the -p option on the threadpoolworker.sh - Manage Threadpools command line.
Ordinality	Mandatory
Valid Values	Threadpool names and limit must be valid.
Source	Maintained by product templates. Use Configuring Batch Using Beditto implement a different value.
Applicability	Background Processing
Example	com.splwg.grid.distThreadPool.threads.DEFAULT=5

com.splwg.batch.scheduler.daemon - Scheduler Daemon

Parameter	com.splwg.batch.scheduler.daemon
Description	Configures whether the threadpool should execute the online scheduler daemon. The online scheduler daemon checks that the Batch Submission transaction and initiates execution of pending batch jobs. Note: This setting can be overridden using the -d option on the threadpoolworker.sh - Manage Threadpools command line. Note: This setting should only be set to true in non-production environment where online submission is enabled. Note: In any non-production environment that uses online submission; one threadpoool should have this setting enabled. Typically, this is the DEFAULT threadpool but can be any other threadpool.
Ordinality	Mandatory
Valid Values	[true|false]
Source	Maintained by product templates. Use Configuring Batch Using Bedit to implement a different value.
Applicability	Background Processing
Example	com.splwg.batch.scheduler.daemon=false

jmx.remote.x.access.file - JMX Access Control

Parameter	jmx.remote.x.access.file
Description	Sets relative location of JMX access control file holding the valid user. Refer to JMX Security for more details.
Ordinality	Mandatory
Valid Values	Relative location of file from $SPLEBASE. Defaults to scripts/ouaf.jmx.access.file.
Source	Value inherited from templates. Use Implementing Custom Templates to set this value to the desired location and file, if desired.
Applicability	Web Application Server, Business Application Server.
Example	jmx.remote.x.access.file=scripts/ouaf.jmx.access.file

jmx.remote.x.password.file - JMX Password Control

Parameter	jmx.remote.x.password.file
Description	Sets relative location of JMX password file holding the valid passwords for jmx.remote.x.access.file. Refer to JMX Security for more details.
Ordinality	Mandatory
Valid Values	Relative location of file from $SPLEBASE. Defaults to scripts/ouaf.jmx.password.file.
Source	Value inherited from templates. Use Implementing Custom Templates to set this value to the desired location and file, if desired.
Applicability	Web Application Server, Business Application Server.
Example:	jmx.remote.x.password.file=scripts/ouaf.jmx.password.file

oracle.ouaf.jmx.remote.maxPortsToTry - Ports to Attempt to Connect to

Parameter	oracle.ouaf.jmx.remote.maxPortsToTry
Description	Number of ports to try starting from either oracle.ouaf.jmx.remote.startPort - Override Batch JMX Port or spl.runtime.management.rmi.port - JMX Port. If oracle.ouaf.jmx.remote.startPort - Override Batch JMX Port is not specified, the property spl.runtime.management.rmi.port - JMX Port is used that as the starting port. If neither property is defined or the maximum number of ports to try has been reached, an exception will be thrown that will prevent the system from starting.
Ordinality	Optional
Valid Values	Number. Default: 200
Source	Set by BATCH_RMI_PORT - RMI Port for Batch. Use Configuring Batch Using Bedit to implement a different value.
Applicability	Background Processing
Example:	oracle.ouaf.jmx.remote.maxPortsToTry=100

oracle.ouaf.jmx.remote.startPort - Override Batch JMX Port

Parameter	oracle.ouaf.jmx.remote.startPort
Description	Alternative Port number allocated for Batch JMX Reference. This value is typically the same as spl.runtime.management.rmi.port - JMX Port. But may be set to the Coherence JMX port if Coherence based JMX is used on a different port.
Ordinality	Optional
Valid Values	Valid JMX Port
Source	Set by BATCH_RMI_PORT - RMI Port for Batch. Use Configuring Batch Using Bedit to implement a different value.
Applicability	Background Processing
Example:	oracle.ouaf.jmx.remote.startPort=6510

ouaf.batch.onlineLogDir - Online Line Batch Log Directory

Parameter	ouaf.batch.onlineLogDir
Description	Sets the location of output from online batch submission and batch scheduler integration. If this property is set, batch logs will be accessible through the Batch Run Tree (application UI). Otherwise, the batch logs download link in the application will be disabled.
Ordinality	Optional
Valid Values	Valid location. Defaults to: $SPLOUTPUT
Source	Value inherited from BATCH_ONLINE_LOG_DIR from ENVIRON.INI.
Applicability	Background Processing
Example:	ouaf.batch.onlineLogDir=/tmp

ouaf.batch.onlineLogDir.retain – Retain Online Line Batch Log Files

Parameter	ouaf.batch.onlineLogDir.retain
Description	Sets the total number of log files that are to be stored for each batch code and thread number. The log files for the particular batch code and thread number will be deleted except for the latest number of logs specified.
Ordinality	Optional
Valid Values	Number.
Source	Generated by template. Use Configuring Batch Using Bedit to implement a different value.
Applicability	Background Processing
Example:	ouaf.batch.onlineLogDir.retain=3 The above example will keep the last three logs and delete the rest.

spl.runtime.batch.disableDeferredKeyInserts - Deferred Key Inserts

Parameter	spl.runtime.batch.disableDeferredKeyInserts
Description	Whether the deferring of key insert in batches should be disabled or not. Enables (false) or disables (true) deferred Key Inserts. The default is to use deferred inserts. However, if an aggressive key insert is desired in batches, a value of true should be used. Note: This setting is used by particular base batch jobs. Refer to the online documentation for individual batch jobs for more information.
Ordinality	Mandatory
Valid Values	[true|false]
Source	Generated by template. Use Configuring Batch Using Bedit to implement a different value.
Applicability	Background Processing
Example:	spl.runtime.batch.disableDeferredKeyInserts=false

spl.runtime.batch.L2CacheMode - Threadpoolworker L2 Cache Control

Parameter	spl.runtime.batch.L2CacheMode
Description	Defines the 2nd-level cache mode for threads in threadpool. Valid values are READ_ONLY (default), READ_WRITE or OFF. READ_ONLY is for performance as it loads the configuration entities into the 2nd-level (JVM-level) cache and accesses them from there only. In READ_ONLY mode, the cached entities may not be updated. READ_WRITE also loads them into the L2 cache, but they can be updated. The drawback is that an update of a cached entity hits both the database and cache as it gets updated in both places. In OFF mode the 2nd-level cache is completely disabled. Some jobs, for example LDAP import (F1-LDAP), need to update some of these entities (for example, User), so it requires the L2 cache to be either OFF or READ_WRITE. The choice between OFF and READ_WRITE depends on requirement; the effect is the same. Note: This setting can be overridden using the -l2 option on the threadpoolworker.sh - Manage Threadpools command line.
Ordinality	Mandatory
Valid Values	[READ_ONLY|READ_WRITE|OFF]
Source	Maintained by product templates for threadpoolworker. Use Configuring Batch Using Bedit to implement a different value.
Applicability	Background Processing
Example:	spl.runtime.batch.L2CacheMode=READ_ONLY

spl.runtime.management.connector.url.default - Batch JMX URL

Parameter	spl.runtime.management.connector.url.default
Description	JMX URL for Batch JMX interface. Note: This URL is generated and should not be altered.
Ordinality	Optional
Valid Values	Valid JMX URL
Source	Generated by template
Applicability	Background Processing
Example:	spl.runtime.management.connector.url.default= service:jmx:rmi:///jndi/rmi://{host}:{port} /oracle/ouaf/batchConnector

spl.runtime.management.rmi.port - Batch JMX Port

Parameter	spl.runtime.management.rmi.port
Description	Port number allocated for Batch JMX Reference. Note: This setting can be overridden using the -i option on the threadpoolworker.sh - Manage Threadpools command line.
Ordinality	Optional
Valid Values	Valid JMX Port
Source	Set by BATCH_RMI_PORT - RMI Port for Batch. Use Configuring Batch Using Bedit to implement a different value.
Applicability	Background Processing
Example:	spl.runtime.management.rmi.port=1001

spl.runtime.options.isDevelopmentMode - Development Mode

Parameter	spl.runtime.options.isDevelopmentMode
Description	Enables or disables Development Mode for the product. Development mode disables and enables key features within the architecture to allow the Oracle Utilities SDK to be used optimally. The following settings are affected by this parameter: Caching is disabled at all layers of the architecture. This can be renabled manually. Screen Preloading is disabled. This can be renabled manually. Compression is disabled at all layers of the architecture. This can be renabled manually. The product is set to expanded mode to allow developers access to individual JEE objects rather than using WAR/EAR files.  It is highly recommended that this setting should be set to false in production environments. This setting is only set to true where the Oracle Utilities SDK is used directly.
Ordinality	Mandatory
Valid Values	[true|false]
Source	Derived from WEB_ISDEVELOPMENT parameter from ENVIRON.INI.
Applicability	Web Application Server, Business Application Server, Inbound Web Services.
Example:	spl.runtime.options.isDevelopmentMode=false

tangosol.coherence.distributed.localstorage - DistributedCache Storage

Parameter	tangosol.coherence.distributed.localstorage
Description	Specifies whether this member of the DistributedCache service enables local storage. Note: This setting is used by the Oracle Coherence DistributedCache Service.
Ordinality	Optional
Valid Values	[true|false]
Source	Generated by template. Use Configuring Batch Using Bedit to implement a different value.
Applicability	Background Processing
Example:	tangosol.coherence.localport.adjust=true

tangosol.coherence.distributed.threads - Internal Cache Threads

Parameter	tangosol.coherence.distributed.threads
Description	Specifies the number of daemon threads used by the distributed cache service. Note: This setting is used by the Oracle Coherence DistributedCache Service.
Ordinality	Optional
Valid Values	Valid thread numbers. Default: 0
Source	Generated by template. Use Configuring Batch Using Bedit to implement a different value.
Applicability	Background Processing
Example:	tangosol.coherence.distributed.threads=4

tangosol.coherence.invocation.threads - Internal Invocation Threads

Parameter	tangosol.coherence.invocation.threads
Description	Specifies the number of daemon threads to be used by the invocation service. If zero, all relevant tasks are performed on the service thread. Note: This setting is used by the Oracle Coherence InvocationService.
Ordinality	Optional
Valid Values	Valid thread numbers. Default:0
Source	Generated by template (wka only). Use Configuring Batch Using Bedit to implement a different value.
Applicability	Background Processing
Example:	tangosol.coherence.invocation.threads=4

tangosol.coherence.localhost - Unicast Host Address

Parameter	tangosol.coherence.localhost
Description	Host name for local host for Unicast address. Note: This setting applies to unicast or well known address implementations. Note: This setting is used by the Oracle Coherence unicast-listener.
Ordinality	Optional
Valid Values	Valid host name defined in hosts file and/or DNS.
Source	Generated by template (wka only). Use Configuring Batch Using Bedit to implement a different value.
Applicability	Background Processing
Example:	tangosol.coherence.localhost=myserver.example.com

tangosol.coherence.localport - Unicast Port

Parameter	tangosol.coherence.localport
Description	Port number for local host for Unicast address. Note: This setting applies to unicast or well known address implementations. Note: This setting is used by the Oracle Coherence unicast-listener.
Ordinality	Optional
Valid Values	Valid port number.
Source	Generated by template (wka only). Use Configuring Batch Using Bedit to implement a different value.
Applicability	Background Processing
Example:	tangosol.coherence.localport=6570

tangosol.coherence.localport.adjust - Unicast Port Adjustment

Parameter	tangosol.coherence.localport.adjust
Description	Specifies whether the unicast port is automatically incremented if the specified port cannot be bound to because it is in use. Note: This setting applies to unicast or well known address implementations. Note: This setting is used by the Oracle Coherence unicast-listener.
Ordinality	Optional
Valid Values	[true|false]
Source	Generated by template (wka only). Use Configuring Batch Using Bedit to implement a different value.
Applicability	Background Processing
Example:	tangosol.coherence.localport.adjust=true

tangosol.coherence.role - Threadpoolworker Role

Parameter	tangosol.coherence.role
Description	This contains the name of the member role. This name allows an application to organize members into specialized roles, such as cache servers and cache clients. The name is also useful for displaying management information (for example, JMX) and interpreting log entries. Note: This setting is used by the Oracle Coherence member-identity.
Ordinality	Optional
Valid Values	Role Name
Source	Generated by template. Use Configuring Batch Using Bedit to implement a different value.
Applicability	Background Processing
Example:	tangosol.coherence.role=OUAF_Base_TPW