"JAVA.LANG.NULLPOINTEREXCEPTION" when Adding Users to Application Roles in Enterprise Manager

Hi All,

Recently I faced an issue while adding AD users to specific application role in EM. Even though, users are present in AD and listed in users list in weblogic console, application was throwing error as shown below. Searching for the user with search string in Display Name section, returns the user without Principal name and throws java.lang.nul pointer exception. 

After spending lots of time on finding out the root cause, I finally got a breakthrough. Issue started appearing only after recent upgrade from 11.1.1.6+ to 11.1.1.7 release. So, when I searched in Oracle documents, I found that, certain attributes which are added in security provided configurations are no longer valid.



If you have configured below attributes in Security / Security Provider Configuration under Identity Store Configuration, this is not required in 11.1.1.7+ releases !!

•  user.login.attr
•  username.attr

So, remove those variables, follow below mentioned steps (Doc ID 1570390.1)

1. Log in to Enterprise Manager.
2. Click on WebLogic Domain.
3. Click on bifoundation_domain.
4. Click on the WeblLogic Domain drop down menu.
5. Click on Security / Security Provider Configuration menut item.
6. In the resulting page, remove the following variables then click the 'Configure' button to save the changes:
   •  user.login.attr
   •  username.attr
7. Restart WebLogic Server.
8. Restart the OBIEE services.

You are good to go. ;)

Cheers..

Working with BI Composer

In last post, I explained about installing & configuration of BI Composer. (Installing BI Composer)

Lets concentrate on exploring the features of BI Composer.

BI Composer component is available in modes : 

• Regular Mode -
• Accessible Mode - Accessible mode has same feautures except it is optimized for screen reading mode.
• Also, need to enable "Access to BI Composer" priviledge from the Admin/Manage Priviledges.

Example of BI Composer screen features :

Lets create a simple analysis using available options.

A. Click on New Analysis and select Subject Area (Sample Sales Lite). As we chose "wizard option" earlier from My Account, OBIEE will directly jump to BI Composer screen. First screen is displayed above.

B. Select Columns : In this step, you first select the columns that should be included in analysis.

Also, we can specify :

• Specify column interactions
• Specify/Edit a column formula
• Rename a colum

For Example, I have selected Product, Year, Company, Actual Unit Price, Avg Order Size, # of Orders. We can specify Drill and rename the column name from this step. Column Formula can also be changed as shown below.

C. Select Views : In this step, we will choose the views (Table/Pivot or/and Graphs) which can be added to the analysis. 

D. Edit Table - This option will provide options to change the properties of the Table view.

For example we can add following :

• Create prompts/Sections
• Use a column to create a section of the analysis
• Exclude certain columns from the tabular view.
• You can also preview the results.
• Arranging of the columns can be done only from the left pane properties.

E. Edit Graph : Similar to Edit Table, this option will provide options to edit the graph which is selected earlier.  Following options are avaialable.

Create prompts/Sections

Use a column to create a section of the analysis

Exclude certain columns from the tabular view. 

You can also preview the results.

Arranging of the columns can be done only from the left pane properties.

Change the Chart Sub Type (Ex. changing Horizontal -> Vertical,Stake bar)

F. Sort and Filter — In this step you apply sorting and filters to the views.
Sorting can be applied on the selected columns only, while you can add additional column for filtering the analysis. You can also add "Saved Filter" for this option.

G.Highlight — In this step you apply conditional formatting to the tabular view.

H. Save - Save the report in the new folder/existing folder.

I. View the Analysis -  Navigate to Catalog folder and view the analysis.

BI Composer is a new concept and I believe, this feature will be enhanced significantly in future releases. Still, it is powerful for the end user's analysis who do not want to get into the complexity of Answers development.

cheers..

BI Composer Installation & Setup

BI Composer is a simple-to-use wizard that allows you to quickly and easily create,

edit, or view analyses without the complexities of the "Analysis editor". 

BI Composer tool reminds of "Query Studio" of Cognos 8 Suites. This is mainly designed for Adhoc analysis where end users wants to develop queries/analysis on-the-fly.

Main Components of BI Composer are :

■ On the Top, Buttons for each step in the wizard.

■ On the left are the Catalog tab and the Subject Areas tab.

■ To the right of the tabs is the panel area, where the components for each step are

displayed.

■ To the far right are the Back, Next, Finish, and Cancel buttons.

  

We will cover all the steps in next blog, "Working with BI Composer". Lets focus on the installation/configuration first.

There are two basis steps required for the installation.

1. Extend the Oracle WebLogic Server domain to include the BI Composer application and the BI Composer run-time implementation shared libraries

2. Configuring the instanceconfig.xml file on the installed computer and on any scaled-out computers

Steps :-

A. Stop/Shutdown the server. (Including weblogic/OPMN)

B. Start the Oracle Fusion Middleware Configuration Wizard from Command/Unix located at

cd MW_HOME\wlserver_10.3\common\bin\config.exe

This will open up a new window for extending weblogic domain.

C. Select the Extend an existing WebLogic domain radio button

D. Select a WebLogic Domain Directory and Click Next.

MWHOME/user_projects/domains/bifoundation_domain

 

E. In the Select Extension Source page select the Extend my domain using an existing extension template radio button.

F. Click Browse and then select the oracle.bicomposer_template_11.1.1.jar file in the
following location: 

MWHOME/BI_HOME/common/templates/applications/oracle.bicomposer_tem plate_11.1.1.jar/ 

G.  Click Next -> Next -> Next -> Next -> Next. You don't need to specify/check any options from the list of Data sources/Test/Optional Configurations.

H. Click Done when Process is completed.

I. Add BI Composer Element in InstanceConfig.xml.

<ServerInstance>

.......

<BIComposer>

<Enabled>true</Enabled>

</BIComposer>

.......
</ServerInstance>

J. Start the server ( Admin/Managed/OPMN).

K. BI Composer is now available in Oracle Business Intelligence.


L. Login to OBIEE Application. Go to My Account and click on Wizard(limited functionality) under Analysis Editor option. 

M. Now Edit the Analysis/Create a New Analysis, which will open BI Composer screen for quick analysis.

In next blog, we will discuss about basic features of BI Composer.

Cheers..

Generating Metadata Dictionary

Metadata Dictionary is helpful for end users to retrieve more useful information about how metrics/attributes are derived and calculate in RPD layer.  This also gives a clear picture about how the particular object is brought from Physical -> Logical -> Presentation layer.

Key Notes :-

• A metadata dictionary is a static set of XML documents. This document needs to be updated for every change in RPD file.
• Each XML document describes, how such each object such as column, table is derived and its properties between different objects.
• This document can be viewed within OBIEE Presentation Service UI.
• Metadata dictionary files needs to be hosted on Web Server.

Here are the steps to configure and deploy metadata dictionary in OBIEE11g.

1. Open RPD in offline mode. ( Not possible to generate metadata dict. is online mode.)
2. Click on Execute from Tools->Utilities -> Generate Metadata Dictionary.

3. Provide the destination folder path and click OK. Message will be displayed on successful completion

of the process. It may take a while depending upon the size of the RPD.

4. Navigate to the destination folder to make sure that all the XML files are generated under the RPD name of original file.

Deployment of the metadata file

These files need to be deployed to the webserver so that OBIEE can read the files from the accessible location under the web server directory.

A. Copy the metadata_dict files & folder from the the original folder ( in my case, C:\MetaData_Dict) to the server location inside Instance folder.

Ex. $OBIEE_HOME\OBIEE11_6\instances\instanceX\MetaData_Dict

B. As these files need to be deployed to web server, we need to copy WEB_INF folder from

$OBIEE_HOME\OBIEE11_6\instances\instanceX\bifoundation\OracleBIPresentationServicesComponent\coreapplication_obips1\analyticsRes

C. Make sure both WEB-INF and Metadata files are copied under Metadata_Dict folder.

D. Go to weblogic console. Navigate to "Deployment" and select a new "Install"

E. Provide the path of a metadata dictionary and Click "Next".  For Unix/Linux, path will be the "Relative" path of a metadata_dict folder.

F. Choose Install this deployment as an application and click Next. Select I will make the deployment accessible from the following location and Click Next.

G. Navigate to Deployments. Go to metadata_dict in deployments table.Click on Start-> Servicing all requests.Metadata_dict should changed to Active state.

H. Update the instanceconfig.xml file.  

Open the file instanceconfig.xml located at

$OBIEE_HOME\OBIEE11_6\instances\instanceX\config\OracleBIPresentationServicesComponent\coreapplication_obips1

Add relevant entries within </ServerInstance>

<ServerInstance> ....

<SubjectAreaMetadata>
<DictionaryURLPrefix>http://localhost:7001/metadata_dict/</DictionaryURLPrefix>
</SubjectAreaMetadata>
...</ServerInstance>


I. Restart the services. Login to answers and go to the subject area.

G. Select the presentation table/column and Click on the icon for Metadata Dictionary

Note :-
Please make sure that, exact name is given for the physical paty/ Installed application (under console) and instance config entries. These are case-sensitive,too.

If you see path not found error, check the source of the error page. You would be able to see which path is being hit to retrieve metadata information and based on this, make necessary changes on the installed application or instanceconfig paths.

Also, RPD file name on the physical location should be same as the deployed RPD.

Cheers..