OBIEE 11.1.1.7.0 Step by Step Installation

Installing ODI 11.1.1.6.0 on Windows 7 64bit

I’m going to try ODI again. Current ODI version is 11.1.1.6.0. Now, it has come under Oracle Fusion Middleware domain. A major difference from 10g.

My environment for ODI installation is a Intel Core i5 machine with 8 GB memory. It’s running on Windows 7 Professional 64 bit.

ODI is 11g is supported on my system according to the System Certification matrix; https://www.oracle.com/technetwork/middleware/data-integrator/odi-11gr1certmatrix-163773.xls

I got the installation media downloaded from; https://www.oracle.com/technetwork/middleware/data-integrator/downloads/index.html?ssSourceSiteId=ocomen

Since I’m running a 64 bit OS, required installation files are;

ofm_odi_generic_11.1.1.6.0_disk1_1of2.zip

ofm_odi_generic_11.1.1.6.0_disk1_2of2.zip

According to the new Middleware Architecture, now we have to create a database schemas to store a repository before starting the actual ODI installation. To create database schemas Oracle provides RCU; Repository Creation Utility.

RCU installation is available at the same URL mentioned above.

ofm_rcu_win_11.1.1.6.0_disk1_1of1.zip

A pretty structured Installation Guide is available at; https://docs.oracle.com/cd/E23943_01/core.1111/e16453/overview.htm#CEGJJIFH

So there are 2 parts of my installation.

1. Repository creation
2. ODI installation

The repository is created in a RDBMS. So having access to a running database is a prerequisite.

To start with the repository creation, ofm_rcu_win_11.1.1.6.0_disk1_1of1.zip is extracted.

When extracted, within bin directory, rcu.bat can be found.

rcu.bat is executed;

Welcome screen appears and “Next >” is clicked.

We can use RCU to create or drop repositories. We want to create one here.

We define where we want the repository to be created. I’ve got an Oracle 11g DB on my machine. So we can use that.

I prefer to use SYS account in scenarios like this as it can avoid a lot of issues caused by bugs .

RCU checks the DB for requirements for creating the repository. And here, it complains that the DB hasn’t been created with character set it supposed to be for repository creation.

My DB was not created solely for the ODI installation So I cannot do much about it now. Hope we can ignore this error.

Ignore

Other than the character set issue, my DB is ready for the repository creation.

OK

We have to select which repositories to be created. Since RCU is a common tool that supports many products, we has to select what we want; Oracle Data Integrator in out case.

I’d leave the default prefix as it is. I’m building a development environment anyway.

Prerequisites are checked in another level.

OK

Passwords for the repository schemas are defined. We have only one schema here. So the it doesn’t matter the option selection here.

Some ODI internal parameter settings; I’d accept the default value except the passwords.

The tablespaces where the schemas are created are defined. Even though we can change the tablespaces through “Manage Tablespaces”, I’m going to work with the default tablespaces RCU suggests.

Of course the tablespaces RCU suggested were not on my DB. They should be created fresh.

New tablespaces are created.

OK

All set to launch the repository creation.

Create

Repository creation is going on. It won’t take much time.

It’s done. No errors

Close

RCU has created a tablespace of 200MB out of which 15.6 MB has been used for the repository.

Repository creation is completed. Now, ODI installation can be started.

Also, according to the Certification Matrix, I should have Oracle JDK 1.7.0+ 64bit installed on Windows 7 64 bit. So I had to download the JDK and install since I had only JRE before starting ODI installation.

Now the system is ready for the installation; ODI installation files should be extracted.

When both the files are extracted; setup.exe in Disk1 is executed. In my case, I needed to execute it with “Run as administrator” as the account I had logged in with is not in the Administrators group.

When setup.exe is executed, an error is fired;

“ERROR: Provided the JDK/JRE location while launching the installer. Invoke the setup.exe with -jreLoc parameter(s)”

According to the error message, it seems to be the setup.exe cannot find the JDK installation.

So I called the installer as instructed in the error message; from the command prompt (started with “Run as administrator")

setup.exe -jreLoc “C:\Program Files\Java\jdk1.7.0_09”

Nothing happened. Prompt was just returned.

In the JDK path, there is a space. This could be the issue here.

So I tried the path eliminating the space.

setup.exe -jreLoc “C:\Progra~1\Java\jdk1.7.0_09”

Same :(. Just returned to the prompt.

Another way; without the double-quotes;

setup.exe -jreLoc C:\Progra~1\Java\jdk1.7.0_09

Now something is happening.

ODI installer was launched

It’s a regular “Welcome” screen.

I’d skip the software updates for the moment.

Selecting what’s needed to be installed. The machine I’m installing on is my development environment as well as the data locations (sources and targets). So I’d select both “Developer Installation” and “Standalone Installation”.

My system is through with installation prerequisites check.

I usually keep big installation away from C: drive. I changed installation directory to E: drive.

Better to let the installer do as much as work. So I select to “Configure Repositories”.

Connection detailed to the repository created by RCU is provided.

Supervisor password is provided as defined during setting ODI parameters.

I’d need a work repository as I have to do my developments here.

I defined my agent as “ODIAgent1” with the port 60000.

I’m skipping security updates for the moment.

I’m sure about it.

Yes

Almost there. Better to save the configuration details for future reference.

Install

installation goes on. Hope it’ll complete without errors. Hardly have that comfort.

So far so good…

Installation completes. And configuration process is started automatically. Configurations also has been completed successfully.

Installation completed. Better to save configurations details also.

Finish

Now I have an ODI environment with a Master Repository and a Work Repository named WORKREP ready for development. Both repositories were created in a single database schema.

Informatica Installation Guide

• Download Installation Pack.
• Unpack the Installation Package.
• Install Informatica PowerCenter Server.
• Domain Configure.
• Configure Repository Service.
• Configure Integration Service.
• Client Installation.
• Installation Known Issues and Solution.

Download Installation Pack

Step : 1
Informatica PowerCenter trail version can be downloaded from https://edelivery.oracle.com
Log on to https://edelivery.oracle.com and accept the Terms and Conditions.

Step : 2
Choose the Product package as shown below and Click Continue.



Step : 3
Locate the download package as shown in below image.



Step : 4
Download the packages to D:\INFA9X

Unpack the Installation Package

Step : 1

Unzip all the the four downloaded zip files into D:\INFA9X. Hint : Use the program WinRAR to unzip all the files. After unzipping you will see below files and folders.

Step : 2

Unzip dac_win_101314_infa_win_32bit_910.zip into the the same folder D:\INFA9X. After unzipping you will see below files and folders.

Install Informatica PowerCenter Server

Step : 1
To locate install.exe, Navigate to D:\INFA9X\dac_win_101314_infa_win_32bit_910 as shown in below image. double click on the install.exe.

Step : 2
Installation wizard Starts.  Choose the installation type.
Click Next.



Step : 3
Installation Pre-requisites will be shown before the installation starts as below.
Click Next.



Step : 4

Enter the license key. You can locate the license key from D:\INFA9X\EXTRACT\Oracle_All_OS_Prod.key.

Click Next.



Step : 5

Pre-installation summery will give the items installed during the installation process based on the license key.

Click Next

Step : 6
Installation Begins. It takes couple of minutes to finish. Soon after completion of this step, Configuring Domain window opens. Continue the steps from Domain Configuration.

Domain Configuration.

Step : 1

• Choose “Create a Domain” radio button.
• Check “Enable HTTPS for Informatica Administrator”
• Leave the Port number as it is and choose “Use a keystore file generated by the installer”

Click Next.



Step : 2
Provide the Repository database details as below.

• Database Type : Choose your Repository database (Oracle/SQL Server/Sybase)
• Database user ID : Database user ID to connect database.
• User Password  : Password.
• Schema Name : If Schema name is not provided default schema will be used.
• Database Address and Port : Machine on which database in installed and default port number.
• Database Service Name :  Database Name.

Below image shows the configuration using SQL Server.
Click Next.



Step : 3
You can give the Domain details, Admin user details now.

• Domain Name : Name of your Domain.
• Node Host Name : Machine name on which Informatica Server is running.
• Node Name : Name of the Node.
• Node Port Number : Leave the default port Number.
• Domain user name : This is the Administrator user
• Domain password : Administrator password

Note : Remember your Admin User ID, Password to log on to Admin Console later in the installation.



Step : 4
Use the default configuration and Click Next.



Step : 5
Installation is complete and you get the post-installation summery. You get a link to the installation log file and a link to Admin console.
Click Done.

Configure Repository Service

Step : 1
Go to Start menu and Click on “Informatica Administrator Home Page”. This will open up the Admin Console in a web browser.



Step : 2
Log on to Admin console using your Admin User ID and Password. You set your Admin User ID and Password in “Domain Configuration” section Step 3

 

Step : 3
Once you Log on you will see the Screen just like shown below.



Step : 4
Choose your Domain Name from “Domain Navigator”, Click on “Actions”, Choose “New” and “PowerCenter Repository Service”.



Step : 5
A new screen will appear, Provide the details as shown below.

• Repository Name : Your Repository Name.
• Description :  An optional description about the repository.
• Location : Choose the Domain you have already created. If you have only one Domain, this value will be pre populated.
• License : Choose the license key from the drop down list.
• Node : Choose the node name from the drop down list.

Click Next.



Step : 6
A new screen will appear, Provide the Repository database details.

• Database Type : Choose your Repository database (Oracle/SQL Server/Sybase)
• Username : Database user ID to connect database.
• Password : Database user Password.
• Connection String : Database Connection String.
• Code Page : Database Code Page
• Table Space : Database Table Space Name
• Choose “No content exists under specified connection string. Create new content”

Click Finish



Step : 7
It takes couple of minutes create Repository content. After the repository creation below screen will be seen.



Step : 8
The repository service will be running in “Exclusive” mode as shown below. This needs to be change to “Normal” before we can configure Integration service.
Click “Edit” Repository Properties.



Step : 9
A pop up window appears, Set the properties

• Operation Mode : Normal
• Security Audit Trail : No

Click OK.

Click OK for the next two pop up windows which confirms the Repository Restart to change the Repository Operating Mode.

Configure Integration Service

Step : 1
Choose your Domain Name from “Domain Navigator”, Click on “Actions”, Choose “New” and “PowerCenter Integration Service”.



Step : 2
A new window will appear, Provide the details as shown below.

• Name : Your Integration Service Name.
• Description :  An optional description about the repository.
• Location : Choose the Domain you have already created. If you have only one Domain, this value will be pre populated.
• License : Choose the license key from the drop down list.
• Node : Choose the node name from the drop down list.

Click Next.



Step : 3
A new window will appear, Provide the details as shown below.

• PowerCenter Repository Service : Choose your Repository Service Name from the drop down list.
• Username :  Admin user name.
• Password : Admin password.
• Data Movement Mode : ASCII.

Click Finish.



Step : 4
A pop up window will appear, Choose the Code Page as ANSI.
Click OK.



Step : 5
Window will be closed and you can see all the configured services in the “Domain Navigator”



With that we are all done with the installation and configuration for Informatica PowerCenter Server.

Client Installation.

Step : 1
Go to D:\INFA9X  as shown in below image. Click on the install.bat.

Step : 2
Installation wizard Starts.
Click Start.



Step : 3
Installation wizard Starts.  Choose the installation type as in the below image.
Click Next.



Step : 4
Installation Pre-requisites will be shown before the installation starts as below.
Click Next.



Step : 5
Choose the client tools you need. Only PowerCenter  Client is mandatory.
Click Next.



Step : 6
Choose the client installation directory.
Click Next.


Step : 7
You can choose the type of Eclipse installation in this step. This window will be available if you choose to install “Informatica Developer” or “Data Transformation Studio”.
Click Next.



Step : 8
Pre-installation summery will give the items installed during the installation process.
Click Next.


Step : 9
Installation Begins. It takes one or two minutes to complete this step.



Step : 10
Installation is complete and you get the post-installation summery.



With that we are all done with the installation and configuration for Informatica PowerCenter Client.

Installation Known Issues and Solution.

Checkout the article for the for the  Installation Known Issues and Solution.

Informatica Installation Issues and Solutions

Database driver event...Error occurred loading library [pmora8.dll]

Cause

This error occurs when the Oracle client installed in the Windows machine is 32-bit and PowerCenter is 64-bit.

Solution

To resolve this issue re-install the Oracle client 64 bit on the machine where PowerCenter 64-bit server is running.

To check which version you use, run TNSPING.

For Oracle 10g, you should have: 32 bits Oracle C:\oracle\product\10.2.0\client_1\BIN>tnsping TNS Ping Utility for 32-bit Windows: Version 10.2.0.3.0 - Production on 04-J+N-2 008 08:52:08

PowerCenter Informatica Services does not start on Windows

Cause

This issue is caused because the User specified during the installation is not Part of Operating System and Log on as a Service privilege and the user is not part of the Administrator Group.

Solution

Confirm that the Windows user specified in This Account has the following privileges: Act as Part of the Operating System Log on as a Service by doing the following:

Go to Start > Settings > Control Panel > Administrative Tools > Local Security Policy . Select Local Policies > User Rights Assignment . Add the user to Act as Part of the Operating System and Log on as a Service.

ERROR: "This installation package can not be opened.." when installing PowerCenter 9.x

Cause

This issue occurs because of the native zip extraction package on Windows, which results in an incomplete extraction with large files or big file names.

Solution

To resolve this issue, use another zip utility such as WinZip, Peazip, or WinRar to unzip the installation package.

ERROR: "Unable to handle request because repository content do not exist" when starting the Integration service

Cause

This error occurs when the PowerCenter Repository Service is running on Exclusive Mode

Solution

To resolve this issue, change the Repository to run on the Normal Mode and restart both the Repository and Integration Services.

Pre requistics

1. 64 bit OS is must
2. Loopback adapter settings
3. Make sure you unzip the downloaded setup files in the same machine where you’re intended to install obiee. I saw few issues when extracted file is brought from 2008 r2 to win8.
4. Decide user with whom you’re proceeding with installations and ensure oraInventory access.
5. Windows Firewall set to Off
6. JDK 1.8.0_51+
7. Oracle Database 11.2.0.4+ or 12.1.0.1+;

Downloading Software

For downloading required software(s) https://www.oracle.com/technetwork/middleware/bi-enterprise-edition/downloads/business-intelligence-2717951.html.
Below is the list of software to be downloaded:

1. Java Developers Kit 8 (JDK8)
   • Download For Linux and Microsoft Windows
2. Web Logic Server
   • Download Generic (1.4 GB)
3. Oracle Business Intelligence 12c (12.2.1.0.0)
   • for Microsoft Windows x86-64-bit:
   • Download File 1 (1.4 GB)
   • Download File 2 (1.8 GB)
4. Oracle Business Intelligence Developer Client Tool (12.2.1.0.0)
   • Download for Microsoft Windows x86-64-bit (676 MB)

Installation of OBIEE 12c

This installation is divided in to 4 parts as below :

1. Installing Weblogic 12c : Install Oracle Fusion Middleware Infrastructure (no configuring domain for infrastructure)
2. Installing Oracle BI 12c
3. Configuring RCU : run rcu part of /oracle_common/bin to create schema required
• Set BI_PRODUCT_HOME env variable for ex: C:\oracle\product\Middleware\Oracle_Home\bi
4. Configuring OBIEE 12c Configure obiee standard topology using 12c configuration assistant

Overall Steps

1. Installing Weblogic 12c : Install Oracle Fusion Middleware Infrastructure (no configuring domain for infrastructure)
2. Installing Oracle BI 12c
3. Configuring RCU : run rcu part of /oracle_common/bin to create schema required
4. Configuring OBIEE 12c Configure obiee standard topology using 12c configuration assistant

Extract the file so that you have fmw_12.2.1.0.0_infrastructure.jar

Click Next

Click Next

Specify the OBIEE Location Path

Click Next

Click Next

Check the Checkbox

Click Yes

Click Install

Click Next

Now move to step :Installing Oracle BI 12c

Overall Steps

1. Installing Weblogic 12c : Install Oracle Fusion Middleware Infrastructure (no configuring domain for infrastructure)
2. Installing Oracle BI 12c
3. Configuring RCU : run rcu part of /oracle_common/bin to create schema required
4. Configuring OBIEE 12c Configure obiee standard topology using 12c configuration assistant

Now install SetupBI_platform

Click Next

Click Next

Specify the Path

Specify the ORACLE_HOME path

Click Next

Click Next

Now move to step : Configuring RCU : run rcu part of /oracle_common/bin to create schema required

Overall Steps

1. Installing Weblogic 12c : Install Oracle Fusion Middleware Infrastructure (no configuring domain for infrastructure)
2. Installing Oracle BI 12c
3. Configuring RCU : run rcu part of /oracle_common/bin to create schema required
4. Configuring OBIEE 12c Configure obiee standard topology using 12c configuration assistant

Now move to step : Configuring OBIEE 12c Configure obiee standard topology using 12c configuration assistant

Overall Steps

1. Installing Weblogic 12c : Install Oracle Fusion Middleware Infrastructure (no configuring domain for infrastructure)
2. Installing Oracle BI 12c
3. Configuring RCU : run rcu part of /oracle_common/bin to create schema required
4. Configuring OBIEE 12c Configure obiee standard topology using 12c configuration assistant

Migrating From OBIEE 11g to 12c in Windows

What you need to know before we begin:
OBIEE 12c has already been installed and configured, therefore our bi-migration-tool.jar file has been generated. Also, this example is migrating from an OBIEE 11.1.1.9 release.

Overview steps

1. Create the Export Bundle
2. Import the Export Bundle

Before you procced keep below paths handy:

Create the Export Bundle

The export bundle is a .jar file that consists of metadata information from the 11g Oracle home.

Navigate to location [ORACLE_HOME]\bi\migration-tool\jlib location

Copy "bi-migration-tool.jar" to folder name "migration"

1. From the command line enter into above folder path (this should be where your bi-migration-tool.jar file is located)

2. Run the following command to generate the export bundle

java -jar bi-migration-tool.jar out <oracle 11g home> <domain home> <output export bundle path>

Where :

• out is telling the migration tool to lierform the export operation
• <oracle 11g home> is the Oracle BI home directory
• <domain home> is the 11g domain directory
• is the location where you want the export bundle. NOTE: the file must have a .jar extension

Example : java -jar bi-migration-tool.jar out E:\donot_delete_server\Oracle11\Middleware\Oracle_BI1 E:\donot_delete_server\Oracle11\Middleware\user_projects\domains\bifoundation_domain E:\Migration\My11gExport.jar

Import the Export Bundle

Again, 12c has been installed and configured, so our domain and BI instance have already been created. With that in mind, we will be using the BI Migration script to import the export bundle. You can use the BI 12c Configuration Assistant to reference the export bundle if you’re configuring 12c for the first time.

1. You should be in the same file location as before:

2. Run the following command:

java -jar bi-migration-tool.jar in <12c Oracle Home> <12c domain home> <export bundle> <service instance name>

• in tells the migration tool to perform an import operation
• e:\obiee12c\middleware\oracle_home is the Oracle Home
• e:\obiee12c\middleware\oracle_home\user_projects\domains\bat_domain is the 12c domain directory
• e:\11g\11gexport.jar is the previously created export bundle
• ssi is the BI service instance

Example : java -jar bi-migration-tool.jar in E:\donot_delete_server\Oracle12\product\Oracle_Home E:\donot_delete_server\Oracle12\config\domains\bi E:\Migration\My11gExport.jar ssi

3. You will be prompted to enter the RPD password

4. If the migration is successful you will receive a Migration action succeeded message

To verify login to OBIEE 12c and you should see your dashboards, subject areas, etc that have been imported from your 11g.

Experimenting with the new Oracle BI Baseline Validation Tool

The Oracle BI Baseline Validation Tool is a long overdue new tool introduced in 12c that allows BI administrators to perform regression testing after a BI migration or a BI upgrade. The goal of this post is to document my experimentation with this new tool in Windows 7. As an example I’ve got an environment with OBIEE 11.1.1.7 installed and another equivalent environment with version 11.1.1.9. The BVT is run from the command with a configuration file and set of arguments. Following are the high-level steps for using the Oracle BI BVT:

1. Establish a baseline (set of dashboards, reports), in this example we compare all items
2. Configure the configuration file to specify the location of the target catalog, Oracle BI Presentation Services login information, and the plug-ins to activate. A sample configuration testconfig.xml is provided out the box, one can create a new using the BVT utility
3. Run the Oracle BVT tool three times:
   • First run to generate the baseline
   • Second run to generate the same data from the patched environment
   • Third run to compare results between the before and after web catalog

The BVT allows a fine grain level comparison allowing even the ability to set a maximum tolerance for floating point fluctuations between reports.

Oracle BI Validation Tool Installation

Requirements
• Java 1.6 and higher
• Windows: Windows 7 and higher, Windows Server 2012 and higher
• Linux: Oracle Linux U5 or Oracle Linux 7
• Mozilla Firefox or IE

It  is shipped with the Oracle Business Intelligence Developer Client Tool, after installation, the tool is located in

[Installation Folder]\bi\components\oracle.bi.bvt

Once the zip file is uncompressed

Configuration File

Looking at the sample configuration file, there are 2 sections:

Deployment

Description of the target environment that the tests will run against, the deployment name can be updated in order to describe your specific environment, in our case we will define the following deployment names; “OBIEE11117base” to designate our baseline OBIEE 11.1.1.7 environment and ““OBIEE11119upgrade” to designate the upgraded environment. The deployment names will be fed to the BVT as command line arguments

Test Plug-ins

This section describes the different types of comparisons (5) that are available for the web catalog; each type of comparison is developed as a plug-in. Following are the plug-ns available out of the box:

• Catalog Plug-in Compares the metadata of objects in catalog folders,
  
• UI Plug-in [com.oracle.biee.bvt.plugin.ui] : Compares screen captures of individual analyses and dashboards.
  
• Reports Plug-in [com.oracle.biee.bvt.plugin.report]: Exports the results of the analyses to CSV and generates a comparison report.
  
• Logical Query Plug-in [com.oracle.biee.bvt.plugin.logicalquery] : Downloads and saves the logical SQL generated for analyses
  
• Dashboard Plug-in [com.oracle.biee.bvt.plugin.dashboard]: Exports the results of the analyses to XML and generates a comparison
  report.

The plug-ins can be enabled by setting the “enabled” tag to true.

Let’s update the sample configuration file and capture the baseline for our OBIEE 11.1.1.7 web catalog. We enter the URL for the BI environment and the username/password. Note that you can chose to enter the password as a command line argument with the “-password” flag followed by the actual password; if no value is passed with the flag, you will be prompted to enter it.

We run the following command in order to capture our 11.1.1.7 baseline, the syntax to capture the configuration for our BI 11.1.1.7 is:

bin\obibvt.bat -config TestConfig.xml -deployment BI11117base

Where testconfig.xml is the name of the configuration file and BI111117base is the deployment name to run. As an example, we’ve enabled all the tests and run the BVT to capture our OBIEE 11.1.1.7 baseline. A folder named after the deployment name is created under the results folder, a progress status is displayed on the screen while the processing is underway.

Note that you can set timeout for loading each report, by default, the timeout to download a single report is 15000 milliseconds (15 seconds). Once the script is done executing, sub folders are created in the main results folder

We run the script again in order to capture the 11.1.1.9 environment, this will enable us to run comparisons between environments

bin\obibvt.bat -config TestConfig.xml -deployment BI11119

Once the script is done running, a second folder is created in the main Results folder

We can now run the same script with the –compareresults flag in order to perform comparisons between the 11.1.1.7 and the 11.1.1.9 environments.

Now navigate to the Comparisons folders and examine the differences between 11.1.1.7 and 11.1.1.9; for each test there is an html file with the color coded test results, relevant details and hyperlinks to items of concern.

Web Catalog comparisons

Details are provided such as :

• number of of BI objects in the base environment
  
• number of BI objects in the target environment
  
• items only present in the base environment
  
• items only present in the target environment
  
• items that are different

Drill down links provide more details where there are exceptions

Dashboard comparisons

Differences between dashboard details are provided.

Logical Query comparisons

Differences in logical SQLs between both environments are documented.

Reports Comparisons

An export to CSV of the results for each of the analyses is performed for each environment and a comparison report is performed.

UI comparisons

UI plugin compares screen captures pixel by pixel of individual analyses and dashboards and displays a comparison report side by side. A score is assigned to each comparison based on the match: a score of 1 indicates a perfect match while 0 indicates a complete mismatch. The threshold for a pass of fail score can be set in the configuration file, it is 0.95 by default. The side by side comparisons is very handy and help you see the discrepancies in look and feel.

Error

p.s: Note that we were only to have all tests run successfully using Firefox version 34.0; tests will fail while running with Internet 11.0 and Firefox 42.0 we got the following error in the log:

NS_ERROR_XPC_CI_RETURNED_FAILURE: Component returned failure code: 0x80570015 (NS_ERROR_XPC_CI_RETURNED_FAILURE)

Apparently this error is caused by the Selenium web driver in later version of Firefox, you can read more about it here.

It is worth noting that there is a flag in the configuration file that allows you (1) to set the default browser for running the tests and (2) another flag where you can specify the number of browser instances to run concurrently while performing the tests.

Conclusion

The goal of this post was to document a preliminary experiment with the new regression testing tool that shipped with obiee 12c; setting up the configuration and the running comparisons is fairly straightforward; the results are detailed and handy. There is no doubt that this tool will be useful for OBIEE regression testing. In conclusion, the Oracle BI development team is making big strides in addressing pain points that have made working with OBIEE and migrating and maintaining different Oracle BI environments a challenge. One shortcoming of the tool though is that BI-Publisher reports are not included in the comparisons, hopefully future releases of the BVT will include this type of comparisons.

How to start and stop services in OBIEE 12c

OBIEE 12c has very simple commands to restart services. but very useful.

Go to below path

Windows:

ORACLE_HOME\user_projects\domains\bi\bitools\bin

Start.cmd for start services

Stop.cmd for stop services

Status.cmd for Status of the services

Linux:

ORACLE_HOME/user_projects/domains/bi/bitools/bin

Start.sh for start services

Stop.sh for stop services

Status.sh for Status of the services

Downloading the installation packages for WebLogic Server, ADF Runtime, and the Sun JDK

To download the installation packages for Oracle Endeca Information Discovery:

1. Log in to https://edelivery.oracle.com.

2. On the Terms and Restrictions page, check the checkboxes to accept the terms and restrictions, then click Continue.

3. On the Media Pack Search page:
(a) From the Select a Product Pack drop-down list, select Oracle Endeca.
(b) From the Platform drop-down list, select Windows.
(c) Click Go.

Steps for Downloading JDK 6

Installing the Sun Java JDK

When you install the Sun Java SDK, you must install it to a path that does not have any spaces.

To install the Sun Java SDK:

1. Double-click the JDK installer file that you downloaded (jdk-6u43-windows-x64.exe). The welcome page of the JDK installation wizard is displayed.

2. On the welcome page, click Next.

3. On the Custom Setup page, because the default installation location (under space, you must change it here. To change the JDK installation location:

4. The Destination Folder page sets the location of the public JRE. Because this JRE is not used by Endeca Information Discovery, you can leave the default directory. Click Next.

The installation process begins.

When the installation is completed, click Close.

Installing WebLogic Server

After downloading the installation packages and installing the JDK, you next install WebLogic Server. Note that this procedure only installs the minimum WebLogic Server configuration needed for Oracle Endeca Information Discovery.

To install WebLogic Server:

1. From a command prompt, navigate to the directory where you placed wls1036_generic.jar.

2. To launch the installer, issue the following command:

java -jar wls1036_generic.jar

The Welcome page of the installation wizard is displayed.

3. On the Welcome page, click Next.

4. On the Choose Middleware Home Directory page:
(a) Click the Create a new Middleware Home radio button.
(b) Accept the default location for the Middleware Home Directory.
(c) Click Next.

5. To bypass the Register for Security Updates page:
(a) Click Next without entering an email address.
(b) On the Email Address Not Specified dialog, click Yes.
(c) On the Are You Sure? dialog, click Yes.
(d) If the Connection failed dialog is displayed, check the I wish to remain uninformed of security
issues in my configuration or the machine has no Internet access checkbox, then click Continue.

6. On the Choose Install Type page, click the Custom radio button, then click Next.

7. On the Choose Products and Components page, check the following products, then click Next:
• Core Application Server
• Administration Console
• Configuration Wizard and Upgrade Framework
• Evaluation Database

8. On the JDK Selection page, verify that the JDK you installed is selected. If it is, click Next.
If that version of the JDK is not selected:
(a) Under Local JDK, click the Browse button.
(b) Browse to and select the directory that contains the JDK (C:\Java\jdk1.6.0_43\).
The Local JDK section is updated to display the selected JDK with a checked box next to it.

(c) Click Next.
9. On the Choose Product Installation Directories page, accept the default installation directory, then
click Next.

10. If the Install Windows Service page is displayed, click the No radio button, then click Next.

11. If the Choose Shortcut Location page is displayed, click a radio button to select the location of the Windows shortcut, then click Next.

12. On the Installation Summary page, verify that you are installing the correct products, then click Next.

13. On the Installation Complete page, uncheck the Run Quickstart checkbox, then click Done.

Installing Oracle ADF Runtime

After you install WebLogic Server, you next install ADF Runtime 11.1.1.6, which contains the JRF needed byOracle Endeca Server.

To install Oracle ADF Runtime:

1. Unpack the ADF zip package (m_appdev_generic_11.1.1.6.0_disk1_of1.zip).
The package contains:
• readme.htm file
• Disk1 directory
• Disk2 directory


2. From a command prompt, change to the Disk1 directory.

3. Run the installer:

setup.exe -jreLoc
is the full path to the location of the Sun Java 6 JRE (Java Runtime Environment) that
you installed. The JRE is located in the JDK installation directory.

For example:
setup.exe -jreLoc c:\Java\jdk1.6.0_43\jre

The Welcome page of the ADF installation wizard is displayed.

4. On the Welcome page, read the information, then click Next.

5. On the Install Software Updates page, click the Skip Software Updates radio button, then click Next.

6. On the Prerequisite Checks page, wait until the installation process passes all the necessary checks.If everything passes the checks, click Next.

7. On the Specify Installation Location page, verify that the Oracle Middleware Home directory is the location where you installed WebLogic, then click Next.

8. On the Application Server page, click the WebLogic Server radio button, then click Next.

9. On the Installation Summary page, verify the installation details, then click Install.

10. On the Installation Progress page, when the installation process has completed, click Next.

11. On the Installation Complete page, to exit the installer, click Finish.

Running the Oracle Endeca Server installer

is the full path to the location of the Sun Java 6 JRE (Java Runtime Environment) that
you installed earlier.

For example:
setup.exe -jreLoc C:\Java\jdk1.6.0_43\jre
The installation wizard Welcome page is displayed.


3. On the Welcome page, read the information, then click Next.



4. On the Prerequisite Checks page, if everything passes the checks, click Next.



5. On the Specify Installation Location page:
(a) For the Oracle Middleware Home field, verify the name of the Oracle Middleware home directory.
(b) For the Oracle Home Directory field, accept the default Endeca Server home directory.
This is the root directory of the Endeca Server installation.
(c) Click Next.





6. On the Select Deploy Mode page, uncheck the YES checkbox, then click Next.


7. On the Installation Summary page, verify the installation details, then click Install.


8. On the Installation Progress page, when the installation progress has completed, click Next.


9. On the Installation Complete page, to exit the installation wizard, click Finish.


When the installation finishes, the Endeca Server files and directories are written to the Oracle Home Location.

Creating the WebLogic domain for Endeca Server

Verifying the Endeca Server deployment

Installing Integrator

Creating the WebLogic domain for Studio

set JAVA_OPTIONS=-DUseSunHttpHandler=true -Djavax.xml.transform.TransformerFactory =com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl -Djavax.xml.parsers.DocumentBuilderFactory =com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl -Djavax.xml.parsers.SAXParserFactory =com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl

:

For example: https://localhost:8101

you get a "page not found" (404) error, then there are no applications on the domain's root context,and you can continue the Studio installation process.

you see the login page for a previously deployed Studio application, then you should un-deploy this application.

you see another application, then you should log in to the WebLogic Console, and then either remove the application or untarget it from the WebLogic Server instance.
For example, one common conflicting application is Oracle Enterprise Manager, which deploys an application to /em, but also installs the FMW Welcome Page Application to the root context.

Deploying Studio into the domain

Creating the WebLogic domain for and installing the Provisioning Service

Configuring the Provisioning Service

Verifying the Provisioning Service deployment

Configuring the Studio connection to the Provisioning Service

Oracle Endeca Installation Guidelines

1. Downloading the required for Oracle Endeca
2. Installing the Sun Java JDK for Oracle Endeca
3. Installing WebLogic Server and ADF Runtime for Oracle Endeca
   1. Installing WebLogic Server for Oracle Endeca
   2. Installing Oracle ADF Runtime for Oracle Endeca
4. Installing Oracle Endeca Server
   For Endeca Server, you first install the application, then create a WebLogic domain for it.
   1. Running the Oracle Endeca Server installer for Oracle Endeca
   2. Creating the WebLogic domain for Endeca Server for Oracle Endeca
   3. Verifying the Endeca Server deployment for Oracle Endeca
5. Installing Integrator
6. Installing Studio
   To install Studio, you first create the WebLogic domain for it, then deploy Studio into that domain.
   
   1. Creating the WebLogic domain for Studio for Oracle Endeca
   2. Deploying Studio into the domain for Oracle Endeca
7. Installing the Provisioning Service
   For the Provisioning Service, you use its domain template to create the WebLogic domain, then update the configuration.
   
   1. Creating the WebLogic domain for and installing the Provisioning Service for Oracle Endeca
   2. Configuring the Provisioning Service for Oracle Endeca
   3. Verifying the Provisioning Service deployment for Oracle Endeca
   4. Configuring the Studio connection to the Provisioning Service for Oracle Endeca

Weblogic 11g Installation

Install Java 64Bit:

Download the latest and check for compliance matrix.

Download WebLogic Server 10.3.6

Installation:

1. Install Java
2. Go to the folder where Weblogic server has been downloaded

3. java -Xmx1024m -jar wls1036_generic.jar (This is for Windows 64bit only)

Webloigc 12c Installation

Extract the file so that you have fmw_12.2.1.0.0_infrastructure.jar

Click Next

Click Next

Specify the OBIEE Location Path

Click Next

Click Next

Check the Checkbox

Click Yes

Click Install

Click Next

ODI 12c Installation on Windows (12.1.3)

Installation of ODI 12.1.3 is much easier and smoother than 12.1.2. Entire installation process consists of 2 wizards: infrastructure and odi.

Download ODI 12.1.3 Installers

From Oracle Website: https://www.oracle.com/technetwork/middleware/data-integrator/downloads/index.html download the following .zip installers:
+ Oracle Data Integrator 12cR1 (12.1.3) + Oracle Fusion Middleware Infrastructure

Unzip 2 downloaded files and you should see the following 2 folders in your odi_12c_installer folder:

FWM Infrastructure Installation

Run infrastructure jar installer:

Welcome screen:

Pick the location of Oracle_Home:

Installation type (we go with “Fusion Middleware Infrastructure with Examples”):

Prerequisites Check (java version and space available check)

Security updates:

Installation process:

ODI 12.1.3 Installation

Run ODI installer:

Welcome screen:

Installation locaation:

Installation type (we go with “Enterprise Installation”):

Prerequisite checks:

Installation progress:

Installation Complete:

Start ODI Studio:

You can find installed ODI 12c components in start menu:

Start ODI 12c Studio:

Post-Installation steps:

In relation to post-installation steps we need to create master and work repositories as well as configure ODI agents.

Create Master and Work Repositories:

Master and work repositories can be created with:

• ODI Studio Wizard
• RCU (Repository Creation Utility) that can be launched from: Oracle_HOME\oracle_common\bin\rcu.bat

Oracle Database 11g XE Installation

Bulk User/Group Creation in OBIEE using WLST

To create users in bulk and assigning groups for those users, use below python script and follow steps as given in screenshot

adminUser = 'weblogic' 
adminPassword = 'pwd' 
adminURL = 'adminserver_url:port' 

connect(adminUser, adminPassword, adminURL) 
serverConfig()
print 'lookup DefaultAuthenticator'
password = 'weblogic123'
atnr=cmo.getSecurityConfiguration().getDefaultRealm().lookupAuthenticationProvider("DefaultAuthenticator")
print 'create group gcp_group'
group = 'gcp_group'
atnr.createGroup(group,group)
atnr.addMemberToGroup('BIConsumers','gcp_group')
users = ['user1','user2']
for user in users:       
  print 'create user: ',user
  atnr.createUser(user,password,user)
  atnr.addMemberToGroup(group,user)

Archival of old OBIEE RPD File

import shutil
import os

# Change path of the source folder
path="/oracle/middle/instances/instance1/bifoundation/OracleBIServerComponent/coreapplication_obis1/repository"

source = os.listdir(path)

largest=None
smallest=None

# Calculate min and max version numbers of the RPD file
# RPD name SampleApp_BI0013.rpd

for files in source:
  if len(files) > 7:
          num=int(files[12:16])
   if largest is None:
        largest = num
    elseif num > largest:
        largest = num

    if smallest is None:
         smallest = num
   elseif num < smallest:
         smallest = num

# Initialize a counter to count number of files moved to archive folder

j=0
# Keeping latest 3 RPD version files
for i in range (smallest, largest-2):
    for files in source:
        if len(files) > 7:
          mmn=int(files[12:16])
         if i == mmn:
               j=j+1
               src = path +"/"+files
               dst = "/oracle/middle/instances/instance1/bifoundation/OracleBIServerComponent/coreapplication_obis1/repository/archive"+"/"+files
                shutil.move(src, dst)
print j, "files are moved"
 

OBIEE RPD Deployment Automation using WLST

1. Connects to WLST
2. Locks the System
3. Uploads the RPD
4. Commits Changes
5. Restarts BI Services

#
# This scripts expects the following arguments:
#
# 1. wls.host (localhost)
# 2. wls.port (7001)
# 3. wls.user  (user1)
# 4. wls.password  (password1)
# 5. repository filename and location
# 6. repository password
# ===================================================================
 
import sys
import os
 
# Check that the arguments to this script are as expected.
# argv[0] is script name, [1]-[6] are the user parameters

argLen = len(sys.argv)
if argLen -1 != 6:
    print "ERROR: got ", argLen -1, " args."
    print "USAGE: wlst.cmd RPDUpload.py WLS_HOST WLS_PORT WLS_USER WLS_PASSWORD repository_location repository_password"
    print "   eg: wlst.cmd RPDUpload.py localhost 7001 weblogic welcome1 c:\SampleAppLite.rpd Admin123" 
    exit()
 
WLS_HOST = sys.argv[1]
WLS_PORT = sys.argv[2]
WLS_USER = sys.argv[3]
WLS_PW = sys.argv[4]
rpdlocation = sys.argv[5]
rpdpassword = sys.argv[6]

# Connect to the WLS Admin Server, so that the script then runs “online”
 
print 'Connecting to '+ WLS_HOST+ ':' + WLS_PORT + ' as user: ' + WLS_USER + ' ...'
 
connect(WLS_USER, WLS_PW, WLS_HOST+ ':' + WLS_PORT);

# Connect to the BIDomainMBean that controls the BI domain
# We will use this MBean to lock and then commit our config changes

print 'Connecting to Domain ...'
domainCustom()

cd ('oracle.biee.admin')

cd ('oracle.biee.admin:type=BIDomain,group=Service')

# define the MBean parameters and data types as arrays  
 
objs = jarray.array([],java.lang.Object)
strs = jarray.array([],java.lang.String)

# Invoke the lock operation from the BIDomainMBean
# (equivalent to the Lock and Edit Configuration button in 
# Enterprise Manager

print 'Locking the domain ...'

invoke('lock',objs,strs)

# Read the name of the first instance from first entry 
# in the BIInstances property within the BIDomainMBean
# (initially returned as an array, first value selected)

biinstances = get('BIInstances')
biinstance = biinstances[0]

# Connect to the corresponding BIInstanceMBean

print ('Connecting to BIInstance MBean')

cd ('..')
cd (biinstance.toString())

# Retrieve the name of the MBean for managing the 
# BI Server configuration

biserver = get('ServerConfiguration')

# Connect to the ServerConfigurationMBean for this BI Server

cd ('..')
cd (biserver.toString())

# Now prepare for the RPD upload
# Prepare arrays for parameters and datatypes
# Load the parameters with the RPD name and password
# Then invoke the uploadRepository within the ServerConfigurationMBean

print ('Uploading repository ...')

argtypes = jarray.array(['java.lang.String','java.lang.String'],java.lang.String)
argvalues = jarray.array([rpdlocation,rpdpassword],java.lang.Object)

invoke('uploadRepository',argvalues,argtypes)

# Now go back to the BIDomainMBean and commit the change
# (equivalent to the Activate Changes button in Enterprise Manager)

print ('Committing the update ...')

cd('..')
cd('oracle.biee.admin:type=BIDomain,group=Service')
objs = jarray.array([],java.lang.Object)
strs = jarray.array([],java.lang.String)

invoke('commit',objs,strs)

print ('Now restarting the instance, to pick up the new RPD file')

print 'Connecting to BIInstance MBean ...'
cd ('..')
cd (biinstance.toString())

# The BIInstanceMBean controls the overall status of
# the Oracle instance, and if directed to stop or start
# will stop/start all components together

print 'Getting instance status ...'

# ServiceStatus property in BIInstanceMBean returns
# the current status of the instance

servicestatus=get('ServiceStatus')
print 'BIInstance MBean; ServiceStatus: ' + servicestatus

# Stop action, if invoked, will stop entire instance

print 'Calling stop ...'
objs = jarray.array([], java.lang.Object)
strs = jarray.array([], java.lang.String)
invoke('stop', objs, strs)
servicestatus=get('ServiceStatus')

print 'BIInstance MBean; ServiceStatus: ' + servicestatus

# Start action will start the instance, and pick up
# the configuration change (the new RPD file path)

print 'Calling start ...'
objs = jarray.array([], java.lang.Object)
strs = jarray.array([], java.lang.String)
invoke('start', objs, strs)
servicestatus=get('ServiceStatus')

print 'BIInstance MBean; ServiceStatus: ' + servicestatus

print 'RPD Upload now complete!'

exit()