Professional Documents
Culture Documents
This topic area is part of the Roadmap for Configuring Oracle BI Infrastructure Components on page 27.
After the Oracle Business Intelligence installer is finished, there are a number of additional tasks you
must complete in order to properly configure Oracle Business Intelligence Scheduler server
components.
You must configure the Oracle BI Scheduler before running Oracle Business Intelligence. Otherwise,
the Scheduler service fails to start and the Delivers component does not function.
TIP: If you are migrating an Oracle Business Intelligence environment to a new system, make sure
that you also migrate the Oracle Business Intelligence Server repository file and the Scheduler
tables. The Scheduler tables are required for Oracle Delivers iBots.
■ “Creating Oracle BI Scheduler Database and Tables for Specific Databases” on page 116
■ “Specifying the Scheduler Host and Port in Presentation Services Configuration File” on page 124
■ “Configuring Oracle BI Presentation Services to Identify the Credential Store” on page 128
The Scheduler service starts only if the back-end database satisfies the following conditions:
■ Configured. There is a one-to-one relationship between the back-end database and Oracle BI
Scheduler. Do not configure multiple Oracle BI Scheduler applications to use a single back-end
database.
■ Operational. For information about the specific back-end databases supported by Oracle BI
Scheduler, see System Requirements and Supported Platforms on OTN.
■ Mixed Authentication Mode. For example, if the database is SQL Server, then the security
mode should be set to allow both SQL Server and Windows Authentication for logon.
NOTE: Do not use operating system authentication for the back-end database login. If you do, the
Scheduler service may not start.
Table 17 gives brief descriptions of the database tables used by Oracle BI Scheduler. The scripts are
located in OracleBI_HOME\server\Schema.
If usage tracking is enabled in NQSConfig.INI, then the Oracle BI Server generates Usage Tracking
data files. A sample JavaScript is provided, which extracts information from the Usage Tracking files
and loads them to a table in the relational database. The S_NQ_ACCT table stores all the information
regarding Accounting Data. (For information about usage tracking, see Oracle Business Intelligence
Server Administration Guide.)
S_NQ_JOB This table is used by Scheduler to store information about scheduled jobs.
S_NQ_ERR_MSG This table stores error messages for Scheduler job instances that do not
complete successfully.
S_NQ_JOB_PARAM This table holds information about Scheduler job parameters for
scheduled jobs.
NOTE: If you are not using Scheduler, you do not need the information in this topic.
Depending upon your specific deployment, you may need to refer to one or more of the following
Oracle BI Scheduler configuration topics:
■ “Creating Oracle BI Scheduler Database and Tables for Specific Databases” on page 116
For all other Scheduler Server configuration tasks involving the Job Manager or scripting, see the
Oracle Business Intelligence Scheduler Guide, located under the Windows directory
OracleBI_HOME\server\Document.
You can either use an existing database or create a new database in which to store the tables.
The following procedure shows how to create a generic database and tables.
3 Create the Scheduler tables by executing SAJOBS.xxx.sql (where xxx is the database type).
Use the appropriate procedure for your back-end database, as shown in “Creating Oracle BI
Scheduler Database and Tables for Specific Databases” on page 116.
The following procedures describe how to create a database and tables for specific relational
databases:
See the topic “Creating a Scheduler Database and Tables for Oracle Database Server” on page 117
See the topic “Creating a Scheduler Database and Tables for SQL Server” on page 117.
Use the following procedure to create a Scheduler database and tables for Oracle.
■ Create a new database named S_NQ_SCHED, and create a user named S_NQ_SCHED.
3 Using the Oracle Net configuration tool, create an Oracle Service to the current S_NQ_SCHED
database with this user ID and password.
4 Using the SQL*Plus Worksheet or the SQL*Plus tool, open the file SAJOBS.Oracle.sql and execute
it to create Oracle Business Intelligence Scheduler tables.
5 Open the file SAACCT.Oracle.sql and execute it to create the Accounting table.
Use the following procedure to create a Scheduler database and tables for Microsoft SQL Server.
Make sure that you have enough free disk space to accommodate Oracle Business Intelligence
Scheduler Tables (a minimum of 500 MB for Oracle Business Intelligence applications).
2 Using S_NQ_SCHED as the current database, use SQL Query Analyzer to open the file
SAJOBS.MSSQL.sql and execute it to create the Oracle Business Intelligence Scheduler tables.
3 Open the file SAACCT.MSSQL.sql and execute it to create the Accounting table.
The following procedures describe how to configure the back-end database and tables:
See the topic “Configuring Oracle Server Databases for the Oracle BI Scheduler” on page 118
See the topic “Configuring SQL Server Databases for the Oracle BI Scheduler” on page 118.
3 In the Connection Pool section, enter the Oracle database service alias for the Data Source Name.
Select the appropriate Database Type from the drop down list (for example, Oracle 10g R1).
4 Enter the username and password for the user S_NQ_SCHED created in “Creating a Scheduler
Database and Tables for Oracle Database Server” on page 117.
The Call Interface is updated automatically according to the Database Type chosen.
If you do not have a System DSN entry, create a new one as shown in the following procedure.
5 In the wizard Create a New Data Source to SQL Server, do the following:
b Select your SQL Server from the drop down Server list, and then click Next.
c For server verification of the login ID authenticity, select the appropriate authentication for the
S_NQ_SCHED SQL Server database that was created in “Creating a Scheduler Database and
Tables for SQL Server” on page 117. Click Next.
6 Select the tick box Change the default database to and select the S_NQ_SCHED database from
the drop down list. Click Next.
7 Update any language or log file settings if appropriate, and then click Finish.
8 To verify your connection settings, click the Test Data Source button, and then click OK.
NOTE: For organizations that use Oracle Application Server, Oracle recommends that you use Oracle
Application Server Control to modify configuration files. For organizations that use other application
servers, Oracle recommends that you use JConsole. For more information, see the topic “Updating
Configuration Settings Using Oracle Application Server Control or JConsole” on page 89.
The following procedure shows how to change Oracle BI Scheduler table names. For this procedure,
a new tag, DB Column Names, has been created as an example.
3 For each of the entries under the tag DB Column Names, add the parameter and string values
shown in the following table. The values created in the data string become the values used for
Oracle BI Scheduler table names.
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.
If you do not want to create a new administrator for Scheduler, you can set the Scheduler
administrator credentials to those of the Oracle BI user, Administrator, that exists in the repository.
NOTE: The Scheduler Administrator is referred to in the following topics as the SchedulerAdmin.
For more information on the Administrator user in the repository, and on creating users and granting
Group membership, see the Oracle Business Intelligence Server Administration Guide.
Regardless of the operating system, configuring the Scheduler database uses the settings shown in
Table 18:
Connection Pool Database Type From the drop down list, select the appropriate
Database Type for the S_NQ_SCHED database.
The Call Interface is automatically updated
according to the Database Type chosen.
See the Oracle Business Intelligence Scheduler Guide for further details on configuring functionality
for the Oracle BI Scheduler component, including how to configure the Scheduler for SMTP mail
delivery.
3 In the Scheduler > General tab of the Scheduler Configuration window, set the fields as shown
in Table 18 on page 122.
4 In the Scheduler > Database tab, in the Connection Pool box, set the fields as shown in Table 18
on page 122.
. sa-init.sh
schconfig
2 From the Delivers Configuration choices that appear, select 1 – Configure Scheduler.
5 Select 0 to quit and save changes to the Database configuration when prompted.
8 Select 0 to quit and save changes to the General configuration when prompted.
As shown by the “Diagram of Oracle BI Infrastructure Deployment” on page 28, the Oracle BI Scheduler
and Oracle BI Presentation Services servers work together. This topic covers their configuration.
When the Oracle Business Intelligence Scheduler and the Oracle BI Presentation Services are not
installed on the same machine, you must point the Oracle BI Presentation Services machine to the
Scheduler machine address. See the topic “Specifying the Scheduler Host and Port in Presentation
Services Configuration File” on page 124.
You must provide the Oracle BI Presentation Services machine with the credentials to use in order
to establish a connection with the Scheduler. See the following topics:
■ “Configuring Oracle BI Presentation Services to Identify the Credential Store” on page 128
The Scheduler host name and port are specified in the instanceconfig.xml file for Oracle BI
Presentation Services. The Presentation Services instanceconfig.xml file is located in the directory
OracleBIData_HOME\web\config on Windows, and in OracleBIData_HOME/web/config on Linux.
■ When Oracle BI Scheduler and Oracle BI Presentation Services components are installed together
on the same machine, the installer sets the instanceconfig.xml setting to the local host and
default Scheduler port of 9705.
If Oracle BI Scheduler and Oracle BI Presentation Services are installed on the same machine
and Scheduler uses the default port 9705, proceed to topic “Adding Scheduler Administrator
Credentials to Oracle BI Presentation Services Credential Store” on page 126.