Invoke Webservice with multiple parameters from OBIEE 11g.

Nabil RIFKI

Hello,

I have a Webservice that require 7 parameters.

I want to call this webservice from an OBIEE Action.

Steps to reproduce the bug :

In OBIEE, I open an Analysis => Criteria Tab => Drag a drop a column => Column property => Interaction => Action Link

I add an action "Invoke a Webservice"

I put the WSDL file Location, I can then select the operation in my Webservice.

In the "Define Parameter" step, I have 7 lines (as my WebService require 7 parameters), but I notice many bugs

1) All the Parameters have the same name (which is the name of the Webservice operation)

2) When I put a value for a Parameter, this value is duplicated to all the 7 parameters.

It looks like OBIEE is invoking my WebService giving one single parameter duplicated 7 times.

Does anyone already tried to invoke a WebService with multiple parameters from OBIEE ?

Thanks

Gianni Ceresa

What exact version (including bundle patch) ?

Nabil RIFKI

I tried in OBIEE  11.1.1.7.150120 (Build 150113.1200 64-bit)  and OBIEE 12.2.1.4.0 (Build BIPS-20180409090153 64-bit)

Both are showing the same issue.

In OBIEE 11g you can call directly call a WSDL file, while in OBIEE 12c you need first to deploy the WSDL file as a webservice in Weblogic then call the webservice using URL.

I have tested both methods, both are showing the same issue. When calling the webservice the first parameter is duplicated 7 times.

The business need we want to implement is the following :

Users want to enter data in the OBIEE dashboard using WriteBack feature.

Once data is entered, users want this data to be pushed to Siebel Application using the webservice.

The webservice has been created on Siebel side with 7 parameters as input (Record_ID + 6 Values).

Nabil RIFKI

Hello Giani,

Do you have any idea on how to safely implement this ?

Thanks

Gianni Ceresa

I don't have a webservice giving me a WSDL with a method with multiple parameters handy, so can't test.

If the GUI issues you have are when building your analysis and defining the action, you can definitely have a look at the XML and "fix" things there setting the various things.