Upload
trinhque
View
229
Download
0
Embed Size (px)
Citation preview
http://www.peakindicators.com [email protected]
Oracle Business Intelligence 11g
Peak ETA
Installation Guide
Version 2.4
September 2015
Peak Indicators Limited
Tapton Park Innovation Centre
Brimington Road
Tapton
Chesterfield
S41 0TZ
+44 (0) 114 360 2945
Page 2 www.peakindicators.com [email protected]
TABLE OF CONTENTS
1. Overivew ............................................................................................................................................................ 3
2. Installation Pre-Requisites .................................................................................................................................. 4
2.1 Database ....................................................................................................................................................... 4
2.2 Oracle BI 11g ................................................................................................................................................ 4
2.3 Download Software ...................................................................................................................................... 4
3. Installing Peak ETA ............................................................................................................................................. 5
3.1 Peak ETA Repository Schema ....................................................................................................................... 5
3.2 Aggregate and Staging Aggregate Schemas ................................................................................................. 6
3.2.1 Create Aggregate Schemas on TimesTen (Optional) ............................................................................. 6
3.2.2 Create Aggregate Schemas on Oracle Database (Optional) .................................................................. 7
3.2.3 Configure BI Repository (RPD) with Aggregate Schema Connections ................................................... 8
3.3 Peak ETA Server ............................................................................................................................................ 9
3.3.1 Copy Peak ETA Server Scripts ................................................................................................................ 9
3.3.2 Configure Shell Script ........................................................................................................................... 10
3.3.3 Modify Configuration File .................................................................................................................... 10
3.3.4 Copy Oracle Java Libararies ................................................................................................................. 12
3.4 Peak ETA Console ....................................................................................................................................... 13
3.4.1 Create LDAP Security Group “Peak ETA Admin” .................................................................................. 13
3.4.2 Create JDBC Connection to Peak ETA Repository ................................................................................ 17
3.4.3 Deploy Peak ETA Console to WebLogic ............................................................................................... 21
3.5 Configure Peak ETA Console ...................................................................................................................... 24
Page 3 www.peakindicators.com [email protected]
1. OVERIVEW
This document details all the steps needed to install Peak ETA. There are a number of steps required, each
step is relatively straight forward but you should be careful to make sure none of the steps are overlooked.
Here is a breakdown of the installation and configuration:
Peak ETA Repository Schema
A small schema is required to store the Peak ETA repository tables, views, sequences and triggers.
This should be an Oracle Database version 10g or above (editions XE, SE1, SE or EE)
Aggregate and “Staging” Aggregate Schemas
Schemas are required to store the target aggregate tables and also the “staging” aggregate tables.
These can be created on either TimesTen 11.2+ or Oracle Database 10g+.
Once created, the BI Repository (RPD) will be configured with their connections in the RPD “Physical”
Layer
Peak ETA Server
A set of scripts and code used to drive the loading process for the aggregate tables.
The Peak ETA Server is a parallel execution engine built using Java.
A small configuration file needs to be updated with connection settings to the Peak ETA Repository
schema.
Peak ETA Console
The Peak ETA Console is a java user interface built using the Oracle ADF Essentials 11g development
framework. It comes in the form of an .ear file which can be deployed to your Weblogic application
server (or any other J2EE application server).
Before deploying the application to Weblogic, we need to create a database connection for the Peak
ETA Repository schema and also an LDAP security group “Peak ETA Admin” which will be used to
determine who can log on to the Peak ETA Console.
Oracle ADF Essentials 11g
The Peak ETA Console user interface is an Oracle ADF Essentials 11g application. Oracle ADF
Essentials is a java development framework which allows you to build and deploy form-based
applications using Oracle JDeveloper.
Before we can deploy the Peak ETA Console to Weblogic, we need to first install the Oracle ADF library
files on the Weblogic server.
NOTE: Oracle ADF Essentials 11g requires no additional licenses – it is a “free” Oracle product
Peak ETA Dashboards and RPD
This is an optional component. A set of BI Repository (RPD) metadata and BI Dashboards is provided
so that the load processes can be monitored (read-only) within Oracle BI 11g.
This enables additional possibilities such as the creation of BI Delivers agents to alert when the load
processes have started or completed.
Page 4 www.peakindicators.com [email protected]
2. INSTALLATION PRE-REQUISITES
2.1 DATABASE
The database pre-requisites are as follows
You need to have SYSTEM or DBA access to create the Peak ETA Repository schema on an Oracle
Database
You need to have SYSTEM or DBA access to create the aggregate and staging aggregate schemas (or
your target TimesTen or Oracle Database)
2.2 ORACLE BI 11G
Please ensure you have the following details for your Oracle BI 11g installation:
BI Repository (RPD) password
Weblogic administrator password
You will also need access to the BI Server in order to copy over the necessary Peak ETA Server scripts. The following software versions are supported:
Oracle BI 11g version 11.1.1.6.0+
Oracle WebLogic 10.3.5+ NOTE: You do not need to install the Peak ETA Server scripts on the Oracle BI Server, but it is recommended
(especially in your development environments)
2.3 DOWNLOAD SOFTWARE
In order to complete the installation, you will need to have obtained the following software:
Peak ETA.zip
This is the Peak ETA software bundle
You can obtain the software from the Peak Indicators website: http://www.peakindicators.com
Page 5 www.peakindicators.com [email protected]
3. INSTALLING PEAK ETA
3.1 PEAK ETA REPOSITORY SCHEMA
NOTE: The Peak ETA Repository schema needs to be installed on Oracle Database 10g or above. The
database can be any edition (XE, Standard Edition One, Standard Edition or Enterprise Edition)
Connect to your Oracle Database as a DBA or SYSTEM user
Create a new schema (user) to store the Peak ETA Repository objects. For example, to create a user
“peaketa” with password “welcome1” and with permission to create objects in the “users” tablespace
run the following SQL:
CREATE USER peaketa IDENTIFIED BY welcome1
DEFAULT TABLESPACE users
QUOTA UNLIMITED ON users;
Then grant the necessary system privileges so that it is possible to for the user to create a session and
also create tables, views, triggers and sequences:
GRANT CREATE SESSION, CREATE TABLE, CREATE VIEW,
CREATE SEQUENCE, CREATE TRIGGER
TO peaketa;
Now connect to the database as this new Peak ETA Repository schema account. For example:
CONNECT peaketa/welcome1@orcl
Run the “peaketa.sql” script which is provided as part of the Peak ETA software bundle:
@[path to file]\peaketa.sql
For example:
@C:\Temp\PeakETA\peaketa.sql
When you initiate the script, you will be prompted for a tablespace in which to store the repository
tables and indexes. Enter the name of a valid tablespace (e.g. USERS) and then press <RETURN> to
create all the objects:
SQL> @peaketa.sql
Enter value for tablespace: users
Page 6 www.peakindicators.com [email protected]
3.2 AGGREGATE AND STAGING AGGREGATE SCHEMAS
NOTE: It might be the case that you already have an aggregate schema created. If this is the case then you
can omit the step to create the aggregate schema however you must still create the “staging”
aggregate schema and apply the stated grants to both aggregate and staging aggregate schemas
3.2.1 CREATE AGGREGATE SCHEMAS ON TIMESTEN (OPTIONAL)
NOTE: You only need to perform this Section 3.2.1 if you are wishing to deploy aggregates to Oracle
TimesTen
Connect to your TimesTen instance using the ttIsql utility. For example, if you TimesTen instance was
called “AGGREGATES” then the command is as follows:
Command> connect DSN=AGGREGATES;
Create two aggregate schemas, one to store the aggregates (e.g. AGG) and the other to store the
staging aggregates (e.g. AGG_STG). Specify also a password (e.g. welcome1):
CREATE USER agg IDENTIFIED BY welcome1;
CREATE USER agg_stg IDENTIFIED BY welcome1;
Grant the necessarily privileges to both schemas:
GRANT CREATE SESSION, SELECT ANY TABLE, INSERT ANY TABLE,
CREATE ANY TABLE, CREATE ANY INDEX, DROP ANY TABLE
TO agg;
GRANT CREATE SESSION, SELECT ANY TABLE, INSERT ANY TABLE,
CREATE ANY TABLE, CREATE ANY INDEX, DROP ANY TABLE
TO agg_stg;
Page 7 www.peakindicators.com [email protected]
3.2.2 CREATE AGGREGATE SCHEMAS ON ORACLE DATABASE (OPTIONAL)
NOTE: You only need to perform this Section 3.2.1 if you are wishing to deploy aggregates on an Oracle
Database
Connect to your Oracle Database as a DBA or SYSTEM user:
Create the aggregate (e.g. AGG) and staging aggregate (e.g. STG_AGG) schemas. Specify a password
(e.g. welcome1) and a default tablespace (e.g. users):
CREATE USER agg IDENTIFIED BY welcome1
DEFAULT TABLESPACE users
QUOTA UNLIMITED ON users;
CREATE USER agg_stg IDENTIFIED BY welcome1
DEFAULT TABLESPACE users
QUOTA UNLIMITED ON users;
Then grant the necessary system privileges so that it is possible to for the user to create a session and
also create tables, views, triggers and sequences:
GRANT CREATE SESSION, SELECT ANY TABLE, INSERT ANY TABLE,
CREATE ANY TABLE, CREATE ANY INDEX, DROP ANY TABLE
TO agg;
GRANT CREATE SESSION, SELECT ANY TABLE, INSERT ANY TABLE,
CREATE ANY TABLE, CREATE ANY INDEX, DROP ANY TABLE
TO agg_stg;
Page 8 www.peakindicators.com [email protected]
3.2.3 CONFIGURE BI REPOSITORY (RPD) WITH AGGREGATE SCHEMA CONNECTIONS
Open up your BI Repository (RPD)
In the Physical Layer, make sure the following 5 objects exist:
1) A “physical database” for your aggregates database
For example: Aggregates
2) A “physical schema” and “connection pool” for your aggregate tables
For example: AGG
Aggregates Connection Pool
3) A “physical schema” and “connection pool” for your staging aggregate tables
For example: AGG_STG
Aggregates Stage Connection Pool
NOTES:
The physical schemas and connection pools must all reside inside the same physical
database
You MUST enable the “Require fully qualified table names” option in both
connection pools
The example below is for a TimesTen data source:
Save your RPD
Page 9 www.peakindicators.com [email protected]
3.3 PEAK ETA SERVER
NOTE: You can install the Peak ETA Server scripts and code on to any server, but it is best if you copy and run
the script on the Oracle BI Server. The code is java based, so there is no OS install required. The
instructions below are for a Windows server, but the steps are precisely the same for Linux
3.3.1 COPY PEAK ETA SERVER SCRIPTS
On your Oracle BI Server, create a director for the Peak ETA Server scripts and code. For example:
C:\PeakETA
NOTE: Make sure there are no spaces in the directory path
From the Peak ETA software bundle, copy the following in to the above folder:
/lib [Empty folder, some .jar libraries will be copied in here later]
client.properties [Configuration file with database and OBI connection parameters]
peaketa.jar [The parallel execution engine]
peaketa.bat [Script to initiate a load on a Windows server]
peaketa.sh [Script to initiate a load on a Linux server]
Depending on your operating system, open up either the “peaketa.bat” (Windows) or “peaketa.sh”
(Linux) script for editing
Page 10 www.peakindicators.com [email protected]
3.3.2 CONFIGURE SHELL SCRIPT
At the top, configure the two parameters for “JAVA_HOME” and “PETA_HOME”:
JAVA_HOME The home folder for your JDK or JRE installation
PETA_HOME The home folder of your Peak ETA Server scripts (e.g. C:\PeakETA)
NOTE: Make sure there are no spaces in the folder paths
For example, on Windows:
set JAVA_HOME=C:\Progra~1\Java\jdk1.6.0_25
set PETA_HOME=C:\PeakETA
For example, on Linux:
JAVA_HOME=/opt/java/jdk1.6.0_22
PETA_HOME=/home/oracle/peaketa
Save the file and exit
3.3.3 MODIFY CONFIGURATION FILE
Finally, open up the client.properties file for editing
Modify the parameters as follows:
NOTES:
Do not change any parameters other than the ones listed here
Some parameters appear duplicated, this is to cater for future enhancements
[OBI EE Configuration]
anaUserName=weblogic - Weblogic admin username
anaPassword=welcome1 - Weblogic admin password
anaHostName=localhost - Hostname of Oracle BI Server
biHost=localhost - Hostname of Oracle BI Server
anaJDBCPort=9703 - Port for Oracle BI Server (default 9703)
biPort=9703 - Port for Oracle BI Server (default 9703)
anaHttpPort=9704 - Port used for BI Dashboards (default 9704)
biHttpPort=9704 - Port used for BI Dashboards (default 9704)
anaTarget=PEAK - Do not modify
[APC Repository]
repUserName=peaketa - Schema name of the Peak ETA Repository user
repPassword=welcome1 - Password for the Peak ETA Repository user
repHostName=localhost - Database host for the Peak ETA Repository
repPort=1521 - Port of the Peak ETA Repository database
repSID=ORCL - SID of the Peak ETA Repository database
repSchemaName=peaketa - Schema name of the Peak ETA Repository user
Page 11 www.peakindicators.com [email protected]
Save file and exit
Page 12 www.peakindicators.com [email protected]
3.3.4 COPY ORACLE JAVA LIBARARIES
Some Oracle java libraries are required so that the Peak ETA Server can connect to the Oracle BI Server and
Oracle Database. These can be obtained from your existing Oracle BI 11g installation folders:
Locate and copy the following files into the Peak ETA Server “lib” folder (e.g. C:\PeakETA\lib):
1) bijdbc.jar
This can be found in [BI MIDDLEWARE HOME]\Oracle_BI1\clients
2) ojdbc6.jar
This can be found in [BI MIDDLEWARE HOME]\Oracle_BI1\jdbc\lib
Page 13 www.peakindicators.com [email protected]
3.4 PEAK ETA CONSOLE
This section will deploy the Peak ETA Console user interface to your Weblogic application server. Before we
can do this there are some initial steps to perform:
Create LDAP security group for accessing the console
Create JDBC connection for connecting to Peak ETA Repository
Once these steps have been performed it will be possible to deploy the user interface.
3.4.1 CREATE LDAP SECURITY GROUP “PEAK ETA ADMIN”
The Peak ETA Console integrates with the Weblogic application server security. By default, a security group
“Peak ETA Admin” needs to be created in any of the identity providers which are configured for use with
Weblogic. The instructions below assume the creation of this security group in the embedded Weblogic
LDAP. However, you should also be able to create the group in an external LDAP identity provider, should it
be required.
It is technically quite easy to configure Peak ETA Console to use a different security group to “Peak ETA
Admin”. If you need to do this then please email Peak Indicators to request instructions
3.4.1.1 CREATE GROUP
Log on to Weblogic console as your “weblogic” adminstrator user account:
http://[server]:7001/console
Navigate to the following screen:
Security Realms > myrealm > Users and Groups > Groups
Page 14 www.peakindicators.com [email protected]
Click the “New” button to create a new Group:
Specify the following details for your Group:
Name: Peak ETA Admin
Provider: DefaultAuthenticator
Click “OK”
Page 15 www.peakindicators.com [email protected]
3.4.1.2 CREATE USER ACCOUNT
NOTE: If you prefer to use an existing account to use the Peak ETA Console then you can skip this step and
move to the next Section 3.4.2.3
Go to the “Users” tab
Create a new user by clicking the “New” button
Enter the following details:
Name: [Choose a suitable username e.g. peaketa]
Password: [Enter a password]
Confirm Password: [Confirm password]
Click “OK”
Page 16 www.peakindicators.com [email protected]
3.4.1.3 ASSIGN USER TO GROUP
Staying within the “Users” tab, browse for and locate the user account for the Peak ETA Console
Click on the user account:
On the “Groups” tab, browse for an select the group “Peak ETA Admin”:
Click “Save”
Page 17 www.peakindicators.com [email protected]
3.4.2 CREATE JDBC CONNECTION TO PEAK ETA REPOSITORY
Staying within the Weblogic Console, navigate to the following screen:
Services > Data Sources
Click the “Lock and Edit” button
Click the “New” button and choose “Generic Data Source”:
Page 18 www.peakindicators.com [email protected]
Specify the following details:
Name: Peak ETA
JNDI Name: /jdbc/PeakETADS (please copy exactly)
Database Type: Oracle
Click “Next” and click “Next” again to accept the default settings on the following screen:
Click “Next” and click “Next” again to accept the message on the following screen
Page 19 www.peakindicators.com [email protected]
Enter the following details for connecting to the Peak ETA Repository database:
Database Name: [Database SID e.g. ORCL]
Host Name: [Database Server Host e.g. localhost]
Port: [Database Port e.g. 1521]
Database User Name: [Peak ETA Repository schema e.g. peaketa]
Password: [Peak ETA Repository schema password]
Confirm Password: [Peak ETA Repository schema password]
Click “Next” and then click on the “Test Configuration” button on the following screen. Ensure the
connection is established successfully:
Assign the new data source to the “Admin” server only:
You can now click “Finish” to complete the configuration
Page 20 www.peakindicators.com [email protected]
Click the “Activate Changes” button:
Page 21 www.peakindicators.com [email protected]
3.4.3 DEPLOY PEAK ETA CONSOLE TO WEBLOGIC
From the Peak ETA software bundle, copy the “PeakETA.ear” file to the WebLogic server
Log on to Weblogic console as your “weblogic” adminstrator user account:
http://[server]:7001/console
Navigate to the “Deployments” screen and click the “Lock and Edit” button:
Click on the “Install” button:
Browse for and locate your “PeakETA.ear” file which should be located on the Weblogic server:
Click “Next” and choose the option “Install this deployment as an application”:
Page 22 www.peakindicators.com [email protected]
On the next screen, choose to deploy the application to the “Admin” server only (NOTE: if you only
have an “Admin” server in your Weblogic domain then you will not see this screen, the “Admin”
server will be chosen by default):
Click “Next” and then click “Next” again to accept the default name for the application:
Click “Next” and then click “Finish” to complete the configuration:
Click “Activate Changes”:
Page 23 www.peakindicators.com [email protected]
Back on the “Deployments” screen, browse for and select the new “PeakETA” application and choose
to “Start > Servicing all requests”:
That’s it!
Page 24 www.peakindicators.com [email protected]
3.5 CONFIGURE PEAK ETA CONSOLE
Log on to the Peak ETA Console using the user account configured in section 3.4:
http://[server]:7001/PeakETA
Go to the “Configuration” tab (you will see a sample set of configuration already entered):
Page 25 www.peakindicators.com [email protected]
Configure the paramters carefully as follows:
Physical Database: The name of the Physical Database in the RPD used for storing the aggregates e.g. Aggregates Database Type: Choose the type of database used for storing your aggregates.
Either “Oracle TimesTen” or “Oracle Database” Staging Schema: The name of the schema used for storing the “staging” aggregates e.g. AGG_STG Stage Connection Pool: The name of the connection pool in the RPD used for connecting to the “staging”
aggregate schema (surround with double-quotes). e.g. “Aggregates Stage Connection Pool” Target Schema: The name of the schema used for storing the target aggregates e.g. AGG Target Connection Pool: The name of the connection pool in the RPD used for connecting to the target
aggregate schema (surround with double-quotes). e.g. “Aggregates Connection Pool” Path to “nqquery.log”: The full path to the Oracle BI “nqquery.log” file. This should be a directory path
on the Weblogic server hosting the Peak ETA Console. If your Oracle BI server is on another machine, then you will need to publish the log directory as a network share or manually copy the “nqquery.log” file over to the server hosting the Peak ETA Console whenever it is needed to configure new aggregates
e.g. C:\Oracle\Middleware\instances\instance1\diagnostics\logs\OracleBIServerComponent\coreapplication_obis1\nqquery.log
Path to “peaketa.log”: The full path to the “peaketa.log” file which will be created within the same
folder which stores the Peak ETA Server scripts. Note that, at this moment in time, the actual file may not exist yet – it will be created the first time you run the Peak ETA Server process
e.g. C:\PeakETA\peaketa.log Server Command: This is the OS shell command needed to initiate the Peak ETA Server process.
The command will run the server script and output all results to a “peaketa.log” file stored in the same directory. You’ll need to include prefixed for the full path to the Peak ETA home directory.
e.g. for Windows:
C:\PeakETA\peaketa.bat > C:\PeakETA\peaketa.log 2>&1
NOTE: The “2>&1” syntax at end end is required to ensure all server debug
output is captured in the log file
e.g. for Linux:
/home/oracle/PeakETA/peaketa.sh > /home/oracle/PeakETA/peaketa.log
Once configured, click the “Save” button