This chapter contains information on variables used when creating the BI domain, creating database schemas and configuring the BI domain.
DefaultAuthenticator
). However, for an enterprise deployment, Oracle recommends that you use a dedicated, centralized LDAP-compliant authentication provider.Parent topic: Configuring the Enterprise Deployment
As you perform the tasks in this chapter, you will be referencing the directory variables listed in this section.
The directory variables are defined in File System and Directory Variables Used in This Guide.
ORACLE_HOME
ASERVER_HOME
MSERVER_HOME
APPLICATION_HOME
JAVA_HOME
In addition, you'll be referencing the following virtual IP (VIP) addresses and host names defined in Physical and Virtual IP Addresses Required by the Enterprise Topology:
ADMINVHN
DBHOST1
DBHOST2
BIHOST1
SCAN Address for the Oracle RAC Database (DB-SCAN.example.com)
Before you being creating the initial Business Intelligence (BI) domain, be sure to review the following key concepts.
You create the initial Business Intelligence domain for an enterprise deployment, using the Oracle Fusion Middleware Infrastructure distribution. This distribution contains both the Oracle WebLogic Server software and the Oracle JRF software in one distribution.
The Oracle JRF software consists of Oracle Web Services Manager, Oracle Application Development Framework (Oracle ADF), Oracle Enterprise Manager Fusion Middleware Control, the Repository Creation Utility (RCU), and other libraries and technologies required to support the Oracle Fusion Middleware products.
For more information, see About the Oracle Fusion Middleware Infrastructure in Oracle Fusion Middleware Understanding Oracle Fusion Middleware.
Review these key characteristics of the initial BI domain. By reviewing and understanding these characteristics, you can better understand the purpose and context of the procedures used to configure the domain.
Many of these characteristics are described in more detail in Understanding a Typical Enterprise Deployment.
Table 10-1 Characteristics of the Initial BI domain
Characteristic of the Domain | More Information |
---|---|
Uses a separate virtual IP (VIP) address for the Administration Server. |
Configuration of the Administration Server and Managed Servers Domain Directories |
Uses separate domain directories for the Administration Server and the Managed Servers in the domain. |
Configuration of the Administration Server and Managed Servers Domain Directories |
Uses Per Domain Node Manager and separate Node Manager processes for the Administration Server and Managed Servers on each host. |
About the Node Manager Configuration in a Typical Enterprise Deployment |
Requires a separately installed LDAP-based authentication provider. |
Understanding OPSS and Requests to the Authentication and Authorization Stores |
Use this section to install the Oracle Fusion Middleware Infrastructure software in preparation for configuring a new domain for an enterprise deployment.
Oracle Fusion Middleware requires that a certified Java Development Kit (JDK) is installed on your system. See the following sections for more information:
To find a certified JDK, see the certification document for your release on the Oracle Fusion Middleware Supported System Configurations page.
After you identify the Oracle JDK for the current Oracle Fusion Middleware release, you can download an Oracle JDK from the following location on Oracle Technology Network:
http://www.oracle.com/technetwork/java/index.html
Be sure to navigate to the download for the Java SE JDK.
Install the JDK in the following locations:
On the shared storage device, where it will be accessible from each of the application tier host computers. Install the JDK in the /u01/oracle/products/jdk
directory.
On the local storage device for each of the Web tier host computers.
The Web tier host computers, which reside in the DMZ, do not necessarily have access to the shared storage on the application tier.
For more information about the recommended location for the JDK software, see the Understanding the Recommended Directory Structure for an Enterprise Deployment.
The following example describes how to install a recent version of JDK 1.8.0_101.
To start the installation program, perform the following steps.
When the installation program appears, you are ready to begin the installation. See Navigating the Installation Screens for a description of each installation program screen.
The installation program displays a series of screens, in the order listed in the following table.
If you need additional help with any of the installation screens, click the screen name or click the Help button on the screen.
Table 10-2 Navigating the Infrastructure Installation Screens
Screen | Description |
---|---|
On UNIX operating systems, this screen will appear if this is the first time you are installing any Oracle product on this host. Specify the location where you want to create your central inventory. Make sure that the operating system group name selected on this screen has write permissions to the central inventory location. For more information about the central inventory, see Understanding the Oracle Central Inventory in Oracle Fusion Middleware Installing Software with the Oracle Universal Installer. |
|
This screen introduces you to the product installer. |
|
Use this screen to automatically search My Oracle Support for available patches or automatically search a local directory for patches that you’ve already downloaded for your organization. |
|
Use this screen to specify the location of your Oracle home directory. For the purposes of an enterprise deployment, enter the value of the ORACLE_HOME variable listed in Table 7-2. |
|
Use this screen to select the type of installation and consequently, the products and feature sets you want to install. For this topology, select Fusion Middleware Infrastructure. Note: The topology in this document does not include server examples. Oracle strongly recommends that you do not install the examples into a production environment. |
|
This screen verifies that your system meets the minimum necessary requirements. If there are any warning or error messages, refer to the Oracle Fusion Middleware System Requirements and Specifications document on the Oracle Technology Network (OTN). |
|
If you already have an Oracle Support account, use this screen to indicate how you would like to receive security updates. If you do not have one and are sure you want to skip this step, clear the check box and verify your selection in the follow-up dialog box. |
|
Use this screen to verify the installation options you selected. If you want to save these options to a response file, click Save Response File and provide the location and name of the response file. Response files can be used later in a silent installation situation. For more information about silent or command-line installation, see Using the Oracle Universal Installer in Silent Mode in Oracle Fusion Middleware Installing Software with the Oracle Universal Installer. |
|
This screen allows you to see the progress of the installation. |
|
This screen appears when the installation is complete. Review the information on this screen, then click Finish to dismiss the installer. |
After you install the Oracle Fusion Middleware Infrastructure and create the Oracle home, you should see the directory and sub-directories listed in this topic. The contents of your installation vary based on the options you selected during the installation.
To check the directory structure:
Use this section to install the Oracle Business Intelligence software in preparation for configuring a new domain for an enterprise deployment.
Use these steps to start the BI Installer.
For more information about the actual file names for each distribution, see Identifying and Obtaining Software Distributions for an Enterprise Deployment.
When the installation program appears, you are ready to begin the installation. See Navigating the Installation Screens for a description of each installation program screen.
The installation program displays a series of screens, in the order listed in Table 10-3.
If you need additional help with any of the installation screens, click the screen name.
Table 10-3 Oracle Business Intelligence Install Screens
Screen | Description |
---|---|
On UNIX operating systems, this screen appears if this is the first time you are installing any Oracle product on this host. Specify the location where you want to create your central inventory. Make sure that the operating system group name selected on this screen has write permissions to the central inventory location. For more information about the central inventory, see Understanding the Oracle Central Inventory in Oracle Fusion Middleware Installing Software with the Oracle Universal Installer. |
|
This screen introduces you to the product installer. |
|
Use this screen to automatically search My Oracle Support for available patches or automatically search a local directory for patches that you’ve already downloaded for your organization |
|
Use this screen to specify the location of your Oracle home directory. For the purposes of an enterprise deployment, enter the value of the ORACLE_HOME variable listed in Table 7-2. |
|
Use this screen to select the type of installation and consequently, the products and feature sets you want to install. For this topology, select BI Platform Distribution with Samples. |
|
This screen verifies that your system meets the minimum necessary requirements. If there are any warning or error messages, refer to the Oracle Fusion Middleware System Requirements and Specifications document on the Oracle Technology Network (OTN). |
|
This screen appears if the both of the following statements are true:
This screen lists the patches that were found by the Auto Updates feature. Select one or more patches and click Next to apply the selected patches to the Oracle home. |
|
Use this screen to verify the installation options you selected. If you want to save these options to a response file, click Save Response File and provide the location and name of the response file. Response files can be used later in a silent installation situation. For more information about silent or command line installation, see Using the Oracle Universal Installer in Silent Mode in Oracle Fusion Middleware Installing Software with the Oracle Universal Installer. |
|
This screen allows you to see the progress of the installation. |
|
This screen appears when the installation is complete. Review the information on this screen, then click Finish to close the installer. |
After you install Oracle Business Intelligence, you should see the directory structure as shown in this topic. The contents of your installation vary based on the options you selected during the installation.
For more information about the directory structure after installation, see What are the Key Oracle Fusion Middleware Directories? in Oracle Fusion Middleware Understanding Oracle Fusion Middleware.
Before you can configure a BI domain, you must install the schemas listed in this section on a certified database for use with this release of Oracle Fusion Middleware.
Metadata Services (MDS)
Audit Services (IAU)
Audit Services Append (IAU_APPEND)
Audit Services Viewer (IAU_VIEWER)
Oracle Platform Security Services (OPSS)
User Messaging Service (UMS)
WebLogic Services (WLS)
WebLogic Runtime Services (WLS_RUNTIME)
Common Infrastructure Services (STB)
Business Intelligence Platform (BIPLATFORM)
You use the Repository Creation Utility (RCU) to create the schemas. This utility is installed in the Oracle home for each Oracle Fusion Middleware product. For more information about RCU and how the schemas are created and stored in the database, see Preparing for Schema Creation in Oracle Fusion Middleware Creating Schemas with the Repository Creation Utility.
Make sure you have installed and configured a certified database, and that the database is up and running.
For more information, see the following resources:
Preparing the Database for an Enterprise Deployment, which includes information about creating database services, using SecureFiles for Large Objects (LOBs), and other topics important in an enterprise deployment.
Understanding Database Requirements for an Oracle Fusion Middleware Installation in Planning an Installation of Oracle Fusion Middleware.
To start the Repository Creation Utility (RCU):
Follow the instructions in this section to create the schemas for the Oracle Business Intelligence domain.
Review the Welcome screen and verify the version number for RCU. Click Next to begin.
If you have the necessary permission and privileges to perform DBA activities on your database, select System Load and Product Load on the Create Repository screen. The procedure in this document assumes that you have the necessary privileges.
If you do not have the necessary permission or privileges to perform DBA activities in the database, you must select Prepare Scripts for System Load on this screen. This option generates an SQL script that you can provide to your database administrator. See Understanding System Load and Product Load in Oracle Fusion Middleware Creating Schemas with the Repository Creation Utility.
Tip:
For more information about the options on this screen, see Create Repository in Oracle Fusion Middleware Creating Schemas with the Repository Creation Utility.
On the Database Connection Details screen, provide the database connection details for RCU to connect to your database.
In the Host Name field, enter the SCAN address of the Oracle RAC Database.
Click Next to proceed, then click OK on the dialog window confirming that connection to the database was successful.
Tip:
For more information about the options on this screen, see Database Connection Details in Oracle Fusion Middleware Creating Schemas with the Repository Creation Utility.
Specify the custom prefix you want to use to identify the Oracle Fusion Middleware schemas.
The custom prefix is used to logically group these schemas together for use in this domain. For the purposes of this guide, use the prefix FMW1221
.
Tip:
Make a note of the custom prefix you choose to enter here; you need them later during the domain creation process.
Select AS Common Schemas.
When you select AS Common Schemas, all of the schemas in this section are automatically selected.
A schema called Common Infrastructure Services is also automatically created; this schema is grayed out and cannot be selected or deselected. This schema (the STB schema) enables you to retrieve information from RCU during domain configuration. For more information, see Understanding the Service Table Schema in Oracle Fusion Middleware Creating Schemas with the Repository Creation Utility.
Select Business Intelligence Platform.
Tip:
For more information about custom prefixes, see Understanding Custom Prefixes in Oracle Fusion Middleware 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 Oracle Fusion Middleware Creating Schemas with the Repository Creation Utility.
Click Next to proceed, then click OK on the dialog window confirming that prerequisite checking for schema creation was successful.
Specify how you want to set the schema passwords on your database, then specify and confirm your passwords.
Tip:
Make a note of the passwords you set on this screen; you need them later during the domain creation process.
Navigate through the remainder of the RCU screens to complete schema creation.
For the purposes of this guide, you can accept the default settings on the remaining screens, or you can customize how RCU creates and uses the required tablespaces for the Oracle Fusion Middleware schemas.
For more information about RCU and its features and concepts, see About the Repository Creation Utility in Oracle Fusion Middleware Creating Schemas with the Repository Creation Utility.
When you reach the Completion Summary screen, click Close to close the RCU.
This section provides instructions for creating a WebLogic domain using the configuration wizard.
For more information on other methods available for domain creation, see Additional Tools for Creating, Extending, and Managing WebLogic Domains in Creating WebLogic Domains Using the Configuration Wizard.
The following tasks are covered in this section.
To begin domain configuration, run the following command in the Oracle Fusion Middleware Oracle home on BIHOST1.
ORACLE_HOME/oracle_common/common/bin/config.sh
On the Configuration Type screen, select Create a new domain.
In the Domain Location field, specify the value of the ASERVER_HOME variable, as defined in File System and Directory Variables Used in This Guide.
Tip:
More information about the other options on this screen can be found in Configuration Type in Creating WebLogic Domains Using the Configuration Wizard.
On the Templates screen, make sure Create Domain Using Product Templates is selected, then select the following templates:
Oracle BIEE Suite – 12.2.1.2.0 [bi]
Selecting this template automatically selects the following dependencies:
Oracle MapViewer – 12.2.1.2.0 [oracle_common]
Oracle Enterprise Manager – 12.2.1.2.0 [em]
Oracle WSM Policy Manager – 12.2.1.2.0 [oracle_common]
Oracle JRF - 12.2.1.2.0 [oracle_common]
WebLogic Coherence Cluster Extension - 12.2.1.2.0 [wlserver]
Oracle BI Publisher Suite – 12.2.1.2.0 [bi]
Oracle BI Essbase Suite – 12.2.1.2.0 [bi]
In addition, the Basic WebLogic Server Domain – 12.2.1.2.0 [wlserver] template should already be selected and grayed out.
Tip:
More information about the options on this screen can be found in Templates in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.
On the High Availability Options screen, retain the default selections and click Next. For more information about the options on this screen, click Help.
On the Application Location screen, specify the value of the APPLICATION_HOME variable, as defined in File System and Directory Variables Used in This Guide.
Tip:
More information about the options on this screen can be found in Application Location in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.
On the Administrator Account screen, specify the user name and password for the default WebLogic Administrator account for the domain.
Make a note of the user name and password specified on this screen; you will need these credentials later to boot and connect to the domain's Administration Server.
On the Domain Mode and JDK screen:
Select Production in the Domain Mode field.
Select the Oracle Hotspot JDK in the JDK field.
Selecting Production Mode on this screen gives your environment a higher degree of security, requiring a user name and password to deploy applications and to start the Administration Server.
Tip:
More information about the options on this screen, including the differences between development mode and production mode, can be found in Domain Mode and JDK in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.
In production mode, a boot identity file can be created to bypass the need to provide a user name and password when starting the Administration Server. For more information, see Creating the boot.properties File.
Select RCU Data to activate the fields on this screen.
The RCU Data option instructs the Configuration Wizard to connect to the database and Service Table (STB) schema to automatically retrieve schema information for the schemas needed to configure the domain.
Note:
If you choose to select Manual Configuration on this screen, you will have to manually fill in the parameters for your schema on the JDBC Component Schema screen.
After selecting RCU Data, fill in the fields as shown in the following table:
Field | Description |
---|---|
DBMS/Service |
Enter the service name for the Oracle RAC database where you will install the product schemas. For example: orcl.example.com Be sure this is the common service name that is used to identify all the instances in the Oracle RAC database; do not use the host-specific service name. For more information, see Preparing the Database for an Enterprise Deployment. |
Host Name |
Enter the Single Client Access Name (SCAN) Address for the Oracle RAC database, which you entered in the Enterprise Deployment Workbook. |
Port |
Enter the port number on which the database listens. For example, |
Schema Owner Schema Password |
Enter the user name and password for connecting to the database's Service Table schema. This is the schema user name and password that was specified for the Service Table component on the Schema Passwords screen in RCU. The default user name is |
Click Get RCU Configuration when you are finished specifying the database connection information. The following output in the Connection Result Log indicates that the operation succeeded:
Connecting to the database server...OK Retrieving schema data from database server...OK Binding local schema components with retrieved data...OK Successfully Done.
Click Next if the connection to the database is successful.
Tip:
More information about the RCU Data option can be found in Understanding the Service Table Schema in Oracle Fusion Middleware Creating Schemas with the Repository Creation Utility.
More information about the other options on this screen can be found in Datasource Defaults in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard
Verify that the values on the JDBC Component Schema screen are correct for all schemas.
The schema table should be populated because you selected Get RCU Data on the previous screen. As a result, the Configuration Wizard locates the database connection values for all the schemas required for this domain.
At this point, the values are configured to connect to a single-instance database. However, for an enterprise deployment, you should use a highly available Real Application Clusters (RAC) database, as described in Preparing the Database for an Enterprise Deployment.
In addition, Oracle recommends that you use an Active GridLink datasource for each of the component schemas. For more information about the advantages of using GridLink data sources to connect to a RAC database, see Database Considerations in the Oracle Fusion Middleware High Availability Guide.
To convert the data sources to GridLink:
Select all the schemas by selecting the check box in the first header row of the schema table.
Click Convert to GridLink and click Next.
On the GridLink Oracle RAC Component Schema screen, provide the information required to connect to the RAC database and component schemas, as shown in Table 10-4.
Table 10-4 Recommended Values for Selected Fields on the GridLink Oracle RAC Component Schema Screen
Element | Description and Recommended Value |
---|---|
SCAN, Host Name, and Port |
Select the SCAN check box. In the Host Name field, enter the Single Client Access Name (SCAN) Address for the Oracle RAC database. In the Port field, enter the SCAN listening port for the database (for example, |
ONS Host and Port |
In the ONS Port field, enter the SCAN address for the Oracle RAC database. In the Port field, enter the ONS Remote port (typically, To obtain the ONS information on the GridLink with Oracle RAC Database, check the ons.config file on either nodes of the RAC machine. The ons.config file is present at the following location: |
Enable Fan |
Select the Enable Fan check box to receive and process FAN events, |
For more information about specifying the information on this screen, as well as information about how to identify the correct SCAN address, see Configuring Active GridLink Data Sources with Oracle RAC in Oracle Fusion Middleware High Availability Guide.
You can also click Help to display a brief description of each field on the screen.
Use the JDBC Component Schema Test screen to test the data source connections you have just configured.
A green check mark in the Status column indicates a successful test. If you encounter any issues, see the error message in the Connection Result Log section of the screen, fix the problem, then try to test the connection again.
Tip:
More information about the other options on this screen can be found in Test Component Schema in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard
Enter a unique user name and password for the Business Intelligence system.user
account. Note that the system.user
account is not an actual user. It is used for internal authentication between the different Business Intelligence components. You must provide a unique, random user name and password that are not used by an actual system user to log in and use BI applications with.
Enter a user name and password for the jms.queue.auth
user account. This user must be a user in the WebLogic Administrator group.
Note:
Thejms.queue.auth
user must be created with default authenticator after starting the Administration Server and before starting the Managed Server/system components.To complete domain configuration for the topology, select the following options on the Advanced Configuration screen:
Administration Server
This is required to properly configure the listen address of the Administration Server.
Node Manager
This is required to configure Node Manager.
Topology
This is required to configure the Managed Server and cluster, and also for configuring the machine and targeting the Managed Server to the machine.
File Store
This is required to configure the appropriate shared storage for JMS persistent stores.
Note:
When using the Advanced Configuration screen in the Configuration Wizard:
If any of the above options are not available on the screen, then return to the Templates screen, and be sure you selected the required templates for this topology.
Do not select the Domain Frontend Host Capture advanced configuration option. You will later configure the frontend host property for specific clusters, rather than for the domain.
On the Administration Server screen:
In the Server Name field, retain the default value - AdminServer.
In the Listen Address field, enter the virtual host name that corresponds to the VIP of the ADMINVHN that you procured in Procuring Resources for an Enterprise Deployment and enabled in Preparing the Host Computers for an Enterprise Deployment.
For more information on the reasons for using the ADMINVHN virtual host, see Reserving the Required IP Addresses for an Enterprise Deployment.
Leave the other fields at their default values.
In particular, be sure that no server groups are assigned to the Administration Server.
Select Per Domain Default Location as the Node Manager type.
Under Node Manager Credentials, specify the username and the password same as that of the admin user.
Tip:
For more information about the options on this screen, see Node Manager in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.
For more information about per domain and per host Node Manager implementations, see About the Node Manager Configuration in a Typical Enterprise Deployment.
For additional information, see Configuring Node Manager on Multiple Machines in Oracle Fusion Middleware Administering Node Manager for Oracle WebLogic Server.
On the Managed Servers screen, a new Managed Server for Oracle Business Intelligence appears in the list of servers. This server was created automatically by the Oracle BIEE Suite configuration template you selected on the Templates screen. Perform the following tasks to modify the default Oracle Business Intelligence Managed Server (bi_server1
).
Rename the default Managed Server to WLS_BI1
.
Tip:
The server name recommended here will be used throughout this document; if you choose a different name, be sure to replace it as needed.
Use the information in the following table to fill in the rest of the columns for the Oracle Business Intelligence Managed Server.
Tip:
More information about the options on the Managed Server screen can be found in Managed Servers in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.
Table 10-5 Values Required for Oracle Business Intelligence Managed Server
Server Name | Listen Address | Listen Port | Enable SSL | SSL Listen Port | Server Groups |
---|---|---|---|---|---|
WLS_BI1 |
BIHOST1 |
7003 |
No |
Disabled |
BISUITE-MAN-SVR |
In this task, you create a cluster to which you can target the Oracle BI software.
You will also set the Frontend Host property for the cluster, which ensures that, when necessary, WebLogic Server will redirect Web services callbacks and other redirects to bi.example.com
on the load balancer rather than the address in the HOST header of each request.
For more information about the bi.example.com
virtual server address, see Configuring Virtual Hosts on the Hardware Load Balancer.
On the Clusters screen, a new cluster (bi_cluster
) for Oracle Business Intelligence appears in the list of clusters. Perform the following tasks to modify the default Oracle Business Intelligence cluster:
Specify bi.example.com
in the Frontend Host field.
Specify 80
as the Frontend HTTP Port and 443
as the Frontend HTTPS port.
From the Dynamic Server Groups drop-down list, select Unspecified.
Note:
By default, server instances in a cluster communicate with one another using unicast. If you want to change your cluster communications to use multicast, refer to Considerations for Choosing Unicast or Multicast in Oracle Fusion Middleware Administering Clusters for Oracle WebLogic Server.
Tip:
More information about the options on this screen can be found in Clusters in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.
Click Next to continue.
Verify that all dynamic server options are disabled for clusters that are to remain as static clusters.
Confirm that the Dynamic Cluster, Calculated Listen Port, and Calculated Machine Names checkboxes on this screen are unchecked.
Confirm the Server Template selection is Unspecified.
Click Next.
Use the Assign Servers to Clusters screen to assign WLS_BI1
to the new cluster bi_cluster
:
In the Clusters pane, select the cluster to which you want to assign the servers; in this case, bi_cluster
.
In the Servers pane, assign WLS_BI1
to bi_cluster
by doing one of the following:
Click once on WLS_BI1
Managed Server to select it, then click on the right arrow to move it beneath the selected cluster in the Clusters pane.
Double-click on WLS_BI1
to move it beneath the selected cluster in the clusters pane.
Tip:
More information about the options on this screen can be found in Assign Servers to Clusters in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.
Use the Coherence Clusters screen to configure the Coherence cluster that is automatically added to the domain.
In the Cluster Listen Port, enter 9991
.
Note:
For Coherence licensing information, see Oracle Coherence Products in Oracle Fusion Middleware Licensing Information.
Use the Machines screen to create a new machine in the domain. A machine is required in order for the Node Manager to be able to start and stop the servers.
Select the Unix Machine tab.
Click the Add button to create the new UNIX machine.
Specify the values listed in the following table to define the Name and Node Manager Listen Address of each machine.
Note:
Do not specifylocalhost
in the Node Manager Listen Address field.Verify the port in the Node Manager Listen Port field.
The port number 5556
, shown in this example, may be referenced by other examples in the documentation. Replace this port number with your own port number as needed.
Table 10-6 Values to Use When Creating UNIX Machines
Name | Node Manager Listen Address | Node Manager Listen Port |
---|---|---|
BIHOST1 |
The value of the BIHOST1 host name variable. For example, |
Not applicable |
ADMINHOST |
Enter the value of the ADMINVHN variable. |
5556 |
Tip:
More information about the options on this screen can be found in Machines in Creating WebLogic Domains Using the Configuration Wizard.
Use the Assign Servers to Machines screen to assign the Administration Server and the Oracle BI EE Suite Managed Server to the appropriate machine.
The Assign Servers to Machines screen is similar to the Assign Managed Servers to Clusters screen. Select the target machine in the Machines column, select the Managed Server in the left column, and click the right arrow to assign the server to the appropriate machine.
Assign the servers as follows:
Assign the AdminServer to the ADMINHOST machine.
Assign the WLS_BI1 Managed Server to the BIHOST1 machine.
Tip:
More information about the options on this screen can be found in Assign Servers to Machines in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.
Click Next to proceed to the next screen.
Click Next to proceed to the next screen.
When you configure a domain using the BI configuration template, you should select the proper location of the Metadata Services (MDS) JMS File Store, especially when you are configuring an enterprise deployment.
On the JMS File Stores screen, assign the following directory for each of the BI Persistence stores:
ASERVER_HOME/bi_cluster
In this example, replace ASERVER_HOME with the actual value of the ASERVER_HOME variable, as defined in File System and Directory Variables Used in This Guide. Replace bi_cluster
with the name you assigned to the Oracle BI cluster.
The Configuration Summary screen contains the detailed configuration information for the domain you are about to create. Review the details of each item on the screen and verify that the information is correct.
You can go back to any previous screen if you need to make any changes, either by using the Back button or by selecting the screen in the navigation pane.
Domain creation will not begin until you click Create.
Tip:
More information about the options on this screen can be found in Configuration Summary in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.
The Configuration Success screen will show the following items about the domain you just configured:
Domain Location
Administration Server URL
You must make a note of both items as you will need them later; the domain location is needed to access the scripts used to start the Node Manager and Administration Server, and the URL is needed to access the Administration Server.
Click Finish to close the Configuration Wizard.
Perform the steps in this section to create the BI Cluster Controller, BI Scheduler, BI Presentation Services, and BI JavaHost system components on BIHOST1.
Note:
Replace ASERVER_HOME with the actual path to the domain directory you created on the shared storage device.
Perform the steps in this section to create a new BI Service instance.
Note:
Replace ASERVER_HOME with the actual path to the domain directory you created on the shared storage device.
Oracle Business Intelligence metadata is stored in a Singleton Data Directory (SDD). Metadata is managed in an Oracle Business Intelligence archive (BAR) file containing information about the Presentation Catalog, the metadata repository, and security authentication.
Perform the following steps to set up a shared directory for the Singleton Data Directory:
Note:
The path to the Singleton Data Directory (SDD) is defined in theASERVER_HOME
/config/fmwconfig/bienv/core/bi-environment.xml
file.Essbase components installed using the Oracle Business Intelligence installer cannot use Native Essbase or Hyperion Shared Services (HSS) security.
However, when you install Essbase with Oracle Business Intelligence, the Common Security Service (CSS) token-based identity assertion continues to be available and enables Oracle Business Intelligence to connect to Essbase data sources (both Essbase installed with Oracle Business Intelligence and Essbase installed with Enterprise Performance Management (EPM)) with the credentials of the end user. For this mechanism to work with an Essbase data source external to the Oracle Business Intelligence installation, you must follow the documentation. Also note that if multiple Essbase data sources are being used by Oracle Business Intelligence and there is a requirement to use this mechanism, all Essbase data sources must use the same shared secret for producing CSS tokens.
For more information, see Configuring Oracle Business Intelligence to Use Hyperion SSO Tokens when Communicating with Essbase, Hyperion Financial Management, Hyperion Planning in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
To configure Common Security Services (CSS) security for Essbase components, you must run the following after creating the initial BI domain and before starting the domain:
cd ASERVER_HOME/bitools/bin
./generate_css_secrets.sh
After configuring CSS, you must update the jps-config.xml file present at the following locations:
Primary host - BIHOST1:
/u01/oracle/config/domains/biedg_domain/config/fmwconfig/jps-config.xml
/u02/oracle/config/domains/biedg_domain/config/fmwconfig/jps-config.xml
Secondary host - BIHOST2:
/u01/oracle/config/domains/biedg_domain/config/fmwconfig/jps-config.xml
/u02/oracle/config/domains/biedg_domain/config/fmwconfig/jps-config.xml
Add the following in to the jps-config.xml file, if not present already:
<property name="odbc.dsn" value="opss_datasource"/>
The jps-config.xml file should look like this:
<propertySet name="props.db.1"> <property name="server.type" value="DB_ORACLE"/> <property name="oracle.security.jps.farm.name" value="cn=opssSecurityStore"/> <property name="datasource.jndi.name" value="jdbc/OpssDataSource"/> <property name="oracle.security.jps.db.useDSAdminMapKey" value="true"/> <property name="oracle.security.jps.ldap.root.name" value="cn=opssRoot"/> . . . <property name="odbc.dsn" value="opss_datasource"/> </propertySet>
After you update the jps-config.xml file, restart BIHOST1 and BIHOST2 using stop.sh and start.sh commands.
After the domain is created, you must perform a series of additional configuration tasks on BIHOST1. For example, you start the Node Manager and Administration Server. You then create a separate domain directory for the Managed Server. In this new and separate Managed Server directory, you start a second Node Manager instance and start the Managed Server and the Business Intelligence system components.
boot.properties
if you want to start the Administrator Server without being prompted for the Administrator Server credentials. This step is required in an enterprise deployment. The credentials you enter in this file are encrypted when you start the Administration Server.Use these steps to start the per-domain Node Manager for the ASERVER_HOME domain directory.
You must create a boot.properties
if you want to start the Administrator Server without being prompted for the Administrator Server credentials. This step is required in an enterprise deployment. The credentials you enter in this file are encrypted when you start the Administration Server.
To create a boot.properties
file for the Administration Server:
Use these steps to start the Administration Server using the Node Manager.
Before proceeding with the configuration steps, validate that the Administration Server has started successfully by making sure you have access to the Oracle WebLogic Server Administration Console and Oracle Enterprise Manager Fusion Middleware Control, which both are installed and configured on the Administration Servers.
To navigate to Fusion Middleware Control, enter the following URL, and log in with the Oracle WebLogic Server administrator credentials:
ADMINVHN:7001/em
To navigate to the Oracle WebLogic Server Administration Console, enter the following URL, and log in with the same administration credentials:
ADMINVHN:7001/console
When you initially create the domain for enterprise deployment, the domain directory resides on a shared disk. This default domain directory will be used to run the Administration Server. You can now create a copy of the domain on the local storage for both BIHOST1 and BIHOST2. The domain directory on the local (or private) storage will be used to run the Managed Servers.
Placing the MSERVER_HOME on local storage is recommended to eliminate the potential contention and overhead cause by servers writing logs to shared storage. It is also faster to load classes and jars need from the domain directory, so any temporary or cache data that Managed Servers use from the domain directory is processed quicker.
As described in Preparing the File System for an Enterprise Deployment, the path to the Administration Server domain home is represented by the ASERVER_HOME variable, and the path to the Managed Server domain home is represented by the MSERVER_HOME variable.
To create the Managed Server domain directory:
After you create the Managed Server domain directory, there are two domain home directories and two corresponding Node Manager instances on BIHOST1. You use one Node Manager to control the Administration Server, running from Administration Server domain home, and you use the other Node Manager to control the Managed Servers, running from the Managed Server domain home.
You must start the two Node Managers independently.
Note:
The Node Manager for the Managed Server's MSERVER_HOME will be reset every time the domain configuration is unpacked. TheListenAddress
will be changed to the ADMINVHN instead of the correct hostname. This needs to be changed to the correct value before starting the Node Manager service after an unpack is performed.Follow these steps to update and start the Node Manager from the Managed Server home:
For information about additional Node Manager configuration options, see Oracle Fusion Middleware Administering Node Manager for Oracle WebLogic Server.
Use Oracle Enterprise Manager Fusion Middleware Control to start the Managed Server on BIHOST1.
Fusion Middleware Control is available because you already started the Node Manager and Administration Server in a previous step:
Use Oracle Enterprise Manager Fusion Middleware Control to start the system components for Oracle Business Intelligence.
The global cache is a query cache that is shared by all Oracle BI servers participating in a cluster. It is recommended that you configure the global cache so that cache seeding and purging events can be shared by all Oracle BI servers participating in a cluster.
For more information about the global cache, see About the Global Cache in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
To set up the global cache:
After starting the components in the domain on BIHOST1, access these URLs to verify the configuration of Oracle Business Intelligence.
When you configure an Oracle Fusion Middleware domain, the domain is configured by default to use the WebLogic Server authentication provider (DefaultAuthenticator
). However, for an enterprise deployment, Oracle recommends that you use a dedicated, centralized LDAP-compliant authentication provider.
The following topics describe how to use the Oracle WebLogic Server Administration Console to create a new authentication provider for the enterprise deployment domain. This procedure assumes you have already installed and configured a supported LDAP directory, such as Oracle Unified Directory or Oracle Internet Directory.
BIAdministrators
) as a member to the policy.Updater
role in the wsm-pm
application stripe.Oracle Fusion Middleware supports a variety of LDAP authentication providers. For more information, see Identity Store Types and WebLogic Authenticators in Securing Applications with Oracle Platform Security Services.
The instructions in this guide assume you will be using one of the following providers:
Oracle Unified Directory
Oracle Internet Directory
Oracle Virtual Directory
Note:
By default, the instructions here describe how to configure the identity service instance to support querying against a single LDAP identity store with an unencrypted connection.
If the connection to your identity provider has to be secured through SSL, then additional keystone configuration is required for role management in the Enterprise Manager Fusion Middleware Control to function correctly. For additional configuration information, see Doc ID 1670789.1 at support.oracle.com.
Also, you can configure the service to support a virtualized identity store, which queries multiple LDAP identity stores, by using LibOVD.
For more information about configuring a Multi-LDAP lookup, refer to Configuring the Identity Store Service in Securing Applications with Oracle Platform Security Services.
The following topics provide important information on the purpose and characteristics of the enterprise deployment administration users and groups.
When you use a central LDAP user store, you can provision users and groups for use with multiple Oracle WebLogic Server domains. As a result, there is a possibility that one WebLogic administration user can have access to all the domains within an enterprise.
Such an approach is not recommended. Instead, it is a best practice to assign a unique distinguished name (DN) within the directory tree for the users and groups you provision for the administration of your Oracle Fusion Middleware domains.
For example, if you plan to install and configure an Oracle Business Intelligence enterprise deployment domain, then create a user called weblogic_bi
and an administration group called BIAdministrators
.
Oracle recommends that you create a separate domain connector user (for example, biLDAP
) in your LDAP directory. This user allows the domain to connect to the LDAP directory for the purposes of user authentication. It is recommended that this user be a non-administrative user.
In a typical Oracle Identity and Access Management deployment, you create this user in the systemids
container. This container is used for system users that are not normally visible to users. Placing the user into the systemids
container ensures that customers who have Oracle Identity Manager do not reconcile this user.
After you configure a central LDAP directory to be the authenticator for the enterprise domain, then you should add all new users to the new authenticator and not to the default WebLogic Server authenticator.
To add new users to the central LDAP directory, you cannot use the WebLogic Administration Console. Instead, you must use the appropriate LDAP modification tools, such as ldapbrowser or JXplorer.
When you are using multiple authenticators (a requirement for an enterprise deployment), login and authentication will work, but role retrieval will not. The role is retrieved from the first authenticator only. If you want to retrieve roles using any other authenticator, then you must enable virtualization for the domain.
To enable virtualization:
Locate and open the following configuration file with a text editor:
ASERVER_HOME/config/fmwconfig/jps-config.xml
Find the following section:
<serviceInstance name="idstore.ldap" provider="idstore.ldap.provider">
Add the following line under the serviceInstance
section or update the virtualize property as follows:
<property name="virtualize" value="true"/>
For more information about the virtualize property, see OPSS System and Configuration Properties in Securing Applications with Oracle Platform Security Services.
Each Oracle Fusion Middleware product implements its own predefined roles and groups for administration and monitoring.
As a result, as you extend the domain to add additional products, you can add these product-specific roles to the BIAdministrators
group. After they are added to the BIAdministrators
group, each product administrator user can administer the domain with the same set of privileges for performing administration tasks.
Instructions for adding additional roles to the BIAdministrators
group are provided in Common Configuration and Management Tasks for an Enterprise Deployment.
In this guide, the examples assume that you provision the following administration user and group with the DNs shown below:
Admin User DN:
cn=weblogic_bi,cn=users,dc=example,dc=com
Admin Group DN:
cn=BIAdministrators,cn=groups,dc=example,dc=com
cn=biLDAP,cn=systemids,dc=example,dc=com
This is the user you will use to connect WebLogic Managed Servers to the LDAP authentication provider. This user must have permissions to read and write to the Directory Trees:
cn=users,dc=example,dc=com cn=groups,dc=example,dc=com
Note:
When using Oracle Unified Directory, this user will need to be granted membership in the following groups to provide read and write access:
cn=orclFAUserReadPrivilegeGroup,cn=groups,dc=example,dc=com cn=orclFAUserWritePrivilegeGroup,cn=groups,dc=example,dc=com cn=orclFAGroupReadPrivilegeGroup,cn=groups,dc=example,dc=com cn=orclFAGroupWritePrivilegeGroup,cn=groups,dc=example,dc=com
Before you create a new LDAP authentication provider, back up the relevant configuration files:
ASERVER_HOME/config/config.xml ASERVER_HOME/config/fmwconfig/jps-config.xml ASERVER_HOME/config/fmwconfig/system-jazn-data.xml
In addition, back up the boot.properties
file for the Administration Server in the following directory:
ASERVER_HOME/servers/AdminServer/security
This example shows how to create a user called biLDAP
in the central LDAP directory.
To provision the user in the LDAP provider:
Create an ldif file named domain_user.ldif
with the contents shown below and then save the file:
dn: cn=biLDAP,cn=systemids,dc=example,dc=com changetype: add orclsamaccountname: biLDAP userpassword: password objectclass: top objectclass: person objectclass: organizationalPerson objectclass: inetorgperson objectclass: orcluser objectclass: orcluserV2 mail: biLDAP@example.com givenname: biLDAP sn: biLDAP cn: biLDAP uid: biLDAP
Note:
If you are using Oracle Unified Directory, then add the following four group memberships to the end of the LDIF file to grant the appropriate read/write privileges:
dn: cn=orclFAUserReadPrivilegeGroup,cn=groups,dc=example,dc=com changetype: modify add: uniquemember uniquemember: cn=biLDAP,cn=systemids,dc=example,dc=com dn: cn=orclFAGroupReadPrivilegeGroup,cn=groups,dc=example,dc=com changetype: modify add: uniquemember uniquemember: cn=biLDAP,cn=systemids,dc=example,dc=com dn: cn=orclFAUserWritePrivilegeGroup,cn=groups,dc=example,dc=com changetype: modify add: uniquemember uniquemember: cn=biLDAP,cn=systemids,dc=example,dc=com dn: cn=orclFAGroupWritePrivilegeGroup,cn=groups,dc=example,dc=com changetype: modify add: uniquemember uniquemember: cn=biLDAP,cn=systemids,dc=example,dc=com
Provision the user in the LDAP directory.
For example, for an Oracle Unified Directory LDAP provider:
OUD_INSTANCE_HOME/bin/ldapmodify -a \ -h oudhost.example.com -D "cn=oudadmin" \ -w password \ -p 1389 \ -f domain_user.ldif
For Oracle Internet Directory:
OID_ORACLE_HOME/bin/ldapadd -h oidhost.example.com \ -p 3060 \ -D cn="orcladmin" \ -w password \ -c \ -v \ -f domain_user.ldif
To configure a new LDAP-based authentication provider:
Log in to the WebLogic Server Administration Console.
Click Security Realms in the left navigational bar.
Click the myrealm default realm entry.
Click the Providers tab.
Note that there is a DefaultAuthenticator
provider configured for the realm. This is the default WebLogic Server authentication provider.
Click Lock & Edit in the Change Center.
Click the New button below the Authentication Providers table.
Enter a name for the provider.
Use one of the following names, based on the LDAP directory service you are planning to use as your credential store:
OUDAuthenticator
for Oracle Unified Directory
OIDAuthenticator
for Oracle Internet Directory
OVDAuthenticator
for Oracle Virtual Directory
Select the authenticator type from the Type drop-down list.
Select one of the following types, based on the LDAP directory service you are planning to use as your credential store:
OracleUnifiedDirectoryAuthenticator
for Oracle Unified Directory
OracleInternetDirectoryAuthenticator
for Oracle Internet Directory
OracleVirtualDirectoryAuthenticator
for Oracle Virtual Directory
Click OK to return to the Providers screen.
On the Providers screen, click the newly created authenticator in the table.
Select SUFFICIENT from the Control Flag drop-down menu.
Setting the control flag to SUFFICIENT indicates that if the authenticator can successfully authenticate a user, then the authenticator should accept that authentication and should not continue to invoke any additional authenticators.
If the authentication fails, it will fall through to the next authenticator in the chain. Make sure all subsequent authenticators also have their control flags set to SUFFICIENT; in particular, check the DefaultAuthenticator
and make sure that its control flag is set to SUFFICIENT.
Click Save to save the control flag settings.
Click the Provider Specific tab and enter the details specific to your LDAP server, as shown in the following table.
Note that only the required fields are discussed in this procedure. For information about all the fields on this page, consider the following resources:
To display a description of each field, click Help on the Provider Specific tab.
For more information on setting the User Base DN, User From Name Filter, and User Attribute fields, see Configuring Users and Groups in the Oracle Internet Directory and Oracle Virtual Directory Authentication Providers in Oracle Fusion Middleware Administering Security for Oracle WebLogic Server.
Parameter | Sample Value | Value Description |
---|---|---|
Host |
For example: |
The LDAP server's server ID. |
Port |
For example: |
The LDAP server's port number. |
Principal |
For example: |
The LDAP user DN used to connect to the LDAP server. |
Credential |
Enter LDAP password. |
The password used to connect to the LDAP server. |
SSL Enabled |
Unchecked (clear) |
Specifies whether SSL protocol is used when connecting to the LDAP server. |
User Base DN |
For example: |
Specify the DN under which your users start. |
All Users Filter |
|
Instead of a default search criteria for All Users Filter, search all users based on the If the User Name Attribute for the user object class in the LDAP directory structure is a type other than For example, if the User Name Attribute type is (&(cn=*)(objectclass=person))) |
User From Name Filter |
For example: (&(uid=%u)(objectclass=person)) |
If the User Name Attribute for the user object class in the LDAP directory structure is a type other than For example, if the User Name Attribute type is
|
User Name Attribute |
For example: |
The attribute of an LDAP user object that specifies the name of the user. |
Group Base DN |
For example: |
Specify the DN that points to your Groups node. |
Use Retrieved User Name as Principal |
Checked |
Must be turned on. |
GUID Attribute |
|
This value is prepopulated with |
Click Save to save the changes.
Return to the Providers page by clicking Security Realms in the right navigation pane, clicking the default realm name (myrealm), and then Providers.
Click Reorder, and then use the resulting page to make the Provider you just created first in the list of authentication providers.
Click OK.
In the Change Center, click Activate Changes .
Restart the Administration Server and all managed servers.
To stop the Managed Servers, log in to Fusion Middleware Control, select the Managed Servers in the Target Navigator and click Shut Down in the toolbar.
To stop and start the Administration Server using the Node Manager:
Start WLST:
cd ORACLE_COMMON_HOME/common/bin
./wlst.sh
Connect to Node Manager using the Node Manager credentials you defined in when you created the domain in the Configuration Wizard:
wls:/offline>nmConnect('nodemanager_username','nodemanager_password', 'ADMINVHN','5556','domain_name', 'ASERVER_HOME')
Stop the Administration Server:
nmKill('AdminServer')
Start the Administration Server:
nmStart('AdminServer')
Exit WLST:
exit()
To start the Managed Servers, log in to Fusion Middleware Control, select the Managed Servers, and click Start Up in the toolbar.
After the restart, review the contents of the following log file:
ASERVER_HOME/servers/AdminServer/logs/AdminServer.log
Verify that no LDAP connection errors occurred. For example, look for errors such as the following:
The LDAP authentication provider named "OUDAuthenticator" failed to make connection to ldap server at ...
If you see such errors in the log file, then check the authorization provider connection details to verify they are correct and try saving and restarting the Administration Server again.
After you restart and verify that no LDAP connection errors are in the log file, try browsing the users and groups that exist in the LDAP provider:
In the Administration Console, navigate to the Security Realms > myrealm > Users and Groups page. You should be able to see all users and groups that exist in the LDAP provider structure.
This example shows how to create a user called weblogic_bi
and a group called BIAdministrators
.
To provision the administration user and group in LDAP provider:
Create an ldif file named admin_user.ldif
with the contents shown below and then save the file:
dn: cn=weblogic_bi,cn=users,dc=example,dc=com changetype: add orclsamaccountname: weblogic_bi userpassword: password objectclass: top objectclass: person objectclass: organizationalPerson objectclass: inetorgperson objectclass: orcluser objectclass: orcluserV2 mail: weblogic_bi@example.com givenname: weblogic_bi sn: weblogic_bi cn: weblogic_bi uid: weblogic_bi
Provision the user in the LDAP directory.
For example, for an Oracle Unified Directory LDAP provider:
OUD_INSTANCE_HOME/bin/ldapmodify -a \ -h oudhost.example.com -D "cn=oudadmin" \ -w password \ -p 1389 \ -f admin_user.ldif
For Oracle Internet Directory:
OID_ORACLE_HOME/bin/ldapadd -h oidhost.example.com \ -p 3060 \ -D cn="orcladmin" \ -w password \ -c \ -v \ -f admin_user.ldif
Create an ldif
file named admin_group.ldif
with the contents shown below and then save the file:
dn: cn=BIAdministrators,cn=Groups,dc=example,dc=com displayname: BIAdministrators objectclass: top objectclass: groupOfUniqueNames objectclass: orclGroup uniquemember: cn=weblogic_bi,cn=users,dc=example,dc=com cn: BIAdministrators description: Administrators Group for the Oracle Business Intelligence Domain
Provision the group in the LDAP Directory.
For Oracle Unified Directory:
OUD_INSTANCE_HOME/bin/ldapmodify -a \ -D "cn=oudadmin" \ -h oudhost.example.com \ -w password \ -p 1380 \ -f admin_group.ldif
For Oracle Internet Directory:
OID_ORACLE_HOME/bin/ldapadd -h oid.example.com \ -p 3060 \ -D cn="orcladmin" \ -w password \ -c \ -v \ -f admin_group.ldif
Verify that the changes were made successfully:
Log in to the Oracle WebLogic Server Administration Console.
In the left pane of the console, click Security Realms.
Click the default security realm (myrealm).
Click the Users and Groups tab.
Verify that the administrator user and group you provisioned are listed on the page.
After adding the users and groups to Oracle Internet Directory, the group must be assigned the Administration role within the WebLogic domain security realm. This enables all users that belong to the group to be administrators for the domain.
To assign the Administration role to the new enterprise deployment administration group:
After you create the new administration user and group, you must update the Administration Server boot.properties
file with the administration user credentials that you created in the LDAP directory:
After you configure a new LDAP-based Authorization Provider and restart the Administration Server, add the enterprise deployment administration LDAP group (BIAdministrators
) as a member to the policy.Updater
role in the wsm-pm
application stripe.
It is an Oracle best practices recommendation to create a backup after successfully configuring a domain or at another logical point. Create a backup after verifying that the installation so far is successful. This is a quick backup for the express purpose of immediate restoration in case of problems in later steps.
The backup destination is the local disk. You can discard this backup when the enterprise deployment setup is complete. After the enterprise deployment setup is complete, you can initiate the regular deployment-specific Backup and Recovery process.
For information about backing up your configuration, see Performing Backups and Recoveries for an Enterprise Deployment.