Categories
- All Categories
- Oracle Analytics Learning Hub
- 29 Oracle Analytics Sharing Center
- 18 Oracle Analytics Lounge
- 236 Oracle Analytics News
- 45 Oracle Analytics Videos
- 16K Oracle Analytics Forums
- 6.2K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 88 Oracle Analytics Trainings
- 15 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
OBIEE 11g and ODI 11g integration
Dear Experts,
I am trying to integrate OBIEE 11g and ODI 11g by following the below url but not able to.
I have deployed ODI as java web in epm environment and trying to use the WSDL in OBIEE configuration but got error.
Have anyone done integration before? Please share your ideas.
I need to trigger ODI scenario from OBIEE that my agenda.
Thanks,
Raja
Answers
-
RMDR wrote:I have deployed ODI as java web in epm environment and trying to use the WSDL in OBIEE configuration but got error.
What's the exact error? At which exact step of the blog post you linked are you blocked?
0 -
Dear Gianni,
I got stuck in Registering ODI Web Services in OBIEE in the document.
Server 1 : EPM and ODI 11G installed
server 2 : OBIEE11G and essbase installed
I redeployed the oraclediagent.ear after updating by providing ODI11g details in wsil file.
http://localhost:8001/oraclediagent/OdiInvoke.wsil this step is success
http://localhost:8001/oraclediagent/OdiInvoke?WSDL this step also success
When I try to provide the above in OBIEE action framework xml which is available in server2 am getting the below error.
Error :
Soap invocation failure. HTTP error code: '<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope"><env:Header/><env:Body><env:Fault><env:Code xmlns:env="http://www.w3.org/2003/05/soap-envelope"><env:Value>env:Receiver</env:Value></env:Code><env:Reason><env:Text xml:lang="en-US">Error in Action Framework configuration - please contact your system administrator and ask them to check the Actions log files for further information on how to correct this error.</env:Text></env:Reason><env:Detail><ns4:ServiceFault xmlns:ns2="http://oracle.bi.action.registry.ws/" xmlns:ns3="com.siebel.analytics.web/report/v1.1" xmlns:ns4="http://oracle.bi.action.ws/types/fault/"><ns4:message>Error in Action Framework configuration - please contact your system administrator and ask them to check the Actions log files for further information on how to correct this error.</ns4:message><ns4:location xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/></ns4:ServiceFault></env:Detail></env:Fault></env:Body></env:Envelope>'.
ActionFrameworkConfig.xml file content below:
<?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>
<registry>
<id>ETLWS</id>
<name>ETL Web Services</name>
<content-type>webservices</content-type>
<provider-class>oracle.bi.action.registry.wsil.WSILRegistry</provider-class>
<description></description>
<location>
<path>http://server1:20910/oraclediagent/OdiInvoke.wsil</path>
</location>
</registry>
<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>Any advise or am I doing wrong way?
Thanks
0 -
I didn't do that integration myself (never had the need for it), but based on the blog post I would say that in the WSIL you better use the full domain / IP of the ODI server and not localhost.
The blog post is based on ODI and OBIEE installed on the same server, so "localhost" works for reaching each other. In your case you have 2 distinct servers, so setup URLs by using the real domain / IP of your servers (for example if OBIEE try to call the ODI WSDL using the setting of your WSIL file it will try to get the WSDL from the OBIEE server (aka localhost for OBIEE) instead of the ODI server).
In the ActionFrameworkConfig.xml on the OBIEE server same thing, but you already set it right apparently (using "server 1" full domain).
So start by fixing all the URL using full domains / IP that both servers can resolve and reach and try again.
0 -
Dear @Gianni Ceresa,
I have used full domain name only in ear deployment. I used the same odiagant url in the ActionFrameworkConfig.xml.
Thanks
0 -
Sorry, seeing you posted "checks" using localhost I thought it could be easy
Did you try looking into the Actions log file as the error tell? (I guess it is bi_server1-diagnostic.log)
Error in Action Framework configuration - please contact your system administrator and ask them to check the Actions log files for further information on how to correct this error.
0
