[vijayjose]

Steven,

It worked,But still execution of vdb failing with 401.

Attaching server.log

[rareddy]

Then you need to figure out else is needed by your web service to authenticate. Any other headers etc. If you have any wire sniffing tools Wireshark/TCPMon you can see what Teiid is sending then fix it accordingly.

Ramesh..

[vijayjose]

Ramesh,

This is the only header required.

With this header i am getting success (200) in preview-data (procedure) and in another 1 application.

It is giving 401 only after creating vdb.

[rareddy]

The only thing you can do now is watching the http traffic to make sure header is being sent. You can also enable CXF logging to see the same. See the section "All CXF Usage" at https://teiid.gitbooks.io/documents/content/admin/Web_Service_Data_Sources.html

Ramesh..

[vijayjose]

Ramesh,

The token value is not passing through the  Header

Headers: {User-Agent=[Teiid Server], Content-Type=[text/xml; charset=utf-8], Accept=[*/*]}

attaching server.log

[rareddy]

If you want to attach your VDB and also mention the Teiid Server version, then I can take a look why there is a discrepancy. I suspect, something still wrong with how you are sending your authorization header.

Ramesh..

[vijayjose]

shawkinsrareddy  I am using  Wildfly 10.0.0

[rareddy]

Vijay,

Sorry it taking long, but my local Designer got wiped out and having little difficulty looking at your VDB. Using your Designer can you convert this into a Dynamic VDB and attach it, that way I do not need to reinstall Designer right now.

Thanks

Ramesh..

[vijayjose]

Ramesh,

Attaching Dynamic vdb and server.log

[rareddy]

Vijay,

I took your VDB deployed on my latest 10.CR2 version of Teiid, and then using a JDBC client I executed

EXEC proc();

The following log output I saw on the console

---------------------------
ID: 1
Address: http://google.com/
Http-Method: GET
Content-Type: text/xml; charset=utf-8
Headers: {X-Auth-Token=[9af7d953-f5a3-4a89-8126-60177269708a], User-Agent=[Teiid Server], Content-Type=[text/xml; charset=utf-8], Accept=[*/*]}
--------------------------------------

Note above http://google.com is dummy site to replace your service endpoint. So, I do see the header.

Ramesh..

[vijayjose]

Ramesh,

This is the output for me

ID: 1

Address: http:(service endpoint)

Http-Method: GET

Content-Type: text/xml; charset=utf-8

Headers: {User-Agent=[Teiid Server], Content-Type=[text/xml; charset=utf-8], Accept=[*/*]}

Attaching the log in console

The header is present correctly in procedure and also in the starting portion of execution of vdb.

Then why is it showing 401.

[shawkins]

Vijay,

> Then why is it showing 401.

I cannot reproduce this either using the vdb.xml.  Based upon your -vdb.xml, or something similar the headers are passed.  I tried this on both Teiid 9.3.1 and master/10.0.0.CR3.  And with or without the metadata tag defining the invokeHttp procedure (if you omit that, the metadata will be pulled from the translator).

However using the .vdb file reproduces the issue.

Unfortunately several versions of designer used metadata definitions for the invokeHttp method that were not recognizable, see [TEIIDDES-2329] WS translator Procedure definition defined in correctly - JBoss Issue Tracker This is a variation of that issue.

What version of designer are you using?

In short what is happening is that RESULT parameters are always expected to be in position 0 for a procedure - matching to the JDBC calling semantics of "? = EXEC ...", however the parser is flexible and will allow the RESULT parameter to appear anywhere and will reorder accordingly.  This does not occur for metadata coming from designer, thus the parameters no longer match positions at runtime.  I can't find the doc note on the ddl result param behavior, so I'll probably need to add one.

Steve

[vijayjose]

Steven,

I am using JBoss Developer Studio 10.4 and Teiid Designer 11.0.1 Final . shawkinsrareddy

How can i solve this issue?

Should I change the designer version or any other patches are currently available ?

[shawkins]

> How can i solve this issue?

The simplest workaround would be to change the web service physical model invokeHttp procedure in designer so that the result is the first parameter.  The runtime will then understand the position of the header parameter with the metadata that designer provides regardless of whether it's a -vdb.xml or a .vdb.

> Should I change the designer version or any other patches are currently available ?

There looks to be an active support case on this as well.  The will likely be patches made that will applied to both community and product versions.  The Designer folks will need to weigh in though on the approach they want to take to fix this.

[blafond]

I would recommend upgrading to Designer 11.1.  There was work done on cleaning up Designer's procedure definition logic with expected Teiid runtime definitions, especially exporting/importing from -vdb.xml.