RSS

Tag Archives: data transformation

OBIEE 11G – Important Security Considerations (SSL) if using external LoadBalancer

In OBIEE enterprise topology, make sure the external load balancer used should be able to terminate SSL requests at the load balancer and forward traffic to the back-end real servers using the equivalent non-SSL protocol (for example, HTTPS to HTTP).

For security purposes, and because the load balancer terminates SSL requests (Oracle HTTP Server routes the requests as non-SSL to WebLogic Server), after SSL is configured for the load balancer, turn on the WebLogic Plugin Enabled flag for the domain. To do this, follow these steps:

1. Log in to the Administration Console.
2. Click the domain name in the navigation tree on the left.
3. Click the Web Applications tab.
4. In the Change Center, click Lock & Edit.
5. Select WebLogic Plugin Enabled.
6. Click Save, then click Activate Changes.
7. Restart the Administration Server and Managed Server.

Tip: WebLogic Plugin Enabled: Specifies whether or not the proprietary WL-Proxy-Client-IP header should be honored. (This is needed only when WebLogic plugins are configured.)

In additon to above, make sure Oracle HTTP Server (OHS) to add the following SSL directives in each <location> section to the ORACLE_BASE/admin/instance_name/config/OHS/component_name/mod_wl_ohs.conf file:

WLProxySSL ON

WLProxySSLPassThrough ON

Tips: Set WLProxySSL parameter to ON to maintain SSL communication between the plug-in and WebLogic Server when the following conditions exist:

An HTTP client request specifies the HTTPS protocol
The request is passed through one or more proxy servers (including the WebLogic Server proxy plug-ins)
The connection between the plug-in and WebLogic Server uses the HTTP protocol
When WLProxySSL is set to ON, the location header returned to the client from WebLogic Server specifies the HTTPS protocol.

Reference: https://blogs.oracle.com/pa/entry/obiee_11_1_1_important1

Thanks,
Shiva

 
Leave a comment

Posted by on July 16, 2012 in BI Publisher, OBI EE, OBIEE 11g

 

Tags: , , , , , , , , , , , , , ,

RCU Schema Configuration failed with the error “The specified prefix already exists”

We all know that we need to create RCU schemas before starting OBIEE 11G (In fact, for any Fusion Middleware application) Installation. Because it is the base store for FMW.

Recently I came across a scenario where my customer created RCU schemas with Oracle Repository Creation Utility (RCU) version 11.1.1.3.0 and Installed OBIEE 11.1.1.3.0. Now after new OBIEE 11.1.1.5.0 release he wants to upgrade his application from 11.1.1.3.0. But he is not interested at the In-place upgrade. So we uninstalled weblogic and OBIEE 11.1.1.3.0 and started RCU 11.1.1.3.0 to drop the _BIPLATFORM and _MDS schemas.

The RCU shown up with successful message and so we thought everything is cleaned up and it’s good to create schemas again. I started RCU 11.1.1.5.0 and selected Oracle Business Intelligence component and given prefix as DEV. But am not able to assign this prefix and got a message like “The specified prefix already exists”.  Though I got successful dropped schemas message, just for cross check I looked at database for the DEV_BIPLATFORM and DEV_MDS schemas. There I am not seeing any of them.

Then I checked at dropped schemas log generated by RCU and realized that there is an entry in System.SCHEMA_VERSION_REGISTRY$ table which is stopping me to assign the same DEV prefix which we used for earlier version schemas.

Actually the RCU should drop schemas using mdsschemamanager.pl script. This script has capability to do cascade delete and will delete entries in System.SCHEMA_VERSION_REGISTRY$ table.

To make sure this log into RCU DATABASE as sys and run the following SQL Query:

Select * from System.SCHEMA_VERSION_REGISTRY$;

If this query returns any record then it means the RCU didn’t drop the schemas properly.

Actually what happened in this case is the RCU schemas were not dropped using mdsschemamanager.pl script, it’s just dropped with normal schema delete and the resulting repository record for the schema is not clean. Keep in mind, this is just in case if you want to use same prefix. Otherwise RCU will let you proceed to create new prefixed Schemas.

If the RCU schemas have been deleted incorrectly using the RCU drop user command, then We need to clean these entries before starting new repository schemas creation.

To do this, run the following SQL*Plus command as sys to complete the removal of the RCU schemas records in the repository database:

delete from System.SCHEMA_VERSION_REGISTRY$;

Once you confirmed there are no entries in System.SCHEMA_VERSION_REGISTRY$  table and start the RCU to create repository schemas with the prefix (DEV in my case). The RCU will go smooth and wont complain with any error.

Hope this helps you in your RCU issues troubleshooting.

 

Thanks,

Shiva

 
8 Comments

Posted by on November 16, 2011 in BI Publisher, OBI EE, OBIEE 11g

 

Tags: , , , , , , , , , , , , ,

Predefined Presentation Variables in OBIEE 11G

The OBIEE has couple of predefined presentation variables which we can reference in analyses, dashboards, KPIs, and agents. we can take advantage of these varaibles and can be used in analysis for better presentation.

The below table contains a list of the predefined presentation variables. For time zone variables, the time zone for a user must be set to a value other than Default in order for this variable to work. (Users set their preferred time zone in the “My Account dialog: Preferences tab”.)

Note that the syntax for these predefined presentation variables omits the variables qualifier. 
for example, @{session.locale} rather than @{session.variables.locale}.


Hope this post helps you in your report developments.


Thanks,
Shiva
 
Leave a comment

Posted by on October 23, 2011 in BI Publisher, OBI EE, OBIEE 11g

 

Tags: , , , , , , , ,

what is the DXE Execution in OBIEE 11G Session log?

In OBIEE 11G if we look at Session logs, we will see a new status called ‘DXE Execution’ with amount of time its been executed. I did some research on this to answer my burning questions ‘ What this new alien will do? and How it is helpful for Performance tuning?.

Then I founded interesting news about this and actually the DXE Execution means “Data Transformation Engine which handles post-processing of the BIServer results within OBIPS”.

The post-processing can involve resorting, filtering, aggregating, and/or indexing the original BIServer result set so that the data can be consumed by a view’s renderer. And It can be automatically kicked off when the BIServer query finishes.

So if the DXE Execution is running long time, Then it’s time to open your arms to tune your report UI/Presentation Server.

Of course if the sql query is taking long time, We know how to tune DB(A)’s  :).

 

 

Thanks,

Shiva.

 
9 Comments

Posted by on September 30, 2011 in BI Publisher, OBI EE, OBIEE 11g

 

Tags: , , , , , , , , , , , , ,