This section consists of the following topics:
Parent topic: Installing Software on an 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.
Network configuration is complete and the computer is accessible from the network.
If installing Oracle Business Intelligence Enterprise Edition 11.1.1.7.0, download and install JAVA 6 by performing the following steps:
Navigate to http://www.oracle.com/technetwork/java/javase/downloads/index.htm
l
Scroll to the "Previous Releases - Java Archive" section at bottom of the page, and click Download.
Click Java SE6.
Click Java SE Development Kit 6u45.
Click and download jdk-6u45-linux-x64.rpm.bin.
To install the rpm file, enter the following command as the root user:
# ./jdk-6u45-linux-x64.bin
Set JAVA_HOME to the location where you installed JAVA 6. For example, if you installed JAVA 6 in the /usr/java/jdk1.6.0 directory, you set JAVA_HOME=/usr/java/jdk1.6.0_45.
If installing Oracle Business Intelligence Enterprise Edition 11.1.1.9.0, download and install JAVA 7 by performing the following steps:
Navigate to http://www.oracle.com/technetwork/java/javase/downloads/index.html
Scroll to the "Previous Releases - Java Archive" section at bottom of the page, and click Download.
Click Java SE 7.
Click Java SE Development Kit 7u76.
Click and download the jdk-7u79-linux-x64.rpm.
To install the rpm file, enter the following command as the root user:
# rpm -Uvh <rpm name>
Set JAVA_HOME to the location where you installed JAVA 7. For example, if you installed JAVA 7 in the /usr/java/jdk1.7.0 directory, you set JAVA_HOME=/usr/java/jdk1.7.0_80+.
You have installed Oracle Exalytics Release 2.2 (Oracle Exalytics Base Image 2.0.0.2.el6).
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.
A supported database (For example: Oracle Database In-Memory) is available and accessible from the Exalytics Machine to host the schemas that are required by the Exalytics Domain Management Utility 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.
Before you install software on the Exalytics Machine, you must run configuration scripts to verify the software and network configurations of the Exalytics Machine.
This section consists of the following topics:
You run the exalytics_CheckSWProfile
script to verify the current Exalytics software and storage configurations.
To verify Exalytics software and storage configurations:
Parent topic: Verifying Configuration of the Exalytics Machine
You run the exalytics_imageinfo
script to verify the current Exalytics image and version details.
To verify the Exalytics image information:
Parent topic: Verifying Configuration of the Exalytics Machine
Installing software on an Exalytics Machine involves running the Exalytics Domain Management Utility. The Exalytics Domain Management Utility provides an automatic way of installing software on the Exalytics Machine by performing the following tasks:
Creating the RCU BIPLATFORM and MDS database schemas (if needed)
Installing Oracle WebLogic Server
Performing a Software Only install of Oracle Business Intelligence
Installing Oracle Essbase Suite (if needed)
Creating an Oracle Business Intelligence instance
Configuring the Oracle Business Intelligence domain
If required, the Exalytics Domain Management Utility also provides an automated way of installing Oracle TimesTen In-Memory Database and configuring communication with a software install of Oracle BI EE.
The steps in the process are:
If you are installing the software on an Exalytics Machine with the Release 1 Patchset 3 Base Image or later, a user named "oracle" and a group named "oinstall" already exists. You next create a password for the user.
To create a password:
Note:
You must use the same operating system user to create multiple Exalytics domains on a single Exalytics Machine.
The procedures throughout this section assume a user named "oracle" and a group named "oinstall".
Note:
To add a different user and group, enter the following commands as root user:
groupadd
<name of the group>
useradd -g
<name of the group> <name of the user>
If you are installing Oracle TimesTen, then create the inventory for Oracle TimesTen after you log in as the root user by entering the following commands:
mkdir /etc/TimesTen chmod 770 /etc/TimesTen chgrp oinstall /etc/TimesTen touch /etc/TimesTen/instance_info chmod 770 /etc/TimesTen/instance_info chgrp oinstall /etc/TimesTen/instance_info
Ensure that the group who runs the script has write access to the /etc/TimesTen directory.
If you are installing Oracle TimesTen, then set resource limits for Oracle TimesTen by performing the following tasks:
To set the resource limits for Oracle TimesTen:
If not yet done, assign user limits to new users. User limit is the maximum amount of processors a user can run at the same time. When you add a new user, the user is assigned a low user limit by default. To ensure the new user can run enough processors, you must assign new user limits.
To assign user limits to a new user:
Before installing the software you must download the required files into an organized Installers directory structure. Please note that the directory structures detailed in Step 3 below are not mandatory, but is just an example. You can choose any structure to organize the files.
For information about which version of the software to download, see the Oracle Exalytics Certification Matrix at the following location:
http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html
To download the installation files into the directory structure:
Figure 6-2 illustrates the Installers directory structure.
Figure 6-2 Installers Directory Structure
You next create an input properties file. You reference the input properties file when running the command to create an Exalytics domain. The input properties file contains the following parameters:
Location of the "Installers" directory. See Step 3 in Downloading the Oracle Installation Files into a Staging Directory Structure.
Install group of the user performing the installation. See Creating a Password on the Operating System.
To create an input properties file:
The procedures throughout this section assume the name of the input properties file as "input.properties" and the location of the file at /home/oracle.
Open a text editor.
Add the following lines in the text editor:
EXALYTICS_INSTALLERS_DIR=<location of your installers directory>
For example: EXALYTICS_INSTALLERS_DIR=/home/oracle/Installers
INST_GROUP=<the install group of the user performing the install>
For example: INST_GROUP=oinstall
The following is an example of an input properties file:
EXALYTICS_INSTALLERS_DIR=/home/oracle/Installers
INST_GROUP=oinstall
Save the file in a directory of your choice.
To run the Exalytics Domain Management Utility in silent mode, you must provide additional parameters in the input properties file. An example of the silent mode properties file named noprompts.exalytics.properties is located in the /opt/exalytics/domainconfig/properties directory.
The following is an example of the silent mode input properties file:
Note:
You can optionally exclude passwords from the response file. This prompts users to enter the required passwords when they run the input properties file in silent mode.
############################################################################### # This example input properties file allows a "silent" install without any prompts # # EXALYTICS_INSTALLERS_DIR - the repository containing all the shiphome installers # # # Download and Copy the WebLogic Linux X64 installer from Oracle EDelivery to the SHIPHOME_INSTALLERS_DIR/wls directory # Download and Copy the BISHIPHOME zip files from Oracle EDelivery to the SHIPHOME_INSTALLERS_DIR/bi directory and unzip the zips # Download and Copy the RCU zip file from Oracle EDelivery to the SHIPHOME_INSTALLERS_DIR/rcu directory and unzip it # # # INST_GROUP - The group name of the installing user eg. oinstall ################################################################################ EXALYTICS_INSTALLERS_DIR=/home/oracle/EXALYTICS_INSTALLERS INST_GROUP=oinstall ################################################################################ # Admin Credentials ################################################################################ ADMIN_USER_NAME=weblogic ADMIN_PASSWORD=welcome1 ################################################################################ # Schema details: # These are only required for "add_domain" action ################################################################################ # Specify whether you want to create new schemas or use existing schemas # Can be true or false. If you say yes, then the script will create the schemas using RCU DATABASE_CREATE_SCHEMAS=false #Connection string to the database DATABASE_CONNECTION_STRING=host:1521:orcl #Database type DATABASE_TYPE='Oracle Database' #------------------------------------------------------------------------------- # The following properties are only required if DATABASE_CREATE_SCHEMAS=false, ie. use existing schemas #------------------------------------------------------------------------------- DATABASE_SCHEMA_USERNAME_BI=EXAMPLE_BIPLATFORM DATABASE_SCHEMA_PASSWORD_BI=welcome1 DATABASE_SCHEMA_USERNAME_MDS=EXAMPLE_MDS DATABASE_SCHEMA_PASSWORD_MDS=welcome1 #------------------------------------------------------------------------------- # The following properties are only required if DATABASE_CREATE_SCHEMAS=true, ie. create new schemas using RCU #------------------------------------------------------------------------------- DATABASE_SCHEMA_CREATOR_USERNAME=sys DATABASE_SCHEMA_CREATOR_PASSWORD=welcome1 DATABASE_SCHEMA_CREATOR_ROLE=sysdba DATABASE_SCHEMA_PREFIX=EXAMPLE DATABASE_SCHEMA_PASSWORD_BI=welcome1 DATABASE_SCHEMA_PASSWORD_MDS=welcome1 ########################################################################################################## # These are only required for "scaleout_domain" action ########################################################################################################## DOMAIN_HOSTNAME=myhost.example.com DOMAIN_PORT=12000 #Other prompts CONFIGURE_ESSBASE_SUITE=true INSTALL_EXALYTICS_IN_MEMORY_SOFTWARE=true
Before running the configuration script, ensure that the user who is running the script has write permissions to the /u01 directory.
If the user cannot write to the /u01 directory, then, as root user, enter the following commands to change permissions:
chown <name of the user>:<name of the group> /u01
chmod 775 /u01
For example:
chown oracle:oinstall /u01
chmod 775 /u01
You run the Exalytics Domain Management Utility to create an Exalytics domain.
To create an Exalytics domain:
Log in to the Exalytics Machine as the user "oracle" or the new user you created. See Creating a Password on the Operating System.
To create an Exalytics domain, enter the following command:
/opt/exalytics/bin/exalytics-domain-management.sh --action=add_domain --input=<location and name of the input properties file> --domain=<domain_name>
For example:
/opt/exalytics/bin/exalytics-domain-management.sh --action=add_domain --input=/home/oracle/Installers/input.properties --domain=menlo
When prompted by the Exalytics Domain Management Utility, perform the following tasks:
Enter the user name and password you want to use for the Oracle WebLogic Server administrator.
Select a database type from the following list:
Oracle Database
Microsoft SQL Server
IBM DB2
Choose whether you want to create new schemas or use existing schemas.
If you are creating new schemas, enter the following information:
Database connect string (in the host: port: servicename format)
For example: oracle.com:1521:orcl
sys/dba user name and password
sys/dba role
Prefix for the schemas
BIPLATFORM and MDS schema passwords
If you are using existing schemas, enter the following information:
Database connect string (in the host:port:servicename format)
For example: oracle.com:1521:orcl
Real Application Clusters Database (RAC DB) connect string in the host1:port1:instance1^host2:port2:instance2@servicename format.
For example:
custdbhost1:1521:custdb1^custdbhost2:1521:custdb2@orcl
BIPLATFORM schema user name and password
MDS schema user name and password
Choose whether you want to install and configure Oracle Essbase Suite.
If you choose this option, the Exalytics Domain Management Utility automatically installs and configures Oracle Essbase.
Note:
To install Oracle BI Applications on the Exalytics Machine, you must install and configure Oracle Essbase Suite. See Installing and Configuring Oracle BI Applications on an Exalytics Machine.
Choose whether you want to install Oracle Exalytics In-Memory Software.
If you choose to install Oracle Exalytics In-Memory Software, the HardwareAcceleration MBean attribute is enabled.
The Exalytics Domain Management Utility performs the following tasks:
Creates schemas (if chosen)
Installs and configures Oracle BI EE, Oracle WebLogic Server, Oracle Essbase Suite (if needed).
After the installation completes, the status of the domain is displayed as follows:
************************************************************************** Status report for the Exalytics Domain: menlo * * ************************************************************************** ========================================================================== OPMN Managed Processes Status ========================================================================== OPMN status report as of Thu Nov 07 14:12:33 2013 Processes in Instance: menlo ---------------------------------+--------------------+---------+--------- ias-component | process-type | pid | status ---------------------------------+--------------------+---------+--------- essbasestudio1 | EssbaseStudio | 23985 | Alive essbaseserver1 | Essbase | 15518 | Alive coreapplication_obiccs1 | OracleBIClusterCo~ | 14823 | Alive coreapplication_obisch1 | OracleBIScheduler~ | 15418 | Alive coreapplication_obijh1 | OracleBIJavaHostC~ | 15189 | Alive coreapplication_obips1 | OracleBIPresentat~ | 14994 | Alive coreapplication_obis1 | OracleBIServerCom~ | 14866 | Alive ========================================================================== WebLogic Servers Status ========================================================================== WebLogic status report as of Thu Nov 07 14:12:33 2013 Servers in this host for WebLogic domain bifoundation_domain: ------------+-------------------------+-----------+-------+--------- Server name | type | pid | port | status ------------+-------------------------+-----------+-------+--------- AdminServer | WebLogic AdminServer | 18223 | 12200 | RUNNING bi_server1 | WebLogic Managed Server | 19585 | 12201 | RUNNING ========================================================================== The script execution took 40 minutes and 13 seconds. For details, see the log file /u01/app/oracle/product/exalytics/logs/exalytics_domain_menlo_add_domain_2013-11-07_125423.log
If required, you can use the Exalytics Domain Management Utility to install Oracle TimesTen on an existing Exalytics domain.
For information on the Installers directory structure and where to download Oracle TimesTen installers, see Downloading the Oracle Installation Files into a Staging Directory Structure.
To install Oracle TimesTen:
Log in to the Exalytics Machine as the user "oracle" or the new user you created. See Creating a Password on the Operating System.
Verify the status of the existing domain. The domain should be up and running. See Viewing Status of an Exalytics Domain.
To install Oracle TimesTen, enter the following command:
/opt/exalytics/bin/exalytics-domain-management.sh --action=add_timesten --input=<location and name of the input properties file> --domain=<name of existing domain>
For example:
/opt/exalytics/bin/exalytics-domain-management.sh --action=add_timesten --input=/home/oracle/Installers/input.properties --domain=menlo
The Exalytics Domain Management Utility performs the following actions:
After the installation is complete, the following message is displayed:
[LOGMSG] [11-12-13 11:11:10] [INFO] [menlo] [add_timesten] TimesTen Installed Successfully
If required, you can also use the Exalytics Domain Management Utility to install Oracle Database In-Memory on an existing Exalytics domain.
For information on the Installers directory structure and where to download Oracle TimesTen installers, see Downloading the Oracle Installation Files into a Staging Directory Structure.
To verify that the installation was successful, you run the <list_domain> command of the Exalytics Domain Management Utility. The command displays all existing domains. If the domain is displayed, then the installation succeeded. For instructions on running the <list_domain> command, see Listing Exalytics Domains.
If the installation is successful, the output looks similar to the following:
Exalytics Domain: menlo ============================================================ Node type: Primary node Provisioning status: Completed Middleware Home: /u01/app/oracle/product/exalytics/exalyticsdomains/menlo/fmw BI Instance Home: /u01/app/oracle/product/exalytics/exalyticsdomains/menlo/instances/instance1 | Application URLs | ------------------- Oracle Enterprise Manager: http://<server-name>:12000/em Oracle WebLogic Admin Console: http://<server-name>:12000/console Oracle Business Intelligence: http://<server-name>:12001/analytics Oracle BI Publisher : http://<server-name>:12001/xmlpserver ------------ | WebLogic | ------------ Domain Home: /u01/app/oracle/product/exalytics/exalyticsdomains/menlo/user_projects/domains/bifoundation_domain Admin Server Host: <server-name> Admin Server Port: 12000 BI Managed Server Host: <server-name> BI Managed Server Port: 12001 ------------ | TimesTen | ------------ TimesTen enabled: Yes Timesten Instance Name: ttmenlo Instance Directory: /u01/app/oracle/product/exalytics/exalyticsdomains/menlo /TimesTen/ttmenlo Timesten Daemon Port: 12158 Timesten Server Port: 12159 ----------------- | Essbase Suite | ----------------- Essbase Suite enabled: Yes Workspace: http://<server-name>:12001/workspace APS: http://<server-name>:12001/aps EAS Console: http://<server-name>:12001/easconsole Essbase Port: 12016 ============================================================ Found 1 domain(s) in total
The postinstallation tasks vary depending on whether you are deploying on multiple computers, as described in Deploying Oracle Exalytics for High Availability. The tasks include updating files and configuring an ODBC connection.
For a single-node installation, the Exalytics Domain Management Utility performs many of the configuration tasks. For a multiple node system, you must perform the configuration tasks manually. The sections of this chapter indicate on which computers to perform the tasks.
Note:
If you are deploying software on a Exalytics Machine configured for virtualization, postinstallation tasks and various parameters may vary.
The section includes the following topics:
Perform this task one time regardless of the number of computers in the cluster.
You must install the Oracle Business Intelligence Administration Tool, Oracle Business Intelligence Job Manager, and Oracle Business Intelligence Catalog Manager on a Windows computer. See "Installing and Deinstalling Oracle Business Intelligence Client Tools" in Installing and Configuring Oracle Business Intelligence.
Perform the following steps to create a boot.properties file for the Administration Server. This file enables the Administration Server to start without prompting you for the administrator user name and password.
Perform this task on each computer in the cluster.
To create boot.properties file:
After making configuration changes, you stop and start components on the Exalytics Machine to enable those changes to take effect.
You run the Exalytics Domain Management Utility to start and stop the Exalytics domain. When you start a primary or scaled-out Exalytics domain, all components on the domain start. If Oracle TimesTen is installed, the Oracle TimesTen Server starts. Similarly, when you stop a primary or scaled-out Exalytics domain, all components on the domain stop. If Oracle TimesTen is installed, the Oracle TimesTen Server stops. See Starting and Stopping an Exalytics Domain.
You run the daemon configuration scripts to enable Oracle TimesTen services to start each time you restart the Exalytics Machine.
Perform this task on each computer in the cluster.
Run the daemon configuration scripts for Oracle TimesTen as root, using the following command:
<install_location>/TimesTen/tt1122/bin/setuproot -install
Perform this task on each computer in the cluster.
When you configure memory settings, keep the following in mind:
If an Oracle TimesTen In-Memory Database larger than 256 GB is required, then you must configure and use large pages.
See "Large pages" in Oracle TimesTen In-Memory Database Installation Guide for additional information on defining the Oracle TimesTen In-Memory Database in the DSN and on editing the limits.conf file for kernel parameters and semaphores.
The largest recommended size for a Oracle TimesTen In-Memory Database on a single machine is a total of 800 GB for an X2-4 Exalytics Machine, and 1800 GB for an X3-4 Exalytics Machine, which includes the values for the PermSize and TempSize attributes.
Note:
Increasing large page settings for more memory will result in other applications (Oracle BI EE, Oracle Essbase) unable to allocate memory. Exceeding more than 80% of the physical memory is not recommended. Depending on how much more PermSize memory is required, you can transfer memory from the TempSize.
You can configure and activate the number of large pages by setting the nr_hugepages parameter in the /etc/sysctl.conf file. For example, for an 800 GB Oracle TimesTen In-Memory Database, you must specify greater than 410122 pages to create an 800 GB store based on the following calculation:
(PermSize + TempSize + LogBufMB + 20) / hugepage_size [All in bytes] (400*1024*1024*1024) + (400*1024*1024*1024) + (1024*1024*1024) + (20*1024*1024) = 860088172544 860088172544 / (2 * 1024 * 1024) = 410122
For example, to allow for spare capacity, modify the following setting in the /etc/sysctl.conf file:
vm.nr_hugepages = 410200
then either restart the machine or run the following command as the root user:
/sbin/sysctl –p
Note:
The above calculations are an example for a 800 GB Oracle TimesTen database. Depending on the size of your Oracle TimesTen database deployed and the type of deployment (virtual or non-virtual), you can use different calculations.
Parent topic: Configuring Memory Settings on the Server
You can configure large pages for the Oracle TimesTen In-Memory Database by editing the following file:
<install_location>/TimesTen/tt1122/info/ttendaemon.options
and adding the following line:
-linuxLargePageAlignment 2
Parent topic: Configuring Memory Settings on the Server
After configuring large pages for the Oracle TimesTen In-Memory Database, you can increase the PermSize on existing Oracle TimesTen In-Memory Databases.
To increase PermSize on existing Oracle TimesTen In-Memory Databases:
Disconnect all applications, including Oracle BI EE, from the Oracle TimesTen In-Memory Database.
If needed, change the RAM policy from inUse to Manual.
Unload the RAM memory from the Oracle TimesTen In-Memory Database by executing the following command:
ttAdmin -ramunload
<Your_TT_DSN>
For example:
ttAdmin -ramunload TT_AGGR_STORE
Modify the timesten-install-dir/info/sys.odbc.ini file in the Oracle TimesTen In-Memory Database to increase the PermSize.
Reload the RAM memory in the Oracle TimesTen In-Memory Database, by executing the following command:
ttAdmin -ramload
<Your_TT_DSN>
For example:
ttAdmin -ramload TT_AGGR_STORE
Reconnect all applications, including Oracle BI EE, to the Oracle TimesTen In-Memory Database.
For more information, see the "Oracle TimesTen In-Memory Database". The link to "Oracle TimesTen In-Memory Database Documentation" is available on the Oracle Exalytics Documentation Library.
Parent topic: Configuring Memory Settings on the Server
Perform this task on each computer in the cluster. For the first computer, the Exalytics Domain Management Utility updates the sys.odbc.ini file, then you perform the rest of the task manually.
The Oracle TimesTen In-Memory Databases are defined using a DSN that is contained in the sys.odbc.ini file in the following directory:
<install_location>/TimesTen/tt1122/info
The Exalytics Domain Management Utility automatically updates the sys.odbc.ini file for Oracle TimesTen with a default configuration for the in-memory aggregate store for Oracle Exalytics, as shown in the following excerpts from a sample file on an Exalytics Machine:
[ODBC Data Sources] TT_AGGR_STORE=TimesTen 11.2.2 Driver [TT_AGGR_STORE] Driver=/u01/app/oracle/product/TimesTen/tt1122/lib/libtten.so DataStore=/u01/app/oracle/product/aggregate_store/tt_aggr_store LogDir=/u01/app/oracle/product/aggregate_store/logs DatabaseCharacterSet=AL32UTF8 ConnectionCharacterSet=AL32UTF8 LogFileSize=1024 LogBufMB=1024 LogBufParallelism=16 Preallocate=0 PermSize=25000 TempSize=25000 MemoryLock=4 CkptFrequency=30 CkptLogVolume=0 CkptRate=20 PrivateCommands=1 RecoveryThreads=40
This DSN supports an Oracle TimesTen In-Memory Database of 25GB with overall memory consumption of approximately 50GB. To support larger in-memory data stores, increase the settings of the PermSize and TempSize parameters. To support this DSN definition, the semi-automated installation process creates the following directories on the Exalytics Machine:
On computers other than the first one in the cluster, manually edit the sys.odbc.ini file for Oracle TimesTen to add the DSN definition. Before instantiating this DSN, remove the comment character (#) that the Exalytics Domain Management Utility included for the lines that define the DataStore and LogDir parameters in the sys.odbc.ini file.
The Oracle TimesTen In-Memory Database is instantiated when the first connection is made to the database. Navigate to the bin directory, run the ttIsql utility, and create a user (with a name such as "exalytics" and password such as "welcome1") as shown in the following sample commands:
cd /u01/app/oracle/product/TimesTen/tt1122/bin ./ttIsql connect dsn=TT_AGGR_STORE; create user exalytics identified by welcome1; grant create session to exalytics; grant create table to exalytics; grant select on SYS.OBJ$ to exalytics;
Use the following sample commands to test the connection to the Oracle TimesTen In-Memory Database. There are no tables of data yet configured to return.
connect "DSN=TT_AGGR_STORE;uid=exalytics"; tables; exit
You can use a tool such as SQL Developer on the client computer, if the Windows TimesTen client drivers that are installed can make a connection to the Oracle TimesTen instance that is used for aggregate storage. This tool can allow you to easily view the contents of the Oracle TimesTen In-Memory Database and to create a dummy table that facilitates the mapping of the Oracle TimesTen schema into the physical layer of the repository for Oracle Business Intelligence.
Perform this task on each computer in the cluster. The Exalytics Domain Management Utility performs this task on the first computer.
The Client/Server DSN in Oracle TimesTen spans computer boundaries and the remote Oracle TimesTen server can be configured as part of the DSN. You create the DSN for the two Oracle TimesTen instances by modifying the following file:
/EXALYTICS_MWHOME/instances/instance1/bifoundation/OracleBIApplication/coreapplication/setup/odbc.ini
On the second computer in a cluster, the directory name includes the string "instance2" for the second computer instead of "instance1".
The following provides sample modifications to the file:
[ODBC Data Sources] AnalyticsWeb = Oracle BI Server Cluster = Oracle BI Server SSL_Sample = Oracle BI Server TT_AGGR_STORE = TimesTen 11.2.2 Driver [TT_AGGR_STORE] Driver = /u01/app/oracle/product/TimesTen/tt1122/lib/libttclient.so TTC_SERVER_DSN = TT_AGGR_STORE TTC_SERVER = <tt_hostname> TTC_TIMEOUT = 0
Define the DSN Servers for Oracle TimesTen by modifying the following file:
<install_location>/TimesTen/tt1122/info/sys.ttconnect.ini
The following provides sample modifications to the file:
[tt_hostname] Description=TimesTen Server Network_Address=example1.com TCP_PORT=53397
In a multiple node cluster, you achieve high availability of in-memory aggregates by installing a Oracle TimesTen instance on each computer and ensuring that each instance is aware of the Oracle TimesTen instance on the other computer. You edit the odbc.ini file for Oracle Business Intelligence to contain references to both Oracle TimesTen instances. A two-node cluster might contain the following configuration details in the odbc.ini file on each computer:
[ODBC Data Sources] AnalyticsWeb = Oracle BI Server Cluster = Oracle BI Server SSL_Sample = Oracle BI Server TT_AGGR_STORE1 = TimesTen 11.2.2 Driver TT_AGGR_STORE2 = TimesTen 11.2.2 Driver [TT_AGGR_STORE1] Driver = /u01/app/oracle/product/TimesTen/tt1122/lib/libttclient.so TTC_SERVER_DSN = TT_AGGR_STORE TTC_SERVER = <tt_hostname1> TTC_TIMEOUT = 0 [TT_AGGR_STORE2] Driver = /u01/app/oracle/product/TimesTen/tt1122/lib/libttclient.so TTC_SERVER_DSN = TT_AGGR_STORE TTC_SERVER = <tt_hostname2> TTC_TIMEOUT = 0
With this configuration, edit the sys.ttconnect.ini in the <install_location>/TimesTen/tt1122/info directory to correspond to the odbc.ini file as shown in the following example:
[tt_hostname1] Description=TimesTen Server Network_Address=<fully qualified hostname> TCP_PORT=53397 [tt_hostname2] Description=TimesTen Server Network_Address=<fully qualified hostname> TCP_PORT=53397
You must map all instances of Oracle TimesTen into the Physical layer of the Oracle BI repository. To map the instances, manually create the necessary database, connection pool, and physical schema objects using the Administration Tool. Then, upload the changed repository using the Repository tab of the Deployment page in Fusion Middleware Control.
When mapping an Oracle TimesTen source into the Physical layer of the Oracle BI repository, ensure that the database type and version are set correctly in the Database field of the General tab of the Database dialog. You must also ensure that the Call interface field in the General tab of the Connection Pool dialog is set correctly. For example, for Oracle TimesTen version 11.2.2., use the ODBC 3.5 call interface.
For more information, see the following:
"Setting Up Database Objects and Connection Pools" in Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition
"Configuring Repositories" in System Administrator's Guide for Oracle Business Intelligence Enterprise Edition
Perform this task on each computer in the cluster.
See "Installing and Configuring BI Composer for Oracle BI EE" in Installing and Configuring Oracle Business Intelligence.
Perform this task one time regardless of the number of computers in the cluster if you use IBM DB2 or Microsoft SQL Server.
See "Creating a DSN for IBM DB2 or Microsoft SQL Server" in Installing and Configuring Oracle Business Intelligence.
Perform this task one time regardless of the number of computers in the cluster if you use IBM DB2.
See "Configuring IBM DB2 to Support Multibyte Data" in Installing and Configuring Oracle Business Intelligence.
Perform this task on each computer in the cluster.
See "Configuring Sample Reports for Oracle BI Publisher" in Installing and Configuring Oracle Business Intelligence.
Perform this task once for the domain.
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, then Oracle recommends that you change the default password for security reasons. For complete information on changing the password, see “Changing the Oracle BI Repository Password” in Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.
You can download the Sample Application (full version) from the following location on Oracle Technology Network:
http://www.oracle.com/technetwork/middleware/bi-foundation/obiee-samples-167534.html
If Essbase is installed, you must add the ORACLEHARDWAREACCELERATION TRUE parameter to the essbase.cfg file.
To add the ORACLEHARDWAREACCELERATION TRUE parameter:
Open the essbase.cfg file for editing.
The essbase.cfg file is located in:
ORACLE_INSTANCE/Essbase/essbaseserver1/bin/essbase.cfg
Edit the essbase.cfg file by adding the following parameter:
ORACLEHARDWAREACCELERATION TRUE
Save the file.
Stop and restart the Essbase server by performing the following actions:
Log in to Fusion Middleware Control.
For information, see Section 2.2.2, "Logging into Fusion Middleware Control to Manage Oracle Business Intelligence" in System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
Select Business Intelligence then coreapplication.
Display the Processes page in the Availability tab.
For example, expand Essbase Agents and select essbaseserver1 in the Processes section.
This enables you to start or stop just the Essbase Server process.
Click Stop Selected to stop the selected process.
Click Start Selected to start the selected process.
Enabling bursting optimization mode for BI Publisher significantly enhances the performance of bursting jobs run through the BI Publisher scheduler.
To enable bursting optimization:
To handle high volume jobs (normal scheduled jobs or bursting jobs) configure the system temporary directory and the JMS shared directory in the BI Publisher Administration pages. For best performance configure these temp directories to use RAM disk (for non-clustered environments only) or solid-state drive. For information, see "Setting the System Temporary Directory" and "Configuring the Shared Directory" in the Administrator's Guide for Oracle Business Intelligence Publisher.
You use the Exalytics Domain Management Utility to manage Exalytics domains. You can use the Exalytics Domain Management Utility to start or stop the Exalytics domain, view current status of the domain, list all domains on the Exalytics Machine, and so on.
This section consists of the following topics:
You use the Exalytics Domain Management Utility to start and stop an Exalytics domain. Starting and stopping the Exalytics domain starts and stops all services (WebLogic Administration Server, WebLogic Managed Server, OPMN managed process, and TimesTen) of the installation on the domain.
To start an Exalytics domain:
Log in to the Exalytics Machine as the user "oracle" or the new user you created. See Creating a Password on the Operating System.
To start an Exalytics domain, enter the following command:
/opt/exalytics/bin/exalytics-domain-management.sh --action=start_domain --input=<location and name of the input file> --domain=<domain_name>
For example:
/opt/exalytics/bin/exalytics-domain-management.sh --action=start_domain --input=/home/oracle/Installers/input.properties --domain=menlo
The utility performs the following actions:
Prompts you to enter the user name and password for the Oracle WebLogic Server administrator.
Starts WebLogic Administration Server
Starts WebLogic Managed Server
Starts OPMN and all managed processes
Starts TimesTen (if installed)
All services are started. If the Node Manager was stopped, it restarts.
To stop an Exalytics domain:
Log in to the Exalytics Machine as the user "oracle" or the new user you created. See Creating a Password on the Operating System.
To stop an Exalytics domain, enter the following command:
/opt/exalytics/bin/exalytics-domain-management.sh --action=stop_domain --input=<location and name of the input file> --domain=<domain_name>
For example:
/opt/exalytics/bin/exalytics-domain-management.sh --action=stop_domain --input=/home/oracle/Installers/input.properties --domain=menlo
The utility performs the following actions:
Prompts you to enter the user name and password for the Oracle WebLogic Server administrator.
Stops TimesTen (if installed)
Stops OPMN and all managed processes
Stops WebLogic Managed Server
Stops WebLogic Administration Server
All services are stopped. The Node Manager is not stopped.
Parent topic: Managing Exalytics Domains
To view status of an Exalytics domain:
Log in to the Exalytics Machine as the user "oracle" or the new user you created. See Creating a Password on the Operating System.
To view status of an Exalytics domain, enter the following command:
/opt/exalytics/bin/exalytics-domain-management.sh --action=status --input=<location and name of the input file> --domain=<domain_name>
For example:
/opt/exalytics/bin/exalytics-domain-management.sh --action=status --input=/home/oracle/Installers/input.properties --domain=menlo
The utility performs the following actions:
Prompts you to enter the user name and password for the Oracle WebLogic Server administrator.
Displays the TimesTen (if present), OPMN Managed processes, and WebLogic Administration and Manager server statuses for the domain.
The output looks similar to the following:
******************************************************************* Status report for the Exalytics Domain: menlo ************************************************************************** ========================================================================= TimesTen Status ========================================================================== TimesTen status report as of Wed Nov 6 13:44:26 2013 Daemon pid 11265 port 12158 instance ttmenlo TimesTen server pid 11274 started on port 12159 ------------------------------------------------------------------------ Accessible by group oinstall End of report ========================================================================== OPMN Managed Processes Status ========================================================================== OPMN status report as of Wed Nov 06 13:44:29 2013 Processes in Instance: menlo ---------------------------------+--------------------+---------+--------- ias-component | process-type | pid | status ---------------------------------+--------------------+---------+--------- essbasestudio1 | EssbaseStudio | 14481 | Alive essbaseserver1 | Essbase | 26528 | Alive coreapplication_obiccs1 | OracleBIClusterCo~ | 26527 | Alive coreapplication_obisch1 | OracleBIScheduler~ | 26531 | Alive coreapplication_obijh1 | OracleBIJavaHostC~ | 26525 | Alive coreapplication_obips1 | OracleBIPresentat~ | 26524 | Alive coreapplication_obis1 | OracleBIServerCom~ | 26530 | Alive ========================================================================== WebLogic Servers Status ========================================================================== WebLogic status report as of Wed Nov 06 13:44:29 2013 Servers in this host for WebLogic domain bifoundation_domain: ------------+-------------------------+-----------+-------+--------- Server name | type | pid | port | status ------------+-------------------------+-----------+-------+--------- AdminServer | WebLogic AdminServer | 22224 | 12000 | RUNNING bi_server1 | WebLogic Managed Server | 22685 | 12001 | RUNNING ==========================================================================
Parent topic: Managing Exalytics Domains
You use the Exalytics Domain Management Utility to view a listing of all existing Exalytics domains on the Exalytics Machine.
To list Exalytics domains:
Log in to the Exalytics Machine as the user "oracle" or the new user you created. See Creating a Password on the Operating System.
To list existing Exalytics domains, enter the following command:
/opt/exalytics/bin/exalytics-domain-management.sh --action=list_domains --input=<location and name of the input file>
For example:
/opt/exalytics/bin/exalytics-domain-management.sh --action=list_domains --input=/home/oracle/input.properties
The utility performs the following actions:
Lists all existing domains on the Exalytics Machine and displays the following information for each domain:
Node type
Provisioning status
Location of Middleware Home
Location of BI Instance Home
Application URLs
Host name and port number for WebLogic Administration server
Host name and port number for BI Managed server
Instance name, instance directory, daemon and server port numbers for Oracle TimesTen (if installed)
URLs for Workspace, Analytical Provider Services (APS), Essbase Administration Services (EAS) console, and port number for Oracle Essbase Suite (if installed)
The output looks similar to the following:
Exalytics Domain: menlo ============================================================ Node type: Primary node Provisioning status: Completed Middleware Home: /u01/app/oracle/product/exalytics/exalyticsdomains/menlo/fmw BI Instance Home: /u01/app/oracle/product/exalytics/exalyticsdomains/menlo/instances/instance1 | Application URLs | ------------------- Oracle Enterprise Manager: http://<server-name>:12000/em Oracle WebLogic Admin Console: http://<server-name>:12000/console Oracle Business Intelligence: http://<server-name>:12001/analytics Oracle BI Publisher : http://<server-name>:12001/xmlpserver ------------ | WebLogic | ------------ Domain Home: /u01/app/oracle/product/exalytics/exalyticsdomains/menlo/user_projects/domains/bifoundation_domain Admin Server Host: <server-name> Admin Server Port: 12000 BI Managed Server Host: <server-name> BI Managed Server Port: 12001 ------------ | TimesTen | ------------ TimesTen enabled: Yes Timesten Instance Name: ttmenlo Instance Directory: /u01/app/oracle/product/exalytics/exalyticsdomains/menlo /TimesTen/ttmenlo Timesten Daemon Port: 12158 Timesten Server Port: 12159 ----------------- | Essbase Suite | ----------------- Essbase Suite enabled: Yes Workspace: http://<server-name>:12001/workspace APS: http://<server-name>:12001/aps EAS Console: http://<server-name>:12001/easconsole Essbase Port: 12016 ============================================================ Exalytics Domain: greenwood ============================================================ Node type: Primary node Provisioning status: Completed Middleware Home: /u01/app/oracle/product/exalytics/exalyticsdomains/greenwoo d/fmw BI Instance Home: /u01/app/oracle/product/exalytics/exalyticsdomains/greenwo od/instances/instance1 ------------------- | Application URLs | ------------------- Oracle Enterprise Manager: http://<server-name>:12100/em Oracle WebLogic Admin Console: http://<server-name>:12100/console Oracle Business Intelligence: http://<server-name>:12101/analytics Oracle BI Publisher : http://<server-name>:12101/xmlpserver ------------ | WebLogic | ------------ Domain Home: /u01/app/oracle/product/exalytics/exalyticsdomains/greenwood/us er_projects/domains/bifoundation_domain Admin Server Host: <server-name> Admin Server Port: 12100 BI Managed Server Host: <server-name> BI Managed Server Port: 12101 ------------ | TimesTen | ------------ TimesTen enabled: Yes Timesten Instance Name: ttgreenwood Instance Directory: /u01/app/oracle/product/exalytics/exalyticsdomains/green wood/TimesTen/ttgreenwood Timesten Daemon Port: 12138 Timesten Server Port: 12139 ----------------- | Essbase Suite | ----------------- Essbase Suite enabled: Yes Workspace: http://<server-name>:12101/workspace APS: http://<server-name>:12101/aps EAS Console: http://<server-name>:12101/easconsole Essbase Port: 12116 Found 2 domain(s) in total
Parent topic: Managing Exalytics Domains
You can scale out an existing Oracle Business Intelligence domain for scalability and performance. For instructions on how to scale out an existing Oracle Business Intelligence domain, see Configuring for High Availability.
Parent topic: Managing Exalytics Domains
When you remove the domain on an Exalytics Machine, all components of the domain are automatically removed.
Note:
When removing scaled-out domains, you must first remove all secondary domains before removing the primary node.
For instructions on how to remove an Exalytics domain and deinstall software, see Deinstalling Business Intelligence Software on the Exalytics Machine.
Parent topic: Managing Exalytics Domains
This section provides the following information on troubleshooting:
If you have any issues installing software on the Exalytics Machine, check the following items:
Check the networking configuration of the machine including the /etc/hosts file.
If the Exalytics Domain Management Utility fails, then perform the following steps:
Check the log files in the /u01/app/oracle/product/exalytics/logs directory. See Viewing Log Files.
Review and fix the error. Depending on the type of error, rerun the Exalytics Domain Management Utility.
Note:
If the list_domains command shows the Provisioning Status of the domain as "Failed", then you must first remove the domain by running the remove_domain command.
After installing the software, you can check log files created by the Exalytics Domain Management Utility. The utility creates a unique log file for each executed action. For example, the Exalytics Domain Management Utility creates a different log file when creating a domain and a different log file when listing domains. The format of the log file for an action is as follows:
exalytics_domain_<domain_name>_<action>_<timesstamp>.log
In addition to the "action" log files, the Exalytics Domain Management Utility also provides information about the location of the log files of the underlying process (such as Oracle BI EE installer log file). For example, there are different log files when installing and configuring Oracle Business Intelligence, and a different log file when installing Oracle TimesTen. The location of the log file for each process is displayed in the specific action log file and is prefixed by the word [LOGFILE]. The format of the log file for an underlying process is as follows:
[LOGFILE] [<process>] <location>
To view log files for each executed action and Oracle WebLogic Server installation:
Navigate to the /u01/app/oracle/product/exalytics/logs directory.
The log file for each action is named as follows:
exalytics_domain_<domain_name>_<action>_<timestamp>.log
For example:
exalytics_domain_menlo_list_domain_2013-11-13_005822.log
The log file for Oracle WebLogic Server is named as follows:
weblogic_install_2013-11-21_162945.log
To view log files for software installation and configuration process:
Navigate to the /u01/app/oracle/product/exalytics/logs directory.
Open the log file that is created for the <add_domain> action.
For example:
exalytics_domain_menlo_add_domain_2013-10-13_005822.log
Search for the word [LOGFILE].
Location of the BI Installer and BI Configuration Assistant log files are displayed.
For example:
[LOGFILE] [BI Installer] /u01/app/oracle/product/exalytics/oraInventory/logs/install2013-11-21_11-26-49PM.log
[LOGFILE] [BI Config Assistant] /u01/app/oracle/product/exalytics/oraInventory/logs/install2013-11-21_04-51-20PM.log
To view log files for TimesTen installation:
You might want to reinstall the software. The Exalytics Domain Management Utility 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:
To deinstall software on the Exalytics Machine, you use the Exalytics Domain Management Utility to remove the Exalytics domain. When you remove the Exalytics domain, all software for the domain is deinstalled.
Note:
To manually deinstall software on the Exalytics Machine, see Deinstalling Software on the Exalytics Machine.
To remove an Exalytics domain: