Passing authentication info in soap header

We need to integrate a webservice in ALSB 2.6. This webservice needs authentication information (username and password) to be passed inside the soap header.
I imported the wsdl into ALSB and created a business service on it. When I try to test one of the webservice's method using the test console, I am not sure how do I pass the authentication fields inside the soap header.
Can anyone please provide some inputs.
Regards,
Rishi

The best way to do that is to create an XML file and register it as an Xquery resource in ALSB. You can then access the Xquery file from your pipeline to update your message.
An alternative way is to use th Xquery function "doc" to read files from the file system. However I discourage you to do that since this file will need to be present on your server and won't be managed by the config framework which is going to increase the maintenance burden.
Gregory Haardt
ALSB Prg. Manager
[email protected]

Similar Messages

Pass additional parameter to SOAP header?

We are using webservice datawindows to pass request xmls to call webservices. Additionally we use 'wsconnection' objects authenticationmode, username and password property to send information to SOAP header.
Now we have to send one more value to SOAP header. This new value will be a string(like username).
I checked the wsConnection properties and did not find anything which could be used. Can anyone please advise on it.

If they constructed the web service correctly, the WSDL should include information on the custom header attributes you need to pass. If it's there, any version of PowerBuilder 10.5.1 or later will provide a method you can call to pass it.
Custom header support for .NET Web services

Unable to provide authentication details in SOAP header in 11g

Hi Team,
I have been provided a webservice for which i created a partner link in my BPELProcess. This webservice requires HTTP authentication and i need to provide username/password as provided by them.
When i tried this in SOAP UI by providing the authentication information in Request Properties of SOAUI, i get response from my webservice.
But when i do this using BPEL, it doesnt work on my server and i get Bad Request 404 in response. I tried applying the Http_toekn client policy and provided username/password in its properties in composite.xml but this is not working.
What am i doing wrong. Please help?
Radhika

use tcpmon, wfetch like tools to intercept your call and see if you are able to see HTTP header with username/pwd.
also refer to this blog, may be your problems solution is in here
http://georgie-soablog.blogspot.com.au/2013/09/bpel-calling-web-services-with-http.html
Cheers,
Sahil

How to send authentication information to SOAP Web Service using MATE framework

Hi,
Can anyone please tell me how to pass authentication info (such as user name & password) while calling a webservice using MATE's webserviceinvoker? the SOAP web service expects authentication info in the header.
Thanks in advance..

HI Swayam,
First of all you should tell us what blogs you have seen to avoid you to repeat information that you already know.
we want to avoid setting up SLD configuration for sender system because sender system is just consuming web service .
This is not necessary,
Please let me know the ways we can configure . I did understand we can publish and register the WSDL from Service interface ,but was not clear on over all scenario .
Do you have your ECC webservice available via SOAManager?, you only to access it via soap receiver in SAP PI.
To publish, you need to publish only the sender SOAP, when you register there the sender soap your partner could access there to get the WSDL (Publish services from PI 7.1 to the Service Registry). Also you can generate directly the wsdl (Display WSDL - Integration Directory - SAP Library), what do you want?
Regards,

Sending parameters through SOAP header

Hi all..
Iam using web services model in my web dynpro application. How will i send some paramters/info in SOAP header??

Hello Sujesh,
In your last thread of SOAP Headers I tried to paste the link containing some information on it's usage, but today when i navigated to the link it took me to different location , so the below message
The SOAP Headers Protocol
Definition
In some scenarios, the client may need to add SOAP headers to the request. This can be done using the SOAP headers protocol, which can be accessed by SOAP Web services. This protocol is not available to Web services with HTTP GET or POST bindings.
The SOAP headers protocol is a client runtime plugin located in com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.SoapHeadersProtocol.
Use
To get an instance of the protocol, use:
SoapHeadersProtocol headers = (SoapHeadersProtocol) ((BaseGeneratedStub) client)._getGlobalProtocols().getProtocol("SoapHeadersProtocol");
Structure
The Service Endpoint Interface (SEI) is typecasted to BaseGeneratedStub, which exposes the internal plugin methods of the client:
com.sap.engine.services.webservices.jaxrpc.wsdl2java.BaseGeneratedStub
The basic methods of the SOAP headers protocol are as follows:
· headers.setOutputHeader(new Name("urn:myuri.com","myHeader"),value) With this method you can pass, as a value, any schema-derived element type that is generated by the proxy generator for your client or generic DOM element.
Remember that all header elements must be namespace-qualified and, if you use a schema-derived value, it must be declared by the schema element as follows:
<xs:element name="myHeader" namespace="urn:myuri.com" type=tns:myType/>
· The methods for getting response headers are as follows:
¡ headers.getInputHeader(headerName:QName):Element Returns the DOM element with the header content response
¡ headers.getInputHeader(headerName:QName,headerClass:Class):Object Deserializes the schema-declared header in the response class
and once again the link http://help.sap.com/saphelp_nw04/helpdata/en/45/f957507cb343f78e818c50620ed5ca/frameset.htm
Good Luck,
Dharmi

How to Capture SOAP Header in BPEL

Hi All,
I have a requirement to pass a value from SOAP Header to BPEL and has to capture the value in BPEL and manipulate the data.
In the receive activity i created a variable and assigned Header to it, but iam getting NULL value when i check the instance, this is the code i used in receive
activity.
<receive name="receiveInput" partnerLink="bpelsensor_client" portType="client:BPELSensor" operation="process" variable="inputVariable" createInstance="yes"
bpelx:inputHeaderVariable="headerID"/>
Any suggestions how to do this?

How did you define headerID?
You can also see an example here:
http://java.net/projects/oraclesoasuite11g/pages/BPEL
Arik

No Receiver in SOAP header in sxmb_moni

Hi all
My scenario is using the HTTP sender channel.the url is like this:
http://xiserver:8000/sap/xi/adapter_plain?namespace=http%3A//my&interface=MI_Leo_HTTP_Sou_OB&service=ZBS_Leo_Http&party=&agency=&scheme=&QOS=EO&sap-user=*****&sap-password=****&sap-client=001&sap-language=EN
after i trigger the scenario, i got the message'status scheduled
and the info of SOAP Header in sxmb_moni as followed:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
<SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
<SAP:MessageId>7603ACFE-A4DB-5F48-8F6A-A9DFC3CB97CB</SAP:MessageId>
<SAP:TimeSent>2007-11-01T03:34:43Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Service>ZBS_Leo_Http</SAP:Service>
<SAP:Interface namespace="http://my">MI_Leo_HTTP_Sou_OB</SAP:Interface>
</SAP:Sender>
 <SAP:Interface namespace="http://my">MI_Leo_HTTP_Sou_OB</SAP:Interface>
</SAP:Main>
i think it's really wired, in the info, i couldn't find the receiver info, while my receiver determination is really ok.
the bold highlighted aboved should be like this:
<SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>*******</SAP:Service>
<SAP:Interface namespace="****">*****</SAP:Interface>
<SAP:Mapping notRequired="X" />
</SAP:Receiver>
but it's wrong.how should solve this????
and i restarted the message, it became manual restart status, it didn't work
Please help me.
Thank you in advance.

it works now

Soap Header in Xcelsius: How to pass Credentials

Using Xcelcius 2008 (Excelcius Engage) We are making a dashboard application which uses the Web service connection to call SOAP based web services.
Is there a way to Authenticate the Web Services passing User ID pwd from within one of the excel cells?
The idea is to suppress the authentication and pass the credentials from within the excel cell or any other way which doesn't require user to log in to the Web services while running the Dashboards?
Also I found out an option in Web Service Connection -> Advanced Tab to add a soap header which can include credentials. Is there a format in which I need to create this soap header? Any sample Soap Header would be of great help.

I'd like to know how to do this also, seems silly to have the option to use web services but give no way of passing Basic Authentication credentials.
Cheers
Craig

SOAP Header based user/password authentication in OSB 11g Proxy Service

Hi,
I have implemented SOAP Header based authentication in my OSB 11g Proxy Service.
In the Security settings of my AnySOAP(Soap 1.1) HTTP Proxy service, I have amde the following changes:
1.
In Transport Access Control link, i selected the User predicate, and provided an user already existing on weblogic server with following roles(AppTesters, Monitors, Operators).
The AuthorizationProvider was XACMLAuthorizer
2.
Under Custom Authentication, I selected the Custom User Name and Password option, and provided the below mentiioned xpaths
User Name XPath: ./*/*:Username/text()
User Password XPath: ./*/*:Password/text()
3.
In Message Access Control link, i selected the User predicate with the same user as mentioned in Transport Access Control link.
Now, when I am testing this service from OSB Test Console, I am providing the following input.
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:N1="http://abcd.com/common/bodcomponents/transactional/model/1.0/">
<soap:Header>
<AuthHeader>
<N1:Username>userXYZ</N1:Username>
<N1:Password>passXYZ</N1:Password>
</AuthHeader>
</soap:Header>
<soap:Body>

</soap:Body>
</soap:Envelope>
The response is "The invocation resulted in an error: ."
The OSB server logs show the below error:
####<Feb 9, 2011 6:05:42 PM IST> <Error> <OSB Security> <test.abcd.co.in> <osb_server1> <[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <5a5769b8025ef997:-2bda316:12def49100a:-7fff-0000000000000c92> <1297254942782> <BEA-387082> <Proxy service access denied (proxy: ABCD/Services/Common_HTTP_Proxy, subject: Subject: 0
)>
####<Feb 9, 2011 6:05:42 PM IST> <Error> <OSB Kernel> <test.abcd.co.in> <osb_server1> <[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <5a5769b8025ef997:-2bda316:12def49100a:-7fff-0000000000000c92> <1297254942782> <BEA-382004> <Failed to process request message for service ProxyService ABCD/Services/Common_HTTP_Proxy: com.bea.wli.sb.security.AccessNotAllowedException
com.bea.wli.sb.security.AccessNotAllowedException
 at com.bea.wli.sb.pipeline.RouterSecurity.doAccessControl(RouterSecurity.java:136)
 at com.bea.wli.sb.pipeline.RouterSecurity.doAccessControl(RouterSecurity.java:117)
 at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:586)
 at com.bea.wli.sb.test.service.ServiceMessageSender.send0(ServiceMessageSender.java:329)
 at com.bea.wli.sb.test.service.ServiceMessageSender.access$000(ServiceMessageSender.java:76)
 at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:134)
 at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:132)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
 at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
 at com.bea.wli.sb.test.service.ServiceMessageSender.send(ServiceMessageSender.java:137)
 at com.bea.wli.sb.test.service.ServiceProcessor.invoke(ServiceProcessor.java:454)
 at com.bea.wli.sb.test.TestServiceImpl.invoke(TestServiceImpl.java:172)
 at com.bea.wli.sb.test.client.ejb.TestServiceEJBBean.invoke(TestServiceEJBBean.java:167)
 at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl.invoke(TestService_sqr59p_EOImpl.java:353)
 at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl_WLSkel.invoke(Unknown Source)
 at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
 at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
 at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
 at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
 at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Please suggest where I am going wrong in this. I have cross checked the user/pass credentials with what I am giving in the input, and it is perfectly fine.

I have added the Username and Password as follows, since the namespace declaration was required due to the namespace prefix 'N1' in the XPath
declare namespace N1="http://abcd.com/common/bodcomponents/transactional/model/1.0/";./AuthHeader/N1:Username/text()
declare namespace N1="http://abcdp.com/common/bodcomponents/transactional/model/1.0/";./AuthHeader/N1:Password/text()
I have removed the Message Access Control conditions, have only kept Transport Access Control conditions.
If i keep the condition in Transport Access Control as "Allow access to everyone", and test with proper credentials in the Username/Password tags in SOAP Header, then it works fine. However, if I try to give an incorrect password in the SOAP Header, it denies the access. So that means the XPaths given for Username/Password are working fine. The OSB logs show the below message
+####<Feb 10, 2011 12:59:21 PM IST> <Error> <OSB Security> <test.abcd.co.in> <osb_server1> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <5a5769b8025ef997:-2bda316:12def49100a:-7fff-0000000000000ef2> <1297322961536> <BEA-386008> <Message level username/password authentication failed: [Security:090304]Authentication Failed: User weblogic javax.security.auth.login.FailedLoginException: [Security:090302]Authentication Failed: User weblogic denied>+
However if i add the condition with predicate as "User" and user name argument as "weblogic", and try to pass the same in the SOAP Header as well with the correct password, it denies the access with below message in the logs.
+####<Feb 9, 2011 6:05:42 PM IST> <Error> <OSB Security> <test.abcd.co.in> <osb_server1> <[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <5a5769b8025ef997:-2bda316:12def49100a:-7fff-0000000000000c92> <1297254942782> <BEA-387082> <Proxy service access denied (proxy: ABCD/Services/Common_HTTP_Proxy, subject: Subject: 0+
+)>+
+####<Feb 9, 2011 6:05:42 PM IST> <Error> <OSB Kernel> <test.abcd.co.in> <osb_server1> <[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <5a5769b8025ef997:-2bda316:12def49100a:-7fff-0000000000000c92> <1297254942782> <BEA-382004> <Failed to process request message for service ProxyService ABCD/Services/Common_HTTP_Proxy: com.bea.wli.sb.security.AccessNotAllowedException+
com.bea.wli.sb.security.AccessNotAllowedException
at com.bea.wli.sb.pipeline.RouterSecurity.doAccessControl(RouterSecurity.java:136)
at com.bea.wli.sb.pipeline.RouterSecurity.doAccessControl(RouterSecurity.java:117)
at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:586)
at com.bea.wli.sb.test.service.ServiceMessageSender.send0(ServiceMessageSender.java:329)
at com.bea.wli.sb.test.service.ServiceMessageSender.access$000(ServiceMessageSender.java:76)
at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:134)
at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:132)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
at com.bea.wli.sb.test.service.ServiceMessageSender.send(ServiceMessageSender.java:137)
at com.bea.wli.sb.test.service.ServiceProcessor.invoke(ServiceProcessor.java:454)
at com.bea.wli.sb.test.TestServiceImpl.invoke(TestServiceImpl.java:172)
at com.bea.wli.sb.test.client.ejb.TestServiceEJBBean.invoke(TestServiceEJBBean.java:167)
at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl.invoke(TestService_sqr59p_EOImpl.java:353)
at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

Passing SOAP header while invoking a web service partner link from BPEL

I followed the steps of adding bpelx.inputheadervariable. Which is supposed to add the soad header. But after running the BPEL process if I see the message in the console, I don't see the SOAP header. Is there any way to see how the SOAP header is passed or did I set it incorrectly?
This is what the message looks like:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Header>
<ns0:Context xmlns:ns0="http://www.informatica.com/wsh">
<SessionId>[string]</SessionId>
</ns0:Context>
</soap:Header>
<soap:Body>
<ns0:StartWorkflow xmlns:ns0="http://www.informatica.com/wsh">
<DIServiceInfo>
<DomainName>[string]</DomainName>
<ServiceName>[string]</ServiceName>
</DIServiceInfo>
<FolderName>[string]</FolderName>
<WorkflowName>[string]</WorkflowName>
<WorkflowRunId>[int]</WorkflowRunId>
<WorkflowRunInstanceName>[string]</WorkflowRunInstanceName>
<Reason>[string]</Reason>
<Attribute>
<Name>[string]</Name>
<Value>[string]</Value>
</Attribute>
<Key>
<Key>[string]</Key>
<mustUse>[boolean]</mustUse>
</Key>
<ParameterFileName>[string]</ParameterFileName>
<Parameters>
<Parameters>
<Scope>[string]</Scope>
<Name>[string]</Name>
<Value>[string]</Value>
</Parameters>
</Parameters>
<RequestMode>[ETaskRunMode]</RequestMode>
<TaskInstancePath>[string]</TaskInstancePath>
<IsAbort>[boolean]</IsAbort>
<OSUser>[string]</OSUser>
</ns0:StartWorkflow>
</soap:Body>
</soap:Envelope>
I am trying to invoke the 'startworkflow' operation of Informatica web service Dataintegration.wsdl
Edited by: user611166 on Apr 1, 2010 10:10 AM

Hi,
Try using obtunnel with your bepl console.
Alternatively, if your server is on unix/ linux, try tcpdump to capture packets to a particular server and then open the file in wireshark to analyse the contents.
Wish SOA suite would allow us to view this by default!
Regards,
Sappy

Post user and pass to SOAP Header message in ABAP Proxy

Hi Folks!
I'm trying to post user and pass to SOAP Header on an ABAP proxy. I've already read the thread [Consume web service in ABAP proxy with SOAP header|Re: Consume web service in ABAP proxy with SOAP header; and I see that is possible to manipulate SOAP Header but I cannot understand how I work with function module SDIXML_XML_TO_DOM.
Do I need pass to parameter xml a complete SOAP Envelope? If it is right how can I get the complete xml message to pass to this parameter? I think I don't need the build the xml strucuture as I did on WebAS 6.40, isn't it?
Thanks in advanced.

Hi Rafael,
I would be interested in the solution... could you please post it into forum.
Thanks and best regards
Stefan Bosshard

Passing Soap Header in Web Service

Hi Team,
In our application, we have used web service through webservice proxy wizard using the WSDL file. Now due to security reasons we need to pass Soap Header in the webservice call. Can you please help on how to pass soap header in the webservice call ?
Please find the below webservice code/
Long ll_ret
edpmdata ll_ReturnVal
edpmreq lnv_Request_data
//filter lnv_filter
Datawindowchild dwc_child
str_pass l_str_pass
long l_l_row_count, l_l_row
String l_s_code, l_s_modify, l_l_ret
String str_proxy_name = "sohedpmservice"
String l_s_delivery_pref, l_s_email
String ls_url, l_s_ini_file
l_s_ini_file = g_nv_ini.fnv_get_name ()
ls_url = ProfileString(l_s_ini_file,"External", "EDPM_URL", "")
Soapconnection lsc_Conn
sohedpmservice lproxy_obj
lsc_Conn = create Soapconnection
SetPointer (Hourglass!)
Try
ll_ret = lsc_Conn.CreateInstance(lproxy_obj, str_proxy_name, ls_url)
Catch (SoapException e )
Error.fnv_error("0001", This, "ue_process_fields","Error Creating Instance","",FALSE,1,0)
Message.ReturnValue = -1
RETURN -1
end try
IF ll_ret <> 0 THEN
Error.fnv_error("0001", This, "ue_process_fields","Error Creating Instance","",FALSE,1,0)
Message.ReturnValue = -1
RETURN -1
END IF
Try
lnv_Request_data = create edpmreq
lnv_Request_data.value = l_s_party_key
ll_ReturnVal = lproxy_obj.getcommpref(lnv_Request_data)
If ll_ReturnVal.ws_serviceresult.resultcode = '5' Then
Error.fnv_error("0001", This, "ue_process_fields",String(ll_returnval.ws_serviceresult.ws_resultinfo) ,"Error Response ", FALSE, 1,0)
Message.ReturnValue = -1
RETURN -1
End if
l_s_delivery_pref = ll_ReturnVal.deliverymethod
l_s_email = ll_ReturnVal.emailaddr
i_str_pass.s[86] = l_s_delivery_pref
i_str_pass.s[87] = l_s_email
i_str_pass.s[88] = l_s_party_key
Catch ( SoapException a )
Error.fnv_error("0001", This, "ue_process_fields","Error Response","Error Response",FALSE,1,0)
Message.ReturnValue = -1
RETURN -1
end try
Destroy lsc_Conn
Return 1

What version of PowerBuilder?
PB.Net or Classic?
Are you using the SOAP or .Net Engine (if using Classic)?
What kind of header?
There is limited support for passing custom headers in the .Net engine in Classic. The header would need to be defined in the WSDL for the service.
Anything beyond that (e.g., WS-Security) would need to be handled in a WCF client in PB.Net.

How do pass the UserID and Password in the SOAP header for web services

I am encountering issues trying to pass the userid and password in the SOAP header when consuming a 3rd party web service. Rostewitz posted something similiar but I don't know how to type iv_xml. Any help would be greatly appreciated.
Thank you,
jpina

It helps to post a link to a thread when you refer to it. If you are trying to implement that solution though, you can look at the parameter of the corresponding method being called. The parameter has type 'SIMPLE' which means that it is compatible with all of the predefined elementary ABAP types. In this case, you should use 'STRING'.

Passing Parameter through SOAP Header in ODIInvokeWebService

How to pass parameters in SOAP Header in ODIInvokeWebService and not just in SOAP Body?
Background:
One of our web service provider expects certain parameters set in SOAP Header. Currently, ODIInvokeWebService allows to set parameters through SOAP (Request) Body and not through SOAP Header.
How can we set and send parameters in SOAP Header when using ODIInvokeWebService. Can we set this in a request file. Any workaround?
BTW is this a limitation in the tool. If yes, I am looking for a work around. I can setup a proxy service/servlet and re-route the request to the provider but I would like to know if there is a work that can be done easily through ODIInvokeWebService before I look for other options.
Appreciate your help.
Thank you.
-Muthu

Hi Muthu ,
This is not supported by the ODIInvokeWS Tool.
There are some ER logged against this and may be it will get implemented in ODI 11g
Sutirtha

Customizing header links in wiki while passing authentication.

I'm trying to add a few new different headers to the page to services running outside of the wiki, but passing off authentication to them of the currently logged in user. I'm specifically trying to do this for roundcube and crushftp's web interfaces. From digging through the folders of the wiki, it seems like how they get the images that make up the header is from referencing a gif or jpg that tells it what pixels to display in the header from the image. That's not extremely difficult to me, but, the passing authentication and having it display in the body to the services is.
I'm aware of roundcube having some plugins for this purpose, but unsure of how to implement them not knowing what kind of authentication is being used already for the wiki. As for crushftp's web interface i'm more in the dark as far as how to make this work.
I did notice a reference in wikid.conf to "apple_utilities.Authentication.WikiAuthenticationProvider" for "authenticationProvider", but im not sure what type of authentication is taking place.
Any ideas? Any help would be greatly appreciated.

Thanks every one for your valuable solutions.
Issue is Solved by unchecking the flag.
wa_header-INV_TRAN = 'X'.
Thanks & Regards,
Ramjee.

Passing authentication info in soap header

Similar Messages

Maybe you are looking for