Configuring OBIEE 11g alternative Authentication Provider

This post will guide to reconfigure your Oracle Business Intelligence installation to use Oracle Internet Directory(OID LDAP)

Step 1: Log in to Oracle WebLogic Server Administration Console, and click Lock & Edit in the Change Center

Select Security Realms from the left pane and click myrealm. The default Security Realm is named my realm. Display the Providers tab, then display the Authentication sub-tab

Click New to launch the Create a New Authentication Provider page

Enter values in the Create a New Authentication Provider page as follows: Name: Enter a name for the authentication provider.

For example, MyOIDDirectory. Type: Select OracleInternetDirectoryAuthenticator from the list. Click OK to save the changes and display the authentication providers list updated with the new authentication provider.

Click MyOIDDirectory in the Name column of the Authentication Providers table to display the Settings page. Display the Configuration\Common tab, and use the Control Flag list to select 'SUFFICIENT', then click Save.

Display the Provider Specific tab.

Use the Provider Specific tab to specify the following details:

Perform the following steps to set up the DefaultAuthenticator Control Flag setting: At the main Settings for myrealm page, display the Providers tab, then display the Authentication sub-tab, then select DefaultAuthenticator to display its configuration page. Display the Configuration\Common tab and select 'SUFFICIENT' from the Control Flag list. Click Save.

Reorder Providers as shown below:

Click Save. In the Change Center, click Activate Changes. Restart Oracle WebLogic Server.

MapViewer Runtime Failure

Accessing the MapViewer URL (http://hostname:port/mapviewer), returns an Error 500 Internal Server Error.
In the managed server log 

(MW_HOME/user_projects/domains/bifoundation_domain/servers/bi_server1/logs/bi_server1-diagnostic.log), the following error is recorded at start up:

[ERROR] [] [javax.enterprise.resource.webcontainer.jsf.application] [tid: [STANDBY].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'][userId: <anonymous>] [ecid: 0000Jvu4d^5FKAW5Hzt1if1He7T^000002,0] [APP: mapviewer#11.1.1] JSF1030: The specified InjectionProvider implementation 'com.bea.faces.WeblogicInjectionProvider' cannot be loaded.

Resolution:

Delete the WebLogic internal cache of the MapViewer application.

1. Stop the Managed Server (for example, bi_server1).
2. Delete the following files from the MapViewer deployment (for example, MW_HOME/Oracle_BI1/bifoundation/jee/mapviewer.ear

web.war/WEB-INF/lib/adf-faces-api.jar
web.war/WEB-INF/lib/adf-faces-impl.jar
web.war/WEB-INF/lib/commons-digester.jar
web.war/WEB-INF/lib/commons-logging-1.1.jar
web.war/WEB-INF/lib/jsf-api.jar
web.war/WEB-INF/lib/jsf-impl.jar
web.war/WEB-INF/lib/jsr173_1.0_api.jar
web.war/WEB-INF/lib/mvutil.jar
web.war/WEB-INF/lib/xdb.jar
web.war/WEB-INF/adf-faces-config.xml
web.war/WEB-INF/orion-web.xml

Also Recursively delete the following directory:
MW_HOME/user_projects/domains/bifoundation_domain/servers/bi_server1/tmp/_WL_user/mapviewer_11.1.1

Finally Restart the Managed Server.

Managed Server not starting after Upgrade

After you upgrade from Release 11.1.1.3, you might find that the Managed Server for Oracle Business Intelligence encounters issues. For example, the Managed Server might not start or might time out.

Error messages include:
out-of-memory error message related to "'PermGen Space" in bi_server1-diagnostics.log

Root cause:
Incorrect Java memory settings.

workaround:

You must edit a file called setOBIDomainEnv.cmd on Windows or setOBIDomainEnv.sh on UNIX. Ensure that you do not edit the similarly named setDomainEnv.cmd and setDomainEnv.sh files. The specifications in the setOBIDomainEnv file overwrite those in the setDomainEnv file.

1. Change to the following directory and locate the setup script (setOBIDomainEnv.cmd or setOBIDomainEnv.sh) for the Managed Server environment:
   MW_HOME\user_projects\domains\bifoundation_domain\bin\
2. Make a backup copy of the setOBIDomainEnv file.
3. Open the setOBIDomainEnv file for editing in a text editor.
4. Locate the following line:
   MEM_ARGS="-Xms256m -Xmx1024m -XX:MaxPermSize=256m"
   and replace it with this text:
   MEM_ARGS="-Xms256m -Xmx1024m -XX:MaxPermSize=512m"
5. Save the changes and close the file.
6. Restart the Node Manager and the Managed Server.
7. Rerun the Configuration Assistant to update the Oracle BI Domain.
8. Perform these steps for each Managed Server in the cluster.

Manually Enabling BI Composer

If you run the Configuration Assistant or the Configuration Wizard, then that program installs the files that are required for BI Composer. Before users can run BI Composer, you must manually enable BI Composer using an MBean.

To manually enable BI Composer:

1. Display the Fusion Middleware Control MBean Browser and lock the domain.
2. Navigate to the following folder:
   Application Defined MBeans, oracle.biee.admin, Domain:bifoundation_domain, BIDomain.BIInstance.PresentationConfiguration
3. Locate the following MBean:
   oracle.biee.admin:type=BIDomain.BIInstance.PresentationConfiguration,biInstance=coreapplication,group=Service
4. Set the value of the BIComposerEnabled attribute to "true".
5. Commit the changes and restart the system.

OBIEE 11.1.1.7.1 EXCEL 2007+ Download Error

I was attempted to export to excel 2007 and got a popup saying...
There was an error processing your download. Please check with your administrator' comes up.



Steps to Fix


Step-1:


Make sure that the following paramerters are given in the instance config file.


<Views>

<Pivot>

<!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control-->

<DefaultRowsDisplayedInDelivery>75</DefaultRowsDisplayedInDelivery>

<!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control-->

<DefaultRowsDisplayedInDownload>650000</DefaultRowsDisplayedInDownload>

<!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control-->

  <DisableAutoPreview>false</DisableAutoPreview>

  <MaxVisibleColumns>50000</MaxVisibleColumns>

  <MaxVisiblePages>10000</MaxVisiblePages>

  <MaxVisibleRows>500000</MaxVisibleRows>

  <MaxCells>400000</MaxCells>

  <MaxVisibleSections>55000</MaxVisibleSections>

</Pivot>

<Table>

<!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control-->

<DefaultRowsDisplayedInDelivery>75</DefaultRowsDisplayedInDelivery>

<!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control-->

  <DefaultRowsDisplayedInDownload>650000</DefaultRowsDisplayedInDownload>

  <MaxVisiblePages>10000</MaxVisiblePages>

  <MaxVisibleRows>500000</MaxVisibleRows>

  <MaxCells>400000</MaxCells>

  <MaxVisibleSections>55000</MaxVisibleSections>

</Table>

<Charts>

  <MaxVisibleColumns>50000</MaxVisibleColumns>

  <MaxVisiblePages>10000</MaxVisiblePages>

  <MaxVisibleRows>100000</MaxVisibleRows>

  <MaxVisibleSections>55000</MaxVisibleSections>

  <JavaHostReadLimitInKB>10240</JavaHostReadLimitInKB>

</Charts>

<Cube>

  <CubeMaxRecords>10000000</CubeMaxRecords>

  <CubeMaxPopulatedCells>100000000</CubeMaxPopulatedCells>

</Cube>

</Views>


Step 2:


Open <INSTANCE_HOME>\config\OracleBIJavaHostComponent\coreapplication_obijh1\config.xml, search for:


<XMLP>

<InputStreamLimitInKB>8192</InputStreamLimitInKB>

</XMLP>


* Replace 8192 with 0 and restart the OPMN processes.


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.


Note: It is HIGHLY recommended that you do not leave it unlimited except for testing purposes as it acts as a "governor" for machine resources.


Additionally be carefull to change the InputStreamLimitInKB in the XMLP tag, as there is another one under the DVT tag



Step 3:


1. Take a back-up copy of opmn.xml located in the directory:


<INSTANCE_HOME>/config/OPMN/opmn


·         Open opmn.xml


·         Find the OracleBIJavaHostComponent parameter:


<process-type id="OracleBIJavaHostComponent" module-id="CUSTOM">

<module-data>

<category id="start-parameters">

<data id="start-executable" value="$ORACLE_HOME/jdk/bin/java"/>

<data id="start-args" value="-server -Xmx1024M -Djava.security.manager=default -DXDO_FONT_DIR=$ORACLE_HOME/common/fonts -Djava.security.policy=$ORACLE_INSTANCE/config/$COMPONENT_TYPE/$COMPONENT_NAME/java.policy

-Djava.util.logging.config.class=oracle.core.ojdl.logging.LoggingConfiguration –


·         Change the heap size to 4096M.

·         Save the changes.


Then re-start the OBIEE components in Enterprise Manager.