OBI Presentation Server

The machine name and port where the Oracle BI Presentation Services is running.
The server name must be specified and optionally can be followed by a colon and port number. If you do not specify a port number, Oracle BI Scheduler uses the default Web server port number 9710. For example, if the Web Server runs on machine1 and port 8900, the value for this field is machine1:8900.
If you are using clustered SAW servers, specify the machine names as a comma-separated list. For example: localhost:9710, saw1:9710, oracleBI:9710.

Log Directory

iBots can create log files if exceptional error conditions occur. iBot Log Directory specifies the directory where these files are saved. The directory must be accessible to the Oracle BI Scheduler server. In Windows, the default installation runs the service as a system account, which prevents Oracle BI Scheduler from writing to or reading from network directories. If you put script files on network shares, or your scripts access network shares, then Oracle BI Scheduler must be run as a network user.

Purge files older than (days)

Specifies the number of days after which old iBot logs are deleted automatically. To prevent old logs from being deleted automatically, set the value to 0 (zero). The default value is delete after seven days.

Number of Global Tries

A Web or mail server that has too many people logged on may reject new connections, including connections from Oracle BI Scheduler. To cope with such overload, an iBot retries the connection. This field sets the maximum number of tries to get global information about what to deliver and to whom before the iBot gives up.

Minimum Global Sleep Seconds

The minimum number of seconds that the iBot randomly sleeps after its connection is refused before it attempts to reconnect to the server to get global information about what to deliver and to whom.

Maximum Global Sleep Seconds

The maximum number of seconds that the iBot randomly sleeps after its connection is refused before it attempts to reconnect to the server to get global information about what to deliver and to whom.

Number of Request Tries

After an iBot has received the global information, it issues a series of unique requests to the server for each user. Specifies the number of times Oracle BI Scheduler attempts to connect to the server to issue these requests.

Minimum Request Sleep Seconds

The minimum number of seconds that the iBot randomly sleeps after its connection is refused before it attempts to reconnect to the server to issue requests.

Maximum Request Sleep Seconds

The maximum number of seconds that the iBot randomly sleeps after its connection is refused before it attempts to reconnect to the server to issue requests.

Number of Delivery Tries

After a unique request has executed, the iBot tries to deliver the results to specified devices. Specifies the number of times Oracle BI Scheduler attempts to connect to the server to deliver the results.

Minimum Delivery Sleep Seconds

The minimum number of seconds that the iBot randomly sleeps after its connection is refused before it attempts to reconnect to the server to deliver results.

Maximum Delivery Sleep Seconds

The maximum number of seconds that the iBot randomly sleeps after its connection is refused before it attempts to reconnect to the server to deliver results.

Max Rows Times Columns

When iBots are chained, this value governs the size of filters passed between iBots. When you pass a filter to another iBot in a chain, Oracle BI Scheduler creates a union of the result sets for the Conditional Report for each personalized recipient. This report can grow very large in some cases (1000 users with 100 unique rows each with ten columns per report = 1,000,000 column values in the filter). The Oracle BI servers may not be able to handle such a large filter, so this field specifies the maximum number of rows*columns in the filter. The default is 10,000.

Debug Enabled

Select this to have Oracle BI Scheduler generate a log file for each iBot. This log file has useful logging messages when trying to diagnose a problem. This log file is stored in $OracleBI\server\Log\iBots (where $OracleBI is the location in which the Oracle BI software is installed).

Keep Error Log Files

Select this check box to generate an error log file for each iBot. This log file is created only when an iBot execution encounters errors and contains only error messages. The file is stored in $OracleBI\server\Log\iBots (where $OracleBI is the location in which the Oracle BI software is installed).