This chapter walks you through a step-by-step process to configure Oracle BI standard topology using the Oracle Business Intelligence 12c 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.
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:
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.
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.
Before you create the database schemas, you must install and configure a certified database, and verify that the database is up and running.
Start the Repository Creation Utility (RCU) after you verify that a certified JDK is installed on your system.
To start the RCU:
java -versionfrom the command line. For 12c (184.108.40.206), the certified JDK is 1.8.0_77 and later.
JAVA_HOMEenvironment variable is set to the location of the certified JDK. For example:
Enter required information in the RCU screens to create the database schemas.
The Welcome screen is the first screen that appears when you start the RCU.
Use the Create Repository screen to select a method to create and load component schemas into the database.
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.
On the Database Connection Details screen, provide the database connection details for the RCU to connect to your database.
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
Click Next to proceed, then click OK in the dialog window that confirms a successful database connection.
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
Oracle Platform Security Services
Audit Services Append
Audit Services Viewer
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.
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.
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.
On the Schema Passwords screen, specify how you want to set the schema passwords on your database, then enter and confirm your passwords.
You must make a note of the passwords you set on this screen; you will need them later on during the domain creation process.
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).
For more information about the options on this screen, see Custom Variables in Creating Schemas with the Repository Creation Utility.
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.
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.
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.
Note:To ensure that a consistent set of suites are deployed, the Configuration Assistant automatically adjusts your selection.
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.
Table 4-1 Field-name descriptions for the Define New Domain screen
|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.|
Table 4-2 Field-name descriptions for the Database Schema screen
|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:
|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.
Note:If you are using Oracle Database version 220.127.116.11 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.
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.
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.
Verifying the configuration involves starting the servers (Admin Servers, and the Managed Servers) and the newly configured BI instance.
Note:When prompted to enter the password, specify the Node Manager password that you entered while configuring the BI domain.