How to use SOAP sender adapter

Hi all
i have configured the SOAP sender adapter. Now my 3rd party needs to send me a soap message.
I have checked that the status at the following URL is OK:
http://host:port/XISOAPAdapter/MessageServlet?channel=:MXII_Web_Service:SOAP_MXII_Sender.
This is fine, however
I am unsure of the following:
1. Does XI make a wsdl available to the 3rd party?
2. Where does my 3rd party send the soap message to?
3. Is the SOAP message sent via a query string?
4. Do I need to create a web service?
Thanks for all your help in advance
Clinton

Hi Moorthy
Thanks for your answer.
The problem was solved, we used .Net to write a webservice to our wsdl.
I have now another problem.... When the message comes into XI it shows that no receiver found(RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC). If I just test the scenario with a file adpter as Sender, and Receiver it is fine, but when using the SOAP adapter as Sender, it gives me the no receiver found message.
Any help with this issue will be appreciated.
Thanks again
Clinton

Similar Messages

Using SOAP Sender adapter in PI 7.1

Hi Guys,
I've created a sync scenario with SOAP sender adapter, but I have troubles with calling it.
I use following URL: http://<host>:50000/XISOAPAdapter/MessageServlet?channel=:BS_Bus_Sys:CC_SOAP_Test as I did in XI 3.0, but I'm getting error HTTP 400 Bad Request. I'm using the request generated from the IR Configuration.
Has something changed in 7.1 for this type of scenario?
Thanks guys,
Olian

Hi! Olian,
I think u r going in a wrong way. The above given URL is wrong and incomplete one.
The above url comes only after generating the WSDL. You ill gives that URL to ur source team to post their data at which this URL itselfs acts as an Gateway to enter into SAP XI/PI.
The generated WSDL contains URL like this>>
"http:// Host:Port/XISOAPAdapter/MessageServlet?senderParty=&senderService=Business Service&receiverParty=&receiverService=&interface=SenderInterfaceI&interfaceNamespace=http://XXXXXXXX" />
Also follow the below procedure for generating the WSDL.
Except generating WSDL remaining all development steps are same as creating File to Proxy Scenario.
CREATING THE WEBSERVICE IN XI :
1) In Integration Directory, go to Tools tab --> Define Web Services.
2) Now one Wizard window will opens and follow the below steps:
Here donu2019t go for the u2018 Proposed URLu2019, instead specify the URL as::
http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet?channel=:<service>:<channel>
If there is party then ::
http://host:port/XISOAPAdapter/MessageServlet?channel=<party>:<service>:<channel>.
3) Specify the Source Messageu2019s Message Interface.and remaining other input parameters.
4) Specify the Sender Business Serviceu2019s details:
5) Here, Cross check the details displayed and then click on u2018Finishu2019 button to create the Web Service
document(WSDL)
6) Now Save the WSDL code to the local system. At the bottom u ill get URL based on the above input
URl:
Note: Here in XI there is no XML Testing tool or SOAP client tool to test SOAP messages. That is why most of the people prefer either ALTOVA XML SPY Tool or SOAP CLIENT TOOL or INFO PATH.
If your working on PI 7.1 means::
1) Simply after creating Sender Agreement go to options above to that sender agreement instead of tools menu... and there you can observe 2 options at the bottom side.
a) PUBLISH in SR
b) Generate WSDL.
2) Once after activating your ID componenets just Press or go for option Publish in SR. Then automatically it will generate WSDL and publish that WSDL in the SERVICE REGISTRY. which is latest concept in PI 7.1.
3) Now by entering authentification details you can able to enter into service registry.
There are 4 tabs::
a) Service definitions
b) Publish
c) classifications
d) Manage.
Go for Service definitions::
4) Enter your sender SOAP interface and press GO or enter.
5) Select your interface and then at the bottom u can observe again 4 tabs:
a) General b) End Points c) classifications d) System Details.
6) In the general you can able to see your WSDL URL by again entering Authentification details.
7) Now Click End Points>Test Button>Enter Authentification details-->Seelct your Interface
Note:: Now you can test your scenario in this WEB SERVICE NAVIGATOR.
8) There you can enter you can pass your Input data parameters in your SOAP interface and execute or test your scenario here itself without any using of external tool like Altova XML or SOAP client tool.
I hope the above information will give you a detailed information in generating and testing webservice right.
Regards::
Amar Srinivas Eli

User level Authorization for SSO by using SOAP Sender

Hi,
Scenario : Non-SAP to PI 7.31 using SOAP Sender adapter.
Authentication we need to go for user based level at the receiver system where the information shall be passed from the sender (non-SAP) and also we 're using Single Sign On method for this interface.
Note : Previously we achieved this through WS-RM using SAML certificates, but this adapter doesn't support in PI7.31 single stack since we have option only by using SOAP adapter.
Please suggest how can i achieve this for my current landscape.
Thanks for your help.
Warm regards,
Ram.

Hi!
The SOAP Adapter itself has no queueing mechanism. But the PI has one if you work asynchronously.
To pick files it may be helpful to use the Axis Framework of SOAP Adapter whre you can add your own adapter modules.
Very helpful tips concerning the SOAP Adapter can be found in the SAP Note 856597 (FAQ SOAP Adapter XI 3.0 Pi 7.0 PI 7.1).
For Axis Adapter FAQ refer to SAP note 1039369
Hope this helps.
Regards,
Volker

SAP PI Soap Send adapter is not available.

Hi Experts：
i encounter a issue when use Soap sender adapter. i configured soap sender adapter senario and generate wsdl in the id .
and then import wsdl document to the soapui to test the webservice. but throw some exception blow:
<!see the documentation>
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
   <SOAP:Body>
      <SOAP:Fault>
         <faultcode>SOAP:Server</faultcode>
         <faultstring>Server Error</faultstring>
         <detail>
            <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
               <context>XIAdapter</context>
               <code>ADAPTER.JAVA_EXCEPTION</code>
               <text>java.lang.NullPointerException
+     at com.sap.aii.af.sdk.xi.mo.xmb.XMBMessageOperator.getQualityOfServiceAsString(XMBMessageOperator.java:2109)+
+     at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:943)+
+     at sun.reflect.GeneratedMethodAccessor1126.invoke(Unknown Source)+
+     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)+
+     at java.lang.reflect.Method.invoke(Method.java:585)+
+     at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)+
+     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)+
+     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)+
+     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)+
+     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)+
+     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)+
+     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)+
+     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)+
+     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)+
+     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)+
+     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)+
+     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)+
+     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)+
+     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)+
+     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)+
+     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)+
+     at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)+
+     at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)+
+     at $Proxy3087.process(Unknown Source)+
+     at com.sap.aii.af.app.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:275)+
+     at sun.reflect.GeneratedMethodAccessor518.invoke(Unknown Source)+
+     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)+
+     at java.lang.reflect.Method.invoke(Method.java:585)+
+     at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)+
+     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)+
+     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)+
+     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)+
+     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)+
+     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)+
+     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)+
+     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)+
+     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)+
+     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)+
+     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)+
+     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)+
+     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)+
+     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)+
+     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)+
+     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)+
+     at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)+
+     at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)+
+     at $Proxy330.process(Unknown Source)+
+     at com.sap.aii.adapter.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:175)+
+     at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:470)+
+     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)+
+     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)+
+     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:162)+
+     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:81)+
+     at com.sap.engine.services.servlets_jsp.server.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:124)+
+     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)+
+     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:441)+
+     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:291)+
+     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)+
+     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)+
+     at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)+
+     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
+     at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:76)+
+     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
+     at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:240)+
+     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
+     at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)+
+     at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)+
+     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
+     at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)+
+     at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)+
+     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
+     at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)+
+     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)+
+     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
+     at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)+
+     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)+
+     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
+     at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)+
+     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)+
+     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
+     at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)+
+     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)+
+     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
+     at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:457)+
+     at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:250)+
+     at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)+
+     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)+
+     at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)</text>+
            </s:SystemError>
         </detail>
      </SOAP:Fault>
   </SOAP:Body>
</SOAP:Envelope>
nd the find a note :sapnote_0001239995 can solve the problem in the pi 7.10 .but my pi is 7.11 .anybody know which note should be apply to solve the problem in the pi7.11 .thanks .

hi,
Either you are using an incomplete URL
you can however try with this URL format:
http://<IPAddress OR ServerName>:<PORT_No>/XISOAPAdapter/MessageServlet?channel=:<SenderBusinessService>:<SenderSOAPCC>&version=3.0&Sender.Service=<SenderBusinessService>&Interface=<SenderInterfaceNamespace>%5E<SenderMI>
refer blog related ur issue:
ADAPTER.JAVA_EXCEPTION: Sender soap adapter PI 7.11
thanks,

HTTP Call to SOAP Sender Adapter

Hi All,
I'm working on a scenario where i plan to use SOAP Sender Adapter for receiving Plain HTTP Calls from the client.
The purpose behind this exercise is to have control over the message flow in case of sender HTTP protocol in XI.
I configured a SOAP channel and used the option 'DO Not Use SOAP Envelope'. But when i post the message to the adapter engine using a HTTP client, it fails.
Can somebody guide me in this case.
Regards,
Anurag

Hi,
>>>But when i post the message to the adapter engine using a HTTP client, it fails.
with which error ?
Regards,
Michal Krawczyk

SOAP sender adapter issue

Hi,
We are facing a peculiar issue when using SOAP sender adapter.It is a SOAP-XI-ECC scenario.
We have created WSDL using propose URL. Edited the address location in WSDL and included QoS=ExactlyOnce.
When we are testing from SOAPUI, it is making a asynchronous call, which is the requirement. But when the actual sender is sending the data using the same WSDL, it is making synchronous call. Any idea if Synchronous/Asyncronous decision/setiing is made at XI end or the portal end? And what is the solution?
Thanks,
Vishal

Hi Shabarish,
As mentioned in my query I have already tested it from SOAPUI and it is making asynchronous call.
URL is:
[http://server/sap/xi/engine?type=entry&version=3.0&Sender.Service=BusinessService&Interface=http://namespace^MI_product_oa&QualityOfService=ExactlyOnce]
Regards,
Vishal

Use of variable header XHeaderName1 in SOAP sender adapter

Hi all,
I have a doubt regarding the use of adapter-specific attributes in SOAP sender adapter. In specific:
the SOAP client should be able to pass a variable with the SOAP request (XHeaderName1 header variable) and this should be available in mapping (Dynamic configuration)
I've already checked the [help page|http://help.sap.com/saphelp_nw04/helpdata/en/fc/5ad93f130f9215e10000000a155106/frameset.htm] but it seems I'm doing something wrong.
I tried with those settings in SOAP adapter configuration:
Keep headers checked
XHeaderName1 = Test
I try to call the SOAP adapters in the following 2 ways, but none works (the value is not available in message mapping with Dynamic configuration)
1. Pass "Test" value xxxx in SOAP Header as a tag
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
     <SOAP-ENV:Header>
          *<Test>xxxx</Test>*
     </SOAP-ENV:Header>
     <SOAP-ENV:Body>
     </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
2. Pass "Test" value xxxx in SOAP URL
http://host:50000/XISOAPAdapter/MessageServlet?channel=p:s:c&version=3.0&Sender.Service=...&Interface=...&Test=xxxx
Could anyone give me a hint about how to pass those values in the SOAP call and eventually the correct config. of SOAP sender ?
Thanks a lot,
Manuel

Hi Manuel,
Could you give a bit more detail on how you handled the SOAP message yourself.
I have a similar issue. I am consuming a non SAP Web Service which requires a non-standard token element to be passed back. I have created a an RFC sender to SOAP reciever scenario which works fine for the inital logon and returns the token it expects in the follow up messages.
At present I'm at a loss so your help would be much appreciated. We have got round the immediate issue by creating and sending the SOAP message directly from SAP WAS.
Could we use the XI Adapter and ABAP proxy in a similar way?
Thanks,
Tim J.

SOAP Sender adapter - how to turn off authentication? PI 7.1

Hello
I wolud like to turn off the user authentication in the Soap Sender Adapter PI 7.1. What is the easiest way to do so?
Regards,
Elling Skjetlein

Hello,
If you mean about using Single Sign-On (SSO) for automatic login, then
you can refer to the following links:
http://help.sap.com/saphelp_nwpi71/helpdata/EN/44/31370f01ae23d1e10000000a1553f7/frameset.htm
http://help.sap.com/saphelp_nwpi71/helpdata/EN/48/acb27f23be6200e10000000a421937/frameset.htm
http://help.sap.com/saphelp_nwpi71/helpdata/EN/c4/5c5ae71140bb41868f10bc7f3411db/frameset.htm
http://help.sap.com/saphelp_nwpi71/helpdata/EN/e5/4344b6d24a05408ca4faa94554e851/frameset.htm
Hope that help.
Regards,
Caio Cagnani

Invocation of SOAP Sender Adapter using Apache SOAP

Hi,
I'm trying to invoke the XI SOAP Sender Adapter using the Apache SOAP API. It seems that my message header is missing a few parameters (see exception below). Does anybody know which to set?
Regards,
Heiko
==========
Exception:
<?xml version='1.0'?>

<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
<SOAP:Body>
    <SOAP:Fault>
      <faultcode>SOAP:Server</faultcode>
      <faultstring>Server Error</faultstring>
      <detail>
        <s:SystemError xmlns:s='http://sap.com/xi/WebService/xi2.0'>
          <context>XIAdapter</context>
          <code>Exception</code>
          <text><![CDATA[
com.sap.aii.af.mp.module.ModuleException
     at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:502)
     at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:103)
     at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:227)
     at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process(ModuleProcessorLocalLocalObjectImpl0.java:103)
     at com.sap.aii.af.mp.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:162)
     at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:507)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:392)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
     at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged1(Native Method)
     at java.security.AccessController.doPrivileged(AccessController.java:321)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)
Caused by: java.lang.Exception: Bubble configuration error: parameter 'XI.InterfaceNamespace' is missing
     at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.getParaRequired(XISOAPAdapterBean.java:895)
     at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.createDefaultMessageHeader(XISOAPAdapterBean.java:942)
     at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.setup(XISOAPAdapterBean.java:214)
     at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:496)
     ... 22 more
          ]]></text>
        </s:SystemError>
      </detail>
    </SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>

Hi Heiko,
You are missing the Namespace Parameter in the sender soap adapter configuration in XI3.0
Thanks
Prasad

Use Moduls with SOAP Sender Adapter

Hi Experts,
I have a question regarding the use of modules in the soap sender adapter / communication channel. Is it correct that the use of modules in the soap sender adapter is not possible?
the background of my question is that we use modules from SEEBURGER in our Communication channels for archiving incoming and outgoing documents. the use of modules in the soap receiver adapter is possible. why not in the soap sender???
according to the sap help it is possible to use the axis framwork in the soap adapter. then it should be possible to use modules. Is that correct? I tested it but it is not working. If I send a soap message (with the soap reveicer adapter) to the axis soap sender adapter there occure internal server errors. it is only working if I write my own modules for the axis soap sender adapter? is it not possible to use external modules like in other channels (File/FTP, soap receiver etc.)???
thanks and best regards!
Christopher

we have moduls from SEEBURGER. so I have to test it. but before I need a scenario with which I can test it.
We have a customer who sends xml-files per soap to us. these files we receive succussfully with the soap sender adapter. now we want to use some modules. so we have to use the axis soap sender adapter. I tried to send an xml file with the soap receiver adapter to the axis soap sender adapter, but this was not working. http 500 internal server errors occurred. is it possible that this scenario (soap-to-axis-soap) is not working? need I a specific configuration for this?
thanks and regards
Christopher

How to update two tables in a single call using JDBC Sender adapter

Hello All,
The scenario is, database entries have to be selected from two tables and at the same time those tables have to be udpated with the flag.
We are using JDBC sender adapter and in Select Query, we are fetching the data by joinin the two tables.
Update Statemtent: We can only update one table using this statement.
Is it possible to update two tables using the Update Statement without using Stored Procedures.
Let me know.
Regards,
Sreenivas.

Hi Sreenivas,
> Is it possible to update two tables using the Update Statement without using Stored Procedures.
Yes its possible through join statement
Check this links
Update in JDBC Sender adapter for more than one table
data from 2 tables for jdbc sender adapter
Regards
Ramesh

Using custom http headers in SOAP sender adapter

Hi,
my problem is exactly the same as reported [here|Re: SOAP Sender - Extract Header Values;] and [here|Variable Transport Binding - Soap Sender;
Basically I'd like to send through the soap sender adapter some custom http headers. I check the necessary options in the advanced tab (set adapter-specific message attributes and variable transport binding), and in the variable header one I put x-StoreCode, which is the same http header I send to PI.
But I won't see anything in the dynamic configuration section when the message is persisted in PI.
Very surprised that I've seen this issue is a common problem others have faced before without success.
Thanks!

Hi Michal,
the extra info I'm trying to send separated from the message is an http header, not part of the query string.
If I incorporate the extra info as a parameter to the query string like this, for example:
http://host:50000/XISOAPAdapter/MessageServlet?senderParty=&senderService=S1&receiverParty=&receiverService=&interface=Int&interfaceNamespace=urn:test&x-StoreCode=13&nosoap=true
Then I can see the value in the dynamic configuration section:
<SAP:Record namespace="http://sap.com/xi/XI/System/SOAP" name="SQueryString">senderParty=&senderService=S1&receiverParty=&receiverService=&interface=Int&interfaceNamespace=urn:test&x-StoreCode=13&nosoap=true</SAP:Record>
But what I'm trying to do shoould be possible, according to sap help:
http://help.sap.com/saphelp_nwpi71/helpdata/en/fc/5ad93f130f9215e10000000a155106/content.htm (section Define Adapter-Specific Message Attributes)

How to use Soap with Netweaver?

Hi,
I am new to SAP Netweaver, I was wondering how to use SOAP messaging with SAP Netweaver?
Thanks
Falak

I want to secure the message between my web service and a Automated activity in SAP Netweaver BPM (Process
development). I think in this case the usage of of SOAP adapter may not be useful.
Security parameters (settings) can be defined for Sender SOAP Adapter (as in your case it is)......to know more check this help section: http://help.sap.com/saphelp_nwpi71/helpdata/EN/fc/5ad93f130f9215e10000000a155106/content.htm
Check the section: Define Security Parameters.
Regards,
Abhishek.

Another SOAP Sender adapter "com.sap.aii.af.mp.module.ModuleException" erro

I am working on a synchronous scenario SOAP <-> XI <-> RFC.
This worked fine, when I run it without SOAP adapter, direct via XI Pipeline.
Now I want to use the SOAP sender adapter, but get the error as described below this post.
As this is a real new XI installation, some patches or updates might be required to make it work. Or some adapter modules ?
Any suggestions on how to solve this problem will be rewarded.
What worries me a bit is the line " " in the error description.
Extra info: I use SoapSonar as a test webservice client. The error is the message as received in te test client.
<?xml version="1.0"?>

<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
    <SOAP:Fault>
      <faultcode>SOAP:Server</faultcode>
      <faultstring>Server Error</faultstring>
      <detail>
        <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
          <context>XIAdapter</context>
          <code>ModuleUnknownException</code>
          <text><![CDATA[
com.sap.aii.af.mp.module.ModuleException: either no channelID specified or no channel found for the specified party, service, and channel name, MessageServlet(Version $Id: //tc/xi/645_VAL_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#9 $)
     at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:427)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
          ]]></text>
        </s:SystemError>
      </detail>
    </SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>

Hi Chandravadhana,
The colon should be there :
http://help.sap.com/saphelp_nw04/helpdata/en/69/a6fb3fea9df028e10000000a1550b0/frameset.htm
The inbound address for SOAP messages is: http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
Under party:service:channel enter the party name, the service name, and the name of the communication channel. If no party has been created, enter the following: channel=:service:channel
Regards
Suraj

Anonymous authentication requests via SOAP Sender adapter?

Hi,
Can someone please tell me whether it is possible to call the SOAP Sender adapter anonymously?
We can set user credentials for the receiver system adapter but looking at the options in the SOAP Sender communication channel I can't see how it is possible to send messages though SAP PI without a user who has authorisations to process messages.
Any advice greatly appreciated.
Thanks,
Alan

can't see how it is possible to send messages though SAP PI without a user who has authorisations to process messages.
The source system needs to use a user-id to send message to XI/ PI via SOAP.
If you do not want to use any authorization there is a way to switch off the authentication for the entire SOAP adapter (i.e. for all the SOAP scenarios)....not advisable.
This method was actually described in a discussion ages back
Regards,
Abhishek.

How to use SOAP sender adapter

Similar Messages

Maybe you are looking for