OBIEE JACKED: 2013

Overview

This is intended for anyone that needs to embed an OBIEE 11g dashboard in Siebel 8. At a high level, you will need to:

Congifure the Siebel Screen
Modify the instanceconfig.xml obiee config file to enable iframe support.
Modify the web.xml obiee config file to enable iframe support.
Restart the OBIEE Components.
Create the Host record in Siebel.
Create the Symbolic URL record in Siebel.
View the OBIEE dashboard in Siebel.

Step details and screenprints below...

Configure the Siebel Screen

Add a new Siebel Screen/View/Applet. Look at the oob Sales Dashboard View (and the Screen/applet it's related to). Use these as guidelines to configure your new siebel screen/view/applet. You can use the same Analytics SSO business component, but you will need to add a new calculated field. In this example, the calculated fields value is 'CustomSalesDashboard' (with the single quotes). This will need to be the same value you use as the name of the Symbolic URL record you add in the step below. Compile and restart the Siebel App.

Modify Instanceconfig.xml

Locate the instanceconfig.xml file at the location:

[BIHOME]\instances\[Instance]\config\OracleBIPresentationServicesComponent\coreapplication_obips1\

Update the instanceconfig.xml file to add the highlighted entry within the "security" tag. Possible values are 'allow', 'prohibit' and 'sameDomainOnly':

<InIFrameRenderingMode>allow</InIFrameRenderingMode>

Modify Web.xml

Edit the web.xml file at the following location:

[BIHOME]\oracleBI1\bifoundation\web\app\WEB-INF\

Add the following highlighted entry to the file. The syntax is the opposite of what the syntax for instanceconfig.xml is, since the 'never' means to never block the rendering within IFrame. You can choose 'never' to always allow rendering in the IFrame, or 'differentDomain' to only allow rendering if it is in the same domain.

<servlet-mapping>

<servlet-name>RelatedContent</servlet-name>

<url-pattern>/RelatedContent</url-pattern>

</servlet-mapping>

<context-param>

<param-name>oracle.adf.view.rich.security.FRAME_BUSTING</param-name>

<param-value>never</param-value>

</context-param>

<login-config>

<auth-method>CLIENT-CERT</auth-method>

</login-config>

Restart OBIEE System Components

Now that you've completed both steps, restart the OBIEE System Components using opmnctl (Stop opmnctl and Start opmnctl). If you need to find this, you'll find it in your start menu on the server under the 'Oracle Business Intelligence' folder, called 'Stop BI Services' and 'Start BI Services' respectively.

Create the Host record in Siebel

Create the Symbolic URL record in Siebel

View the OBIEE Dashboard in Siebel

References

http://atlantabi.blogspot.com/2011/12/obiee-11g-obiee-content-cannot-be.html

http://obieeil.blogspot.com/2013/03/embeding-obiee-portalpages-vs.html

http://blog.csdn.net/yexianyi/article/details/4562895

Overview

The following information is for anyone that would like step by step instructions for setting up OBIEE 11.1.1.7 on a single machine for demo purposes. This includes the steps for setting up an RCU database using Oracle Database Express Edition 11g on the same machine. Therefore, you don't necessarily need to get a dba involved. Oracle SQL Developer 3.2.2 client is needed so you can setup the BI and MDS database account/schemas that RCU will need.

Steps

Download Oracle Database Express Edition 11g
Download Oracle SQL Developer 3.2.2
Download Oracle Business Intelligence Enterprise Edition files
Download Oracle Fusion Middleware Repository Creation Utility 11g (11.1.1.7)
Install Oracle Database Express Edition using defaults
Open SQL Developer (no install required) client, connect to XE database, and create DEV4_BI and DEV4_MDS (names can be anything you want). Grant these accounts full access.
Initiate RCU by running RCU.bat file. This will create and load component schemas into the database. In this example, selected only Oracle Business Intelligence Platform, and the install forced the selection of Metadata Services.
Initiate OBIEE 11G install by running setup.exe file. Used the simple install as no load balancing is required. This type of install will not use as many resources, and will allow faster start and stopping of the system.
Validate WebLogic Console is running.
Validate Fusion Middleware EM is running.
Validate OBIEE is running, which will be using the default "sample" rpd.