Sender SOAP  channel

I have a SOAP->RFC sceanario. when i provide the input data to the sender SOAP channel with single name space i.e.
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:OasisGetSalesOrgList xmlns:ns0="http://xi.abc.com/corp/OASIS_GETSALESORGLIST">
- <HeaderInfo>
  <MessageID>uqID</MessageID>
  <MessageTimeStamp>2008-03-04T02:29:11Z</MessageTimeStamp>
  <VersionID>1.0</VersionID>
  <OasisSystemID>DEMO-DB-0000</OasisSystemID>
  <OasisUserID>DEMO</OasisUserID>
  <AgentID>404537</AgentID>
  </HeaderInfo>
  </ns0:OasisGetSalesOrgList>
my scenario gets executed successfully. But when i give the input data to the sender SOAP channel with multiple name space i.e.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!--  Request Message Mapping   -->
- <OasisGetSalesOrgList xmlns="http://xi.abc.com/corp/OASIS_GETSALESORGLIST" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- <HeaderInfo xmlns="">
  <MessageID>uqID</MessageID>
  <MessageTimeStamp>2008-03-04T01:48:54.426Z</MessageTimeStamp>
  <VersionID>1.0</VersionID>
  <OasisSystemID>DEMO-DB-0000</OasisSystemID>
  <OasisUserID>DEMO</OasisUserID>
  <AgentID>HLITOPS</AgentID>
  </HeaderInfo>
  </OasisGetSalesOrgList>
the sender SOAP channel gives the Mapping Transformation error.
What should i do?

hI,
If you have created a message type in conjunction with your source XML then normally you will get only one namespace associated with it. If you want to use multiple namespaces then use the message type as an external definiton where namespace is not specfically defined and try mapping it. I guess you should be able to do it then. Just a suggestion.
Regards,
Merrilly

Similar Messages

  • URL in sender SOAP channel with user and password

    Hi Expert,
    I have developed SOAP to proxy scenario.The serder WSDL is generated by using sender agreement. In the WSDL we are using default below URL.
    http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
    But the client requirement is that he want SAP user and password also in above url.
    Is this possible in sender SOAP channel?
    Any body can please help me for above issue?
    Thanks.
    Edited by: darshana-PI on Feb 1, 2012 5:26 PM

    Thanks prateek,
    we have used HTTP plain adapter for this and used below link to call that interface in PI. And its working.
    http://server:port/sap/xi/adapter_plain?service=<xxx>&namespace=<xxx>&interface=<xxx>&sap-user=<xxx>&sap-password=<xxx>&qos=BE
    I can understand the security related problem, but that was the requirement for end application.
    Thanks,
    Darshana.

  • One of the sender SOAP channel is inactive by itself in the CC monitoring

    HI All
    sender soap channel is showing inactive in the RWB. But when i check the status in Integration directory it is active. It got inactive by itself . can anybody help me  how i can activate it.
    regards
    sandep

    Hi Sandeep,
    There are two ways to Active or Incative communication channel,
    1)Select communication channel in Componnet monitoring and start the communication channel,it will actuvate.if you want inactive stop it.
    or
    2)Iin Integration Directory select mode as Active it will start.
    sometimes it behaves like that...
    REgards,
    Raj

  • SOAP scenario without sender SOAP channel

    Hi Experts,
    I am developing a scenario of SOAP to JDBC.
    Here my test data is coming from Altova Spy for sender SOAP side.
    I have configured the scenario without sender SOAP channel, and sender agreement.
    But while sending the SOAP message I am getting the error as data cannot be posted.
    Can anybody please tell me, whether is it possible to have such configuration without SOAP sender channel.
    And if yes, then what would be the URL that I have to give for posting the data.
    Awaiting your reply.
    Regards,
    Supriya Sawant.

    I have gone throgh this Note.
    But now I m getting this error:
    <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
         <SOAP:Header>
    </SOAP:Header>
         <SOAP:Body>
              <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
                   <faultcode>SOAP:Client</faultcode>
                   <faultstring>Error during parsing of SOAP header</faultstring>
                   <faultactor>http://sap.com/xi/XI/Message/30</faultactor>
                   <detail>
                        <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
                             <SAP:Category>XIProtocol</SAP:Category>
                             <SAP:Code area="PARSER">ITEM_MISSING</SAP:Code>
                             <SAP:P1>Header</SAP:P1>
                             <SAP:P2/>
                             <SAP:P3/>
                             <SAP:P4/>
                             <SAP:AdditionalText/>
                             <SAP:ApplicationFaultMessage namespace=""/>
                             <SAP:Stack>XML element Header missing in SOAP message header (SAP XI Extension)
    </SAP:Stack>
                        </SAP:Error>
                   </detail>
              </SOAP:Fault>
         </SOAP:Body>
    </SOAP:Envelope>

  • Sender Soap Channel is not working - Service Temporarily Unavailable [503]

    dEAR FRIENDS,
    We are facing one critical issue in sender soap adapter. After upgrading our system to PI 7.1 The sender soap channle is not working. From source  system  it is not reaching PI : the log from source system as follows:
    org.springframework.ws.client.WebServiceTransportException: Service Temporarily Unavailable [503]
          at org.springframework.ws.client.core.WebServiceTemplate.handleError(WebServiceTemplate.java:627)
          at org.springframework.ws.client.core.WebServiceTemplate.doSendAndReceive(WebServiceTemplate.java:551)
          at org.springframework.ws.client.core.WebServiceTemplate.sendAndReceive(WebServiceTemplate.java:502)
          at org.springframework.ws.client.core.WebServiceTemplate.marshalSendAndReceive(WebServiceTemplate.java:351)
          at org.springframework.ws.client.core.WebServiceTemplate.marshalSendAndReceive(WebServiceTemplate.java:345)
          at org.springframework.ws.client.core.WebServiceTemplate.marshalSendAndReceive(WebServiceTemplate.java:337)
          at com.palm.txnengine.wsclient.DailyRevenuePostingWSGateWaySupport.postToSap(DailyRevenuePostingWSGateWaySupport.java:23)
          at com.palm.txnengine.wsclient.DailyRevenuePostingImpl.execute(DailyRevenuePostingImpl.java:93)
          at org.springframework.batch.core.step.tasklet.TaskletStep$2.doInChunkContext(TaskletStep.java:264)
          at org.springframework.batch.core.scope.context.StepContextRepeatCallback.doInIteration(StepContextRepeatCallback.java:67)
          at org.springframework.batch.repeat.support.RepeatTemplate.getNextResult(RepeatTemplate.java:352)
          at org.springframework.batch.repeat.support.RepeatTemplate.executeInternal(RepeatTemplate.java:212)
          at org.springframework.batch.repeat.support.RepeatTemplate.iterate(RepeatTemplate.java:143)
          at org.springframework.batch.core.step.tasklet.TaskletStep.doExecute(TaskletStep.java:239)
          at org.springframework.batch.core.step.AbstractStep.execute(AbstractStep.java:198)
          at org.springframework.batch.core.job.AbstractJob.handleStep(AbstractJob.java:348)
          at org.springframework.batch.core.job.flow.FlowJob.access$0(FlowJob.java:1)
          at org.springframework.batch.core.job.flow.FlowJob$JobFlowExecutor.executeStep(FlowJob.java:137)
          at org.springframework.batch.core.job.flow.support.state.StepState.handle(StepState.java:60)
          at org.springframework.batch.core.job.flow.support.SimpleFlow.resume(SimpleFlow.java:144)
          at org.springframework.batch.core.job.flow.support.SimpleFlow.start(SimpleFlow.java:124)
          at org.springframework.batch.core.job.flow.FlowJob.doExecute(FlowJob.java:105)
          at org.springframework.batch.core.job.AbstractJob.execute(AbstractJob.java:250)
          at org.springframework.batch.core.launch.support.SimpleJobLauncher$1.run(SimpleJobLauncher.java:110)
          at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:49)
          at org.springframework.batch.core.launch.support.SimpleJobLauncher.run(SimpleJobLauncher.java:105)
          at org.springframework.batch.core.launch.support.CommandLineJobRunner.start(CommandLineJobRunner.java:207)
          at org.springframework.batch.core.launch.support.CommandLineJobRunner.main(CommandLineJobRunner.java:254)

    Hi,
    Please check this generic description:
    The error message 503 Service unavailable Application stopped! is displayed.
    Description:The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.
    Note: The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish to simply refuse the connection.
    Possible Tips: Because of J2EE application com.sap.aii.af.ms.app not active
    u2022 Try to (re)start the application using the Visual Administrator Choose Server --> Services --> Deploy --> View on Application or restart the J2EE engine
    u2022 The problem is that not all J2EE services can be started by the J2EE. i.e Start the Visual Administrator and select Server->Services->Deploy in the tree on the left. On the right-hand side, choose the Runtime tab page. You see a tree in the right window with all applications if you select the APPLICATION radio button. Check if they are running, otherwise choose Start. Usually the J2EE engine starts all services automatically.
    u2022 Refer SAP Note 803145,807000,791655
    May it helps.
    Regards,
    Caio Cagnani

  • SAP PI 7.31 / Sender SOAP Channel Issue with XML tag Main/@versionMajor has incorrect value 000; expected value is 003

    Hi PI Experts,
    We are on SAP PI 7.31 SP 10.
    We are in the process of integrating ARIBA P2P solution using SOAP Adapter as sender to connect Ariba with our PI system.
    We have configured all required components in ESR and ID(Most of them are content provided by Ariba).When we try to post a message into PI using SOAP UI we are ending with below error.

    http://<host name> : <port name> /XISOAPAdapter/MessageServlet?channel= <party name> : <service name> : <channel name>
    For the above issue we had configured SOAP Sender channel as above,and the URL we are using to hit PI is as above screenshot.
    We have followed the note on this topic with out any luck.
    1378872
    We are not sure where is problem.As the issue is not reaching to PI not able to see the messages in SXMB_MONI.
    and in the SXMB_ADM PI has been configured as Integration Server.
    I had even tried to change the message protocol as XI3.0 in SOAP sender channel and noluck.
    I have tried to ximessage=true query also in URL and noticed that not working.This is clear that the message we are trying to send from Ariba is not compatible with XI3.0 protocol,Ariba is not having any option to change at their end as it is a cloud application and many customers have been using same with out any issues.
    We have tried maintain the Java System properties in NWA as XPI.Adapter.Version.Major = 3 but no luck.
    Can some one provide us the solution to get rid of this issue?

  • Error Re-using Sender SOAP Channel

    Hi,
    I have a requirement to send multiple messages to PI using same SOAP Sender Channel; I referred to help.sap.com and found that there is no restriction in re-using a SOAP Sender Channel.
    However when I sent a message using SAP SOAP client, namespace for soap envelope got added which is failing the messages in PI.
    Correct message:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    <ConsumerData>
      <UserId>12345</UserId>
      <AccountData>9561234</AccountData>
    </ConsumerData>
    Incorrect message (in SXMB_MONI):
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    <ConsumerData xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <UserId>12345</UserId>
      <AccountData>9561234</AccountData>
    </ConsumerData>
    1) How to avoid getting the URL (xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/") in the message?
    2) Is it really possible to re-use the SOAP Sender Channel to get different types of messages (from same sender party & service)?
    I did make use of Do Not Use SOAP Envelope in the channel and &nosoap=true in URL; but no luck.
    Please help. I need to get this approach working
    Thanks
    Pankaj

    >>1) Use one Sender channel per source system; so less number of objects.
    Yes, you can reuse one sender channel for many WSDL scenarios.
    >>2) to keep the PI URL common for one source system; PI URL dependent only on Sender Party, Sender Service and Sender Channel, no mention of Sender Interface Name in the URL I am using the format http://host:port /XISOAPAdapter/MessageServlet?channel=p:s:c (Note - 856597).
    I hope I can achieve the requirement in point 2 without any issue.
    This is not possible.  WSDL URL will be different for every interface.  Because it is also specific to sender interface and sender interface namespace.  When you create you have to specify these variables too.
    Example:
    http://host:port/XISOAPAdapter/MessageServlet?channel=:BC_TEST:CC_SOAPCHANNEL&interface=SI_TEST&interfaceNamespace=http://test/TRI_DatabaseLookup
    When you create initially you input only first
    http://host:port /XISOAPAdapter/MessageServlet?channel=p:s:c
    and subsequent screen you will need to input sender service interface and interface namespace.
    Hope that helps.

  • How to test HTTP request for Sender SOAP Channel

    Hi all,
    We are testing Soap requests from SOAP UI tool.
    We are able to call HTTPS calls from SOAPUI tool, but unable to call HTTP request.
    we eanbles ssl and able to post https requests.
    please advice .
    Thanks
    RGDASARI

    Hi Stefan, I configured the way you have put it, but I get the error "no receiver could be determined"
    Here are my settings:
    Sender service - HTTP_SEND
    sender o/b interface - PROD_MSG_INT_OB_ASYNC
    receiver service - FILE_RECEIVE
    receiver i/b interface - PROD_MSG_INT_IB_ASYNC
    receiver communication channel - FILE adapter
    JAVA script:
    String Party       = "MFC";
    String Service     = "HTTP_SEND";
    String XINameSpace = "mfc%3Anamespace1";
    String Interface   = "PROD_MSG_INT_OB_ASYNC";
    String Url   = "http://nemo:8000/sap/xi/adapter_plain?";
    XML DATA File:
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:PRODUCT xmlns:ns0="mfc:namespace1">
    <ID>E</ID>
    <NAME>thank god</NAME>
    <BRAND>SOME BRAND</BRAND>
    </ns0:PRODUCT>
    Stefan Am I missing anything?
    XML error message:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Receiver Identification
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_BE</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>No receiver could be determined</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    It would be great if you have solution for this.
    Regards
    felix

  • Issue with HTTPS in sender soap channel: HTTP 502 Proxy error

    Hi
    We have a situation where we are providing the target url in SOAP receiver channel dynamically.
    This is a synchronous scenario.
    Whenever we use the url starting with "HTTP" it works but on using "HTTPS" we are getting the following error "HTTP 502 Proxy error"
    Kindly help us resolve this issue.

    Hi Anurag
    Have you tried to open the HTTPS  url in the web browser?
    Please check with 3rd party and find out whether the web service supports the HTTPS url or not.
    Please check the doc below. It may help
    502 Bad Gateway Error (What It Is and How To Fix It)

  • SOAP Sender - RWB "Channel started but inactive"

    I have a sender soap channel configured. In Integration Directory the Adapter Status is active. However when I go to Runtime Workbench and view the channel it says the "Channel is started but inactive". Can someone explain to me why it is not active in Runtime Workbench?
    Also, SOAP messages sent to this channel are failing obviously because the channel is inactive. How can I make this channel active so that XI can receive SOAP requests.

    hi rodel,
    You have to process one message at least to make SOAP adapter Active
    refer this discussion
    how can i enable SOAP Adapter?
    regards
    Ramesh P

  • ADAPTER.JAVA_EXCEPTION: Sender soap adapter PI 7.11

    Hi
    I am using the following URL to post a soap message using Sender Soap channel. (We have SAP PI 7.11 (EHP1) sp0)
    http://<hostname>:50000/XISOAPAdapter/MessageServlet?channel=:Business_Sysytem:Channel.
    I am getting following exception..
    I have searched SAP notes as well and have not found any pertaining to this . Though for SAP PI 7.10 sap has a note (1239995 ) for same issue but that is not applicable for this version.
    <?xml version="1.0"?>
    <!-- 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><![CDATA[
    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.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         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)
    Thanks,
    Lovein

    Complete error message
    http://schemas.xmlsoap.org/soap/envelope/}Server, Error: Server Error, Details: <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.NativeMethodAccessorImpl.invoke0(Native Method)
                at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
                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 $Proxy2974.process(Unknown Source)
                at com.sap.aii.af.app.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:275)
                at sun.reflect.GeneratedMethodAccessor408.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 $Proxy96.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>

  • Reading parameters from Query string : Sender SOAP adapter.

    Hello Experts,
    I have a SOAP to SOAP scenario. Here we will have multiple receivers and dynamic receiver determination is needed.
    The sender will send a Value in Query string of URL to sender SOAP adapter. This value in Query string parameter will decide the receiver at runtime.
    I need to know, how can we read values from Query string of incoming call? I did tried to search blogs & forum threads but unfortunately not able to hit the right links.
    Any inputs will be of great help.
    Should i use "Use Query String" on sender soap channel? I tried it, but i was not able to find any query string parameters in SOAP header or payload.
    Please guide me, its bit urgent.
    Regards,
    Abhi.

    > But the argument provided from their side is: They are using standard XSD and this service is provided out of box with sender application.
    If they can add a URL parameter, they can also add a field to the structure.
    > They cant control the value mapping of parameters in payload to the extent required to implement this change.
    Adding a new field to the structure would not affect any existing mapping.
    > Since they have this custom requirement of multiple receivers & receiver to be determined at runtime, they need to go for Query string.
    This can be done based on any field of the payload.
    > I need to find a way to read the query string in any case.
    This is not supported by SOAP adapter.
    > Can I use one of the header parameters to be mapped to this value  (By selecting "Use Query string" & "Keep Headers" flag in sender CC) & then extract this value from header using Dynamic configuration ?
    This feature works only for XI header fields, like message ID or QoS.
    Not for individual parameters.

  • Sender SOAP adapter error 401

    Hello All,
    Here the scenario is SOAP -> XI -> SAP ECC.
    When the webservice is seding the message I am getting error in Sender SOAP channel.
    Message is not going to Integration Engine.
    Its failing with 401Un Authorized in sender soap adapter channel.My sender soap channel is plain channel with no authentication check and certificated etc.When webservice is seding request to XI its sending wit some usernmae which was there on XI box.I am facing this issue in Quality Env. The same is working fine in Dev box.
    Please give me the list of points that I need to check here.
    Thanks,
    Regards,
    Naresh

    Hi,
    I am facing this issue in Quality Env. The same is working fine in Dev box.
    Once the scenario is transported from Dev to QA the location where the Webservice is hosted will also change
    Hence you will have to change the target URL .....just the HostName / IP address and the port for all the webservices (that you transported to QA)
    Once you are in QA and with no change to the URL the sender (which I suppose is also in QA env) will be still trying to ping the same old Dev-URL....in such situation the sender is bound to get UnAuthorized error....
    So one in all change the URL in your WebService to point to QA and then test....
    Same logic applicable to QA --> PROD
    Regards,
    Abhishek.

  • Queue name in QOS EOIO -Sender SOAP Adapter

    hi,
    While configuring sender soap adapter , if we specify EOIO as QOS , then there is a mandatory parameter Queue name to be specified.
    What is this Queue name ?
    and where is it created
    kindly reply
    Regards,
    loveena

    Hi D' souza
    Goto tcode -> SXMB_ADM -> register queues
    for specifying QOS EOIO you need to assign a queue
    from there you can specify the queue for Outbound side EOIO queue
    Various queue name and there meaning is as follows
    XBT*-Queues for Exactly Once.and time dependent
    XBQ*-Queues Exactly Once In Order.
    XBTI* are inbound queues for EO with time constarint
    XBTO* are outbound queues for EO with time constarint
    XBQI* are inbound queues for EOIO
    XBQO* are outbound queues for EOIO
    for beter understanding of how to configure sender soap channel you may folow this link
    http://help.sap.com/saphelp_nw04/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm
    thanks
    sandeep
    if helpful reward points
    Thanks
    sandeep
    if helpful rewrad points

  • Query on Sender SOAP

    Hello,
    Do we need to Configure Sender in case of Sender SOAP adapters...Normally in which cases we can skip configuring the sender SOAP adapter.
    Because In on of our interfaces ,in production..I have  seen an interface with no sender SOAP Communication channel used in Sender Agreement ....Even then defined Sender SOAP communication channel in some business service...
    What could be the reason...

    1. When we use *Sender SOAP Adapter how the connectivity is happening with Remote Clients.
    A:SOAP is an XML-based protocol for exchanging information in a decentralized, distributed environment.SOAP is a technology that allows XML to move easily over the Web. SOAP does this trough an XML envelope for delivering XML content and specifying a set of rules for services to follow when they receive a SOAP message.The fundamental change brought about by SOAP has been the ability to move data anywhere across the Web.
    When ever XI needs to talk to a webservice you will go for SOAP adapter. If you need to enable some functionality as webservice using XI you can use SOAP Sender adapter. If you need to send request to a webservice you will go for SOAP Receiver
    SOAP Message Structure :
    SOAP Envelop: The outermost element of SOAP message. The envelope element is the root of the XML document that defines a SOAP message.
    SOAP Header: An optional, yet key element in architecting a distributed system around XML. The header element provides a modular way of directing SOAP servers to do processing before passing the SOAP message on. For example, it is possible to add SOAP header information that instructs a server to add transaction or authentication information. Header are also important in building piped architectures where processing is done in stages and data is modified as it is passed from handler to handler.
    SOAP Body: An element that must appear in a SOAP message. The Body element is where the transported XML is loaded. SOAP makes no assumptions about the kind of XML transport in the body of a SOAP message. XML or it may take the form of remote procedure call.
    also these weblogs can give you a view where you can use SOAP adapters
    EP-XI Integration using Web Services and Web Dynpro MVC
    https://www.sdn.sap.com/sdn/weblogs.sdn?blog=/pub/wlg/1334 [original link is broken] [original link is broken] [original link is broken]
    Looking for replacing SAP.NET connectors with SAP XI?
    https://www.sdn.sap.com/sdn/weblogs.sdn?blog=/pub/wlg/2131 [original link is broken] [original link is broken] [original link is broken]
    how the connectivity is happening with Remote Clients?
    A:Configuring the Sender SOAP Adapter
    http://help.sap.com/saphelp_nw04/helpdata/en/fc/5ad93f130f9215e10000000a155106/content.htm
    2.How sender SOAP Adapter get those webservices from remote clients and when exactly Remote clients will send webservices to SOAP Adapter?
    It purely depends on ur client & if ur client provides WSDL file then u no need to develop it in ID and use that WSDL.WSDL describes a particular web service. Using a wsdl, we are requesting the broker to point the exact system, application, message interface. Once it is found, the SOAP channel is opened between the provider and the consumer. So the WSDL is a must to access web services.
    in XI, we have to define the Web service which we want to use for the Sender SOAP channel. It is done by choosing Define Web Service from the tool menu of Integration Directory.
    There is no need to code any thing. Here, what you are doing is, just exposing the sender service,channel,Message Interface as a web service.
    In XI, we need to map the incoming messages to the target message( to the actual web service from the provider) format and to maintain the technical and logical routing between the sender and receiver.
    Check this blog to generate WDSL file...
    Exposing BAPI as Web Services through SAP XI
    Configuring a SOAP Sender Channel:
    When we create a SOAP sender channel we have to define the namespace and the name of a message interface (values can be taken from Integration Repository).
    Select the Quality of Service according to your interface type. If you are using a synchronous interface, select Best Effort. Otherwise, select Exactly Once or Exactly Once in Order.
    Transport protocol : HTTP
    Message protocol : SOAP 1.1
    Adapter Engine: Integration Server
    3. I need exactly how the webservices request is passing through sender SOAP Adapter.
    After completion of ur scenario u can use XML spy for testing ur scenario.
    Refer this Blog how to send SOAP message from XML Spy
    Invoke Webservices using SAPXI
    Web Services Testing: SAP Netweaver Platform
    http://www.crosschecknet.com/web_services_testing_SAP.php
    Using the SOAP inbound channel of the Integration Engine
    XI: Propagation of meaningful error information to SOAP Client
    An Overview of SOAP
    Refer the following blogs for SOAP sender Configuration:
    How to Use the XI 3.0 SOAP Adapter
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d23cbe11-0d01-0010-5287-873a22024f79
    How Tou2026Set Up a Web-Service-Related Scenario with SAP XI
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/befdeb90-0201-0010-059b-f222711d10c0
    have a look at this weblog:
    How to use Client Authentication with SOAP Adapter
    SOAP Adapter
    http://help.sap.com/saphelp_nw04/helpdata/en/69/a6fb3fea9df028e10000000a1550b0/content.htm
    Architecture of connector for SAP XI
    http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.wbia_adapters.doc/doc/sap_xi/sapximst14.htm
    Configuring the Sender SOAP Adapter
    http://help.sap.com/saphelp_nw04/helpdata/en/fc/5ad93f130f9215e10000000a155106/content.htm
    Security Settings for the Sender SOAP Adapter
    http://help.sap.com/saphelp_nw04/helpdata/en/1f/7e2441509fa831e10000000a1550b0/content.htm

Maybe you are looking for