This chapter explains that depending on your specific deployment, you must perform the following Oracle BI Scheduler configuration tasks:
Section 2.1, "Creating an Oracle BI Scheduler Database and Tables Using RCU"
Section 2.2, "Configuring a Database for the Oracle BI Scheduler"
Section 2.3, "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 use the Repository Creation Utility (RCU) to create Oracle BI Scheduler database schemas and tables. The RCU is a graphical tool that enables you to create and manage Oracle Fusion Middleware database schemas in your database.
The RCU enables you to use either an existing database schema or to create a database schema in which to store the Oracle BI Scheduler tables.
For information about using the RCU, see Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence.
You can use Fusion Middleware Control to configure common settings that are used by agents with Oracle BI Scheduler.
The following procedures describe how to configure the back-end database and tables:
The Data Source Name that is specified in the Fusion Middleware Control configuration must match the database service alias that was created in Section 2.1, "Creating an Oracle BI Scheduler Database and Tables Using RCU."
The following procedure configures database connection details. Before you begin this procedure, ensure that you are familiar with the information in "Using Fusion Middleware Control to Update Oracle Business Intelligence Configuration Settings" Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition
To use Fusion Middleware Control to configure a database for the Oracle BI Scheduler:
Go to the Business Intelligence Overview page, as described in "Using Fusion Middleware Control to Manage Oracle Business Intelligence System Components" Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
Display the Scheduler tab of the Deployment page.
Click Lock and Edit Configuration to enable changes to be made.
Complete the elements using the descriptions in the Help topic for the page. Click the Help button on the page to access the page-level help for the following options:
Database list
Call Interface list
The Call Interface is updated automatically according to the Database chosen.
Data Source option
For SQL Server databases, you must have a system DSN configured. For information, see Section 2.2.2, "Configuring a System DSN entry for SQL Server Databases."
Username option
Enter the user name that was created in the procedure that is described in Section 2.1, "Creating an Oracle BI Scheduler Database and Tables Using RCU."
Password option
Enter the password of the existing scheduler schema user. For information, see Section 2.1, "Creating an Oracle BI Scheduler Database and Tables Using RCU."
Confirm Password option
Password details are not checked against the database.
Click Apply, then click Activate Changes.
Return to the Business Intelligence Overview page and click Restart.
See Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition "Configuring and Managing Agents" for information about advanced configuring settings for agents.
For information on using Oracle BI Systems Management API methods to change configuration settings, see "Introducing the Oracle BI Systems Management API" Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition
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 that is used in Section 2.1, "Creating an Oracle BI Scheduler Database and Tables Using RCU."
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 that was created in Section 2.1, "Creating an Oracle BI Scheduler Database and Tables Using RCU." 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.
Use Fusion Middleware Control to configure the SQL Server database as described in Section 2.2.1, "Using Fusion Middleware Control to Configure a Database for the Oracle BI Scheduler."
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. Configure two to support high availability.
For information, see "Using Fusion Middleware Control to Configure Primary and Secondary Instances" in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
You can change the names of the tables that the Oracle BI Scheduler uses. This step is required only if the default table names are incompatible with the database setup. Custom table names are configured by adding settings to the Oracle BI Scheduler configuration files for each Scheduler instance. You must make the same changes for each Scheduler instance. Using different table names for the two Scheduler instances results in inconsistent behavior when the active Scheduler changes.
Use various elements in the instanceconfig.xml file to change these settings.
The following procedure describes how to change the Oracle BI Scheduler table names. For this procedure, a new tag, DB_Column_NamesType, has been created as an example.
When using database scripts to create the Scheduler tables, the changed table names should be included in the scripts.
Before you begin this procedure, ensure that you are familiar with the information in "Using a Text Editor to Update Oracle Business Intelligence Configuration Settings" in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
To manually change the settings for the Oracle BI Scheduler table names:
Open the Oracle BI Scheduler version of the instanceconfig.xml file for editing, as described in "Where are Configuration Files Located" in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
Create a new element named DB_Column_NamesType as shown in the following example from an instanceconfig.xml file:
<xs:complexType name="DB_Column_NamesType">
<xs:all>
<xs:element name="TABLE_JOBS" type="xs:string" default="S_NQ_JOB" minOccurs="0">
<xs:annotation>
<xs:documentation>
The name of the table used as the jobs table in the back-end DB.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="TABLE_INSTANCES" type="xs:string" default="S_NQ_INSTANCE" minOccurs="0">
<xs:annotation>
<xs:documentation>
The name of the table used as the instances table in the back-end DB.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="TABLE_PARAMS" type="xs:string" default="S_NQ_JOB_PARAM" minOccurs="0">
<xs:annotation>
<xs:documentation>
The name of the table used as the job parameters table in the back-end DB.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="TABLE_ERRMSGS" type="xs:string" default="S_NQ_ERR_MSG" minOccurs="0">
<xs:annotation>
<xs:documentation>
The name of the table used to store information about job instances that do not complete successfully in the back-end DB.
</xs:documentation>
</xs:annotation>
</xs:element>
For each of the entries under the tag DB_Column_NamesType, add the parameter and string values that are shown in Table 2-1. The values that are created in the data string become the values that are used for the Oracle BI Scheduler table names.
Table 2-1 Parameters for DB Column Names in instanceconfig.xml
| Parameter Name | Type | String Value |
|---|---|---|
|
TABLE_JOBS |
REG_SA |
S_NQ_JOB |
|
TABLE_INSTANCES |
REG_SA |
S_NQ_INSTANCE |
|
TABLE_PARAMS |
REG_SA |
S_NQ_JOB_PARAM |
|
TABLE_ERRMSGS |
REG_SA |
S_NQ_ERR_MSG |
Note:
The data types for each column should remain true to the intent of the schema. For example, if the job ID is defined as an integer type, do not change it to a varchar type. However, increasing the number of characters in a varchar column is an acceptable change.
Save your changes and close the file.
Restart Oracle Business Intelligence.