Select Page

Using a Proxy with BITeamwork and OBIEE

Author: Christian Screen | | May 13, 2014

As part of the configuration process of leveraging a Proxy Server or HTTP Server with OBIEE, one configures the context-root paths accessible for routing to the target application server used by Oracle BI. This logic will apply when using a proxy with BITeamwork and OBIEE as the integration of the BITeamwork application is deployed to the same application server when deployed to the on-premise OBIEE solution.

Therefore if your Oracle BI implementation uses a Proxy or HTTP server such as Tivoli Access Manager, and F5 Load Balancer, Oracle HTTP Server, MS IIS, etc. then you will also need to represent the BITeamwork context root path if you have selectively identified the other context root paths for the Oracle BI application.

For example, per the OBIEE HA EDG Oracle documentation (http://docs.oracle.com/cd/E23943_01/core.1111/e10106/bi.htm#CHDHBAHG) when configuring the OHS server you will need to add the following routing information for the proxy to ensure proper OBIEE transport between the HTTP server and the application server.

[code language=”xml”]# BIEE Analytics

SetHandler weblogic-handler
WebLogicCluster APPHOST1VHN1:9704, APPHOST2VHN1:9704
WLProxySSL ON
WLProxySSLPassThrough ON

SetHandler weblogic-handler
WebLogicCluster APPHOST1VHN1:9704, APPHOST2VHN1:9704
WLProxySSL ON
WLProxySSLPassThrough ON
[/code]

Therefore when implementing BITeamwork you will need to add the following configuration using the /bitw context-root as show below for Apache, Oracle HTTP, or other possible HTTP Servers:

[code language=”xml”]# BIEE Analytics – BITeamwork

SetHandler weblogic-handler
WebLogicCluster APPHOST1VHN1:9704, APPHOST2VHN1:9704
WLProxySSL ON
WLProxySSLPassThrough ON
[/code]

Once you’ve made the configuration to the appropriate httpd.conf (Apache) or mod_wl_ohs.conf (OHS) configuration file, then restart the HTTP Server and all should be working well to see the BITeamwork integration with your Oracle BI implementation.

In addition if you are using the caching or compression settings of the OHS or Apache HTTP servers you will need to clear the static file cache to allow an upgrades of BITeamwork’s files to be refreshed properly on your user’s browsers. To do this run the following commands as the root user (or owner of the OHS/Apache installations).

Run htcacheclean -D

Then run, htcacheclean -r

Then run, apachectl restart, to restart the server.

In addition, if there is a need to bypass any of the static cached files you can cheery pick these by updating the config file as described by this Oracle documentation (http://docs.oracle.com/cd/E17904_01/bi.1111/e10541/querycaching.htm#BCGFJBDF)

 

How to Solve the Oracle Error ORA-12154: TNS:could not resolve the connect identifier specified

The “ORA-12154: TNS:could not resolve the connect identifier specified” Oracle error is a commonly seen message for database administrators.

Vijay Muthu | February 4, 2021

Using Nulls in DB2

If a column “value” can be null, it can mean one of two things: the attribute is not applicable for certain occurrences of the entity, or the attribute applies to all entity occurrences, but the information may not always be known.

Craig Mullins | April 6, 2015

How To Fix Log Shipping Failure Errors In SQL Server

Learn how to fix common Log Shipping Failure errors in SQL Server. Includes step-by-step instructions, screenshots, and software script.

Eric Russo | August 10, 2016

Subscribe to Our Blog

Never miss a post! Stay up to date with the latest database, application and analytics tips and news. Delivered in a handy bi-weekly update straight to your inbox. You can unsubscribe at any time.

Work with Us

Let’s have a conversation about what you need to succeed and how we can help get you there.

CONTACT US

Work for Us

Where do you want to take your career? Explore exciting opportunities to join our team.

EXPLORE JOBS