Did you create a dedicated connection pool for the EBS Authentication pool ?
Also make sure you have enabled the "Allow first connection pool for Init Blocks" when you go to Tools > Options > General tab > Check the box where it says "Allow first connection pool for Init Blocks"
I am not sure if we can open the Repsitory in the Online mode once you have enabled this Init block with that connect script.
Looks like there is problem with Connect Script , please follow the steps in per the metalink on How To Diagnose "You are not currently logged in to the Oracle BI Server.." Error When Login From EBS to OBI [ID 758392.1].
Below are the troubleshooting steps as per the above note. Please marks if helps.
1) Make sure that E-Business Suite is on the correct patch level needed to integrate with OBIEE.
2) Make sure that E-Business Suite and OBIEE are on the same domain
3) Make sure that the ICX_SESSION_COOKIE is passed correctly from E-Business Suite to OBIEE. You can do this by the following step:
On the browser page where you get the error, type the following in the url address bar:
This is identified by the fact that this cookie value ends with "S".
So if this value is got correctly, it means E-Business Suite is sending the correct cookie information to OBIEE. If, for some reason, the cookie value is not passed from E-Business Suite, then please check the following:
a) E-Business Suite and OBIEE are on the same domain
b) E-Business Suite and OBIEE are both using the same security protocol. When E-Business Suite and OBIEE are configured for different security protocols, for example, E-Business Suite for https and OBIEE for http, then the cookie will not be passed and hence cannot be seen from the OBIEE URL browser and the integration will fail. So E-Business Suite and OBIEE need to be either on http or https . (For setting up SSL on OBIEE its not necessary to setup ssl for all the components - setting up https for webserver/oc4j should be enough)
4) Validate the entry in the \\OracleBIData\web\config\instaneconfig.xml file. For example:
As you can see from the above sample nameInSource is VIS which is the variable that contains the cookie information. Typically nameInSource value is same as the connect string entry in the tnsnames.ora file for your E-Business Suite database. Make sure the nameInSource has the exact same case as in point 1.
For example, if VIS=eu1tJjl_J13s2-27dz85HGLG:S, then the nameInSource is equal to "VIS"
5)In the OBIEE repository the E-Business Suite connection pool has the following PL\SQL script that is called when invoking OBIEE:
call /* valueof(NQ_SESSION.ACF) */ APP_SESSION.validate_icx_session('valueof(NQ_SESSION.ICX_SESSION_COOKIE)')
You can validate that this PL\SQL package returns correct value by executing it directly against the E-Business Suite database.
To do this, first log in to E-Business Suite and click on OBIEE Answers link.
Using document.cookie note down the value of icx_session_cookie (see step 3 for details).
Log in to the E-Business Suite database (via SQL*Plus or some such tool) as the user defined in the E-Business Suite connection pool (typically apps/apps)
Note : you need to substitute the value for icx_session_cookie based on your environment.
If this returns no rows or error then you need to first validate the PL\SQL in the E-Business Suite database and make sure it was created successfully and granted appropriate privileges for the E-Business Suite user.
6) In the repository, you need to then ensure that the Initialization Block for E-Business Suite populates the USER session variable.
The SQL for the Initialization Block is:
FND_GLOBAL.USER_NAME from dual;
FND_GLOBAL.USER_NAME should populate the USER variable. You can set this by clicking on Edit Data Target.
Note: In the out-of-the-box OBIApps repository, the USER variable is populated by the Authentication Initialization Block, which connects to the Siebel OLTP Database. If you want the user to be authenticated with the E-Business Suite Initialization Block, then you must modify the Authentication Initialization Block to re-name the USER variable to something else, or delete the USER variable from the Authentication Initialization Block.
Also if you want both Siebel Authentication and E-Business Suite Authentication, this is currently not possible to accomplish using one webcat and one repository. In this scenario you need two webcatalogs and two rpeositories each configured individually for Siebel and E-Business Suite, respectively.
When you get the error, capturing sawlog.log is quite helpful in knowing what is causing this error. You need to increase the log level for saw by following these steps :
a) Stop Presentation Server
b) Edit logconfig.xml file located in \\OracleBIData\web\config folder. Add these lines in between the <Filters> </Filters> node: