2 Installing Software on the Exalytics Machine

2.1.1 Documents to Review

As you prepare to install software on the Exalytics Machine, do the following:

• Review the Oracle Business Intelligence chapter in the Oracle Fusion Middleware Release Notes for the Linux x86-64 platform, to ensure that you understand the differences between Oracle Business Intelligence and its documented functionality, and any other issues that apply to the current release.

• Review the Oracle TimesTen In-Memory Database Release Notes to ensure that you understand the differences between TimesTen and its documented functionality, and any other issues that apply to the current release.

• Review Oracle Fusion Middleware Owner's Guide for Oracle Exalytics In-Memory Machine for Linux x86-64 to ensure that you have properly configured and commissioned the Exalytics Machine in your data center.

• Review Chapter 1, "Installation Overview" to ensure that you understand the options and architecture related to installing software on the Exalytics Machine.

2.1.2 Prerequisites for Installing on the Exalytics Machine

The following prerequisites must be met before installing Oracle Business Intelligence on the Exalytics Machine:

• The Exalytics Machine has been racked and mounted in a data center.

• The Exalytics Machine is configured with the base operating system at the factory.

  If you need assistance, then Oracle provides Advanced Customer Services for installing software on the Exalytics Machine.

• The network configuration script has been run and the computer is accessible from the network.

• A supported database is available (but not on Oracle Exalytics) and accessible from the Exalytics Machine to host the schemas that are required by the software installation and that you create as part of the installation process. Ensure that the database is running during the installation and that the database is not hardened for security purposes. Installing Oracle Business Intelligence against a hardened database is not supported.

  For information about hardened databases, see Oracle Database Vault Administrator's Guide.

• You have access to the internet from a computer (not necessarily the Exalytics Machine) to download required packages.

2.2.1 Step 1: Creating the User on the Operating System

On the operating system, create a user with a name such as "oracle" and an appropriate password. The procedures throughout this section assume both a user and a group named "oracle".

2.2.2 Step 2: Creating the Inventory for TimesTen

Create the inventory for TimesTen after you log in as the root user by entering the following commands:

mkdir /etc/TimesTen
chmod 770 /etc/TimesTen
chgrp oracle /etc/TimesTen
touch /etc/TimesTen/instance_info
chmod 770 /etc/TimesTen/instance_info
chgrp oracle /etc/TimesTen/instance_info

Ensure that the group who runs the script has write access to the /etc/TimesTen directory.

2.2.3 Step 3: Downloading Oracle Files into the Directory Structure

To download files into the directory structure:

1. Download the following required software installers from the Media Pack for Oracle Exalytics under Oracle Business Intelligence software for Linux X86-64 on Oracle eDelivery at the following location:

   http://edelivery.oracle.com/

   • Oracle BI Enterprise Edition 11g Release 11.1.1.6

   • Repository Creation Utility that corresponds with Oracle BI EE Release 11.1.1.6

   • TimesTen Release 11.2.2.2

   • Oracle WebLogic Server 10g Release 10.3.6

2. As the user who owns the installation of the Exalytics software, create a directory structure such as the following for staging the software installation programs, if the user name is "oracle" and the home directory is /home/oracle:

   • /home/oracle/EXALYTICS_RCU

     Copy the rcuHome.zip file for the Repository Creation Utility (RCU) into this directory and unzip it.

   • /home/oracle/EXALYTICS_INSTALLERS/bi

     Copy the Oracle BI EE installation ZIP files into this directory and unzip them using the following command. The -q parameter reduces the number of lines of output that are sent to the console.

     unzip -q '*.zip'

     The unzip process creates a subdirectory called bishiphome that contains subdirectories with names of Disk1 through Disk5.

   • /home/oracle/EXALYTICS_INSTALLERS/tt

     Copy the TimesTen for Exalytics distribution file into this directory and do not unzip it. The file has an extension such as .zip or .tar.gz. The installation scripts work with a file of either extension.

   • /home/oracle/EXALYTICS_INSTALLERS/wls

     Obtain the ZIP file for Oracle WebLogic Server on 64-bit Linux and extract the wls1036_linux64.bin file into this directory. If the file is not executable, then use the following command to allow it to be executed:

     chmod +x wls1036_linux64.bin

   • /home/oracle/EXALYTICS_INSTALL_LOG

     The installation scripts use this directory for storing the log files from the installation. You use these log files for troubleshooting, as described in Section 2.3, "Troubleshooting the Installation and Configuration Processes."

   • /home/oracle/EXALYTICS_MWHOME

     The installation scripts use this directory as the target directory for the Oracle BI EE installation, which is known as the Middleware Home. In this guide, this directory is referred to as EXALYTICS_MWHOME.

   • /home/oracle/EXALYTICS_INSTALL_TEMP

     The installation scripts use this directory for storing temporary files.

2.2.4 Step 4: Creating the Database Schemas

Follow the instructions in the "Create Database Schemas Using the Repository Creation Utility (RCU)" section in Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence.

You must first create required Oracle Business Intelligence schemas in a database (note that the database must not be hardened). You use a tool called the Repository Creation Utility (RCU) to create these schemas with the appropriate permissions and data.

Before you begin using RCU, review the "Repository Creation Utility (RCU) Requirements" section in the Oracle Fusion Middleware System Requirements document:

http://www.oracle.com/technetwork/software/products/ias/files/fusion_requirements.htm

This section contains important information about your system and component-specific database requirements that should be met before you run RCU.

Ensure that you record the following details, because you use them later in the installation process:

• The database connection details in the following form:

  host-name:port-number:service-name

• The names and passwords of the schemas that you create, which have names such as prefix_BIPLATFORM and prefix_MDS.

2.2.5 Step 5: Editing the Properties File

Edit carefully the properties file that contains values that the installation scripts use. The file is named bim-setup.properties and is stored in the following directory:

/home/oracle/EXALYTICS_INSTALLERS/bi/bishiphome/Disk1/bimachine/scripts

Keep the following points in mind as you edit the file:

• Ensure that you use proper spelling and capitalization in the lines of the file.

• The file contains comments that provide details on how to edit the values to be appropriate for your system.

• In the file, specify the port numbers that you want to use for the Administration Server and the Managed Server using the bim.bi.wls.admin.port and bim.bi.wls.managed.port properties. Before specifying the port numbers in the file, ensure that the ports are empty and unoccupied. The installation scripts pass values from the bim-setup.properties file to the staticports.ini file.

  The staticports.ini file is located in the following directory:

  /home/oracle/EXALYTICS_INSTALLERS/bi/bishiphome/Disk1/bimachine/scripts/templates/staticports.ini

  Avoid manually editing the staticports.ini file.

• Ensure that the file system does not include a bim.mw.home directory.

• In this release, the root directory on the system does not need subdirectories for the Repository Creation Utility or for patches.

• For information on the connect strings that you use for the schemas that you created with RCU, see "Specifying a Database Connect String" in Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence.

The following is the contents of the properties file:

#########################################################
# Exalytics Machine Properties
#########################################################
 
#########################################################
[Generic properties to be used across all the Oracle Products]
#bim.installers.root=The directory should contain following directories [bi, rcu, tt, wls, patches].
#bim.mw.home=This directory has all the Oracle Software binaries installed such as bi, wlserver_10.3, tt and so on.
#The directory of bim.mw.home should be a mounted drive so that Oracle bits can be moved to shared storage later for scale out.
#bim.temp.dir=This directory is used for Oracle Software installation/configuration.
#bim.orainst.loc=The location of oraInst.loc to use. If not set, /etc/oraInst.loc assumed.
 
#########################################################
bim.installers.root=/home/oracle/EXALYTICS_INSTALLERS
bim.mw.home=/home/oracle/EXALYTICS_MWHOME
bim.temp.dir=/home/oracle/EXALYTICS_INSTALL_TEMP
bim.orainst.loc=/etc/oraInst.loc
 
#########################################################
# [RCU/BI specific properties]
#bim.db.connectionstring=Oracle Database connection string in the format of hostname:port:service
#bim.db.bi.schema.user=Schema User for BIPLATFORM
#bim.db.bi.schema.pwd=Password for the bim.db.bi.schema.user
#bim.db.mds.schema.user=Schema User for MDS
#bim.db.mds.schema.pwd=Password for the bim.db.mds.schema.user
#########################################################
 
#bim.db.type=Database type. Specify one of ORACLE, SQLSERVER or IBMDB2. The default is ORACLE.
bim.db.type=
bim.db.connectionstring=IP-address
bim.db.bi.schema.user=EX111111_BIPLATFORM
bim.db.bi.schema.pwd=welcome1
bim.db.mds.schema.user=EX111111_MDS
bim.db.mds.schema.pwd=welcome1
 
#########################################################
# [BI specific properties]
#bim.bi.domain.host=
#bim.bi.domain.admin.user=
#bim.bi.domain.admin.pwd=
#bim.bi.wls.admin.port=
#bim.bi.wls.managed.port=
 
#########################################################
bim.bi.domain.host=host-name
bim.bi.domain.admin.user=biadmin
bim.bi.domain.admin.pwd=welcome1
bim.bi.wls.admin.port=7001
bim.bi.wls.managed.port=9704
 
#########################################################
# [etc properties]
#bim.install.log.dir=The location of log files being generated during installation.
 
#########################################################
bim.install.log.dir=/home/oracle/EXALYTICS_INSTALL_LOG

2.2.6 Step 6: Preparing to Run the Installation Scripts

To prepare to run the installation scripts:

1. Download the Apache Ant software, which the installation scripts require. You can download Release 1.8.2 of Ant using the ".zip" archive from the following location:

   http://ant.apache.org

2. Install the Apache Ant software by simply unzipping the files to a directory with a name such as /home/oracle/ANT/apache-ant-1.8.2.

3. Configure the ANT_HOME and PATH environment variables for the shell that is used to call the Oracle Exalytics installation scripts, as shown in the following sample commands. Start a shell (such as csh), set the appropriate environment variables, and remain in that same shell session to enter all the other commands that are related to the installation process.

   setenv ANT_HOME /home/oracle/ANT/apache-ant-1.8.2
   setenv PATH $ANT_HOME/bin:$PATH
   

4. Download the Java Developer's Kit (JDK), which the installation scripts require. You can download JDK 6 Update 29 for Linux 64-bit from the following location:

   http://www.oracle.com/technetwork/java/javase/downloads/index.html

5. Copy the JDK distribution installer to a directory with a name such as:

   /home/oracle/JDK

   Install the JDK by entering a command such as the following:

   ./jdk-6u29-linux-x64.bin

   This command creates a directory with a name such as the following:

   /home/oracle/jdk1.6.0_29

6. In the same shell session in which you created the environment variables for Apache Ant, configure the JAVA_HOME and PATH variables for the JDK, as shown in the following example:

   setenv JAVA_HOME /home/oracle/JDK/jdk1.6.0_29
   setenv PATH $JAVA_HOME/bin:$PATH
   

7. The Oracle inventory directory is used by the installation program to keep track of all Oracle products installed on the computers running. The inventory directory is stored in a file called oraInst.loc (on UNIX and Linux). Create the inventory for the Oracle Universal Installer for Oracle Business Intelligence using the following steps. In these steps, the assumption is that the Oracle Inventory exists in the /home/oracle/oraInventory directory and that the group of the user installing the software and owning the location where the software is installed is named "oracle".

   1. Log in as the root user in the same shell session in which you created the environment variables.

   2. Enter the following commands:

      cd /etc
      touch oraInst.loc
      

   3. Using a text editor, add the following lines to the oraInst.loc file, if the group that you use is named "oracle":

      inventory_loc=/home/oracle/oraInventory
      inst_group=oracle
      

   4. Save the oraInst.loc file.

   5. Enter the following commands in the same shell session to have the "oracle" group become the owner of the oraInst.loc file:

      chown oracle:oracle oraInst.loc
      chmod 664 oraInst.loc
      

2.2.7 Step 7: Verifying the Checklist

Before running the scripts, ensure that you verify the items in the following checklist:

• You created the inventories in the /etc directory and the oraInventory directory in the /home/oracle directory (if the user name is named "oracle").

• You created the appropriate schemas with the Repository Creation Utility, and the database that contains them is available.

• You created the appropriate directory structures and downloaded and unzipped the appropriate files within those structures.

• You set the installer files (such as for Oracle WebLogic Server) to have the executable permissions where required. (This permission was not automatically applied when you copied the files into the directory structures.)

• You carefully edited the properties file for the script and ensured that it contains no errors.

• You installed the ANT and JDK components and properly set their environment variables.

2.2.8 Step 8: Running the Scripts

To run the scripts:

1. Log in to the Exalytics Machine as the user that you created in Section 2.2.1, "Step 1: Creating the User on the Operating System."

2. Change to the directory that contains the Oracle Exalytics software, such as the following one:

   /home/oracle/EXALYTICS_INSTALLERS/bi/bishiphome/Disk1/bimachine

3. Using the same shell session that you used in Section 2.2.6, "Step 6: Preparing to Run the Installation Scripts," run the main installation script, which is named setup.sh, using a command such as the following one:

   ./setup.sh /home/oracle/EXALYTICS_INSTALLERS/bi/bishiphome/Disk1/bimachine/scripts/bim-setup.properties

   You can store the properties file in any directory when you update it as specified in Section 2.2.5, "Step 5: Editing the Properties File" and specify the full path name when you run the installation script.

The installer scripts for Oracle Exalytics perform the following tasks:

• Install Oracle WebLogic Server.

• Perform a Software-Only Installation of Oracle Business Intelligence.

  For information, see "Software Only Install" in Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence.

• Create the BI Domain.

• Enable the HardwareAcceleration MBean attribute.

  If you must modify the attribute, then you can update it as described in Section 2.3.4, "Manually Setting the HardwareAcceleration MBean Attribute."

• Install TimesTen.

• Make configuration changes in the opmn.xml file to point to the TimesTen libraries.

• Configure the sys.odbc.ini file for TimesTen and the odbc.ini file for Oracle Business Intelligence with DSN details for TimesTen.

2.2.9 Step 9: Verifying the Installation

To verify that the installation is successful, you open a Web browser and attempt to display the following URLs. If you can display and interact with the pages at the following URLs, then the installation succeeded.

• Oracle BI Enterprise Edition:

  http://server-name:9704/analytics

• Oracle WebLogic Server Console:

  http://server-name:7001/console

• Fusion Middleware Control:

  http://server-name:7001/em

2.3.1 Resolving Issues with the Installation

If you have any issues installing software on the Exalytics Machine, check the following items:

• Ensure that the database in which you ran the Repository Creation Utility to create the schemas is running.

• Check the contents of the bim-setup.properties file to ensure that all entries are accurate with no misspellings.

• If the installation scripts fail, then perform the following steps:

  1. Deinstall the TimesTen software.

  2. Delete the Middleware Home for Oracle Business Intelligence.

  3. Verify the contents of the bim-setup.properties file, as described in Section 2.2.5, "Step 5: Editing the Properties File."

     During the installation process, certain properties in the bim-setup.properties file (such as those related to passwords) are removed for security reasons. Before attempting to run the installation scripts again, ensure that you edit the file appropriately.

  4. Restart the installation process.

2.3.2 Viewing Log Files

After installing the software, you can check the log files for Oracle WebLogic Server, Oracle Business Intelligence, and TimesTen in the /home/oracle/EXALYTICS_INSTALL_LOG and /home/oracle/oraInventory/logs directories. The files have names such as tt_install.log for TimesTen.

Consult the bim-setup.log file in the log directory to see the sequence of steps for the task flows that the installation scripts execute. The detailed log files for Oracle Business Intelligence configuration are stored in the oraInventory location that is specified in the oraInst.loc file.

If you encounter errors during installation and run the scripts multiple times, then you might want to save copies of the log files so that they are not overwritten during each installation attempt. The log files to save are wls_install.log, tt_install.log, and bim-setup.log. You can use one of the following means to save the files:

• Specify a unique directory for the log files using the bim-setup.properties file before you run the installation scripts.

• Store the log files in a compressed file, such as ZIP.

• Create a separate directory or save copies of the log files.

The log files that Oracle Universal Installer creates have unique names that include time stamps, so these files are not overwritten with each installation attempt,

2.3.3 Reinstalling Software on the Exalytics Machine

You might want to reinstall the software. The installer does not allow reinstallation of Oracle Business Intelligence in a directory that contains another Oracle Business Intelligence installation on an Exalytics Machine.

To reinstall Oracle Business Intelligence in the same directory as before:

1. Deinstall the software as described in Chapter 4, "Deinstalling Software on the Exalytics Machine."

2. Reboot the computer to ensure that if any processes are running, they are stopped.

3. If you used the Repository Creation Utility to create the BISHIPHOME and MDS schemas, then either drop the schemas or use a new prefix to create new schemas.

4. Delete the /etc/TimesTen/* files.

5. Return to this chapter and follow the installation instructions again.

2.3.4 Manually Setting the HardwareAcceleration MBean Attribute

The HardwareAcceleration MBean attribute specifies whether you are using the Exalytics Machine, as described in the following procedure. This MBean attribute is turned on automatically when you run the script to install Oracle Business Intelligence on the Exalytics Machine. The MBean attribute sets the ORACLEHARDWAREACCELERATION parameter in the NQSConfig.ini file and the OracleHardwareAcceleration element in the instanceconfig.ini file.

To specify the use of the Exalytics Machine using the System MBean Browser:

1. In Fusion Middleware Control, in the Navigator window, expand the WebLogic Domain folder and the bifoundation_domain node.

2. Right-click the AdminServer node and select System MBean Browser.

3. Expand Application Defined MBeans, then expand oracle.biee.admin, then expand Domain: bifoundation_domain.

4. Lock the domain, as follows:

   1. Expand BIDomain and select the BIDomain MBean where group=Service.

   2. Display the Operations tab.

   3. Click the lock link.

5. Display the Attributes tab for the same MBean.

6. Ensure that the HardwareAcceleration attribute is set to true.

7. After applying your changes, release the lock on the domain by displaying the Operations tab and clicking one of the commit operations.

8. Restart Oracle Business Intelligence.

2.3.5 For More Information

For additional information, see the following:

• Section 7.4, "Troubleshooting the Highly Available Deployment."

• Section 4.7, "Troubleshooting the Installation and Configuration Processes of Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence