4 Configuring Oracle Business Intelligence

This chapter walks you through a step-by-step process to configure Oracle BI standard topology using the Oracle Business Intelligence 12c Configuration Assistant.

• About the Oracle Business Intelligence Configuration Assistant
  The Oracle Business Intelligence 12c Configuration Assistant is a multi-functional utility that helps you to create database schemas, specify a port range, create system components, and start the application servers in addition to configuring the BI standard topology. Oracle strongly recommends that you to use the Configuration Assistant to configure the BI domain.
• Configuration Assistant Prerequisites
  It is important to make sure that you meet the criteria listed in this topic for a smooth, error-free domain configuration by using the Configuration Assistant.
• Creating the Database Schemas
  Before you can configure an Oracle Business Intelligence domain, you must install required schemas on a certified database for use with this release of Oracle Fusion Middleware.
• Configuring the BI Domain with the Configuration Assistant
  The Oracle BI 12c Configuration Assistant is a .sh (UNIX) or .cmd (Windows) file. Start the Configuration Assistant by starting the config executable from the bi/bin directory inside the Oracle home. Follow the procedure in this topic to complete the configuration step-by-step.
• Starting the BI Instance
  Verifying the configuration involves starting the servers (Admin Servers, and the Managed Servers) and the newly configured BI instance.

4.1 About the Oracle Business Intelligence Configuration Assistant

The Oracle Business Intelligence 12c Configuration Assistant is a multi-functional utility that helps you to create database schemas, specify a port range, create system components, and start the application servers in addition to configuring the BI standard topology. Oracle strongly recommends that you to use the Configuration Assistant to configure the BI domain.

4.2 Configuration Assistant Prerequisites

It is important to make sure that you meet the criteria listed in this topic for a smooth, error-free domain configuration by using the Configuration Assistant.

To verify whether the required conditions are met, see that:

• You have correctly installed the BI product binary files.
• You have the latest supported JDK installed on your system.
• You have access to any one of the Oracle certified databases: Oracle, DB2, SQLServer, or RAC.
• (Optional) You have connection details of existing RCU schema prefix (STB) and you have already created BIPLATFORM, IAU, OPSS, MDS, STB, and WLS schemas in a single session.

  Note:

  You can, alternatively, generate a schema prefix (STB) and create the BIPLATFORM, IAU, OPSS, MDS, STB, and WLS schemas while you run the BI Configuration Assistant, provided you have the DBA credentials.

Note:

The database schemas are required to store internal housekeeping information. These schemas are different from any data sources which you plan to analyze by using Oracle BI.

4.3 Creating the Database Schemas

Before you can configure an Oracle Business Intelligence domain, you must install required schemas on a certified database for use with this release of Oracle Fusion Middleware.

• Installing and Configuring a Certified Database
  Before you create the database schemas, you must install and configure a certified database, and verify that the database is up and running.
• Starting the Repository Creation Utility
  Start the Repository Creation Utility (RCU) after you verify that a certified JDK is installed on your system.
• Navigating the Repository Creation Utility Screens to Create Schemas
  Enter required information in the RCU screens to create the database schemas.

4.3.1 Installing and Configuring a Certified Database

Before you create the database schemas, you must install and configure a certified database, and verify that the database is up and running.

See Understanding Database Requirements for an Oracle Fusion Middleware Installation.

4.3.2 Starting the Repository Creation Utility

Start the Repository Creation Utility (RCU) after you verify that a certified JDK is installed on your system.

To start the RCU:

1. Verify that a certified JDK already exists on your system by running java -version from the command line. For 12c (12.2.1.1), the certified JDK is 1.8.0_77 and later.

   See Understanding JDK Requirements for an Oracle Fusion Middleware Installation.

2. Ensure that the JAVA_HOME environment variable is set to the location of the certified JDK. For example:
   • (UNIX) setenv JAVA_HOME/home/Oracle/Java/jdk1.8.0_77
   • (Windows) set JAVA_HOME=C:\home\Oracle\Java\jdk1.8.0_77
3. Go to the /oracle_common/bin directory:
   • (UNIX) ORACLE_HOME/oracle_common/bin
   • (Windows) ORACLE_HOME\oracle_common\bin
4. Enter the following command:
   • (UNIX) ./rcu
   • (Windows) rcu.bat

4.3.3 Navigating the Repository Creation Utility Screens to Create Schemas

Enter required information in the RCU screens to create the database schemas.

• Introducing the RCU
  The Welcome screen is the first screen that appears when you start the RCU.
• Selecting a Method of Schema Creation
  Use the Create Repository screen to select a method to create and load component schemas into the database.
• Providing Database Connection Details
  On the Database Connection Details screen, provide the database connection details for the RCU to connect to your database.
• Specifying a Custom Prefix and Selecting Schemas for Oracle B2B and Healthcare
  Specify a custom prefix and database schema to automatically select Common Infrastructure Services and dependent schemas.
• Specifying Schema Passwords
  On the Schema Passwords screen, specify how you want to set the schema passwords on your database, then enter and confirm your passwords.
• Specifying Custom Variables
  Specify the custom variables for the SOA Infrastructure schema.
• Completing Schema Creation
  Navigate through the remaining RCU screens to complete schema creation.

4.3.3.1 Introducing the RCU

The Welcome screen is the first screen that appears when you start the RCU.

Click Next.

4.3.3.2 Selecting a Method of Schema Creation

Use the Create Repository screen to select a method to create and load component schemas into the database.

On the Create Repository screen:

• If you have the necessary permissions and privileges to perform DBA activities on your database, select System Load and Product Load. This procedure assumes that you have SYSDBA privileges.

• If you do not have the necessary permissions or privileges to perform DBA activities in the database, you must select Prepare Scripts for System Load on this screen. This option generates a SQL script that you can give to your database administrator. See About System Load and Product Load in Creating Schemas with the Repository Creation Utility.

• If the DBA has already run the SQL script for System Load, select Perform Product Load.

4.3.3.3 Providing Database Connection Details

On the Database Connection Details screen, provide the database connection details for the RCU to connect to your database.

Note:

If you are unsure of the service name for your database, you can obtain it from the SERVICE_NAMES parameter in the initialization parameter file of the database. If the initialization parameter file does not contain the SERVICE_NAMES parameter, then the service name is the same as the global database name, which is specified in the DB_NAME and DB_DOMAIN parameters.

For example:

• Database Type: Oracle Database
• Name: examplehost.exampledomain.com
• Port: 1521
• Service Name: Orcl.exampledomain.com
• User Name: sys
• Password: ******
• Role: SYSDBA

Click Next to proceed, then click OK in the dialog window that confirms a successful database connection.

4.3.3.4 Specifying a Custom Prefix and Selecting Schemas for Oracle B2B and Healthcare

Specify a custom prefix and database schema to automatically select Common Infrastructure Services and dependent schemas.

Select Create new prefix, specify a custom prefix, then select the SOA Suite schema. This action automatically selects the following schemas as dependencies:

• User Messaging Service

• Metadata Services

• Oracle Platform Security Services

• Audit Services

• Audit Services Append

• Audit Services Viewer

• WebLogic Services

The schema Common Infrastructure Services is also automatically created; this schema is grayed out; you cannot select or deselect it. This schema enables you to retrieve information from RCU during domain configuration. See Understanding the Service Table Schema in Creating Schemas with the Repository Creation Utility.

The custom prefix is used to logically group these schemas together for use in this domain only; you must create a unique set of schemas for each domain as schema sharing across domains is not supported.

Tip:

For more information about custom prefixes, see Understanding Custom Prefixes in Creating Schemas with the Repository Creation Utility.

For more information about how to organize your schemas in a multi-domain environment, see Planning Your Schema Creation in Creating Schemas with the Repository Creation Utility.

Description of the illustration GUID-D79E8701-656A-47FB-8DA2-BC332AD23F46-default.gif

Tip:

You must make a note of the custom prefix you choose to enter here; you will need this later on during the domain creation process.

Click Next to proceed, then click OK on the dialog window confirming that prerequisite checking for schema creation was successful.

4.3.3.5 Specifying Schema Passwords

On the Schema Passwords screen, specify how you want to set the schema passwords on your database, then enter and confirm your passwords.

Tip:

You must make a note of the passwords you set on this screen; you will need them later on during the domain creation process.

4.3.3.6 Specifying Custom Variables

Specify the custom variables for the SOA Infrastructure schema.

For the Oracle SOA Suite standard installation topology, set values for the Database Profile (SMALL) and Healthcare Integration (NO for B2B installation, YES for Healthcare Integration for Oracle SOA Suite).

See About the Custom Variables Required for the SOA Suite Schemas

Description of the illustration GUID-5E9A59FA-5C01-4EF6-9F50-F7E9D12F7F0A-default.gif

Tip:

For more information about the options on this screen, see Custom Variables in Creating Schemas with the Repository Creation Utility.

:

4.3.3.7 Completing Schema Creation

Navigate through the remaining RCU screens to complete schema creation.

On the Map Tablespaces screen, the Encrypt Tablespace check box appears only if you enabled Transparent Data Encryption (TDE) in the database (Oracle or Oracle EBR) when you start the RCU. Select the Encrypt Tablespace check box if you want to encrypt all new tablespaces that the RCU creates.

When you reach the Completion Summary screen, click Close to dismiss the RCU.

4.4 Configuring the BI Domain with the Configuration Assistant

The Oracle BI 12c Configuration Assistant is a .sh (UNIX) or .cmd (Windows) file. Start the Configuration Assistant by starting the config executable from the bi/bin directory inside the Oracle home. Follow the procedure in this topic to complete the configuration step-by-step.

Note:

Oracle recommends that you use the Oracle BI 12c Configuration Assistant to configure your 12c system.

To configure the BI standard topology:

Important:

If you are extending the WebLogic domain with Oracle Business Intelligence by using the Configuration Assistant, make sure that the Administration Server for the domain is named AdminServer. Other names for the Administration Server are not supported.

Note:

Context-sensitive help is available on each screen as you navigate through the Configuration Assistant. Click Help to seek more information about the elements on that screen.

1. Change to the following directory:
   (UNIX) ORACLE_HOME/bi/bin
   (Windows) ORACLE_HOME\bi\bin
2. Start the Configuration Assistant by entering the following command:
   (UNIX) ./config.sh
   (Windows) config.cmd
3. Select the components to install and click Next.

   Note:

   To ensure that a consistent set of suites are deployed, the Configuration Assistant automatically adjusts your selection.
   • Essbase: Includes components such as Essbase Server, Cube Deployment Server, and Analytic Provider Services.
   • Business Intelligence Enterprise Edition: Includes components such as Presentation Services, Visual Analyzer, BI Composer, web services, proactive intelligence (Delivers and Actions), Web Services for SOA (WS4SOA), and Mobile Application Designer.
   • Business Intelligence Publisher: Includes Oracle BI Publisher.
4. On the Prerequisite Checks screen, after the prerequisite checks conclude with no errors, click Next.
   If any of the prerequisite checks fail, then a short error message appears at the bottom of the screen. Fix the error and click Rerun to try again. To ignore the error or warning messages and continue with the installation, click Skip, although this approach is not recommended.

   Note:

   The configuration might not function normally if you continue without resolving the issue that caused an error or warning message during the prerequisite checks.
5. On the Define New Domain screen, specify the following, and click Next:

   Table 4-1 Field-name descriptions for the Define New Domain screen

   Field	Description
   Domains Directory	Specify the path where you want to set up the domain directory.
   Domain Name	Specify domain.
   Username	Specify a username for the System Administrator. Note: This user is created in the embedded LDAP and is granted WebLogic Administrator permissions.
   Password	Specify a password for the System Administrator.
   Confirm Password	Confirm the password by reentering it.

6. On the Database Schema screen, either create a new schema or use an existing schema by clicking the appropriate option.
   If you select to create a new schema, the Configuration Assistant creates a schema for you. Specify the following and click Next.

   Table 4-2 Field-name descriptions for the Database Schema screen

   Field	Description
   Schema prefix	Specify a unique schema prefix.
   Schema password	Specify a password for your schema.
   Confirm password	Confirm the password by reentering it.
   Database type	Select the database that you are using from the list of values. Supported databases are: Oracle Database Microsoft SQL Server IBM DB2
   Username	Enter the privileged username to create the schema.
   Password	Enter the password for the above username.
   Simple connect string	The connect string that you specify varies depending on the type of database you are using. (Oracle Database) host:port/service or host:port:SID or TNS connect string (Microsoft SQL Server) //host:port;DatabaseName=dbname (IBM DB2) //host:port;DatabaseName=dbname

   If you select to use an existing schema, you must create STB, BIPLATFORM, IAU, MDS, OPSS, and WLS schemas using the RCU. Specify the following and click Next.

   Note:

   If you are using Oracle Database version 12.2.0.1 or higher, you must create a pluggable database within a container database to create repository schemas. You cannot create schemas within a container database without using a pluggable database.
7. On the Port Range screen, specify the port range and click Next.

   Note:

   The default, allocated port range is from 9500 to 9999, both inclusive. You can keep the default values or specify different values within this range.
8. On the Initial Application screen, select one of the following options as per your requirement, and click Next:
   • Oracle sample application (SampleAppLite).
   • Your own existing BI Application from export bundle (.jar).

     Note:

     This option is applicable if you are migrating from Oracle BI 11g to 12c. See Migrating from Oracle BI 11g to 12c in Oracle Business Intelligence Migration Guide.
   • Clean Slate (no predefined application).
9. On the Summary screen, verify the values that you specified on each screen.
   Click Save to generate a response file used for silent installation (optional).
   Click Configure.
   The configuration process starts and the Configuration Progress screen is displayed.
10. After the configuration concludes without any errors, click Next to go to the Configuration Complete screen.
11. On the Configuration Complete screen, review the configuration summary.
    Click Save to save the information displayed on this screen in a file.
    Click Finish to close the Configuration Assistant.
    The BI Application opens in the browser. Use the login credentials that you specified while configuring to sign in to the BI application home.

You have configured the standard BI topology. The Configuration Assistant automatically starts the newly configured BI instance after successful completion. However, if you want to restart a domain that has been shut down manually, see Starting the BI Instance.

4.5 Starting the BI Instance

Verifying the configuration involves starting the servers (Admin Servers, and the Managed Servers) and the newly configured BI instance.

To start the BI instance including the components such as the Node Manager, Admin Servers, and the Managed Servers:

1. Change directory to the following:
   On UNIX operating system:
   DOMAIN_HOME/bitools/bin
   On Windows operating system:
   DOMAIN_HOME\bitools\bin
2. To start the servers, enter the following command:
   On UNIX operating system:
   start.sh
   On Windows operating system:
   start.cmd

   Note:

   When prompted to enter the password, specify the Node Manager password that you entered while configuring the BI domain.