Very wide rows/columns when downloading dashboard to excel (OBIEE 12c)

Very wide rows/columns when downloading dashboard to excel
(OBIEE 12c)

         The problem was when you export whole dashboard or answer to excel, columns and rows goes to big (more than they have characters in it). Many of customers want to have identical data/visualization in excel file like they have in OBIEE portal are unhappy about it. Solution to resolve this problem is realy simple. Open file "xdo.cfg" (location: $OMW_HOME/user_projects/domains/bi/config/fmwconfig/biconfig/OBIJH/xdo.cfg) and change parameter named 

<property name="xlsx-keep-values-in-same-column">true</property>

to 

<property name="xlsx-keep-values-in-same-column">false</property> 

After that, restart all BI services and try to export excel file. You'll see that everything in excel is same like you see in OBIEE portal.

Cheers!

Problem when trying to export large PDF/XLSX file from OBIEE 12

If you try to export large report in PDF / XLSX format you will get error codes: "AGEGTYVF".

Reason is thread limit that is being encountered when streaming data from the presentation server to the javahost. To implement the solution, execute the following step:

• Open with text editor "config.xml" file from location:
  $OMWHOME/user_projects/domains/bi/config/fmwconfig/biconfig/OBIJH
• Set value "InputStreamLimitInKB" to "0" (zero, without the quotes).
  
  <XMLP><InputStreamLimitInKB>0</InputStreamLimitInKB>     <ReadRequestBeforeProcessing>true</ReadRequestBeforeProcessing></XMLP>
• Save changes and restart all BI services (including weblogic components)

0 means that this limit is deactivated. If this solves the issue and you would like to limit the maximum input size (in kilobytes) for requests that are sent to the JavaHost service, then gradually increase the parameter's value until you can export correctly.

Cheers!

OBI EE 12c - Changing search defaults

This article describes how to modify the search defaults in OBIEE 12c (12.2.1.0.0 and 12.2.1.1.0) from „Starts“ to „Contains“ and un-check „Match case“ mark which is checked in default. 

You must know that all files you modify in steps described below will be replaced when you apply new patch in the future. In that situation is better first to backup files you have modified before and replace files might changed after patching. 

First, we must backup files we are going to change.

Our „OMW_HOME“ is located on „/ora01/omw“ – please modify this path with yours Oracle Middleware home and locate following files:

• $OMW_HOME/user_projects/domains/bi/servers/bi_server1/tmp/_WL_user/analytics/za01ic/war/res/b_mozilla/common/availabledatabrowser.js
• $OMW_HOME/user_projects/domains/bi/servers/bi_server1/tmp/_WL_user/analytics/eiguw6/war/res/b_mozilla/common/availabledatabrowser.js
• $OMW_HOME/user_projects/domains/bi/servers/obips1/tmp/earmanager/analytics/MQxEfhyTZomEwq1mWe+CHA/res/b_mozilla/common/availabledatabrowser.js
• $OMW_HOME/user_projects/domains/bi/servers/bi_server1/tmp/_WL_user/analytics/za01ic/war/res/b_mozilla/uicomponents/obips.DropDown/obips.dropdownsearchdialog.js
• $OMW_HOME/user_projects/domains/bi/servers/bi_server1/tmp/_WL_user/analytics/eiguw6/war/res/b_mozilla/uicomponents/obips.DropDown/obips.dropdownsearchdialog.js
• $OMW_HOME/user_projects/domains/bi/servers/obips1/tmp/earmanager/analytics/MQxEfhyTZomEwq1mWe+CHA/res/b_mozilla/uicomponents/obips.DropDown/obips.dropdownsearchdialog.js

Open and edit each file specified above with text editor like „VI“ (on Linux) or „Notepad++“ (on Windows). When you open file(s) find string (you can copy string from here):

d.push(new obips.FormFields.Option(obiprp.PromptComponents.Utilities.getPromptResource("kmsgSearchStringContains").getString(),"contains"));

If you look better, you will see that string before that above is this below:

d.push(new obips.FormFields.Option(obiprp.PromptComponents.Utilities.getPromptResource("kmsgSearchStringStarts").getString(),"beginsWith"));

All you must do is to change order between this two strings („contains“ must be before „beginsWith“). If everything is done correctly, finally your strings must be same as this below:

d.push(new obips.FormFields.Option(obiprp.PromptComponents.Utilities.getPromptResource("kmsgSearchStringContains").getString(),"contains"));d.push(new obips.FormFields.Option(obiprp.PromptComponents.Utilities.getPromptResource("kmsgSearchStringStarts").getString(),"beginsWith"));

Repeat the same procedure in the remaining 5 file's specified above.

Second thing we must do is to un-check „Match case“ mark. Procedure is similar like procedure before. First, locate three files („obips.dropdownsearchdialog.js“):

·   

• $OMW_HOME/user_projects/domains/bi/servers/bi_server1/tmp/_WL_user/analytics/za01ic/war/res/b_mozilla/uicomponents/obips.DropDown/obips.dropdownsearchdialog.js
• $OMW_HOME/user_projects/domains/bi/servers/bi_server1/tmp/_WL_user/analytics/eiguw6/war/res/b_mozilla/uicomponents/obips.DropDown/obips.dropdownsearchdialog.js
• $OMW_HOME/user_projects/domains/bi/servers/obips1/tmp/earmanager/analytics/MQxEfhyTZomEwq1mWe+CHA/res/b_mozilla/uicomponents/obips.DropDown/obips.dropdownsearchdialog.js

      

Open and edit each file specified above with text editor. 

First, in each file find this string:

{var c=this.bCaseInsensitiveSearch;var d=this.bCaseInsensitiveSearch;this.matchCase=new obips.FormFields.Checkbox("matchCase","matchCase","matchCase",obiprp.PromptComponents.Utilities.getPromptResource("kmsgSelectionsMatchCase").getString(),d,c);

All you must do is to change part of string which is above highlighted in red, to "false". If you did everything correct, your string finally must be:

{var c=this.bCaseInsensitiveSearch;var d=false;this.matchCase=new obips.FormFields.Checkbox("matchCase","matchCase","matchCase",obiprp.PromptComponents.Utilities.getPromptResource("kmsgSelectionsMatchCase").getString(),d,c);

After all changes restart complete BI services and clear complete BI cache.

Result is:

Enjoy!

Changing the search defaults - OBIEE 11g

Changing the search defaults - OBIEE 11g

This article describes how to change the search defaults values from "Starts" to "Contains". In production, all users want their default value is "Contains", because it speeds up work in answers/dashboards. This customization was done in OBIEE 11.1.1.7.140715 on RHEL 6.7 server.


This is default in OBIEE portal:

All you must do is change order of one value in file (obips.dropdownsearchdialog.js) specified below:

$OMWHOME/user_projects/domains/bifoundation_domain/servers/AdminServer/tmp/_WL_user/analytics_11.1.1/silp1v/war/res/b_mozilla/uicomponents/obips.DropDown/obips.dropdownsearchdialog.js

Please, before starts editing file, make a copy!
In this file find string (without ""):
"c.push(newobips.FormFields.Option(obiprp.PromptComponents.Utilities.getPromptResource("kmsgSearchStringStarts").getString(),"beginsWith"));"

As you can see, this string is written before string specified below. Just "cut" string specified below and paste it before string specified above.
"c.push(newobips.FormFields.Option(obiprp.PromptComponents.Utilities.getPromptResource("kmsgSearchStringContains").getString(),"contains"));"

If operation was successfull it must be written like this ("..." indicate that this is only part of the string):

... c.push(newobips.FormFields.Option(obiprp.PromptComponents.Utilities.getPromptResource("kmsgSearchStringContains").getString(),"contains"));c.push(newobips.FormFields.Option(obiprp.PromptComponents.Utilities.getPromptResource("kmsgSearchStringStarts").getString(),"beginsWith"));
...

 After saving all modifications in file, please restart your OBIEE services from Enterprise Manager Console and when you log in, you can see that default value is "Contains":