This chapter explains that depending on your specific deployment, you must perform the following Oracle BI Scheduler configuration tasks:
Section 2.1, "Configuring a Database for the Oracle BI Scheduler"
Section 2.2, "Configuring Oracle BI Scheduler Instances in a Clustered Environment"
Keep the following points in mind:
If you are not using Oracle BI Scheduler, then you do not need the information in this chapter.
Configuration that is required for running agents (as opposed to running jobs in general) is described in "Configuring and managing Agents" in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
If you are migrating an Oracle Business Intelligence environment to a new system, then ensure that you also migrate the Oracle Business Intelligence Server repository file and the Oracle BI Scheduler tables. For information, see "Moving Between Environments" in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition. The Oracle BI Scheduler tables are required for agents.
You can use Fusion Middleware Control to configure common settings that are used by agents with Oracle BI Scheduler.
Note:
You can automatically populate or repopulate credential information from the Weblogic data source. If connectivity details change (for example, password expiry or database failure), then you update the Weblogic BI platform data source and run DH/bitools/bin/sync_midtier_db.sh.The file DH/config/fmwconfig/biconfig/OBISCH/schedulerconfig.xml contains the DSN name, and the credentials are stored in oracle.bi.system map datasource.biplatform key (visible in EM).
The following procedure describes how to configure the back-end database and tables:
For SQL Server databases, the Data Source Name (DSN) that is used in the Fusion Middleware Control Scheduler configuration must match an existing ODBC DSN for the SQL Server S_NQ_SCHED database.
If you do not have a System DSN entry, then create a new one as described in the following procedure.
To configure the SQL Server database DSN entry:
From the Windows Start menu, select Settings, then Control Panel, then Administrative Tools, then Data Sources (ODBC).
Start the ODBC Data Source Administrator.
Select the System DSN tab, and click Add.
Select the driver SQL Server, and click Finish.
In the Create a New Data Source to SQL Server wizard, do the following:
Enter a name and description for the data source.
Select the SQL Server from the Server list, and click Next.
For server verification of the login ID authenticity, select the appropriate authentication for the S_NQ_SCHED SQL Server database schema. Click Next.
Select the Change the default database to field and select the S_NQ_SCHED database from the list. Click Next.
Update any language or log file settings if appropriate, and click Finish.
To verify the connection settings, click the Test Data Source button, and click OK.
Click OK to exit ODBC Data Source Administrator.
In a clustered environment you can have zero, one, or two scheduler instances. Configure zero if you do not require support for scheduled jobs or agents. Configure one if you do not require high availability.
A two-node cluster environment always consists of two instances of the scheduler which are automatically configured as primary and secondary nodes.