Table 3. Scheduler Tab Fields
|
|
Bulk Fetch Buffer Size (bytes) |
This parameter is for use in the database gateways. It specifies the maximum size in bytes of a bulk fetch page for retrieving data from a data source. The default value is 33,792 bytes. |
|
The type of call the connection to the database makes. The call you choose from the pull-down list determines the application programmer interface (API) used to access the data source. The types of call interfaces in the list varies depending on the database type selected. |
|
Identifies the data source name (DSN) of the data source to use for the connection. For example, if the DSN of the Scheduler back-end database is ORCL8_Scheduler, you would enter ORCL8_Scheduler in this field. The DSN must contain valid logon information for a data source. If the information is invalid, the database logon fails. |
|
The database type of the Scheduler back-end database. Choose a type from the drop-down list. |
|
This field refers to a path where user-created job scripts (not iBots) should be stored. In the Job Manager, if a filename is entered in the Script field when adding or modifying a job, Siebel Analytics Scheduler examines the contents of this directory for the specified file. However, if a full path is given in the Script field, this directory is not examined. By default, this field is set to $(SiebelAnalytics)\Scripts\Common where $(SiebelAnalytics) is the location in which the Siebel Analytics software is installed. |
|
The maximum number of database connections the Scheduler can open concurrently. When this limit is reached, the connection request waits until a connection becomes available. The default value is 5. Specify a value of 1 or greater. |
Maximum Execution Threads |
This field specifies the maximum number of threads that are used in Siebel Analytics Scheduler's thread pool. |
Minimum Execution Threads |
Siebel Analytics Scheduler is a multithreaded application. It uses a thread pool. This field specifies the minimum number of threads in this pool. |
nQS (Siebel) Administrator Name |
Because Siebel Analytics Scheduler runs jobs on Siebel Analytics Server and Siebel Analytics Web on behalf of a user without storing that user's password, the server allows the Scheduler and the Web to impersonate users. To allow these applications to impersonate users, specify a user with administrator's privileges in this field. The user specified must be a Repository Administrator with the ability to impersonate other users, and have basic access to the Web catalog (to access the shared folder). |
nQS (Siebel) Administrator Password/Confirm Password |
These fields contain the password for the Siebel administrator with impersonation privileges. The password is encrypted in the registry. You can change it by using the Job Manager (Windows) or schconfig.exe (UNIX). |
Password/Confirm Password |
These fields contain the password to use to log on to the data source. For security, the password is encrypted in the registry. |
Pause When Service Starts |
This is a flag that specifies that no jobs should execute when Siebel Analytics Scheduler starts. While it is paused, users can add, modify, and remove jobs. However, no jobs execute. The Siebel administrator can use this field for maintenance purposes, such as shutting down the Scheduler, then setting this value, and then restarting the Scheduler to conduct maintenance. Choose Service Management > Continue Scheduling in the Job Manager to continue with regular execution. |
|
Depending on the back-end database, deleting rows from a table may be expensive, while updates are almost always streamlined. Siebel Analytics Scheduler does not actually issue SQL DELETE statements when jobs or instances are removed. Instead, it updates the tables and flags the affected rows as deleted. After every X minutes (where X is defined as the value of this field), the actual SQL DELETE statements are issued. The default value is every 60 minutes. |
Purge Old instances after X days |
Specifies the number of days after which old job instances are deleted from the back-end database automatically. The default value is to delete after seven days. To prevent old job instances from being deleted automatically, set the value to 0 (zero). |
|
The Scheduler's back-end database does not actually store the job scripts. This field refers to the path where Scheduler-created job scripts are stored. In the Job Manager, when adding or modifying a job, if a script is manually entered in the Script field, the Scheduler creates a file in the path defined by this field. The file has an SCS extension. In general, you should not add or remove scripts from this directory. By default, this field is set to $(SiebelAnalytics)\Scripts\Scheduler where $(SiebelAnalytics) is the location in which the Siebel Analytics software is installed. |
|
This is a path that specifies where temporary files are stored during the execution of Siebel Analytics Scheduler. |
|
The timeout 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. The default value is 60. Specify a value of 1 or greater. |
|
The user name the Scheduler uses to log on to the data source. The user name must have read and write permissions to the back-end database. To properly set up Scheduler, the user name must be the same as the table owner for databases like DB2 that require fully qualified table names (for example, SIEBEL.S_NQ_JOB). |