Category Archives: Installation

Filegroup1 Error on 11g

One issue that is still present in the 11.1.1.5 version of OBIEE 11g is the corruption of the download files.
This happens to me one more than half the downloads of the enormous software bundle that is now OBIEE.
It seems that I am not alone, and a quick lap of the interweb reveals many different pieces of advice, but one OTN posting struck a chord with me –

This from CengizU:

Hello,
I’ve download bi_windows_x86_111130_32_disk1_2of2.zip 5 times with 3 different browsers and from 2 different PC ‘s and 3 different internet providers. Tried to extract with winrar, winzip and 7zip. But all I have is CRC error. Do I have to try one more to get the magical number of 6 or is there any place where I can download this file. Or may be Oracle should check the file whether it was really corrupted.
Cheers,

My guess is that there are a bunch different things going on from downing packets error to use of the wrong Zip software.

The most common solution seems to be to keep trying, one chap suggest 6 downloads should get you one working one, and this is usually the case for me too.
I have yet to figure out which Zip software Oracle are using but when I find out I’ll let you know.

The other solution that seems to work, although not always, is to use eDelivery (I have just checked and 1.1.5 version is NOT there yet!)

In the meantime, if you have a way of guarenteeing a succesful download please do tell!

@Adrian

Update:  I just had a clean run of downloads!!  I used a windows machine running w2k8 and IE.  Downloaded each file one at a time.  Opened each download using 7-Zip 9.2 and extracted to short named folder.   I will now try to install all into a clean VM.

Multiple OBIEE Environments on one Box

The Oracle preferred method of having multiple environments is to have them installed on their own machines, either real or virtual. For many organisations this is simple enough, particularly if you run a good environments service which facilitates the easy set-up of virtual Windows or Linux boxes.

Where there are limited resources you can actually choose to run OBIEE 10g many times on the same box. This is particularly useful in development and test servers, but can also work in production.

I have blogged about this in the past, but not passed on too many details, so here is the full step by step on how to create more than one environment.

These instructions are for a Linux box, if you want to see a windows sample head over to Robin Moffats blog. I am also using the inbuilt oc4j web/application server.

Some of these environments can be used in a cluster, there is no SSO here but you can also configure that in the web layer if you need. Integration with LDAP is not effected.

Here I will use example of a Development environment (DEV), and therefore you will see that in the shared areas I have referenced a folder for DEV. You can easily place all config files and repositories in one share for all environments, but would place Production ones on their own.

STEPS

  1. Create users
  2. Set-up box
  3. Install a full set-up
  4. Re-assign the Ports
  5. Configure environment
  6. Test
  7. Install a second set-up
  8. Re-assign the Ports
  9. Configure environment
  10. Test

repeat step 7 to 10 until you have built all your envs.

I built 10 environments in total on each box.

CREATE USERS

I prefer to have specific user accounts for OBI. Create them with an appropriate name, such as obiee_1, obiee_2, etc. Make them all part of the same group, say obi.

Example Commands

Adding a group:

groupadd obiee

Add Users:

useradd obiee_1
passwd obiee_1
useradd -G obiee

(or you could try adduser)

see my friend the internet!

SET-UP BOX

In order to manage your environments you need an install area, logs area, config files area and somewhere for the repositories.  You will also need somewhere to for cluster files (mainly webcat).  For clusters that use multiple boxes I like to use a common set of config files, which means placing the config files on a share that both machines point to.

My advice is to use the following:

/usr/obiee      	Installation folder
/var/obiee_logs         Logs folder
/obiee_share/config	config files
/obiee_share/publish	Webcat and RPD files

Once you have the top level folders in place then just add a sub folder for each environment. So for example, the env 1, which is used by obiee_1 has the following folders:

/usr/obiee/env_1  		Installation folder
/var/obiee_logs/env_1		Logs folder
/obiee_share/DEV/config/env_1	config files
/obiee_share/DEV/publish/env_1	Webcat and RPD files

Only obiee_1 has access to these folder (or if you prefer you can have the group have read only access)

The config folder has sub folders for each service:

/obiee_share/DEV/config/env_1/nq_server  (or bi_server if you prefer)
/obiee_share/DEV/config/env_1/saw_server
/obiee_share/DEV/config/env_1/bip
/obiee_share/DEV/config/env_1/web_server

Now the only thing to add some helpful environment settings, such as aliases and variables. These will help when moving around and finding files. Below are some example ones I have used.

alias l='ls -l'
alias u='ps -u obiee_1'
alias bi='cd /usr/obiee/env_1/OracleBI'
alias cata='cd /obiee_share/publish/env_1/webcat'

The above can be added to a .profile (or similar) file.

INSTALL 1

Now we are ready to install the software, and I will assume that there is not an already running version installed.  If there is, skip the install and just reconfigure it to use a different set of ports (see further below).

Make sure you have a suitable Java installed and decide how you are going to use java installs.  You can choose to use the one install for all the Obiee environments or you can have a version of java installed for each obiee env.

Run the obiee set-up script

/setup.sh –console

When prompted for the install locations specify:

/usr/obiee/env_1/OrcleBI
/usr/obiee/env_1/OrcleBIData

After the install check that your services are up and running (u shortcut).

RE-ASSIGN THE PORTS

Now we can update the ports to use numbers that are not going to clash with other obiee envs.  Note that once you have updated ports you may have to update your firewall settings to external access (i.e. for online repository access).

Richard Halldearn came up with the idea of just adding one thousand to each port setting, and it seems to work great.  So, we have installed environment 1, therefore we will add 1 x 1000 to each port number, for example 9703 becomes 10703.  Below are the ports that relate to OBIEE, and the file they are in.

9700 Monitor Controller port for Intra Cluster Communication with Cluster Controllers NQClusterConfig.INI
9701 Monitor Server port for Intra Cluster Communication with clustered Analytics Server OracleBI/server/Config/ NQClusterConfig.INI
9703 Remote procedure call port of Oracle BI Server, Outfacing port used for ODBC connections NQSConfig.ini / odbc.ini / NQClusterConfig.ini
9704 Standard port for OC4J used for Web Browser access, in Catalog manager etc. OracleBI/oc4j_bi/j2ee/home/config/instanceconfig.xml / default-web-site.xml
9705 standard port for BI Server scheduler instanceconfig.xml
9706 Client controller part Clustering NQClusterConfig.ini / odbc.ini
9707 Scheduler instanceconfig.xml
9708 scheduler instanceconfig.xml
9710 Listener Port for presentation services and ISAPI instanceconfig.xml / isapiconfig.xml / web.xml
9810 Java Host port instanceconfig.

Configure Environment

The next step is to edit the config files for your settings – SSO, Usage tracking, memory, clusters, logging, tns entries, dns entries, etc

Test

Now you have updated the ports and config settings, and pointed at new config file locations it is time to test the first install. The one component that will be shared across the environments is the chart server, so make sure that is running properly at this stage.

Repeat!

You can leave the first installation up and running if you like while you create a second environment, as above but add 2000 to the port numbers.

Keeping repeating until all your environments are built.

You can cluster two together as well and they should work as if you clustered to separate machines (although clustering two machines would be better!).

Footnote

Oh, even though it works absolutely fine, Oracle probably don’t want to support your install with this set-up, so best to use in dev and test environments, and if you have it in prod then you may have to turn off all but one if you get an issue (even though it will not be related to the multi environments!)

@drian

OBIEE 11g Windows Services

In 10g half your installation job is done for you; unix scripts and windows services all delivered out of the box, and pretty much working too!

In 11g you have to do the hard work yourself :(.

Firstly, you may be wondering why Oracle did not provide windows services already installed for you.  ME too!

Anyway, the point is you should create the services so that your OBIEE system stays up and running when you either log off the server, or your RDC is disconnected (normally due to IT time limits).

Now I am no Windows techie (nor Unix for that matter), so I would not know where to begin on creating a windows service (other than my friend Google).  Luckily I don’t have to, the Weblogic install includes a neat utility that does the techie bit for us, we just have to know how to call the utility.

Note that this article is based upon a real install I did last month for a client, on a Win 2008 32bit VM.  This is not just based upon a theory found in some Oracle documentation, or stealing other peoples blog postings.

Step-by-Step

The main tasks are:

  1. Stop your obiee system (of course!)
  2. Create a boot file (for the passwords)
  3. Create the command files (that will be used to create and update the services)
  4. Create the utility files (that call the Weblogic Utility.)
  5. Run the commands created in step 3.

1. Stop OBIEE 11g

This includes:

  • BI Applications
  • Weblogic Managed servers
  • Weblogic Admin Server
  • Windows services (Node manager and OPM)

2.  Boot File

In order for the services to start without user intervention then you need to store the username and password in a file on the server.  It’s a simple file with: username and password on two lines.

username=weblogic
password=mypwdhere

See example here : Shiva

3.  Command Files

The first command file create the Admin Server service, the second creates a BI Server service, and finally a batch file to update the existing Node manager service.

Admin Server Script


@rem *** Install the BI Windows services
@rem Created by:  Adrian Ward
@rem Created March 7th 2011
@rem Includes a delay tag
@rem Calls the beasvc.exe
@rem *************************************************************
@echo off
SETLOCAL
set MW_HOME=C:OracleFMW
set OPMN_PORT=9500
set wls.host=hostnamehere
set wls.admin.port=7001
set wls.mgd.port=9704
set wls.mgd.name=bi_server1
set BI_URL=http://%wls.host%:%wls.mgd.port%/analytics
set JAVA_HOME=C:OracleFMWOracle_BI1jdk
set PRODUCTION_MODE=true
set DOMAIN_HOME=%MW_HOME%user_projectsdomainsbifoundation_domain
set WLS_HOME=%MW_HOME%wlserver_10.3
set INSTANCE_HOME=%MW_HOME%instancesinstance1
set ORACLE_BI_HOME=%MW_HOME%Oracle_BI1
set ANT_HOME=%MW_HOME%modulesorg.apache.ant_1.7.1
set DOMAIN_NAME=bifoundation_domain
set USERDOMAIN_HOME=%MW_HOME%user_projectsdomainsbifoundation_domain
set SERVER_NAME=AdminServer
Call "C:OracleFMWuser_projectsdomainsbifoundation_domainbinsetDomainEnv.cmd"
Call "C:OracleFMWwlserver_10.3serverbininstallSvc_Admin.cmd"
ENDLOCAL

The above script sets the variables you need, then calls a couple of other command files (see below what they do)

BI Server 1

@rem *** Install the BI Windows services
@rem Created by:  Adrian Ward
@rem Created March 7th 2011
@rem Includes a delay tag
@rem Calls the beasvc.exe
@rem ***************************************************************

@echo off
SETLOCAL

set MW_HOME=C:OracleFMW
set JAVA_HOME=C:OracleFMWOracle_BI1jdk
set PRODUCTION_MODE=true
set DOMAIN_HOME=%MW_HOME%user_projectsdomainsbifoundation_domain
set WLS_HOME=%MW_HOME%wlserver_10.3
set INSTANCE_HOME=%MW_HOME%instancesinstance1
set ORACLE_BI_HOME=%MW_HOME%Oracle_BI1
set ANT_HOME=%MW_HOME%modulesorg.apache.ant_1.7.1
set DOMAIN_NAME=bifoundation_domain
set USERDOMAIN_HOME=C:OracleFMWuser_projectsdomainsbifoundation_domain
set SERVER_NAME=bi_server1
set ADMIN_URL=http://localhost:7001

Call "C:OracleFMWuser_projectsdomainsbifoundation_domainbinsetDomainEnv.cmd"
Call "C:OracleFMWwlserver_10.3serverbininstallSvc_BIServer.cmd"

ENDLOCAL

Again this command file sets the variables for managed BI Server service, then calls the command file which calls the create windows service utility.

Update Service Batch Command

In order to run all the services, and in the right order, we need to update the existing service (i.e. the one that Oracle did provide).  This is done by using the sc command (yes my friend Google helped here!).

sc config OracleProcessManager_instance1 depend= "Oracle bi_server1" start= auto

4.  Create Utility Files

There is a command file already in place that calls the utility that create the service (called InstallSvc.cmd).  Some documents and blogs suggest that you update this existing file, run it for the Admin Server service, then update the file again and run it for the BI Server service.  I find it’s much easier to create the exact files you need from a copy of the existing Svc command file, then you can package them all up and can be run by the Sys admin people in any installation, including production.

So, from the above code listings you can se that we call installSvc_Admin.cmd and installSvc_BIServer.cmd.  These are very similar except for the command line which has a subtle difference in the options.  This differences are only in the last section where it calls the beasvc utility.

So, take a copy of the existing InstallSvc.cmd and update the last section as below:

installSvc_Admin.cmd

rem *** Install the service
“%WL_HOME%serverbinbeasvc” -install -svcname:”Oracle AdminServer” -depend:”Oracle WebLogic NodeManager (C_Oracle_FMW_wlserver_10.3)” -delay:240000 -javahome:”%JAVA_HOME%” -execdir:”%USERDOMAIN_HOME%” -maxconnectretries:”%MAX_CONNECT_RETRIES%” -host:”%HOST%” -port:”%PORT%” -extrapath:”%EXTRAPATH%” -password:”%WLS_PW%” -cmdline:%CMDLINE% -log:”CC:OracleFMWuser_projectsdomainsbifoundation_domainserversAdminServerlogswinsrvc_AdminServer-stdout.txt”

installSvc_BIServer.cmd

rem *** Install the service
“%WL_HOME%serverbinbeasvc” -install -svcname:”Oracle bi_server1″ -depend:”Oracle AdminServer” -delay:180000 -javahome:”%JAVA_HOME%” -execdir:”%USERDOMAIN_HOME%” -maxconnectretries:”%MAX_CONNECT_RETRIES%” -host:”%HOST%” -port:”%PORT%” -extrapath:”%EXTRAPATH%” -password:”%WLS_PW%” -cmdline:%CMDLINE% -log:”C:OracleFMWuser_projectsdomainsbifoundation_domainserversbi_server1logswinsrvc_bi_server1-stdout.txt”

Notice that the simple differences are in the -depend, – svcname, -log and -delay options.

Now you have created the files you can call them and your wndows services will appear!

Good luck.

OBIEE 11g Integration With Active Directory

Having just installed 11g in a Windows 2008 I thought I would share the experience.

It was actually fairly simple, but there were a couple of gotchas.

Thankfully Oracle produced a white paper on this in December last year, which I will show extracts of below:

  

Introduction

The paper examines how to configure Oracle Business Intelligence Enterprise Edition (Oracle BI EE) 11.1.1.3.0 to use Windows Server Active Directory (AD) as an LDAP Authentication source and how to use Windows Native Authentication (WNA) in an SSO environment.

The aim is to describe the configuration and setup required so that users may log on to their Windows PCs and access Oracle BI EE via a standard web browser with no further authentication required on their part – Windows Native Authentication and Oracle Weblogic will be doing the hard work to authenticate users to Oracle BI EE using their standard network logins without further troubling authorised users of the system.

There are several steps to be performed in Active Directory itself, in the Weblogic Server hosting Oracle BI EE, in the Oracle BI EE web app and finally on the client machine(s) from which you wish users to access Oracle BI EE using Windows Native Authentication SSO.

The steps in the document have been tested with Oracle BI EE version 11.1.1.3.0 and Active Directory 2008 (Windows Server 2008).

Stage 1: Using Active Directory as a User store

Before we can think about having clients authenticate using Single Sign On from machines in the AD domain, first we must configure Oracle BI EE to recognise the AD domain as a valid user store to authenticate Oracle BI EE users against. This is a standalone operation in its own right – once we have completed this section, XYZ Corp users will be able to log in to Oracle BI EE using the same credentials as they use to log in to the Windows domain.

NB this also requires Group information to be stored in Active Directory – i.e. once authenticated in this way, the system will expect users to be organised in AD groups. So users must be assigned to groups in Active Directory, rather than assigning Group/Role information in INIT blocks, as was the case in Oracle BI EE 10g. AD groups can then be assigned to Application Roles in Enterprise Manager to provide access to functions of the system.

What you need to know

To complete this stage, we need the following pieces of information:

Active Directory Server name/port: we need the name of the AD server and the port on which it’s listening for LDAP requests (defaults to 389). So in our example scenario this is addc.xyzcorp.com:389

Base DN: the base LDAP path from which all searches start for users and groups. In our example scenario, this is: CN=Users,DC=xyzcorp,DC=com 

for the Users Base DN and

CN=Builtin,DC=xyzcorp,DC=com

for the Groups Base DN.

GUID attribute: attribute in LDAP used to represent the GUID of users and groups (defaults to objectguid for Active Directory)

DN/Password for LDAP Principal: the LDAP DN for the user we will connect to Active Directory as when retrieving information about LDAP users. In our example scenario, this is: CN=jsmith,CN=Users,DC=xyzcorp,DC=com

We’ll also need the password for the user, obviously. NB the user need not be an administrative account, but it does need to have sufficient privileges to be able to make arbitrary queries on the LDAP tree.

Configuring Active Directory Authenticator in Weblogic

Log on to the Weblogic Admin console at http://bieesvr1.xyz2.com:7001/console

On the left hand side of the screen is a Domain Structure menu. Select “Security Realms” then on the main page, click on the link for the domain security realm (default “myrealm”), then the Providers tab in the main screen, followed by the Authentication subtab.

Click the “Lock and Edit” button in the top left of the WLS Admin console so we can create a new authentication provider, then click the New button at the bottom of the table of current Authentication Providers in the main screen.

 

 

  

In the Create New Authenticator screen, type in a suitable name (ADAuthenticator in the example below) and select the type as ActiveDirectoryAuthenticator, then click OK.

You’ll now be taken back to table of authentication providers, with your new provider at the bottom and the DefaultAuthenticator at the top. Click on the link to DefaultAuthenticator to edit its properties.

 

 

In the Common Authentication Provider Settings screen, change the Control Flag drop-down from REQUIRED to SUFFICIENT and click on the Save button. For further information on the implications of these settings, consult the Weblogic Server documentation on “Configuring Authentication Providers” at http://download.oracle.com/docs/cd/E14571_01/web.1111/e13707/atn.htm#i1204568 which contains a detailed explanation of these settings 

Go back to the table of authentication providers and click on the link to your new provider (ADAuthenticator in the example) to edit its properties. 

In the Common Authentication Provider Settings screen, change the Control Flag drop-down from OPTIONAL to SUFFICIENT and click on the Save button

  

Next select the Provider Specific tab to bring up the options which apply specifically to connecting to an Active Directory LDAP authentication store. This is where we need specific information about the AD store we’re trying to connect to.

Host Name of the AD server addc.xyzcorp.com  
Port Port the AD server is listening for LDAP requests on 389
Principal the LDAP DN for the user we will connect to Active Directory as when retrieving information about LDAP users CN=jsmith,CN=Users,DC=xyzcorp,DC=com
Credential/Confirm credential password of the principal specified in the stage above welcome1
User Base DN LDAP query used to find users in AD CN=Users,DC=xyzcorp,DC=com
User Name Attribute Attribute used to specify user name in AD – defaults to cn. Do not change unless you know your AD is configured to use a different attribute for user name. If you do change it, see the section on Changing user/group name attributes below cn
User Object class   user
Group base DN  LDAP query to find groups in AD – NB only groups defined under this path will be visible to Weblogic CN=Builtin,DC=xyzcorp,DC=com
GUID attribute The attribute used to define object GUIDs in AD objectguid

Reordering Providers

Return to the main Authentication Provider screen (Security Realms->myrealm->Providers->Authentication). Click the Reorder button, then select the tickbox next to your ActiveDirectoryAuthenticator (ADAuthenticator in our example), then use the shuttle control to put the ActiveDirectoryAuthenticator at the top of the list.

Changing User/Group Name Attributes

If your AD server uses a different attribute for User Name you will need to change the User Name attribute from the default “cn”. If you do change this attribute, you will also need to change the settings for AllUsersFilter and UserFromNameFilter as shown in the table below (using the example of the user name being stored in an attribute called AnOtherUserAttribute)

Attribute Name Default Setting Required New Setting
UserNameAttribute cn AnOtherUserAttribute
AllUsersFilter (&(cn=*)(objectclass=person)) (&(AnOtherUserAttribute =*)(objectclass=person))
UserFromNameFilter (&(cn=%u)(objectclass=person)) (&(AnOtherUserAttribute =%u)(objectclass=person))

For UserName Attribute only, you also need to add two properties to the Identity Store configuration (user.login.attr and and username.attr) to tell it about the attribute you’re expecting to get user name from (it defaults to using “uid” if none is specified). These settings are reached via the Security Provider Configuration screen, which is accessed via Enterprise Manager. Select Weblogic Domain -> bifoundation_domain->(right click) Security -> Security Provider Configuration.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

This brings up the main Security Provider Configuration screen, find the Identity Store Provider section in the middle of the screen and select the “Configure…” button to bring up the Identity Store Configuration screen. Click on the green + icon to add the new properties to the Identity Store and as stated above, two new properties need to be added, user.login.attr and username.attr, both set to the value of the alternate user name attribute.

 

 

On install, Oracle BI EE creates an internal account in the Weblogic LDAP store, BISystemUser, which is used for service-to-service authentication. The credentials of this account are stored in the Credential Store under the system.user key. Before you proceed any further you need to point this system.user key to a set of credentials available in Active Directory.

You can if you wish use the credentials of an existing user, however we would recommend creating a user account explicitly for this purpose – this is not an ordinary user account but rather a set of credentials used to authenticate services within the system to each other.

Whether you decided to use an existing account or create a new one, the process for changing the system.user is the same.

 
In Enterprise Manager, select Weblogic Domain -> bifoundation_domain->(right click) Security -> Credentials, this brings up the Credential Store configuration screen. Select the oracle.bi.system map, expand it and select the system.user key. Reset the username and password to your chosen account credentials – the example below shows resetting to a new bisystemuser 

account created in Active Directory to replace the BISystemUser account in the default WLS LDAP referenced by the Default Authenticator.

Next you need to ensure your new system user account is part of the BISystem Application Role.

In Enterprise Manager, select Weblogic Domain -> bifoundation_domain->(right click) Security ->Application Roles. This brings up the Application Roles configuration screen.
In the drop-down box labelled “Application Stripe to Search”, select “obi” and press the green “play” button next to the Role Name text box.

This will bring up a list of application roles, one of which should be BISystem account created in Active Directory to replace the BISystemUser account in the default WLS LDAP referenced by the Default Authenticator.

Next you need to ensure your new system user account is part of the BISystem Application Role In Enterprise Manager, select Weblogic Domain -> bifoundation_domain->(right click) Security Application Roles. This brings up the Application Roles configuration screen

In the drop-down box labelled “Application Stripe to Search”, select “obi” and press the green “play” button next to the Role Name text box. This will bring up a list of application roles, one of which should be BISystem

Select BISystem, and click the “Edit” button to edit the application role.

 

 

 

 

 

 

 

 

In the Edit Application Role screen, scroll down to the Users section and click on the button marked “Add User”.

An Add User dialog will appear. Either type your system user username into the User Name box or for a full list of users, leave it blank.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Again, click the green “Play” button next to the text box and a list of users will appear in the “Available Users” selection box.

Select the name of your system user account and use the shuttle control to move it into the list of Selected Users. Click OK to dismiss the Add User dialog.

Back in the main Edit Application Role Screen, click the OK button in the top right of the screen to apply the changes to the BI System Application Role.

The final stage of configuring the new system user is to ensure they are part of the Weblogic Global Admin role.

Log into Weblogic Admin console

Select Security Realms from the left-hand menu, click on the link to your security realm in the main screen (e.g. myrealm), then select Roles and Policies from the tabs along the top 

In the list of roles, click on the plus sign to expand Global Roles, then Roles, then click on the link marked View Role Conditions for the Admin Role.

Ensure the conditions specified will match your user, either directly, or by virtue of a group they belong to (e.g. condition may be User = bisystemuser or Group=Administrators

If you have made any changes, click the Save button. Changes should be applied immediately

If you have made any changes, click the Save button. Changes should be applied immediately

Once you have changed the system user credentials in this way, you will need to restart the BI Server and BI Presentation Server before  these changes will take effect. The easiest way to do this is via Enterprise Manager – select Business Intelligence and Restart All Components.

Mapping Active Directory Groups to Application Roles

Access to functions within Oracle BI is controlled via Application Roles. For a detailed discussion of the purpose and function of the Application Roles, please see the product documentation, for now it will suffice to say that in order for your Active Directory domain users to be able to use the system, they (or rather the groups they are in) need to be mapped to Application Roles.

The process for doing this is as for assigning the system user to the BISystemRole, described above, with the exception that we map groups to the role, not just an individual user.

Testing your changes

Once you’ve restarted Weblogic, check that you can still log into the Weblogic Administrative Console as the Weblogic admin user you specified during install.

Next check you can log in to Oracle BI using the credentials of one of the Active Directory users.

 

Source:

Oracle White Paper:  Dec 2010.  Configuring authentication and SSO with Active Directory and Windows Native Authentication in Oracle Business Intelligence Enterprise Edition. 

References

[1] Oracle® Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1) http://download.oracle.com/docs/cd/E14571_01/bi.1111/e10543/toc.htm

[2] Configuring Single Sign-On with Microsoft Clients

http://download.oracle.com/docs/cd/E12839_01/web.1111/e13707/sso.htm

[3] Java GSS-API Troubleshooting Guide

http://download.oracle.com/javase/1.5.0/docs/guide/security/jgss/tutorials/Troubleshooting.html

[4] Microsoft support note on enabling DES encryption on Windows 2008 and Windows 7

http://support.microsoft.com/kb/977321

[5] Microsoft TechNet setspn overview

http://technet.microsoft.com/en-us/library/cc773257(WS.10).aspx

[6] Securing Oracle Weblogic Server

http://download.oracle.com/docs/cd/E14571_01/web.1111/e13707/toc.htm