3 Postinstallation Tasks

3.1 Installing and Uninstalling Oracle Business Intelligence Client Tools

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 Uninstalling Oracle Business Intelligence Client Tools" in Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence.

3.2 Creating the boot.properties File

Perform this task on each computer in the cluster.

For information on creating the boot.properties file, see "Creating boot.properties for the Administration Server on APPHOST1" in Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence.

3.3 Starting and Stopping Components on the Exalytics Machine

Perform this task on each computer in the cluster.

After making configuration changes, you stop and start components to enable those changes to take effect.

To stop components on the Exalytics Machine:

1. Log into Fusion Middleware Control and stop all Oracle Business Intelligence system components.

2. Stop Node Manager. Use the ps command to find the process identifier, then use the kill command to stop Node Manager.

3. Stop OPMN by entering the following commands:

   cd /home/oracle/EXALYTICS_MWHOME/instances/instance1/bin
   ./opmn stopall
   

4. Stop the TimesTen Server. See "Running the TimesTen Server" in Oracle TimesTen In-Memory Database Operations Guide.

To start components on the Exalytics Machine:

1. Change to the following directory:

   /EXALYTICS_MWHOME/user_projects/domains/bifoundation_domain

2. Enter the command to start Oracle WebLogic Server:

   nohup ./startWebLogic.sh &

3. Use the command line to start Node Manager and OPMN if they are not started.

4. Log into the Oracle WebLogic Server console and start the managed servers.

5. Log into Fusion Middleware Control and verify whether the Oracle Business Intelligence system components are running. If they are not running, then start them.

6. Start the TimesTen Server. See "Running the TimesTen Server" in Oracle TimesTen In-Memory Database Operations Guide.

3.4 Running the Daemon Configuration Scripts for TimesTen

Perform this task on each computer in the cluster.

Run the TimesTen daemon configuration scripts as root, using the following command:

/home/oracle/TimesTen/tt1122/bin/setuproot.sh -install

3.5 Configuring Memory Settings on the Server

Perform this task on each computer in the cluster.

See "Large Pages" in Oracle TimesTen In-Memory Database Installation Guide for information on defining the TimesTen In-Memory Database in the DSN and on editing the limits.conf file for kernel parameters and semaphores.

3.6 Instantiating the TimesTen In-Memory Database

Perform this task on each computer in the cluster. For the first computer, the installation scripts update the sys.odbc.ini file, then you perform the rest of the task manually.

The TimesTen In-Memory Databases are defined using a DSN that is contained in the sys.odbc.ini file in the following directory:

/home/oracle/TimesTen/tt1122/info

The semi-automated installation scripts automatically update the sys.odbc.ini file for 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=/home/oracle/TimesTen/tt1122/lib/libtten.so
DataStore=/home/oracle/aggregate_store/tt_aggr_store
LogDir=/home/oracle/aggregate_store/logs
DatabaseCharacterSet=AL32UTF8
ConnectionCharacterSet=AL32UTF8
LogFileSize=1024 
LogBufMB=1024 
LogBufParallelism=12 
Preallocate=0 
PermSize=25000 
TempSize=25000 
MemoryLock=4 
CkptFrequency=30 
CkptLogVolume=0 
CkptRate=20 
PrivateCommands=1 
RangeIndexType=1 
Connections=1024 
RecoveryThreads=40

This DSN supports a 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:

/home/oracle/aggregate_store
/home/oracle/aggregate_store/logs
/home/oracle/aggregate_store/tt_aggr_store

On computers other than the first one in the cluster, manually edit the sys.odbc.ini file for TimesTen to add the DSN definition. Before instantiating this DSN, remove the comment character (#) that the semi-automated scripts included for the lines that define the DataStore and LogDir parameters in the sys.odbc.ini file.

The 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 /home/oracle/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 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 TimesTen instance that is used for aggregate storage. This tool can allow you to easily view the contents of the TimesTen database and to create a dummy table that facilitates the mapping of the TimesTen schema into the physical layer of the BI repository.

3.7 Configuring the ODBC Connection from Oracle Business Intelligence to TimesTen

Perform this task on each computer in the cluster. The semi-automatic installation scripts perform this task on the first computer.

The Client/Server DSN in TimesTen spans computer boundaries and the remote TimesTen server can be configured as part of the DSN. You create the DSN for the two 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 = /home/oracle/TimesTen/tt1122/lib/libttclient.so
TTC_SERVER_DSN = TT_AGGR_STORE
TTC_SERVER = <tt_hostname>
TTC_TIMEOUT = 0

Define the DNS Servers for TimesTen by modifying the following file:

TimesTen-root-dir/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 TimesTen instance on each computer and ensuring that each instance is aware of the TimesTen instance on the other computer. You edit the odbc.ini file for Oracle Business Intelligence to contain references to both 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 = /home/oracle/TimesTen/tt1122/lib/libttclient.so
TTC_SERVER_DSN = TT_AGGR_STORE
TTC_SERVER = <tt_hostname1>
TTC_TIMEOUT = 0
 
[TT_AGGR_STORE2]
Driver = /home/oracle/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 /home/oracle/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

3.8 Mapping TimesTen Instances into the Physical Layer of the Oracle BI Repository

You must map all TimesTen instances into the Physical layer of the Oracle BI repository. To do this, 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 a 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 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 Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition

• "Configuring Repositories" in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition

3.9 Installing and Configuring BI Composer for Oracle BI EE

Perform this task on each computer in the cluster.

See "Installing and Configuring BI Composer for Oracle BI EE" in Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence.

3.10 Creating a DSN for IBM DB2 or Microsoft SQL Server

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 Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence.

3.11 Configuring IBM DB2 to Support Multibyte Data

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 Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence.

3.12 Configuring Sample Reports for Oracle BI Publisher

Perform this task on each computer in the cluster.

See "Configuring Sample Reports for Oracle BI Publisher" in Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence.

3.13 Changing the Default Password for SampleAppLite.rpd

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 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