Is there a way to send custom header information with the a webservice request (HTTP post) that happens via GWWS server?
All the methods I read about deal with managing the soap envelop that gets sent.
We are looking for ways which will allow us to put custom information in the headers.
I am aware there is something we can do using the Salt Plugins.
For example, we can write a Out bound plugin which has a capability of putting the "Authentication:Basic..." in the header.
Then there is message conversion plugin which deals with transformation of message, which gives us control over the soap body.
Is it possible to put information in the header for outgoing request (from GWWS) to a specific web service?
Thanks and Sincere Regards,
We are using the following:
TUXEDO10gR3 PATCH LEV=44
SALT Patch Lev = 15
For obvious reasons, it would be difficult (almost impossible) for us to move to 11gR1 immediately.
It would be wonderful if we can get a patch for 10gR3.
Please do let us know about the patch for 10gR3 if it exists.
Thanks a lot again.
just to be clear: do you need to add HTTP headers or SOAP headers? The title of this thread implies the former.
The documentation Xu points to is for adding SOAP headers, which is indeed available but since 11gR1.
If what you need is custom HTTP headers that is not implemented yet.
Thanks for confirming this.
It clarifies the doubts that I was having while reading through the documentation Xu pointed to.
Yes, we need to add HTTP Headers (not SOAP header).
For now we just need to add Basic Authentication HTTP Header for outbound service calls.
We have developed a plugin to do that for now.
And even if the salt plugin takes care of adding the Basic Authentication in the HTTP Header for outgoing calls, I guess we do not have any option to include some custom information in the HTTP Header which might be required in the future.
At-least, not unless we request that enhancement.
Bringing the plugin into our mix requires a lot of changes to our architecture including inclusion of AUTHSVR in the UBB,
Which, in turn, makes it imperative to change the endpoint clients of our application.
In addition to that, the incoming web service calls also need to include TUXEDO authentication information, which would again require either communicating the authentication information to the consumers of our service or device some kind of a proxy which would add the authentication information for all the incoming requests!
With these facts in mind, we were wondering if we have an easier way to include the HTTP header information.
As you say, Maurice, it seems it is not possible yet.
Thank you again for your replies.