Skip Headers
Oracle® Fusion Middleware Installation Guide for Oracle Business Intelligence
11g Release 1 (11.1.1)

Part Number E10539-05
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

5 Postinstallation Tasks

After completing the installation process, you might have one or more optional or required configuration-related tasks to perform. Such post installation tasks are covered in this chapter, including:

Some configuration and administration topics covered in other guides might be of interest. Table 5-1, "Topics Covered in Other Guides" lists these topics, and indicates where to go for more information.

Table 5-1 Topics Covered in Other Guides

Topic Where to Go for More Information

General configuration

Deployment


5.1 Installing and Deinstalling Oracle Business Intelligence Client Tools

Oracle Business Intelligence supports the following client tools on 32- and 64-bit Windows operating systems only:

Oracle Business Intelligence supports the Oracle Business Intelligence Catalog Manager client tools on 32-bit and 64-bit Windows and Linux operating systems.

Note:

The Catalog Manager on Linux is based on the Eclipse java plugin which utilizes the standard widget toolkit (SWT) which in turn requires gimp toolkit (GTK) to be installed. Therefore, before opening the Catalog Manager in Linux, confirm that you have the GTK (32- bit or 64-bit) packages and its dependencies installed on the Linux operating system. For more information, see "Starting Catalog Manager and Opening Catalogs" in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.

This section provides information on installing and deinstalling the Oracle Business Intelligence client tools, and includes the following topics:

5.1.1 About Oracle Business Intelligence Client Tools

When you install Oracle Business Intelligence, the Oracle Business Intelligence 11g Installer automatically installs the Oracle Business Intelligence client tools. The bit-versions of the client tools that get installed depend on the bit-version of the Oracle Business Intelligence 11g Installer that you use. For example, the 32-bit version of the Oracle Business Intelligence 11g Installer installs 32-bit versions of the client tools; the 64-bit version of the Oracle Business Intelligence 11g Installer installs 64-bit versions of the client tools.

When you install Oracle Business Intelligence on a computer running a Linux, or UNIX operating system, Oracle Business Intelligence Catalog Manager is the only client tool installed. For more information about running Catalog Manager, see "Starting Catalog Manager and Opening Catalogs" in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.

However, if you installed Oracle Business Intelligence on a computer running a Linux, or UNIX operating system, or if you installed Oracle Business Intelligence on a 32- or 64-bit Windows operating system but want to use the client tools on another Windows computer, you must use one of the following options:

  • Run the Oracle BI EE Plus Client Installer to install the Oracle Business Intelligence Administration Tool, Oracle Business Intelligence Job Manager, and Oracle Business Intelligence Catalog Manager (online mode).

  • Run the Oracle Universal Installer to install the Oracle Business Intelligence Administration Tool, Oracle Business Intelligence Job Manager, and Oracle Business Intelligence Catalog Manager.

To continue, refer to the following topics:

For instructions on how to use the client tools after you install them, see:

5.1.2 Considerations for Installing Oracle Business Intelligence Client Tools

Consider the following before installing the Oracle Business Intelligence client tools:

  • The 32- bit and 64-bit Oracle BI EE Plus Client Installer installs the 32-bit and 64-bit versions of the Oracle Business Intelligence Administration Tool, Oracle Business Intelligence Job Manager, and Oracle Business Intelligence Catalog Manager. The 64-bit version of the client tools installed by the Oracle BI EE Plus Client Installer is recommended on a 64-bit operating systems only.

    Note:

    Oracle BI EE Plus Client installer does not install the Oracle Database Client. To access the Oracle database you must separately install the Database Client on the same machine. Similarly, to access the IBM DB2 database, you must install the IBM DB2 CLI on the same machine. For more information, see "Importing Metadata and Working With Data Sources" in Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.

  • The Administration Tool requires its own system DSN for connecting to the Oracle Business Intelligence system. You create and configure the system DSN after you install the Oracle Business Intelligence client tools. Your Oracle Business Intelligence system administrator should supply the details required to create the system DSN. For the instructions on configuring a separate ODBC DSN, see "Configuring an ODBC DSN for the Oracle BI Server on Windows" in Oracle Fusion Middleware Integrator's Guide for Oracle Business Intelligence Enterprise Edition.

    Note:

    When running the Oracle Business Intelligence Enterprise Edition Plus Client Installer, if the install path contains any multi-byte characters, Job Manager and Administration Tool cannot launch. To avoid this issue you must change the install path if it contains any multi-byte characters. Make sure that the install path contains only ASCII characters.

  • Oracle Business Intelligence supports multiple instances of the Oracle Business Intelligence client tools on the same computer. That is, if your organization has installed multiple instances of Oracle Business Intelligence, you can install and configure the Oracle Business Intelligence client tools multiple times, or once for each instance of Oracle Business Intelligence. However, do not install the client tools on the same computers that host your Oracle Business Intelligence server instances, as the client tools are already installed on those computers (as part of the Oracle Business Intelligence installation).

5.1.3 Installing and Deinstalling Oracle Business Intelligence Client Tools with the Oracle BI EE Plus Client Installer

This section describes how to install and deinstall the Oracle Business Intelligence clients using the Oracle BI EE Plus Client Installer, and includes the following topics:

5.1.3.1 Prerequisites for Running the Oracle BI EE Plus Client Installer

Before running the Oracle BI EE Plus Client Installer, do all of the following:

  • Identify a computer running a supported 32-bit or 64-bit Windows operating system where you can install the Oracle Business Intelligence client tools.

  • Verify that the computer where you want to install the Oracle Business Intelligence client tools can access the Linux, UNIX, or Windows computer (32-bit or 64-bit) that hosts your Oracle Business Intelligence system.

  • Contact your system administrator to obtain the information necessary to create the system DSN for the Administration Tool.

  • Obtain the Oracle BI EE Plus Client Installer file (biee_client_install.exe) using one of the following methods:

    • Access the Oracle BI EE Plus Client Installer file from the Oracle BI home page by selecting the Download BI Desktop Tools link and choosing Oracle BI Client Installer. You can display the Oracle BI home page from the following URL:

      http://<host>:<port>/analytics/saw.dll?bieehome

      For example:

      http://computer1:9704/analytics/saw.dll?bieehome

    • Access biee_client_install.exe in your Oracle home and transfer a copy of it to the computer where you want to install the client tools. You can find biee_client_install.exe in the following location:

      ORACLE_HOME/clients/biserver

    • Access the Oracle BI EE Plus Client Installer file on OTN and download it to the computer where you want to install the client tools. You can find the Oracle BI EE Plus Client Installer file on OTN at the following link:

      http://www.oracle.com/technetwork/middleware/bi-enterprise-edition/downloads/bus-intelligence-11g-165436.html

5.1.3.2 Running the Oracle BI EE Plus Client Installer

To install Oracle Business Intelligence client tools with the Oracle BI EE Plus Client Installer:

  1. Ensure that you have satisfied the prerequisites described in Section 5.1.3.1, "Prerequisites for Running the Oracle BI EE Plus Client Installer."

  2. Start the Oracle BI EE Plus Client Installer by accessing and double-clicking biee_client_install.exe. The installer launches and the Introduction screen opens.

    Note:

    If you installed the Oracle Business Intelligence client tools on the current computer, the Manage Instances window opens instead. Click Install a New Instance, and then click OK to open the Introduction screen.

    Click Next. The Choose Install Folder window opens.

  3. In the Choose Install Folder window, you can accept the default install location or specify another one. To specify another location, either enter the location in the text box or click Choose and navigate to the location. To restore the path in the text box to the default location, click Restore Default Folder.

    To continue, click Next. The Choose Shortcut Folder window opens.

  4. In the Choose Shortcut Folder window, you can specify where you want the installer to create product icons for the Oracle Business Intelligence client tools. Select the appropriate option.

    To continue, click Next. The Pre-Installation Summary window opens.

  5. In the Pre-Installation Summary window, confirm your installation settings. To change a setting, click Previous and return to the screen that contains the setting you want to change.

    To begin the installation, click Install.

  6. When the installation concludes, click Done. The ODBC Data Source Administrator dialog opens.

  7. In the ODBC Data Source Administrator dialog window, configure a system DSN for the Administration Tool to connect to your Oracle Business Intelligence system. For the instructions on configuring a separate ODBC DSN, see "Configuring an ODBC DSN for the Oracle BI Server on Windows" in Oracle Fusion Middleware Integrator's Guide for Oracle Business Intelligence Enterprise Edition.

5.1.3.3 Deinstalling Oracle Business Intelligence Client Tools

To deinstall the Oracle Business Intelligence client tools:

  1. Do one of the following:

    • If you chose to create product icons when you installed the Oracle Business Intelligence client, click Change Oracle Business Intelligence Enterprise Edition Plus Client Installation in the location where you created the icons (such as on your desktop or in the Oracle Business Intelligence Enterprise Edition Plus Client program group of the Programs menu).

    • If you chose not to create product icons when you installed the Oracle Business Intelligence clients, access the directory where you installed the Oracle Business Intelligence clients. In the install directory, open the _Oracle Business Intelligence Enterprise Edition Plus Client_installation folder and double-click the file Change Oracle Business Intelligence Enterprise Edition Plus Client Installation.exe.

    The Maintenance Mode window opens.

  2. In the Maintenance Mode window, click Uninstall Product, and then click Next. The Confirm Uninstall window opens.

  3. In the Confirm Uninstall window, click Next to deinstall the Oracle Business Intelligence client tools.

  4. When the deinstall process concludes, click Done.

  5. To deinstall other installations of the Oracle Business Intelligence client tools, repeat steps 1 through 4 for each installation.

5.1.4 Installing Oracle Business Intelligence Client Tools with the Oracle Business Intelligence 11g Installer

To install the Oracle Business Intelligence client tools using the Oracle Business Intelligence 11g Installer:

  1. Create a new set of BIPLATFORM and MDS schemas in the database using RCU (see Section 3.3.6, "Running RCU to Create Oracle Business Intelligence Database Schemas"). This set of schemas are used by a new Oracle Business Intelligence instance for the client tools. You install this new instance in step 3.

  2. Identify a computer running a 32-bit or 64-bit Windows operating system to host the new instance for the client tools. Verify that the Windows computer you identify can access the computer that is hosting your active Oracle Business Intelligence system.

  3. Install the new Oracle Business Intelligence instance on a computer running a 32-bit or 64-bit Windows operating system. For this, you can use the Simple Install type (see Section 4.5.1, "Simple Install").

  4. After installing the new Oracle Business Intelligence instance, shut down all of its services, including OPMN and Node Manager. See Chapter 4, "Starting and Stopping Oracle Business Intelligence" in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.

  5. On the computer hosting the client tools, configure a separate DSN for the Administration Tool to connect to your active Oracle Business Intelligence system. Do not use the default, centrally managed DSN to connect to your active system. For the instructions on configuring a separate ODBC DSN, see "Configuring an ODBC DSN for the Oracle BI Server on Windows" in Oracle Fusion Middleware Integrator's Guide for Oracle Business Intelligence Enterprise Edition.

  6. To deinstall the client tools, follow the procedure for deinstalling Oracle Business Intelligence. See Chapter 6, "Deinstalling Oracle Business Intelligence."

5.2 Configuring Oracle Business Intelligence with the Configuration Assistant

With the Oracle Business Intelligence Configuration Assistant, you configure Oracle Business Intelligence software that was installed through the Software Only Install type. The Oracle Business Intelligence Configuration Assistant enables you to do the following:

Note that if you used the Software Only Install type to install Oracle Business Intelligence into an existing Middleware home of another Oracle Fusion Middleware product, then you can follow the procedures for all of the configuration scenarios (assuming that the installation meets the prerequisites for those scenarios), with the exception of the "Update an Oracle Business Intelligence domain" scenario.

This section contains the following topics:

5.2.1 Considerations and Limitations for Configuring Oracle Business Intelligence with the Configuration Assistant

The following considerations and limitations apply when configuring Oracle Business Intelligence with the Configuration Assistant:

  • Do not run the Oracle Business Intelligence Configuration Assistant to scale your installation vertically. For vertical scaling, see Chapter 5 "Scaling Your Deployment" in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.

  • The Configuration Assistant is not supported on Oracle Business Intelligence installations that were installed with the Simple Install type.

  • Before configuring a scaled-out enterprise installation, ensure that the computer on which you run the Configuration Assistant can route TCP/IP packets to TCP port 7 on the computer on which the Administration Server is running. This routing must occur while the configuration process runs; otherwise an error message is displayed.

  • If the Administration Server has multiple IP addresses (such as multiple network cards), then the default listen address for the Administration Server must be an IP address to which the Managed Server can communicate. To change the default listen address for the Administration Server, see "Configuring Network Resources" in Oracle Fusion Middleware Configuring Server Environments for Oracle WebLogic Server.

    When configuring the scaled-out server, the Configuration Assistant creates the Managed Server. The Configuration Assistant displays an error message and does not create the Managed Server if the Managed Server would be unable to communicate with the Administration Server on the default listen address.

    If Oracle WebLogic Server has been configured to use the administration channel, then you can disable the communication check for the Administration Server by adding the following parameter to the installer command line:

    DISABLE_ACCESS_TO_ADMIN_SERVER_CHECK=true

  • You cannot extend a domain using the Oracle Fusion Middleware Configuration Wizard, which is found in ORACLE_HOME/common/bin. Specifically, you cannot use the Configuration Wizard to add more Oracle Business Intelligence components to an existing Business Intelligence or Oracle WebLogic Server domain, or to the domain of any other Oracle Fusion Middleware product.

5.2.2 Pre-Configuration Tasks

If this is the first time that you are configuring the system (meaning there is no pre-existing Oracle inventory location), then Oracle recommends that you validate that your environment meets the configuration requirements. You can perform this task interactively or silently.

To interactively validate that your environment meets the configuration requirements, run the following command, depending on your operating system:

On UNIX:

./config.sh -validate

On Windows:

config.bat -validate

To silently validate that your environment meets the configuration requirements, run the following command, depending on your operating system:

On UNIX

./config.sh -silentvalidate -response response_file_path

On Windows:

config.bat -silentvalidate -response response_file_path

For information on running the Configuration Assistant in silent mode, see Section 5.2.6, "Running the Configuration Assistant in Silent Mode".

5.2.3 Starting the Oracle Business Intelligence Configuration Assistant

You can start the Oracle Business Intelligence Configuration Assistant in an interactive or silent mode.

This section provides instructions on starting the Oracle Business Intelligence Configuration Assistant in an interactive mode.

For information on starting the Oracle Business Intelligence Configuration Assistant in silent mode, see Section 5.2.6.3, "Starting the Oracle Business Intelligence Configuration Assistant in Silent Mode".

Start the Oracle Business Intelligence Configuration Assistant from the bin directory in the ORACLE_HOME (default folder name is Oracle_BI1), based on the operating system:

UNIX commands:

cd ORACLE_HOME/bin

./config.sh

Windows commands:

cd ORACLE_HOME\bin

config.bat

5.2.4 Creating the oraInst.loc File

The Oracle inventory directory is used by the Configuration Assistant to keep track of all Oracle products installed on computers. The inventory directory is stored in a file called oraInst.loc (on UNIX and Linux). If this file does not exist on the system, then the Configuration Assistant creates it automatically.

5.2.5 Using Command Line Options to Configure Oracle Business Intelligence

You can configure Oracle Business Intelligence through the command line options. Table 5-2 shows the command line options for the Configuration Assistant.

Table 5-2 Command Line Options for the Configuration Assistant

Options Description

-help

--help

--usage

Displays the usage options for the config command.

-invPtrLoc file

Points to the inventory location file. Replace file with the full path and name of the oraInst.loc file.

-response file

-responseFile file

Points to the response file. Replace file with the full path and name of the response file.

-jreLoc location

Points to the location where the Java Runtime Environment (JRE) is installed. Replace location with the full path to the jre directory where the JRE is installed.

-logLevel level

Specifies the level of logging performed by the Configuration Assistant; all messages with a lower priority than the specified level are recorded. Valid levels are:

  • severe

  • warning

  • info

  • config

  • fine

  • finer

  • finest

-debug

Obtains debug information from the Configuration Assistant.

-force

Allows the silent configuration to proceed in a non-empty directory.

-printdiskusage

Logs debugging information relating to disk usage.

-printmemory

Logs debugging information relating to memory usage.

-printtime

Logs debugging information relating to time usage. This command creates the timeTakentimestamp.log file.

-waitforcompletion

Waits for completion instead of starting the Java engine and exiting. This configuration program is for Windows only.

-noconsole

Does not display messages in the console window.

-ignoreSysPrereqs

Ignores the results of the system prerequisite checks and continues with the configuration.

-executeSysPrereqs

Executes the system prerequisite checks only, then exits.

-paramFile path

Specifies the full path to the oraparam.ini file. This file is the initialization file for the Configuration Assistant. The default location is Disk1/install/platform.

-novalidation

Disables all validation checking performed by the Configuration Assistant.

-nodefaultinput

Displays unforeseen results if used. This parameter is no longer supported.


For example, to run the Configuration Assistant to only perform the system prerequisite checks, enter the following commands:

On UNIX commands:

./config.sh -executeSysPrereqs

Windows commands:

config.bat -executeSysPrereqs

5.2.6 Running the Configuration Assistant in Silent Mode

This section describes how to run the Configuration Assistant from the command line in silent mode. When you run the Configuration Assistant in silent mode, it displays no output and you are not prompted for responses.

This section contains the following topics:

5.2.6.1 What Is a Silent Configuration?

Silent configuration is the process of configuring Oracle Business Intelligence by running the Configuration Assistant in silent mode. You run the Configuration Assistant in silent mode by:

  • Creating a response file that specifies the operations you want the Configuration Assistant to perform.

  • Running the Configuration Assistant in silent mode and specifying the name of the response file.

Table 5-3 shows the Configuration Assistant command line option for the silent mode.

Table 5-3 Command Line Option for the Configuration Assistant-Silent Configuration Mode

Option Description

-silent -responseFile file [-invPtr Loc_file]

Configure in silent mode. You must pass the Configuration Assistant a response file.

[-invPtr Loc_file] points to the location of the inventory file.


5.2.6.2 Creating Response Files for the Configuration Assistant

To run the Configuration Assistant in silent mode, you must specify a response file.

You can create a response file in two ways:

  • By using a text editor

  • By saving to a file the inputs you enter when running the Configuration Assistant interactively

To create a response file using a text editor:

  1. Navigate to the directory where the response file is located.

  2. Open the file in a text editor.

  3. Edit the file.

    For details, see the instructions in the file.

To create a response file by saving the inputs you enter when running the Configuration Assistant interactively:

  1. Run the Configuration Assistant and select the configuration preferences in each screen.

  2. On the Installation or Configuration Summary screen, click Save.

    The Configuration Assistant prompts you for a name for the response file and a location where to save it.

  3. Specify the name and location for the file, and exit the Configuration Assistant. You do not need to complete the configuration.

After you create a response file, you can use it to replicate the configuration on other systems, or you can modify it in a text editor as needed.

5.2.6.3 Starting the Oracle Business Intelligence Configuration Assistant in Silent Mode

Use the -silent mode option if you want to start the Configuration Assistant in silent mode.

To start the Oracle Business Intelligence Configuration Assistance in Silent Mode:

  1. Navigate to the directory containing the Configuration Assistant. The Configuration is located at ORACLE_HOME/bin directory.

    For example:

    On UNIX

    cd MW_HOME/Oracle_BI1/bin

    On Windows

    cd c:\MW_HOME\Oracle_BI1\bin

  2. Run the Configuration Assistant in silent mode, specifying the response file to use and (optionally) the location of the Oracle Inventory, as follows:

    On UNIX

    ./config.sh -silent -responseFile file [-invPtrLoc file]

    For example:

    ./config.sh -silent -responseFile /home/jdoe/response/oracle.classicwls.top.Custom.rsp -invPtrLoc /home/jdoe/oraInst.loc

    On Windows

    config.bat -silent -responseFile file [-invPtrLoc file]

    For example:

    config.bat -silent -responseFile C:\jdoe\response\oracle.classicwls.top.Custom.rsp -invPtrLoc C:\jdoe\oraInst.loc

    For a list of command line options, see Table 5-2.

5.2.6.4 Software Update Options Supported by Silent Configuration

Silent configuration supports the following software update options only:

  • Skip software updates

  • Install software updates from a local directory

Silent configuration does not support the option to download and install software updates through My Oracle Support.

5.2.7 Configuring a New Enterprise Installation of Oracle Business Intelligence

Note:

If you used the Software Only Install type to install Oracle Business Intelligence into an existing Middleware home of another Oracle Fusion Middleware product, you can follow the procedure described in this section to complete the configuration of your installation (assuming your installation meets the prerequisites for this configuration scenario).

To configure a new enterprise installation of Oracle Business Intelligence using the Configuration Assistant:

  1. Start the Oracle Business Intelligence Configuration Assistant. See Section 5.2.3, "Starting the Oracle Business Intelligence Configuration Assistant."

  2. On the Welcome screen, click Next.

  3. On the Prerequisite Checks screen, after the prerequisite checks conclude with no errors, click Next.

    If an error message appears, fix the error and then click Retry to run the prerequisite check again (recommended). Repeat this until all prerequisite checks conclude with no errors.

    To stop the configuration process while you fix a prerequisite error, click Abort.

    To ignore an error or warning message, and continue with the configuration process, click Continue (not recommended).

    Note:

    The installation might not function normally if you continue without resolving the issue that caused an error or warning message during the prerequisite checks.

  4. On the Create, Scale Out, or Extend BI System screen, click Create New BI System, and then enter the following information:

    • The user name and password for the system administrator for the new Oracle Business Intelligence system

    • The domain name for the new Oracle Business Intelligence system

    Click Next.

  5. The Specify Installation Location (Enterprise) screen displays the current Middleware home and other key locations for the new installation.

    Optionally, change the following settings:

    • Domain Home Location

    • Oracle Instance Location

    • Oracle Instance Name

    Click Next.

  6. On the Configure Components screen, all products are selected by default. Click the box next to each component that you do not want to configure.

    Select all the products that you want or might want to configure. You cannot configure some products now and then configure others later in the current domain.

    Note:

    If you choose to configure Oracle BI EE, Oracle BI Publisher is configured automatically.

    After you make your selections, click Next.

  7. On the BIPLATFORM Schema screen, specify the following:

    After you specify the database settings, click Next.

  8. On the MDS Schema screen, specify the following:

    After you specify the database settings, click Next.

  9. On the Configure Ports screen, click Auto Port Configuration or Specify Ports Using Configuration File.

    If you select the latter option, you must specify a configuration file that contains the custom port values for the Oracle Business Intelligence installation. Click Browse to navigate to the file and click View/Edit to view and edit it. If you edit the file, click Save to save your changes.

    Note:

    The Oracle Business Intelligence Configuration Assistant automatically assigns the Node Manager port (default is 9556), unless you specify the Oracle Business Intelligence ports manually using a configuration file such as staticports.ini (see Section 4.2.8, "Setting Custom Port Values for Oracle Business Intelligence"). However, if configuring Oracle Business Intelligence in a shared Middleware home where Node Manager is installed, the Oracle Business Intelligence Configuration Assistant uses the existing Node Manager and its port number.

    Click Next.

  10. On the Security Updates screen, enter your My Oracle Support account information, and then click Next.

  11. On the Summary screen, click Save to save the settings for this configuration in a response file (optional), and then click Configure to start the configuration process.

  12. On the Configuration Progress screen, you can monitor the progress of the software configuration and respond to errors, if any occur.

    If a configuration task fails, an error message appears. To retry the task, click Retry. To continue with the next task, click Continue (not recommended). To stop the installation and configuration process entirely, click Abort.

    For more information, see Section 4.7, "Troubleshooting the Installation and Configuration Processes."

    Note:

    The installation might not function normally if you choose to continue the configuration process without resolving the issue that caused an error or warning message. Oracle recommends that you attempt to resolve any issues before continuing or restarting the configuration process. See Section 4.7, "Troubleshooting the Installation and Configuration Processes."

    After the configuration concludes without any errors, click Next.

  13. On the Complete screen, click Save to save the settings for this installation in a response file (optional), and then click Finish to exit the Oracle Business Intelligence Configuration Assistant.

5.2.8 Configuring a Scaled-Out Enterprise Installation of Oracle Business Intelligence

Note:

If you used the Software Only Install type to install Oracle Business Intelligence into an existing Middleware home of another Oracle Fusion Middleware product, you can follow the procedure described in this section to complete the configuration of the installation (assuming the installation meets the prerequisites for this configuration scenario).

To configure a scaled-out enterprise installation of Oracle Business Intelligence using the Configuration Assistant:

  1. Start the Oracle Business Intelligence Configuration Assistant. See Section 5.2.3, "Starting the Oracle Business Intelligence Configuration Assistant."

  2. On the Welcome screen, click Next.

  3. On the Prerequisite Checks screen, after the prerequisite checks conclude with no errors, click Next.

    If an error message appears, fix the error and then click Retry to run the prerequisite check again (recommended). Repeat this until all prerequisite checks conclude with no errors.

    To stop the configuration process while you fix a prerequisite error, click Abort.

    To ignore an error or warning message, and continue with the configuration process, click Continue (not recommended).

    Note:

    The installation might not function normally if you continue without resolving the issue that caused an error or warning message during the prerequisite checks.

  4. In the Create, Scale Out, or Extend BI System screen, click Scale Out BI System, and then enter the following information:

    • The host name and port number for the Administration Server domain

    • The user name and password for logging in to the WebLogic Administration Server.

    Click Next.

  5. On the Scale Out BI System Details screen, optionally change the following settings:

    • Oracle Instance Location

    • Oracle Instance Name

    Click Next.

  6. On the Configure Ports screen, click Auto Port Configuration or Specify Ports Using Configuration File.

    If you select the latter option, you must specify a configuration file that contains the custom port values for the Oracle Business Intelligence installation. Click Browse to navigate to the file and click View/Edit to view and edit it. If you edit the file, click Save to save your changes.

    Note:

    The Oracle Business Intelligence Configuration Assistant automatically assigns the Node Manager port (default is 9556), unless you specify the Oracle Business Intelligence ports manually using a configuration file such as staticports.ini (see Section 4.2.8, "Setting Custom Port Values for Oracle Business Intelligence"). However, if configuring Oracle Business Intelligence in a shared Middleware home where Node Manager is installed, the Oracle Business Intelligence script uses the existing Node Manager and its port number.

    Click Next.

  7. On the Security Updates screen, enter your My Oracle Support account information, and then click Next.

  8. On the Summary screen, click Save to save the settings for this configuration in a response file, and then click Configure to start the configuration process.

  9. On the Configuration Progress screen, you can monitor the progress of the software configuration and respond to errors, if any occur.

    If a configuration task fails, an error message appears. To retry the task, click Retry. To continue with the next task, click Continue (not recommended). To stop the installation and configuration process entirely, click Abort.

    For more information, see Section 4.7, "Troubleshooting the Installation and Configuration Processes."

    Note:

    The installation might not function normally if you choose to continue the configuration process without resolving the issue that caused an error or warning message. Oracle recommends that you attempt to resolve any issues before continuing or restarting the configuration process. See Section 4.7, "Troubleshooting the Installation and Configuration Processes."

    After the configuration concludes without any errors, click Next.

  10. On the Complete screen, click Save to save the settings for this configuration in a response file (optional), and then click Finish to exit the Oracle Business Intelligence Configuration Assistant.

5.2.9 Extending an Oracle WebLogic Server Domain with Oracle Business Intelligence

Note:

If you used the Software Only Install type to install Oracle Business Intelligence into an existing Middleware home of another Oracle Fusion Middleware product, you can follow the procedure described in this section to complete the configuration of the installation (assuming the installation meets the prerequisites for this configuration scenario).

You can use the Oracle Business Intelligence Configuration Assistant to configure an instance of Oracle Business Intelligence that was previously installed into an existing Middleware home of an Oracle WebLogic Server domain. This is referred to as extending the domain.

Before you use the Oracle Business Intelligence Configuration Assistant to extend an existing Oracle WebLogic Server domain, ensure the following:

  • Oracle WebLogic Server was previously installed and the associated domain was created using the WebLogic Server Configuration Wizard. For more information, see Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server.

  • Oracle Business Intelligence was previously installed into an existing Middleware home using the Software Only Install type. For more information, see Section 4.5.4, "Software Only Install."

  • The domain exists on the same computer where you installed Oracle Business Intelligence. Extending domains remotely is not supported.

  • The domain is empty.

  • The domain is running.

  • The Administration Server for the domain is named AdminServer. Other names for the Administration Server are not supported.

To extend an Oracle WebLogic Server domain with Oracle Business Intelligence using the Configuration Assistant:

  1. Start the Oracle Business Intelligence Configuration Assistant. See Section 5.2.3, "Starting the Oracle Business Intelligence Configuration Assistant."

  2. On the Welcome screen, click Next.

  3. On the Prerequisite Checks screen, after the prerequisite checks conclude with no errors, click Next.

    If an error message appears, fix the error and then click Retry to run the prerequisite check again (recommended). Repeat this until all prerequisite checks conclude with no errors.

    To stop the configuration process while you fix a prerequisite error, click Abort.

    To ignore an error or warning message, and continue with the configuration process, click Continue (not recommended).

    Note:

    The installation might not function normally if you continue without resolving the issue that caused an error or warning message during the prerequisite checks.

  4. On the Create, Scale Out, or Extend BI System screen, click Extend BI System, and then enter the following information:

    • The host name and port number for the existing WebLogic Server domain

    • The user name and password for the administrator account that was created when Oracle WebLogic Server was installed and configured

    Click Next.

  5. The Specify Installation Location (Enterprise) screen displays the current Middleware home and other key locations for the new installation.

    Optionally, change the following settings:

    • Domain Home Location

    • Oracle Instance Location

    • Oracle Instance Name

    Click Next.

  6. On the Configure Components screen, all products are selected by default. Click the box next to each component that you do not want to configure.

    Select all the products that you want or might want to configure. You cannot configure some products now and then configure others later in the current domain.

    Note:

    If you choose to configure Oracle BI EE, Oracle BI Publisher is configured automatically.

    After you make your selections, click Next.

  7. On the BIPLATFORM Schema screen, specify the following:

    • The type of database for the Oracle Business Intelligence system.

    • The connect string for the database. See Section 4.2.9, "Specifying a Database Connect String."

    • The user name for the Business Intelligence Platform schema.

    • The password for the Business Intelligence Platform schema.

    After you specify the database settings, click Next.

  8. On the MDS Schema screen, specify the following:

    After you specify the database settings, click Next.

  9. On the Configure Ports screen, click Auto Port Configuration or Specify Ports Using Configuration File.

    If you select the latter option, you must specify a configuration file that contains the custom port values for the Oracle Business Intelligence installation. Click Browse to navigate to the file and click View/Edit to view and edit it. If you edit the file, click Save to save your changes.

    Note:

    The Configuration Assistant refers to the Domain and Node Manager ports for the existing WebLogic Server domain, and ignores any Domain and Node Manager port values specified in a custom configuration file, such as staticports.ini (see Section 4.2.8, "Setting Custom Port Values for Oracle Business Intelligence").

    Click Next.

  10. On the Security Updates screen, enter your My Oracle Support account information, and then click Next.

  11. On the Summary screen, click Save to save the settings for this configuration in a response file (optional), and then click Configure to start the configuration process.

  12. On the Configuration Progress screen, you can monitor the progress of the software configuration and respond to errors, if any occur.

    If a configuration task fails, an error message appears. To retry the task, click Retry. To continue with the next task, click Continue (not recommended). To stop the installation and configuration process entirely, click Abort.

    For more information, see Section 4.7, "Troubleshooting the Installation and Configuration Processes."

    Note:

    The installation might not function normally if you choose to continue the configuration process without resolving the issue that caused an error or warning message. Oracle recommends that you attempt to resolve any issues before continuing or restarting the configuration process. See Section 4.7, "Troubleshooting the Installation and Configuration Processes."

    After the configuration concludes without any errors, click Next.

  13. On the Complete screen, click Save to save the settings for this installation in a response file (optional), and then click Finish to exit the Oracle Business Intelligence Configuration Assistant.

5.3 Installing and Configuring BI Composer for Oracle BI EE

Installing and configuring BI Composer for Oracle BI EE depends on whether you are performing a new 11.1.1.7.0 installation or upgrading to 11.1.1.7.0 from a previous 11.1.1.x release.

This section includes the following topics:

5.3.1 Installing and Configuring BI Composer when Performing a New 11.1.1.7.0 BI Installation

When you perform a new 11.1.1.7.0 BI installation, BI Composer is automatically installed and configured.

5.3.2 Installing and Configuring BI Composer when Upgrading to 11.1.1.7.0 from a Previous 11.1.1.x Release

To upgrade to 11.1.1.7.0 from a previous 11.1.1.x release, see "Enabling Oracle Business Intelligence Composer Features" in Oracle Fusion Middleware Patching Guide.

5.4 Creating a DSN for IBM DB2 or Microsoft SQL Server

If you installed the Oracle Business Intelligence schemas using RCU on an IBM DB2 or Microsoft SQL Server database, and you have scaled out your system on multiple hosts, you must create an ODBC data source name (DSN) on each node where you scaled out Oracle Business Intelligence. You create each ODBC DSN by using the same data source details of the ODBC DSN used by the BI Scheduler on the primary node of the cluster. The steps that you perform depend on the operating systems of the computers where you scaled out Oracle Business Intelligence.

To create an ODBC DSN on the scaled-out nodes of an Oracle Business Intelligence cluster:

  1. Log in to Fusion Middleware Control.

  2. Open the Scheduler tab of the Deployment page to identify the IBM DB2 or Microsoft SQL Server data source of the primary node of the cluster.

  3. Close Fusion Middleware Control.

  4. Access the primary node of your Oracle Business Intelligence cluster and identify the data source details, as follows:

    • UNIX:

      The data source details are available in odbc.ini. Open odbc.ini from the following location:

      ORACLE_INSTANCE/bifoundation/OracleBIApplication/coreapplication/setup/

    • Windows:

      The data source details are available in the ODBC Data Source Administrator window. To access this window, click Start, select Settings, and click Control Panel.

      In Control Panel, double-click Administrative Tools. In the Administrative Tools window, double-click Data Sources (ODBC).

      In the ODBC Data Source Administrator window, click the System DSN tab, select the SQL Server or DB2 data source of the primary node of the cluster, and then click Configure.

  5. Make a note of the driver types and the data source details. The BI Scheduler uses ODBC data sources, which appear in the following formats, depending on the database type:

    • IBM DB2:

      instancename_DB2

    • Microsoft SQL Server:

      instancename_MSSS

  6. Close odbc.ini or the ODBC Data Source Administrator window, depending on the operating system.

  7. On each scaled-out node, do the following depending on the operating system:

    • UNIX:

      Open odbc.ini from the following location:

      ORACLE_INSTANCE/bifoundation/OracleBIApplication/ coreapplication/setup/

      Update odbc.ini with the same data source details as those of the primary node. Save your changes and close odbc.ini.

    • Windows:

      Click Start, select Settings, and click Control Panel. In Control Panel, double-click Administrative Tools, and then double-click Data Sources (ODBC).

      In the ODBC Data Source Administrator window, click the System DSN tab, and then click Add. In the Create New Data Source window, select the driver type and click Finish.

      Then, follow the steps in the wizard to enter the data source details of the primary node.

5.5 Configuring IBM DB2 to Support Multibyte Data

When Oracle Business Intelligence is installed with an IBM DB2 database, the Oracle Business Intelligence installer configures an ODBC 2.0 driver, which can result in issues with multibyte data. To avoid these issues, use Oracle Fusion Middleware Control to configure Oracle Business Intelligence to use the native DB2 CLI driver instead.

To configure Oracle Business Intelligence to use DB2 CLI driver with IBM DB2:

  1. Install the IBM DB2 client software on the computers where Oracle Business Intelligence resides, and create a data source for the scheduler database.

  2. After installing Oracle Business Intelligence, log in to Fusion Middleware Control.

  3. Expand the Business Intelligence folder and select the coreapplication node.

  4. Go to the Scheduler tab.

    Click the Help button on the page to access the page-level help for its elements.

  5. Click Lock and Edit Configuration.

  6. Click the Call Interface drop-down list and select DB2 CLI - Unicode.

  7. In the Data Source field, enter the data source name.

  8. Click Apply, and then click Activate Changes.

5.6 Managing the OPMN Service on Windows Operating Systems

After installation, the OPMN Service appears as stopped in the Services list on Windows operating systems, as Oracle Business Intelligence 11g Installer starts OPMN directly. You can manage OPMN by running opmnctl.bat, which is located in the following directory:

ORACLE_INSTANCE\bin

The OPMN Services is set to manual, therefore, you must manually restart it if you restart your system.

5.7 Configuring Sample Reports for BI Publisher

Oracle Business Intelligence provides several sample reports that you can access through BI Publisher. Some reports depend on data models that source data from the OE sample schema provided by Oracle Database. For these reports to run correctly, unlock the OE sample schema and configure the "demo" JDBC connection on the BI Publisher Administration page as described in the following procedure.

To configure the sample reports for BI Publisher:

  1. Unlock the OE sample schema and obtain the connection string for it. For more information, see Oracle Database Sample Schemas.

  2. In a supported Web browser, open the BI Publisher Admin page for the JDBC Data Source Connections.

  3. In the demo JDBC Data Source connection details, specify and save the connection string for the OE sample schema.

    For example:

    Connection String: jdbc:oracle:thin:@foobar.com.example:1521:orcl

    Username: OE

    Password: oe password

Note:

If you do not have access to an OE schema or privileges to update the demo JDBC Data Source, some sample reports are very likely to fail with errors of the following form:

Error:

The report cannot be rendered because of an error, please contact the administrator.

Error Detail Parameter name:

param Invalid number format for port number

5.8 Installing SampleApp.rpd and SampleAppLite.rdd Sample Repositories, and Changing the Default Password for SampleAppLite.rpd

When you install Oracle Business Intelligence, the Oracle Business Intelligence installer automatically installs the SampleAppLite.rpd file with a default repository password of Admin123. If you intend to use the SampleAppLite.rpd file in a production system, Oracle recommends that you change the repository password for security reasons. For more information, see "Changing the Repository Password" in Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.

You can download the Sample Application (full version) from the following location on OTN:

http://www.oracle.com/technetwork/middleware/bi-foundation/obiee-samples-167534.html

5.9 Changing Administration Server or Managed Server Port Numbers on Windows Operating Systems

If you change the Administration Server or Managed Server port numbers after you finish installing Oracle Business Intelligence on a Windows operating system, you must also update their values in the StartStopServices.cmd file.

To change port number settings in StartStopServices.cmd file after making post installation Administration Server or Managed Server port number changes on Windows operating systems:

  1. Open the StartStopServices.cmd file for editing, from the following directory:

    INSTANCE\bifoundation\OracleBIApplication\coreapplication

  2. Update the port values for the Administration Server and Managed Server as required, for example:

    set wls.admin.port=7002

    set wls.mgd.port=9705

    The above example from the StartStopServices.cmd file, shows the updated values you would need to enter if you had changed the Administration Server and Managed Server ports to 7002 and 9705 respectively.

  3. Save the StartStopServices.cmd file.