This is the fourth (and final!) part of a series of blogs showing how to perform a standard single server/instance installation of OBIEE 12c. In the first part I covered the prerequisites of JDK and Fusion Middleware. In the second part I performed the basic software installation for OBIEE; and in the third part covered creating the database repositories required for OBIEE.
In this final part I will perform the configuration of OBIEE 12c. This will setup the domain with Fusion Middleware, configure the BI components and most importantly setup the URLs so you can connect!
This is performed with the configuration utility which can be found under <obiee_home>/bi/bin
You need to be a little careful here, there are two config.sh (config.cmd for windows) files, but in different directories.
<obiee_home>/bi/bin contains the one for standard single server installations
ORACLE_HOME/oracle_common/common/bin contains the one for enterprise deployments. This is far more comprensive than the single server installation and allows you to configure multiple instances on multiple servers.
So to start the standard configuration utility:
cd /u01/app/obiee/bi/bin ./config.sh
As usual this is a graphical wizard, so you may need an x-windows emulator for linux/unix servers.
Unusually the welcome screen includes some options – don’t simply skip past as usual!
In here you get to choose which BI components you wish to configure:
- Business Intelligence Enterprise Edition – the main BI product
- Business Intelligence Publisher – if you need “pixel perfect” professional formatted output
- Essbase – if you want to use the BI accelerator to speed up reporting for users
A quick word on the Essbase option. There is a new component in OBIEE 12 called the “Essbase Business Intelligence Acceleration Wizard”. This is a tool that will build Essbase cubes based on fact/dimension structures in the RPD. It will interrogate the RPD for the hierarchies & data sources, build an Essbase ASO cube, load the dimensions and data and finally configure the RPD to use it, all via a small number of simple screens. I will probably blog about this separately later on.
However the full Essbase development tools are no longer available. You cannot use the Essbase Admin Console or Essbase Studio to build your own cubes and manually load them into the RPD – that’s not the reason Essbase is included within the OBIEE 12c product suite any more.
You can still implement Essbase separately from OBIEE 12c and import the cubes you build into OBIEE just as you could under OBIEE 11g, but that would be a completely separate implementation from OBIEE and of course require specific Essbase licences.
So why would you not simply tick all three options and carry on? I guess if you never intend to use any of these components then there is no point installing them – if you include Essbase then the Essbase agent and associated services will always be running, unnecessarily using resources if you never intend to use it.
So select your options and carry on.
Then the standard prerequisite checks are performed to ensure the server is configured correctly. I’m not really sure what the difference is between this pre-req check and the same one that happened during the earlier software install (in part 2 of this blog series). The list of checks seems to be identical.
So now we need to specify some details for the new BI domain.
All three of the settings for “Location of New Domain” default to the values:
Domains Directory: <obiee_home>/user_projects/domains
Domain Name: bi
Domain Home: <obiee_home>/user_projects/domains/bi
And you can change each of these if you see fit. Right now these are fine for me, so I’m going to leave them as they are.
Beneath these you need to specify the user name and password domain administrator. Again weblogic is the default, but can be changed and you must enter a password. Initially once the OBIEE 12c installation is complete you can login to the Weblogic Console, Enterprise Manager and OBIEE with this user-id (as we’ll see later on).
Now the wizard needs to know if you’ve already created the database repository schemas and if so where. This was done in part 3 of this blog series, however you do have the option of not installing the schemas with the RCU and letting this wizard do it for you.
If you did use the RCU, then choose ‘use existing schemas’, enter the connection string for the repository database and specify the prefix used on the schema names and the password.
There’s an interesting point here. In the RCU you have the ability to enter a single password for all schemas or individual passwords for each one. But in the screen below you are only asked for one password. I assume this is the password to the xxx_BIPLATFORM schema
If you decide to skip the RCU step and let this wizard create the schemas the screen appears as below. There are fewer options available:
- The only database type options are Oracle, Oracle RAC or MS SQL Server (no IBM DB2 or MySQL).
- You can’t specify different passwords for each schema.
- You can’t control the tablespaces the schemas are created in.
Next you need to specify the port range for the BI and WLS processes to use. There are quite a few port numbers required and it doesn’t seem to use then sequentially. Weblogic itself (console and enterprise manager) will get the first port number, the various OBIEE components will get allocated numbers in the next 15 or so, Essbase if included will get some much higher numbers.
I’ve left the default port range at 9500 to 9999. Which means the following ports get allocated:
Weblogic console/enterprise manager: 9500
Presentation Services: 9507
BI Server: 9514
BI Schedule: 9511
BI Cluster Controller: 9508
BI Java Hosts: 9510
Essbase Agent: 9799
All of these ports can be found in the enterprise manager after installation.
I’ve not so far found any options for specifying specific ports (as per the static-ports.ini file in OBIEE 11g)
You’re then asked if you want the sample application installed or your own BI application – this is an interesting new feature allowing you to install OBIEE with a pre-built suite of reports/dashboards etc… Definitely worth investigating later on.
The summary screen then displays showing the settings you’ve selected and main URLS for accessing the weblogic console, enterprise manager, OBIEE and BI Publisher (they’ve still not renamed this URL from xmlpserver…)
I usually save the response file at this point so I have a record of these details.
Clicking Configure then begins the process…
This can take a while to run through…took around 45 minutes for me on a slowish VM.
If you chose to let this wizard create the database repository schemas then it is done during this step as one of the long list of tasks – you shouldn’t see anything happen other than another ‘Success’ tick.
Once complete you will get the configuration complete screen:
This mentions the ports that have been allocated to each of the OBIEE components… except for the BI Server – the one you need to know the most as you’ll need it when you install the client tools and create an ODBC connection for the Administration Tool. If using the default port range it will be on 9514, alternatively look in the enterprise manager.
Click finish to close down the configuration wizard.
Upon closing it attempts to open a browser so you can login to OBIEE, but in my case it couldn’t find the default browser – no idea why, I’ve got three (IE, Firefox & Chrome) and entering the path to either of them did nothing:
No matter, I know how to open a browser…
So, enter the URL given in the summary screen above, in my case: http://linux66.local.com:9502/analytics
Use the weblogic (or whatever you changed it to above) user-id/password to login:
Definitely more colourful and some new features are immediately apparent – ‘Data Exploration & Discovery’ (Visual Analyzer) and the link to the new Home Page, which is at the alternative URL: http://<server_name>:9502/va
But back at the main OBIEE home page everything else is pretty much where it used to be and you can quickly view dashboards, create reports, etc. as you could before.
The final piece of the puzzle for installing OBIEE 12c is knowing how to start and stop all of its services. This is much simpler than before as there are now single scripts to start, stop and view the status of OBIEE.
These are all located in the <obiee_home>/user_projects/domains/bi/bitools/bin directory. The scripts being
(Presumably .cmd or .bat equivalents under windows).
So to start OBIEE:
cd /u01/app/obiee/user_projects/domains/bi/bitools/bin ./start.sh
Which once complete will show the following:
So there you have it, OBIEE 12c all installed, configured and running. There are a lot of differences to earlier versions, not just in functionality and look & feel, but also in the background and how it is deployed within the newer version of Weblogic. Keep an eye on our blogs for more!