Tuesday, July 19, 2011

OBIEE11g / WLST Adding Users to a Group

Posted this one on my WLST blog:

#
# Adding Users to a Group using WLST (online)
# John Minkjan Ciber Netherlands
#
print 'lookup DefaultAuthenticator'
atnr=cmo.getSecurityConfiguration().getDefaultRealm().lookupAuthenticationProvider('DefaultAuthenticator')

groups = ['companya','BIConsumers','BIAuthors']
for group in groups:
    users = ['user1','user2']
    for user in users:       
        print 'working user: ',user, ' group:', group
        try:
            atnr.addMemberToGroup(group,user)
        except:
            print 'user: ', user , ' can not be placed in group: ', group

Till Next Time

Saturday, July 16, 2011

OBIEE11g Multi Skin and Style Deployment

Before you read any further, start with reading the Oracle white paper :

http://www.oracle.com/technetwork/middleware/bi/customizing-oracle-biee-11g-176387.pdf

I don’t like doing any customisation within the weblogic server. First of all the paths are always long: d:\obiee11g\instances\instance1\bifoundation\OracleBIPresentationServicesComponent\coreapplication_obips1. Second, it’s very easy to loose you work when doing a reinstall….

Let’s start with create a new folder called OBIEE_LAF (OBIEE Look and Feel).

image

In this example i’m going to make 3 different Skins and Styles for 3 different companies (A, B and C). I made a copy from the original S_ & SK_blafp:

image

Keep the name lower case and without spaces!!

Next we have to tell the server that it is a application directory. Copy the WEB-INF folder from <<OBIEE_HOME>>\instances\instancen\bifoundation\OracleBIPresentationServicesComponent\coreapplication_obips1\analyticsRes to your LAF Folder:

image

Log in to the console > deployments and press the lock & edit button

image

Next press the install button:

image

Select the LAF folder:

image

Select install this deployment as a library

image

Deploy it to a bi server

image

Check I will make the deployment accessible from the following location:

image

Press Finish

image

Press activate changes

image

Check if it’s started:

image

Let’s check if it is reachable:

companya

image

companyb

image

companyc

image

Let’s tell the INSTANCECONFIG.XML what to do:

 

<!-- My Custom Stuff -->

<URL>
<CustomerResourcePhysicalPath>D:\OBIEE_LAF</CustomerResourcePhysicalPath>
<!-- CustomerResourcePhysicalPath is a tag that specifies the actual target directory name -->
<CustomerResourceVirtualPath>/OBIEE_LAF</CustomerResourceVirtualPath>
<!-- CustomerResourceVirtualPath provides the URLPrefix that will be added for sourcing all the files -->
<!-- If we don’t give this tag, BI EE will automatically add analyticsRes (System target directory) -->
</URL>
<UI>
<DefaultStyle>companya</DefaultStyle>
<!-- Without the S_ -->
<DefaultSkin>companya</DefaultSkin>
<!-- Without the SK_ -->
</UI>
</ServerInstance>

Till Next Time

Friday, July 15, 2011

OBIEE11g Exposing the Metadata Dictionary

You might have seen a couple of these on the net the last couple of days. So I thought I will give it a shot also. Problem was I couldn’t get it to work, which was driving me nuts….. Thanks to Paul from http://total-bi.com for leading me trough this temporary period of insanity Knipogende emoticon 

Ok here we go:

Start with a new folder on you file system called OBIEE_META:

image

copy the WEB-INF folder from the analyticsRes into this folder:

image

open the current active rpd offline in the administration tool: (this is the one ending with the highest _BI00xx number!)

image

goto tools > utilities

image

select Generate Metadata Dictionary:

image

Browse to the OBIEE_META folder

image

image

close the administration tool.

Check the OBIEE_META folder

image

!! sometimes the administration tool adds an .rpd extension to the folder, if so remove it !!

image

next open your weblogic console:

image

press the lock & edit button, go to deployments:

image

select install.

image

Enter the OBIEE_META folder location, press next

image

Select Install this deployment as an application, press next

image

Select the bi_cluster as deployment target, press next

image

Select I will make the deployment accessible from the following location, press next.

image

press finish.

image

press activate changes

image

go to the deployment screen and locate OBIEE_META.

image

start the application.

image

check the status:

image

open the instanceconfig.xml in an editor, add the following:

<!-- My Custom Stuff  Metadata Dictionary—>

<SubjectAreaMetadata>
   <DictionaryURLPrefix>http://localhost:9704/OBIEE_META/</DictionaryURLPrefix> 
<!-- replace localhost with the actual hostname –>

</SubjectAreaMetadata>

just above the </ServerInstance> tag

image

Open your enteprise manage en restart the presentation server:

image

Log in to analytics and create a new request:

image

don’t panic if the dictionary symbol isn’t enabled, you have to click on the subject area first!

image

Click on the symbol

image

Till Next Time

OBIEE11.1.1.5 Setting the Log Level in the online RPD.

First of all kudos to L. based on my article here: http://obiee101.blogspot.com/2011/07/obiee11-how-to-use-log.html he pointed me out how to set the log level in the rpd in 11.1.1.5.

Open the rpd in online mode and select manage > Identity

image

Select the BI repository and users tab:

image

Don’t be fooled (like me Knipogende emoticon) the users are already in the RPD.

Select Action > Set Online User Filter

image

Enter a *

image

Now you can set the loglevel:

image

Till Next Time

Thursday, July 14, 2011

OBIEE11g GROUPS are ROLES now

If you are old-school like me, you might be accustomed to using the NQ_SESSION.GROUPS variable. If you are setting up a new RPD in 11g this variable is depreciated. Use the NQ_SESSION.ROLES instead.

 image

Till Next Time

Wednesday, July 13, 2011

OBIEE11g Setting up Usage Tracking

---

Update: Paul McGarrick provides you with an update RPD: http://total-bi.com/2011/09/obiee-11g-usage-tracking-rpd/

---

Before you are going to send me an email “didn’t you do this here: http://obiee101.blogspot.com/2008/08/obiee-setting-up-usage-tracking.html ?”

Yes, I did, I just wanted to do an 11g variant, after getting this screen:

image

If you look around in the BIPLATFORM repository created by the RCU you will see that the S_NQ tables already have been created for you:

image

What is missing are the S_ETL tables. You can find the scripts in <<OBIEE_HOME>>\instances\instance1\bifoundation\OracleBIServerComponent\coreapplication_obis1\sample\usagetracking\SQL_ServerTime

image

Add the tables to your BIPLATFORM repository:

image

Open your RPD and set up a new database and connection pool:

image

Import the usage tracking tables:

image

For the S_NQ_ACCT table switch off the cache:

image

Create an alias for each table and put them in a separate physical display folder called Usage Tracking:

image

Set up your physical joins:

"A1_S_ETL_DAY"."DAY_DT" ="A1_S_NQ_ACCT"."START_DT"

and

"A1_S_ETL_TIME_DAY"."HOUR_MIN" = "A1_S_NQ_ACCT"."START_HOUR_MIN"

image

! Deploy your RPD to the BISERVER , do not yet restart !

Edit your NQSConfig.ini (found in <<OBIEE_HOME>>\instances\instance1\config\OracleBIServerComponent\coreapplication_obis1)

image

Restart the bi server:

image

Run some reports to check the tracking:

image

Check in your repository if the data gets loaded:

image

Next you can make a BM and presentation Layer:

image

And create a nice dashboard…..

 

Till Next Time