Requirements for the Write-Back Template

Configuring and Managing Agents 19-5 19.3.3 What Additional Scheduler Configuration Settings Affect Agents? You can change the following additional Oracle BI Scheduler configuration settings that affect agents: ■ Section 19.3.3.1, General Scheduler Configuration Settings That Affect Agents ■ Section 19.3.3.2, E-Mail Scheduler Configuration Settings That Affect Agents ■ Section 19.3.3.3, Agent Scheduler Configuration Settings

19.3.3.1 General Scheduler Configuration Settings That Affect Agents

General configuration settings include access to, and configuration of, the Scheduler back-end database, some behavior settings, and settings for secure sockets and clustering configuration. Table 19–2 describes the settings. Table 19–2 General Scheduler Configuration Settings That Affect Agents Element Description Default Value PoolTimeout Specifies the amount of time in minutes that a connection to the data source remains open after an operation completes. During this time, new operations use this connection rather than open a new one, up to the number specified for Maximum Connections. The time is reset after each completed connection request. Specify a value of 1 or greater. 60 NumDbConnecti ons Specifies the maximum number of database connections that Oracle BI Scheduler can open concurrently. Specify a value of 1 or greater. When this limit is reached, the connection request waits until a connection becomes available. 5 TABLE_JOBS Specifies the name of a database table used to store information about scheduled jobs. Note : For information about modifying the database table names, see Changing Oracle BI Scheduler Table Names in Oracle Fusion Middleware Scheduling Jobs Guide for Oracle Business Intelligence Enterprise Edition and see Oracle Business Intelligence Applications Installation and Configuration Guide. S_NQ_JOB TABLE_ INSTANCES Specifies the name of a database table used to store information about job instances. S_NQ_ INSTANCE TABLE_PARAMS Specifies the name of a database table used to store information about job parameters. S_NQ_JOB_ PARAM TABLE_ ERRMSGS Specifies the name of a database table used to store information about job instances that do not complete successfully. S_NQ_ERR_ MSG SchedulerScriptP ath Refers to the path where Oracle BI Scheduler-created job scripts are stored. In general, you should not add or remove scripts from this directory. By default, this field is set to ORACLE_ INSTANCE\bifoundation\OracleBISchedulerComponent\ coreapplication_obischn\scripts\scheduler, for example D:\OBI11g\instances\instance1\bifoundation\OracleBISc hedulerComponent\coreapplication_ obisch1\scripts\scheduler. scripts\sche duler 19-6 System Administrators Guide for Oracle Business Intelligence Enterprise Edition DefaultScriptPath Specifies the path where user-created job scripts not agents are stored. If a file name is entered in the Script field when adding or modifying a job, then Oracle BI Scheduler examines the contents of this directory for the specified file. However, if a full path is given in the Script field, then this directory is not examined. By default, this field is set to ORACLE_ INSTANCE\bifoundation\OracleBISchedulerComponent\ coreapplication_obischn\scripts\scheduler\common, for example D:\OBI11g\instances\instance1\bifoundation\OracleBISc hedulerComponent\coreapplication_ obisch1\scripts\scheduler\common. scripts\sche duler\comm on TempPath Specifies the path where temporary files are stored during Oracle BI Scheduler execution. NA BulkFetchBufferSi ze Used in the database gateways. Specifies the maximum size in bytes of a bulk fetch page for retrieving data from a data source. 33,792 bytes. LogAllSqlStmts Occasionally you might set up the Scheduler to point to a database using a generic protocol like ODBC. This is usually done when the Target Type is not specified. When this happens, and a SQL statement fails, you must be able to determine which statement failed. Turning this setting on places the SQL statements in the Scheduler log file. Do not set this to TRUE in production mode as the overhead for this is quite high. false ServerPortNumbe r Specifies the port number for the server. Defaults to the Oracle BI Scheduler port number. The port number set for the Scheduler. PurgeInstDays Specifies the number of days after which old job instances are deleted from the back-end database automatically. To prevent old job instances from being deleted automatically, set the value to 0 zero. 7 days PurgeIntervalMin utes Specifies the number of minutes in which Oracle BI Scheduler updates the tables and flags the affected rows as deleted. Note : Oracle BI Scheduler does not actually issue SQL DELETE statements when jobs or instances are removed, instead rows are flagged for deletion. After every X minutes where X is defined as the value of this field, the actual SQL DELETE statements are issued. 60 minutes MinExecThreads Specifies the minimum number of multiple threads in the Oracle BI Scheduler thread pool that executes jobs at run time. 1 MaxExecThreads Specifies the maximum number of multiple threads in the Oracle BI Scheduler thread pool that executes jobs at run time. 100 PauseOnStartup Specifies that no jobs should execute when Oracle BI Scheduler starts. While Oracle BI Scheduler pauses, users can add, modify, and remove jobs. However, no jobs execute. From the Service Management menu, select Continue Scheduling to continue with regular execution. false Table 19–2 Cont. General Scheduler Configuration Settings That Affect Agents Element Description Default Value