OBIEE11g Tips and Tricks

Nice one from the people at BICG:

Till Next Time

OBIEE11g Geo Data

Mark did a nice one for the oracle magazine:

http://www.oraclemagazine-digital.com/oraclemagazine/20110506?sub_id=XlEEkfqlGJ7M&folio=49#pg52

Till Next Time

OBIEE11g DEFAULT_PRIVILEGES

By default every group or user defined in the RPD has read rights to each new element you add. This can be a bit of a pain in the a$$$ if you have a lot elements which each try own security group. Better to develop the RPD so that you have to grant each group access to a element.

This can be set in the NQSconfig.ini file:

Till Next Time

OBIEE Oracle Virtual Box Screen size

I had to configure an Oracle Virtual Box on my laptop, but the default max screen size was 800x600 . You can adjust this with:

VBoxManage.exe setextradata global GUI/MaxGuestResolution 1920,1080

from a windows command box.

Till Next Time

OBIEE11g Setting Multi User Development Options

When you are working on a MUD or Multi User Development RPD you can set some extra options.

In the MUD directory create a new option file for each master repository. It’s a TXT file called [RPD_NAME].opt fi: paint.opt. (be aware CaseSensitive!)

Set the properties of the file to hidden:

open the file in a text editor:

Add the following (INI style):

[Options]

BuildNumber = Yes

Admin = admin1;admin2

Mandatory Consistency Check = Yes

Equalize During Merge = Yes

Option	Description
BuildNumber	When set to Yes, the build version of the Administration Tool is displayed in the MUD history.
Admin	Lists multiuser development administrators. Administrators must be defined in the option file before they can delete MUD history. Administrators are defined by their computer/network login names. When multiple administrators exist, administrator names are separated by semicolons. For example: Admin=jsmith;mramirez;plafleur
Mandatory Consistency Check	When set to Yes, the publish step performs a consistency check. Publishing cannot proceed unless there are no errors in the given repository.
Equalize During Merge	When set to Yes, the multiuser development merge process performs mandatory equalization during MUD merges. Note that setting this option to Yes affects the performance of the merge process.

Mandatory Consistency Check &  Equalize During Merge can be experienced as a real pain in b*&t for developers because it forces them that everything is ok when checking in. I advise it only projects which are close to deployment for production to ensure some basic error checking.

Till Next Time

OBIEE11g using Dashboard Templates

When logging in for the first time you normally get an empty dashboard page:

Wouldn’t it be nicer if you can give a dashboard which already has some content ?

Let prep the instance config.xml

add: <DefaultName>Template</DefaultName> between the <Dashboard> tags

Now let’s make a template dashboard.

Step 1 build a nice dashboard:

Save this dashboard in the shared folder with the name ‘Template’

 

First create a folder Template:

 

Create a folder dashboards:

Next save:

Set the owner in the catalog

Create a new user:

don’t forget to assign it to a group:

Log in to OBIEE:

 

Check the catalog folder of the user to see that it’s actually saved as a personal dashboard.

This is ideal to create cooperate standard default dashboards for all users.

Till Next Time