AST White Paper-EBS-OBIEE 11g Integration

Oracle E-Business Suite - Oracle Business Intelligence Enterprise Edition

11g Integration By: Arun Chaturvedi, Business Intelligence Architect

& Phani Kottapalli, Technical Architect

AST Corporation

November 19, 2012

Specialized. Recognized. Preferred. The right partner makes all

the difference.

1755 Park Street, Suite 100 | Naperville, Illinois 60563 | 1.888.278.0002 | www.astcorporation.com

A p p l i c a t i o n s S o f t w a r e T e c h n o l o g y C o r p o r a t i o n

Oracle E-Business Suite -- Oracle Business Intelligence Enterprise Edition 11g Integration Page i

Contents

ABSTRACT ............................................................................... 1

PURPOSE ............................................................................... 1

PREREQUISITES AND ASSUMPTIONS ..................................... 1

EMBEDDING LINK TO NAVIGATE (EBS TO OBIEE) ..................... 2

CREATE FUNCTION ................................................................ 2

CREATE MENU ....................................................................... 4

ASSIGN MENU TO A RESPONSIBILITY .................................... 5

ASSIGN RESPONSIBILITY TO USERS ....................................... 7

SETTING UP THE PROFILE ...................................................... 8

MODIFYING THE OBIEE REPOSITORY FILE (RPD) .................... 11

SETUP THE CONNECTION POOLS ........................................ 11

SETUP THE INITIALIZATION BLOCK ...................................... 11

MODIFYING OBIEE CONFIGURATION FILES (XML) .................. 16

MODIFY AUTHENTICATIONSCHEMAS.XML ......................... 16

MODIFY INSTANCECONFIG.XML ......................................... 18

MODIFY ACTIONFRAMEWORKCONFIG.XML ....................... 19

CREATING APPLICATION ROLES ............................................. 22

CREATE APPLICATION ROLE IN EM ...................................... 22

ASSIGN ACCESS TO NEW APPLICATION ROLE ..................... 24

ASSIGN PRIVILEGES TO CATALOG/SUBJECT AREA ACCESS ..... 25

ASSIGN PRIVILEGES TO DASHBOARDS & ANSWERS ............ 25

ASSIGN PERMISSIONS TO CATALOG COMPONENTS ........... 27

ASSIGN PERMISSIONS TO PRESENTATION SUBJECT AREAS 28

EMBEDDING LINK TO NAVIGATE BACK (OBIEE TO EBS) .......... 31

ACTION LINK TO EBS FORM ................................................. 31

PASSING CONTEXT TO EBS FORMS ..................................... 31

SIGN‐OUT AND SIGN‐IN ....................................................... 33

TROUBLESHOOTING & TIPS ................................................... 35

COOKIE FOR INTEGRATION ................................................. 35

VERIFY VARIABLE VALUES FOR INTEGRATION .................... 35

CONNECTION POOL AND USE OF VARIABLES ..................... 36

VERIFY APPLICATION ROLES BEING PASSES ........................ 36

REFERENCES .......................................................................... 38

ORACLE DOCUMENTATION ................................................. 38

Oracle E-Business Suite -- Oracle Business Intelligence Enterprise Edition 11g Integration Page 1

Abstract

PURPOSE

What if you want to use users defined in your Oracle E-Business Suite for login and use Oracle Business EE/BI Applications? They can login into EBS using their username/password and navigate to OBIEE so they do not have to remember two usernames and passwords separately.

This document details the steps required to integrate Oracle BI Applications (7.9.6.3) with Oracle E-Business Suite Applications R12.1.3 in the following ways:

Single Sign-On first into Oracle E-Business Suite R12.1.3 and have that authentication passed through to Oracle BI EE 11g

Embed links to Oracle BI EE 11g dashboard/answers in Oracle E-Business Suite pages

Create Action Links within Oracle BI EE 11g reports and dashboards that take you back into Oracle E-Business Suite in context

Activate Sign-Out Link within Oracle BI EE 11g that take you back into Sign-In page of your choice (Oracle E-Business Suite or Oracle BI EE)

PREREQUISITES AND ASSUMPTIONS

This document is using instance with software versions. Integration steps for other versions may vary.

o Oracle E-Business Suite R12.1.3

o Oracle BI EE 11g (11.1.1.5)

o Oracle Business Applications 7.9.6.3

For Oracle EBS R12, there are no pre-requisite patches required since base R12 has all the functionality that OBIEE leverages, namely the OBIEE profile is defined in b5869360.ldt, OracleOasis.jsp and APP_SESSION package which are in base R12.

Please make backup of all files before making changes (i.e. repository, configuration files, catalog etc.)

As an example:

o We will create two responsibilities in EBS (OBIEE-Financials & OBIEE-Projects) and users will have access to Financial Analytics or Project Analytics based on these responsibilities.

o OBIEE-Financials: This application role will have access to only Finance Analytics (Dashboard and Subject Areas)

o OBIEE-Projects: This application role will have access to only Project Analytics (Dashboard and Subject Areas)


Embedding Link to Navigate (EBS to OBIEE)

To embed a link in Oracle E-Business Suite that opens Oracle Business Intelligence dashboards/answers, you need to create a form functions, menu and responsibility.

Before you begin, log in to Oracle E-Business Suite as the system administrator. Then, select the System Administrator responsibility from the responsibility navigator pane on the left. The available menus appear on the right.

Follow the steps in this section to create the following objects, in sequence:

o Function

o Menu

o Responsibility

o User

o Profile

Figure 1: Login to Oracle E-Business Suite

CREATE FUNCTION

From the Application menu, select Function. The Form Functions dialog appears.


Figure 2: Form Functions Dialog

In ‘Description’ tab of Form Function:

Enter the name of the function in the Function Field

Enter the User Function Name

Enter a description

Save your changes using the Save button on the toolbar

In ‘Properties’ tab of Form Function:

Specify the Type as SSWA jsp function


In ‘Web HTML’ tab of Form Function:

For the HTML Call, enter one of the following options:

To link to answers, enter OracleOasis.jsp?mode=OBIEE&function=Answers

To link to dashboards, enter OracleOasis.jsp?mode=OBIEE&function=Dashboard

Save your changes using the Save button on the toolbar

CREATE MENU

From the Application menu, select Menu. The Menus dialog appears.


Enter the name of the Menu

Enter a User Menu Name

For Function, enter the name of the function(s) created in the previous section (i.e. OBIEE-DASBOARD and OBIEE-ANSWERS)

Save you changes using the Save button on the toolbar, and then close the Menus dialog.

ASSIGN MENU TO A RESPONSIBILITY

You can create a new responsibility or an existing responsibility can be used. Below steps shows how to create a new responsibility:

From the Security Menu, Click on Responsibility and select Define

Enter the name of the responsibility (‘OBIEE-Financials’)


Select the application for which the responsibility is being created

Specify a unique Responsibility Key (OBIEE-Financials)

For Available Form, Select Oracle Self Service Web Applications

For Data Group, enter ‘Standard’ for Name and re-enter the application name for Application

For Menu, enter the name of the menu you created in the previous section (OBIEE)

Save you changes using the Save button on the toolbar, and then close the responsibilities dialog.

Repeat same steps given above to create another responsibility name: ‘OBIEE-Projects’


ASSIGN RESPONSIBILITY TO USERS

You can create a new user or an existing users can be used. Below steps shows how to create a new user:

From the Security Menu, Click on User and then Select Define

Enter the name of the user

Specify the responsibilities that this user will have access to. (OBIEE-Financials or OBIEE-Projects)


Save you changes using the Save button on the toolbar, and then close the Users dialog.

SETTING UP THE PROFILE

Click on Profile and then select System Profile

Select Responsibility and then enter the name of the responsibility which you created earlier (OBIEE-Financials)

Enter %Business Intelligence% in the Profile field


Click Find

On the resulting screen, specify the Oracle Business Intelligence URL. For example:


http://my_server.domain.com:port (http://otap1.lahd.pola:9704)

For port, enter the Web server port where Oracle Business Intelligence is running (for example, 9704).

Save your changes using the save button on the toolbar

Repeat same steps given above for another responsibility name: ‘OBIEE-Projects’

Save your changes using the save button on the toolbar

Note: The BI URL should be the fully qualified hostname including the domain name. It shouldn’t be an IP Address.


Modifying the OBIEE Repository File (rpd)

You have to modify OBIEE repository file (rpd) for EBS-OBIEE integration. If you haved implemented BI Application, all required variables, connections pools will already be there for you. If not, you need to create them manually using this document as an example.

SETUP THE CONNECTION POOLS

In the Oracle BI Administration tool, open the rpd in offline mode

In physical layer, select the ‘Oracle EBS OLTP Initblocks Connection Pool’

On the Connection Scripts tab, the value of Execute on Connect property should be:

call /* valueof(NQ_SESSION.ACF) */ APP_SESSION.validate_icx_session(‘valueof(NQ_SESSION.ICX_SESSION_COOKIE)’)

SETUP THE INITIALIZATION BLOCK

o Open the rpd

o From Menu Bar, select Manage Variables Initialization Block

o Check whether the Initialization Block ‘EBS Security Context’ exists or not.

o If not, please follow steps a - j mentioned below.

o If it exists, please skip steps (a) and (b) below, start with (c.) and verify that the settings for this initialization block is similar to as mentioned here:

a. From the Action menu, select new and then select New, then Session and then Initialization Block

b. Enter/Select the name of the initialization block ‘EBS Security Context’

c. If Initialization Block ‘EBS Security Context’ is disabled, Right click on it and select ‘Enable’.

d. For ‘default Initalization string’ enter the following:

select FND_GLOBAL.RESP_ID,


FND_GLOBAL.RESP_APPL_ID, FND_GLOBAL.SECURITY_GROUP_ID, FND_GLOBAL.RESP_NAME, FND_GLOBAL.USER_ID, FND_GLOBAL.EMPLOYEE_ID, FND_GLOBAL.USER_NAME, FND_GLOBAL.RESP_NAME from dual

e. For Connection Pool, Click Browse and select the ‘Oracle EBS OLTP Initblocks Connection Pool’

f. Clock Ok

g. Click ‘Edit Data Target’

h. Create the following session variables (in same order):

OLTP_EBS_RESP_ID OLTP_EBS_RESP_APPL_ID OLTP_EBS_SEC_GROUP_ID OLTP_EBS_RESP_NAME OLTP_EBS_USER_ID OLTP_EBS_EMPLOYEE_ID USER ROLES

Note: To add variable ‘USER’ at the end of this list, follow steps given below.

- First, Delete existing session variable ‘USER’

- In initialization block ‘EBS Security Context’ Click on ‘Edit Data Target’ Delete existing target variable ‘OLTP_EBS_USER’ Add new target variable ‘USER’


Similarly, create seesion variable ROLES

i. Click ok

j. Select Required for ‘authentication’ checkbox.

k. Click on ok.

Note: In this example:

We already have Initialization Block ‘EBS Security Context’ in repository. If this is disabled by default, please select, right-click and ‘Enable’ it.

We are not enabling ‘Authentication’ and ‘Authorization’ initialization blocks


Finally, Initialization block ‘EBS Security Context’ should look like as given below.


Session Variables created by this process: USER, ROLES


Modifying OBIEE Configuration Files (xml)

You need to modify few OBIEE configuration files to enable EBS – OBIEE integration for user security.

After making changes in all XML configuration files, Restart Oracle Business Intelligence services.

MODIFY AUTHENTICATIONSCHEMAS.XML

This file can be found on server at:

ORACLE_HOME/bifoundation/web/display

Example: /u01/oracle/prod/Oracle_BI1/bifoundation/web/display

o Open the file authenticationschemas.xml for editing.

o Find the following element in the file:

<AuthenticationSchema name="EBS-ICX"

o Locate the sub-element RequestVariable source="cookie" and change the value of the nameInSource attribute from ICX_SESSION to the name of the EBS ICX authentication cookie prefix.

<RequestVariable source="cookie" type="auth" nameInSource="TEST" biVariableName="NQ_SESSION.ICX_SESSION_COOKIE" />

Note: Ask your Oracle E-Business Suite administrator for the name of the EBS ICX authentication cookie if you do not know it. Alternatively, follow these steps to find the cookie name: Log in to Oracle E-Business Suite. Enter the following text in the address bar of your browser:

javascript:write(document.cookie)

The cookie is displayed. For example: TEST=hEXoGr7ZPJW0ZDVE3gTU7YPM4d

The value you need to provide in authenticationschemas.xml is the prefix of the EBS ICX authentication cookie. In the previous example, the EBS ICX authentication cookie is TEST=hEXoGr7ZPJW0ZDVE3gTU7YPM4d, and the prefix is TEST.

In the same entry (RequestVariable source="cookie"), ensure that the value of the biVariableName attribute is the same as the value you entered as part of the connection script when you created the connection pool for the Oracle E-Business Suite database.

Find the following element: <SchemaKeyVariable source="cookie"

Change the value of the nameInSource attribute from ICX_SESSION to the name of the EBS ICX authentication cookie prefix (i.e. TEST).

For example:

<SchemaKeyVariable source="cookie" nameInSource="TEST" forceValue="EBS-ICX"/>

Save and close the file.


Original XML:



<AuthenticationSchema name="EBS-ICX" displayName="Oracle eBusiness Applications ICX Session" options="noLogoffUI noLogonUI" >





<RequestVariable source="cookie" type="auth" nameInSource="ICX_SESSION" biVariableName="NQ_SESSION.ICX_SESSION_COOKIE"/>

<RequestVariable source="url" type="informational" nameInSource="ACF" biVariableName="NQ_SESSION.ACF"/>

</AuthenticationSchema>

Modified XML:



<AuthenticationSchema name="EBS-ICX" displayName="Oracle eBusiness Applications ICX Session" options="noLogoffUI noLogonUI" >




<RequestVariable source="cookie" type="auth" nameInSource="TEST" biVariableName="NQ_SESSION.ICX_SESSION_COOKIE"/>

<RequestVariable source="url" type="informational" nameInSource="ACF" biVariableName="NQ_SESSION.ACF"/>

</AuthenticationSchema>

Original XML:


<SchemaKeyVariable source="cookie" nameInSource="ICX_SESSION" forceValue="EBS-ICX"/>

Modified XML:



<SchemaKeyVariable source="cookie" nameInSource="TEST" forceValue="EBS-ICX"/>

MODIFY INSTANCECONFIG.XML

This file can be found on server at: ORACLE_INSTANCE/config/OracleBIPresentationServicesComponent/coreapplication_obipsn

Example: /u01/oracle/prod/instances/obprod/config/OracleBIPresentationServicesComponent/coreapplication_obips1

Open the file instanceconfig.xml for editing.

Locate the <Authentication> element.

Include EBS-ICX in the list of enabled schemas.

For example:

o <EnabledSchemas>UidPwd,Impersonate,UidPwd-soap,Impersonate-soap,EBS-ICX</EnabledSchemas>

Ignore the comment in instanceconfig.xml that says this setting is centrally managed. EBS-ICX must be manually added to the EnabledSchemas element.

If you want to have ‘Sign-Out’ link in OBIEE page (so you can log out from OBIEE and go to any webpage of you choice, for example EBS login page); You need to perform the following steps in order to get the Log out (Sign out) link displayed in OBIEE 11g.

Inside the <Authentication> section, add the following tag block <SchemaExtensions> as given below:

<!–‐Adding Logout Link–‐>

<SchemaExtensions>

<Schema name="EBS‐ICX" logonURL="{your SSO logon URL}" logoffURL="{your

logoff URL}"/>

</SchemaExtensions>

<!‐–Adding Logout Link–‐>

As example, you may use the following log-off / log-on URL options: EBS Homepage: http://<your EBS server:port>/OA_HTML/OA.jsp?OAFunc=OAHOMEPAGE Analytics logoff: http://<your BI server:port>/analytics/saw.dll?Logoff Analytics logon : http://<your BI server:port>/analytics/saw.dll?bieehome&startPage=1

Save and close the file.


Original XML:

<Authentication>



<EnabledSchemas>UidPwd,Impersonate,UidPwd-soap,Impersonate-soap</EnabledSchemas>

</Authentication>

Modified XML:

<Authentication>



<EnabledSchemas>UidPwd,Impersonate,UidPwd-soap,Impersonate-soap,EBS-ICX</EnabledSchemas>



<SchemaExtensions>

<Schema name="EBS-ICX" logonURL="http://epap1.lahd.pola:8016" logoffURL="http://epap1.lahd.pola:8016"/>

</SchemaExtensions>



</Authentication>

MODIFY ACTIONFRAMEWORKCONFIG.XML

This file can be found on server at:

<Oracle Middleware Home>\user_projects\domains\bifoundation_domain\config\fmwconfig\biinstances\coreapplication

Example: /u01/oracle/prod/user_projects/domains/bifoundation_domain/config/fmwconfig/biinstances/coreapplication

This change is needed when you create action link inside OBIEE to navigate back to Oracle EBS form.

Original XML:

<obi-action-config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="afconfig.xsd">

<aliases/>

<registries/>


<content-types>

<content-type>

<typename>webservices</typename>

<displayname>Web Services and BPEL Processes</displayname>

<actionType>WebServiceActionType</actionType>

</content-type>

<content-type>

<typename>misc</typename>

<displayname>Mixed Services</displayname>

<actionType>URLActionType</actionType>

</content-type>

</content-types>

<accounts/>

</obi-action-config>

Modified XML:

<?xml version="1.0" encoding="UTF-8"?>

<obi-action-config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="afconfig.xsd">

<aliases/>

<registries/>

<content-types>

<content-type>

<typename>webservices</typename>

<displayname>Web Services and BPEL Processes</displayname>

<actionType>WebServiceActionType</actionType>

</content-type>

<content-type>

<typename>misc</typename>

<displayname>Mixed Services</displayname>

<actionType>URLActionType</actionType>

</content-type>

</content-types>

<accounts/>


<ebusinesssuiteconfig>

<visible>true</visible>

</ebusinesssuiteconfig>

</obi-action-config>

After making changes in all XML configuration files, Restart Oracle Business Intelligence services.


Creating Application Roles

You need to create an application role which must be same as responsibility name you created in EBS (in this example, we created EBS responsibility ‘OBIEE-Financials’ so we need to create application role name ‘OBIEE-Financials’ using Oracle Enterprise Manager 11g.

To access to subject areas and catalog, we can add this new application role to an eixisting application role as a member (in this example, it will be member of ‘BIAuthor’) or we can use these newly created application roles without using any other existing application roles. In this example, we will use newly created application roles directly; without using any existing application roles.

CREATE APPLICATION ROLE IN EM

Login to Enterprise Manager 11g using administrator user (i.e. weblogic)

Navigate to Business Intelligence coreapplication

Right click on ‘coreapplication’: Security Application Role

Click in ‘Create’

Enter Role Name, Display name, Description [‘OBIEE-Financials’]

Click OK

Repeat same steps to create anoter application role: ‘OBIEE-Projects’


Note: No need to assign ‘members’ or ‘users’ in these application role here in Enterprise Manager.

NOTE: You Application Role name must be the same as the responsibility name you created in EBS.


ASSIGN ACCESS TO NEW APPLICATION ROLE

If you want to use an existing application role to have same access/privileges for newly created application role, we can assign newly created application role to existing roles ‘BIAuthor’

You can also use newly created application role directly; without using any existing application role

Using existing application role ‘BI Author’ to use it’s access level for newly created application role (for example: ‘OBIEE’)

Click on existing role name ‘BIAuthor’

Click ‘Add Application Role’ in Members section

Search, move ‘OBIEE’ application role name from left to right pane (Selected Roles), Click OK

Click on OK

Now, newly created application role ‘OBIEE’ is member of existing application role ‘BIAuthor’ (which already have privileges for subject areas and catalog)


Assign Privileges to Catalog/Subject Area Access

We need to assign appropriate access to application role inside Dashboard’s ‘Administration’ area so users related to new responsibility can access catalog as per requirement.

ASSIGN PRIVILEGES TO DASHBOARDS & ANSWERS

Login to BI Analytics using administrator type user (such as weblogic)

Click on ‘Administration’ Link

Click on ‘Manage Privileges’ Link

Add Application Role ‘OBIEE-Financials’ and ‘OBIEE-Projects’ to give access to Dashboard and Answers


Add new application roles in appropriate ‘Subject Area’ sections

Assign other privileges as required

You may apply appropriate access to other areas as shown in following screenshot

Click on ‘Back’ and sign-out.


ASSIGN PERMISSIONS TO CATALOG COMPONENTS

Login to BI Analytics using administrator type user (such as weblogic)

Click on ‘Catalog’ link

Navigate to appropriate folder name within ‘Shared Folders’

Click on ‘More’ drop-down and then select ‘Permissions’


Select ‘No Access’ for Authenticated User

Select Full Control for newly created application role.

‘OBIEE-Financials’ for ‘Financials’ folder

‘OBIEE-Projects’ for ‘Projects’ folder

Select OK

Note: For all shared folders which you do not want to show for any users, Select ‘No Access’ for Authenticated User.

ASSIGN PERMISSIONS TO PRESENTATION SUBJECT AREAS

In repository’s presentation subject area, you need to assign permissions to newly created application role (i.e. ‘OBIEE-Financials’, ‘OBIEE-Projects’).

Check permission property tab for all related subject areas (in presentation layer) and make appropriate changes for appropriate application role. i.e. select ‘Read’, ‘Read/Write’, ‘No Access’ radio buttons etc

Using BI Administration desktop tool, open repository in ONLINE mode.


In presentation layer, repeat following to all subject areas where you want to assign permissions to newly created Application Role.

Select presentation subject area, right click to open property tab

‘Check-Out’ to make changes in repository

Click ‘Permission’ to open permission tab

Select ‘No Access’ radio button for ‘Everyone’ application role

Select ‘Read’ or ‘Read/Write’ radio button for newly created application roles as per your requirement.

Click OK

‘Check-in’ the changes, save the repository (in Online mode)

Assign appropriate permissions to all subject areas related to Financial Analytics. (for OBIEE‐

Financials role)


Assign appropriate permissions to all subject areas related to Project Analytics. (for OBIEE-Projects role)

NOTE: You are assigning these permissions in ONLINE mode so you may need to check and validate them again whenever you are deploying repository file.


Embedding Link to Navigate Back (OBIEE to EBS)

You can choose few options when you want to navigate back to EBS from OBIEE. In this document, we will discuss 2 options (a) Navigate back to Oracle EBS form using Action Link (b) Sign-Out from OBIEE and show any login web page of our choice (example, EBS login page or BI Analytics login page).

ACTION LINK TO EBS FORM

Configure Oracle BI EE Action Framework:

Modify ActionFrameworkConfig.xml as per instruction given above.

Include the following element: <ebusinesssuiteconfig><visible>true</visible></ebusinesssuiteconfig>

Save and close the file

PASSING CONTEXT TO EBS FORMS

Identify the e-Business Suite Form that is to be linked to. Identify the parameters required by the Form/Page. Please refer to e-Business Suite Documentation for details.

Create a new Action which will enable OBIEE to call the e-Business Suite Target form.

Log into OBIEE

Click on New -> Action

In the Resultant Screen, Select ‘Navigate to e-Business Suite’


In the resultant screen, two mandatory parameters, FunctionCode and Connection pool need to be specified. For FunctionCode, Specify the function code of the target form which need to be launched. Also, Specify the connection pool (mentioned under section rpd changes ). In addition to these two mandatory parameters, create new parameters which has the same name as the identified parameter (Identified in Step 1) and specify a value.

For better user experience, Mark the FunctionCode and ConnectionPool parameters as Hidden.

Save the Action

Navigate to location where the Action is saved and Click on Execute to test the Action

Clicking on Execute should launch e-Business Suite Form.

The Action Link created above can be used in Analysis/Dashboards. For details, how to use Action Links in Analysis/Dashboard, Refer to Oracle Business Intelligence Enterprise Edition


documentation. Steps below provides a simple example on how to use Action Link in Analysis:

Login into OBIEE

Navigate to New->Analysis

Select a Subject Area and then select a column on which the Action Link is to be set as an Interaction

Navigate to Column Properties

Click on Interaction tab

Select Primary Interaction as Action Link under Value

Click on + icon and Specify the Action Link (which was created in earlier step).

Specify parameters if a dialog box for parameters is prompted. Set the value to be based on Column. Check the Hidden Checkbox. Click on ok.

Save the Analysis

Now, Test navigation as given below:

Login to e-Business Suite. Click on the OBIEE Answers link to navigate to OBIEE

Open the newly created Analysis

Click on the column value to navigate back to e-Business Suite.

SIGN‐OUT AND SIGN‐IN

If you do not want go back to same Oracle EBS form after working in OBIEE, you can just sign-out from OBIEE and display any web page of your choice.

When we add following tags in instanceconfig.xml file, sign-out link appears on home page (top-right side of screen). You can define any URL which you want to see after sign-out (example: Login screen for EBS or BI Analytics)

Follow instruction given above in this document.


<Authentication>

<EnabledSchemas>UidPwd,Impersonate,UidPwd-soap,Impersonate-soap</EnabledSchemas>  <!–-Adding Logout Link–-> <SchemaExtensions> <Schema name="EBS-ICX" logonURL="{your SSO logon URL}" logoffURL="{your logoff URL}"/> </SchemaExtensions> <!-–Adding Logout Link–-> </Authentication>


Troubleshooting & Tips

COOKIE FOR INTEGRATION

How to get cookie’s value which is being used for EBS-OBIEE integration?

a. Log in to Oracle E-Business Suite. Enter the one of following text in the address bar of your browser:

o javascript:alert(document.cookie),

o javascript:document.write(document.cookie)

o javascript:document.writeLn(document.cookie);

b. The cookie is displayed.

c. For example: TEST=hEXoGr7ZPJW0ZDVE3gTU7YPM4d

VERIFY VARIABLE VALUES FOR INTEGRATION

1. How to verify the Responsibility Name defined in EBS is being passed to OBIEE?

2. Get cookie’s value as per steps given above

3. Execute following command first and then SQL in sql*plus/TOAD etc

call /* valueof(NQ_SESSION.ACF) */ APP_SESSION.validate_icx_session('valueof(NQ_SESSION.ICX_SESSION_COOKIE)')

Example:

call /* valueof(NQ_SESSION.ACF) */ APP_SESSION.validate_icx_session('hEXoGr7ZPJW0ZDVE3gTU7YPM4d')

Execute this query against your EBS database: (Example: TEST)

select FND_GLOBAL.RESP_ID,

FND_GLOBAL.RESP_APPL_ID,

FND_GLOBAL.SECURITY_GROUP_ID,

FND_GLOBAL.RESP_NAME,

FND_GLOBAL.USER_ID,

FND_GLOBAL.EMPLOYEE_ID,

FND_GLOBAL.USER_NAME

from dual

You should get values in result set. For example, RESP_NAME will have value ‘OBIEE’


CONNECTION POOL AND USE OF VARIABLES

DSN and User values in Connection pool: I noticed that sometimes it works with repository variable name and sometime with complete TNS entry in it. Try it which style works in your case.

a. (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=etdb1.lahd.pola)(PORT=1539))(CONNECT_DATA=(SERVICE_NAME=UAT)(INSTANCE_NAME=UAT)))

b. VALUEOF(ORA_EBS_OLTP_DSN) and VALUEOF(ORA_EBS_OLTP_USER)

VERIFY APPLICATION ROLES BEING PASSES

Login to Oracle EBS using your username/password.

Click on appropriate OBIEE related responsibility (example: OBIEE-Financials)

When you come to BI Abalytics home page, click your username (top-right corner of screen)

Click on ‘My Account’

Click on ‘Role and Catalog Groups’

Now, you should see the Responsibility Name which you selected in Oracle EBS (which is your Application Role defined in Oracle Enterprise Manager)



References

ORACLE DOCUMENTATION

Please refer to Chapter 2 from document below: (2 Integrating Security for Oracle BI Applications)

http://download.oracle.com/docs/cd/E20490_01/bia.7963/e19042/security.htm#CJADEAEH

Please refer to Chapter 6 from document below: (6 Integrating with Oracle E-Business Suite Security)

http://docs.oracle.com/cd/E21764_01/bi.1111/e16364/ebs_actions.htm#CJADIFBA

Oracle E-Business Suite -- Oracle Business Intelligence Enterprise Edition 11g Integration November 19, 2012 AST Corporation 1755 Park Street, Suite 100 Naperville, Illinois 60563 Phone : 888-278-0002 Fax : 630-778-1179 www.astcorporation.com Copyright © 2012 AST Corporation AST Corporation is a privately held company founded in 1995 to serve commercial and public sector organizations in utilizing the full potential of their investment in Oracle Applications. We have built our practice by providing top quality full life cycle and turn-key consulting services for Oracle Applications implementation and upgrade projects, among other specific services. Our mission is to insure that you, as a valued client, receive the highest level of expertise and personalized service for your Enterprise Applications. We endeavor to help you realize the full benefit from your investment in software applications and integrate them seamlessly to your business processes.

Documents

AST White Paper-EBS-OBIEE 11g Integration