SOAP:XIServer/UNKNOWN/ADAPTER.JAVA_EXCEPTION

Hi All,
I am getting the following error in Receiver SOAP adapter. Can anybody suggest wt could be the resone.
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIServer/UNKNOWN/ADAPTER.JAVA_EXCEPTION - 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/NW04S_18_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#1 $) 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:386) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175) 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:104) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

either no channelID specified or no channel found for the specified party, service, and channel name,
Is the channel properly created and present in ID, visible in RWB and SXI_CACHE?
Also are you refrering the proper channel in Receiver Agreement?
Do a dummy change to the channel...save...activate...refresh cache and then check.
Regards,
Abhishek.

Similar Messages

  • SOAP: response message contains an error XIServer/UNKNOWN/ADAPTER.JAVA_EXCE

    Hi ,
    I am getting below error in SOAP reciever channel.
    Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIServer/UNKNOWN/ADAPTER.JAVA_EXCEPTION - com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Connection SOAP_http://sap.com/xi/XI/System is currently not started. at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:996) at sun.reflect.GeneratedMethodAccessor501_10002.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:43) 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 $Proxy2662_10002.process(Unknown Source) at com.sap.aii.af.app.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:275) at sun.reflect.GeneratedMethodAccessor326_10002.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:43) 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 $Proxy114_10002.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:163) at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:82) 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:74) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:425) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376) at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71) at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71) at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67) at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71) 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:71) 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:71) 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:71) at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:309) at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222) 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:152) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)

    Hi,
    Can you please elaborate more on your problem.
    Regards,
    Raghu.

  • 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>

  • Sender SOAP CC - ADAPTER.JAVA_EXCEPTION

    Hi,
    We are using XI 2.0; This scenario is SOAP -> IDOC; I followed the steps in the document 'How Tou2026
    Use the XI 3.0 SOAP Adapter';
    I have created a sender soap communication channel and defined a web service from the ID; (SOAP adapter channel belongs to service without party, so I used the address as follows http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet?
    channel=:<service>:<channel> in the wizard to create the WSDL file)
    I could not use a third party software to test the interface.
    When the vendor send the test data to the URL he get the message as follows:
    <!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>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/NW04S_19_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#1 $)
                    at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:427)
                    at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code))
                    at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code))
                    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java(Compiled Code))
                    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java(Compiled Code))
                    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java(Inlined Compiled Code))
                    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java(Compiled Code))
                    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java(Compiled Code))
                    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java(Compiled Code))
                    at com.sap.engine.services.httpserver.server.Client.handle(Client.java(Inlined Compiled Code))
                    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java(Compiled Code))
                    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java(Compiled Code))
                    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java(Compiled Code))
                    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java(Compiled Code))
                    at java.security.AccessController.doPrivileged1(Native Method)
                    at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))
                    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code))
                    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))</text>
                </s:SystemError>
             </detail>
          </SOAP:Fault>
       </SOAP:Body>
    </SOAP:Envelope>
    Can anyone give me a hint on what to do to clear this error? Also any better help guide will be useful/helpful.
    Thanks

    Hi,
    I did the recommendation - I keep getting the same error.
    Additionally I wanted to let you know, when I test the URL in the Internet Browser, I get the following message
    Message Servlet is in Status OK
    Status information:
    Servlet com.sap.aii.af.mp.soap.web.MessageServlet (Version $Id: //tc/xi/NW04S_19_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#1 $) bound to /MessageServlet
    Classname ModuleProcessor: null
    Lookupname for localModuleProcessorLookupName: localejbs/ModuleProcessorBean
    Lookupname for remoteModuleProcessorLookupName: null
    ModuleProcessorClass not instantiated
    ModuleProcessorLocal is Instance of com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0
    ModuleProcessorRemote not instantiated
    Thanks and Regards
    Kasee Palaniappan

  • ADAPTER.JAVA_EXCEPTION XMBMessageOperator.getQualityOfServiceAsString error

    I am currently working on a scenario SOAP to idoc using PI 7.11 ep0.  I have generated the WSDL, imported it into SOAPUI for testing and I am receiving the error below.
    HTTP/1.1 500 Internal Server Error
    server: SAP NetWeaver Application Server 7.11 / AS Java 7.11
    transfer-encoding: chunked
    content-type: text/xml; charset=utf-8
    content-encoding: gzip
    date: Mon, 07 Mar 2011 15:01:50 GMT
    set-cookie: saplb_*=(erplab-nwpi70_PC2_00)2615750; Version=1; Path=/
    set-cookie: JSESSIONID=GQ9Gyi8sENqRDRjN4rAYLmOQpBaqqdaQLgHG6ScA_SAP; Version=1; Path=/
    <?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.GeneratedMethodAccessor467.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)
    Any help in resolving this issue will result in points being awarded and great appreciation being heaped on you. 
    Thanks in advance,
    Terri

    Hi Rajhans,
    I have already forwarded OSS Note 1239995 to my Basis team. They have told me this note does not apply to us as the note is for PI7.10.
    As far as the XML structure, I have imported the WSDL into SOAPUI for testing purposes.  The XML structure is a simple structure (only about 10-12 fields) and seems to be correct.
    Can you please confirm this problem still exists in PI 7.11 SP0?
    Thanks
    Terri

  • code ADAPTER.JAVA_EXCEPTION /code

    hi everybody,
      iam doing the scenario soap to file while iam testing the scenario iam getting the following error ..
    <!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>com.sap.aii.af.service.cpa.CPAObjectNotFoundException: Couldn't retrieve binding for the given channelId: Binding:CID=null;
         at com.sap.aii.af.service.cpa.impl.lookup.AbstractLookupManager.getBindingByChannelId(AbstractLookupManager.java:173)
         at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:451)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
         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:461)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:397)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         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:83)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:243)
         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:428)
         at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
         at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:327)</text>
                </s:SystemError>
             </detail>
          </SOAP:Fault>
       </SOAP:Body>
    </SOAP:Envelope>
    note : i also checked with set-adapter specific attributes also

    Hi,
    Make sure all your ID objects are activated. Also, ask your Basis Team or if you have access to refresh CPA cache.
    For complete cache refresh u2013 http://<hostname>:<port>/CPACache/refresh?mode=full
    For delta cache refresh u2013 http://<hostname>:<port>/CPACache/refresh?mode=delta
    You may also perform  SLD cache refresh by going to menu Environment u2192 Clear SLD Data Cache.
    Regards,
    Jenny

  • Channel stopped by administrative task - ADAPTER.JAVA_EXCEPTION

    Hi Guys,
                 Adapter engine at RWB has the following error message.
    ==== Events on Server 44769350 ====
    Adapter Engine, message: Fatal DeleteJob (Default Delete Job) failed.
    (Details: Code: MS.JOB.DELETE, Location: com.sap.aii.af.ra.ms.impl.core.archiving.executor.DeleteExecutor, Reason: com.sap.aii.af.ra.ms.api.DeliveryException: Failed to delete unassigned audit log entry keys. Reason: com.sap.aii.af.ra.ms.api.DeliveryException: Could not get unassigned audit log entry keys, due to: ORA-01089: immediate shutdown in progress - no operations are permitted
    , Time: 08.03.2009 10:00:15)
    Adapter Engine, message: Fatal DeleteJob (Default Delete Job) failed.
    (Details: Code: MS.JOB.DELETE, Location: com.sap.aii.af.ra.ms.impl.core.archiving.executor.DeleteExecutor, Reason: com.sap.aii.af.ra.ms.api.DeliveryException: Failed to delete unassigned audit log entry keys. Reason: com.sap.aii.af.ra.ms.api.DeliveryException: Could not get unassigned audit log entry keys, due to: ORA-01089: immediate shutdown in progress - no operations are permitted
    , Time: 15.02.2009 10:00:11)
    Adapter Engine, message: Fatal DeleteJob (Default Delete Job) failed.
    (Details: Code: MS.JOB.DELETE, Location: com.sap.aii.af.ra.ms.impl.core.archiving.executor.DeleteExecutor, Reason: com.sap.aii.af.ra.ms.api.DeliveryException: Failed to delete unassigned audit log entry keys. Reason: com.sap.aii.af.ra.ms.api.DeliveryException: Could not get unassigned audit log entry keys, due to: ORA-01089: immediate shutdown in progress - no operations are permitted
    , Time: 01.02.2009 10:00:20)
    At the adapter engine monitoring at RWB
    Adapter type JPR has following error message
    SLD host:port = ERPDEV02:50400
    Error getting JPR configuration from SLD. Exception: No entity of class SAP_BusinessSystem for DXI.SystemHome.erpdev02 found
    No access to get JPR configuration
    I am getting following error when try to send a file from other business system to XI server.
    <SOAP:Envelope xmlns:SOAP=''http://schemas.xmlsoap.org/soap/envelope/''><SOAP:Header/><SOAP:Body/></SOAP:Envelope>
    as the response.
    <?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[
    com.sap.aii.af.service.administration.api.cpa.CPAChannelStoppedException: Channel stopped by administrative task.
                    at com.sap.aii.af.service.administration.impl.cpa.CommonCPA.checkChannelState(CommonCPA.java:58)
                    at com.sap.aii.af.service.administration.impl.cpa.LookupManagerDelegate.getCPAObject(LookupManagerDelegate.java:83)
                    at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.setup(XISOAPAdapterBean.java:227)
                    at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:689)
                    at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_3.process(ModuleLocalLocalObjectImpl0_3.java:103)
                    at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:292)
                    at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0.process(ModuleProcessorLocalLocalObjectImpl0_0.java:103)
                    at com.sap.aii.af.mp.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:174)
                    at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:436)
                    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:175)
                    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>
    Thanks for Ur time
    Senthil

    Hi Senthil,
    As suggested by others there is no problem with your communication channels ,,, the problem you face is because Your DBA has initiated the SHUTDOWN IMMEDIATE command. This will shutdown Oracle and terminate all active operations.
    Please tell him to start the services and Wait until Oracle has been restarted by your DBA.
    Regards
    joel

  • ADAPTER.JAVA_EXCEPTION  - java.lang.Exception: no valid message format obje

    Hi experts,
    we have a problem when we call a web service PI (release 7.01 , SP 10), from legacy system : the PI system return this message : ADAPTER.JAVA_EXCEPTION ; - java.lang.Exception: no valid message format object found
    For to test this scenario we use soapUI tool.
    I tried the URL (... /XISOAPAdapter/HelperServlet?action=FindChannel ...) in IE and got the following response :
      <?xml version="1.0"; ?>
    - <s:ChannelInfo xmlns:s="http://sap.com/xi/WebService/xi30">
      <channelID>11ccbb96a7f3349c895a005c9bc09cb7</channelID>
      <name>CC_Soap_Sender_TestWS</name>
      <type xmlns:st="http://sap.com/xi/XI/System">st:SOAP</type>
      <direction>INBOUND</direction>
      <party />
      <service>BS_..........IDB_DEV</service>
      </s:ChannelInfo>
    so I think that this service is OK .
    Thanks in advance for your help,
    Alberto

    Hi,
        1)  Check the URL once again- check for the extra spaces at the end of the link.
    2) please refer below blog i hope it will help you
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/40611dd6-e66e-2910-f383-e80fb44f9cd4?QuickLink=index&overridelayout=true
    Did you check the page no 14 of the document  which has the same problem - in problem analysis it has mentioned that check the URL as well as proxy setting of internet browser.
    3) Try to create the ID objects manually (Sender Channel and Sender Agreement).....when we use the wizard a * gets introduced in the unfilled (unused) fields (party etc) ....however when manually created the unused fields are left blank.
    4) Check if all the ID objects are available in SXI_CACHE.
    regards,
    ganesh.

  • Missing soap action in the soap axis receiver adapter ?

    Hi Guys,
    I could not find the soap action field in the soap receiver adapter and i followed the OSS note
    Note 1054986 - SOAP (Axis) receiver adapter's SOAPAction field missing
    Please apply the following patch and use the handler parameter defaultSOAPAction for the XI30OutboundHandler handler in the request chain. This handler parameter can be configured as a module parameter for the HandlerBean module associated with this handler. It is noted that this module parameter takes precedence over the channel parameter for SOAPAction if this field is available.
    For SP12
    XI ADAPTER FRAMEWORK CORE 7.0
    Support Package 12, Patch Level 1 (SAPXIAFC12P_1.SCA)
    we are on SP15 so i think the option should be available ?
    Do i need to add this parameter in the Module Configuration ?
    Moduel Key : ?
    Parameter Name: handler.type ---> is this right
    Parameter Value ---> ?
    we need to validate the user id and pw on IIS for NTLM authentication. Any help regarding developong the handlers would be great
    any help would be appreciated.
    Thanks,
    Srini

    Srinivas,
    You are on the right path...........yes that is the right note for this issue.
    The problem is this is not a general fix that comes with all service packs as the axis adapter is not used a lot, that being said.if you dont see it with sp15..i would safely go apply this fix and see if it works..else you might have to open an oss note for the same...
    Hope that helps..
    Regards
    Ravi Raman
    P.S: On my home system..i did apply the fix and i was on a much higher sp level ..i saw some errors..in the logs but nothing a restart couldent fix..

  • How to set content type in SOAP AXIS sender adapter

    Hi All,
    I am trying to fetch the data from an URL which has special characters(like Ä, ï) using SAP PI - SOAP AXIS adapter. I am facing the below error in the channel.
    “error during receive: java.io.UnsupportedEncodingException: charset: utf-8”
    I need to set the content type as ISO-9958-1 but there is no such option present in the SOAP AXIS sender Adapter. Please let me know if there is any way to set the content type and fetch the data successfully.
    Thanks,
    Konda

    Hi Sudha,
    I have tried textcodepageconversion, Message
    Transformation and Annomizer beans but didn't help and this error is in sender SOAP AXIS adapter.
    Thanks,
    Konda

  • SSL / X.509 In SOAP Sender/Receiver Adapter

    Hi Friends,
    We have few third party Java based systems which need to integrate with SAP PI7.1
    For this we are using
    SOAP Sender from Third PartyTo PI
    SOAP Receiver From Pi To Third Party Systems                                 
    The Customer Wants to implement SSL.X>509 certificates for encryption and decryption. as one of the option.
    we are  Facing few issues like.
       I am assuming each of the source system webservice calls will have
    to use a username/password to authenticate with the PI system
    a.       Will this use 'basic authentication', ie., credentials sent over as
    part of the HTTP header field ?
       i.
    Assuming we use SSL for transport level security - this is still not secure as the credentials are not encrypted
    ii.      Is  there a way to send in encrypted credentials and for the PI layer to decrypt the same, validate and process the request ?
    b.      Should we consider using a single sign-on mechanism ?
    c         Should we consider using X.509 digital certificates ?
          i.      This would require that the X.509 certs are maintained in the Source & PI webserver Java key stores
    d.      Should we also consider digitally signing the payload ?
         i.      This  requires using an appropriate hashing algorithm such as SHA-1 or MD5
    SOAP Sender /receievr Adapter has few properties not specific to them.How to Acheive this.
    Regards
    Chandra Dasari

    Hi Chandra,
    You may try to implement this using the AXIS framework of the SOAP adapter. This provides functionality for handling of X.509 encryption and decryption.
    You can generate/get the digital certificate and use it for both transport level as well as message level security. You would not require any additional encoding apart from this.
    Coming to your queries:
    Q - I am assuming each of the source system web service calls will have to use a username/password to authenticate with the PI system
    A - If you are using a certificate, then they can call XI using this certificate. You can share your public certificate with each of the parties.
    Q. Will this use 'basic authentication', ie., credentials sent over as part of the HTTP header field?
    A - Depends...if you are using basic authentication, then it will not be via X.509. It will be the normal process. These two are two different things.
    Q. Assuming we use SSL for transport level security - this is still not secure as the credentials are not encrypted
    A - This problem is resolved if you are using digital certificates.
    Q. Is there a way to send in encrypted credentials and for the PI layer to decrypt the same, validate and process the request?
    A - Yes. It is possible. But then you will have to implement encryption decryption logic at both the ends separately if you are not using certificates.
    Q. Should we consider using a single sign-on mechanism?
    A - Is your third party part of your landscape? if not then you might want to check and confirm this approach with your security adviser.
    Q Should we consider using X.509 digital certificates?
    A - Yes...This would resolve most of your problems.
    Q. This would require that the X.509 certs are maintained in the Source & PI web server Java key stores
    A - Yes.
    Q. Should we also consider digitally signing the payload?
    A - If you require message level encryption along with transport layer.
    Q. This requires using an appropriate hashing algorithm such as SHA-1 or MD5. SOAP Sender /receiver Adapter has few properties not specific to them.How to achieve this.
    A - You can provide this option while generating the certificate itself.
    Please let me know if this helps.
    Cheers,
    Sarath.

  • Invalid soap address, unknown protocol jms

    Hi, All,
    I try to create a web service project based on a WSDL which soap based on JMS as following:
    <?xml version="1.0" encoding="UTF-8"?>
    <definitions name="AsyncBusiness"
         targetNamespace="http://www.alsb.com/AsyncBusiness/"
         xmlns="http://schemas.xmlsoap.org/wsdl/"
         xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
         xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
         xmlns:tns="http://www.alsb.com/AsyncBusiness/"
         xmlns:xsd="http://www.w3.org/2001/XMLSchema">
         <types>
              <xsd:schema targetNamespace="http://www.alsb.com/AsyncBusiness/"
                   xmlns:order="http://www.alsb.com/order/">
                   <xsd:import namespace="http://www.alsb.com/order/"
                        schemaLocation="order.xsd" />
                   <xsd:element name="submitOrder" type="order:Order" />
              </xsd:schema>
         </types>
         <message name="submitOrder">
              <part element="tns:submitOrder" name="submitOrder" />
         </message>
         <portType name="AsyncBusiness">
              <operation name="submitAsyncOrder">
                   <input message="tns:submitOrder" />
              </operation>
         </portType>
         <binding name="AsyncBusinessSOAP" type="tns:AsyncBusiness">
              <soap:binding style="document"
                   transport="http://www.openuri.org/2002/04/soap/jms" />
              <operation name="submitAsyncOrder">
                   <soap:operation
                        soapAction="http://www.alsb.com/AsyncBusiness/submitOrder" />
                   <input>
                        <soap:body parts="submitOrder" use="literal" />
                   </input>
              </operation>
         </binding>
         <service name="AsyncBusiness">
              <port binding="tns:AsyncBusinessSOAP" name="AsyncBusiness">
                   <soap:address
                        location="jms://192.168.48.1:7001/AsyncOrderSelf_WS/AsyncBusiness?URI=jms.WebServiceQueue" />
              </port>
         </service>
    </definitions>
    the problem is when I generate web service based on that, error found: invalid soap address, unknown protocol jms. How can I make it work?
    I'm using workshop 10.3 for weblogic. Thanks in advance.
    Best Regards,
    Bill
    Edited by: Bill Cao on May 20, 2009 11:13 AM

    Bill,
    Soap Address should always should be standard.
    But you can change the action type under the wls binding part
    for example I will provide one sample and it work perfectly at my end.
    <!-- ************************************************************* -->
    <!-- Web Service JMS Binding Definition -->
    <!-- ************************************************************* -->
    <wsdl:binding name="SampleJMSSoapBinding" type="invws:SamplePort">
    <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/jms" />
    <wsdl:operation name="DeleteParty">
    <soap:operation soapAction="http://xmlns.oracle.com/communications/webservice/DeleteParty" />
    <wsdl:input>
    <soap:body use="literal" />
    </wsdl:input>
    <wsdl:output>
    <soap:body use="literal" />
    </wsdl:output>
    <wsdl:fault name="InventoryFault">
    <soap:fault name="InventoryFault" use="literal" />
    </wsdl:fault>
    <wsdl:fault name="ValidationFault">
    <soap:fault name="ValidationFault" use="literal" />
    </wsdl:fault>
    </wsdl:operation>
    </wsdl:binding>
    <!-- ************************************************************* -->
    <!-- Web Service Port Binding Definition -->
    <!-- ************************************************************* -->
    <wsdl:service name="Sample">
    <wsdl:port name="SampleHTTPPort" binding="invws:SampleHTTPSoapBinding">
    <soap:address location="http://localhost:7001/Sample/SampleHTTP" />
    </wsdl:port>
    <wsdl:port name="SampleJMSPort" binding="invws:SampleJMSSoapBinding">
    <soap:address location="jms://localhost:7001/Sample/SampleJMS?URI=inventoryWSQueue" />
    </wsdl:port>
    </wsdl:service>
    </wsdl:definitions>
    let me know whether this will help any where.
    Regards,
    Kal.

  • SOAP Async Sender Adapter - Many logons

    Hello,
    I have a SOAP asynchronis sender adapter that is being used to recieve invoices.  We are noticing that the suppliers who are invoicing us are calling the web service with all their invoices at the same time. (i.e. 2000 invoices in a matter of seconds).  It appears that each of these web service calls goes through logon process. 
    Is there a way to configure a SOAP sender adapter to reduce the number of logons required for this situation?
    Thanks,
    Matt

    Thanks VJ.
    You wrote: 
    Change your interface to accept multiple invoices in one call
    Are you suggesting that I should change the occurence setting on the Data Type for the Invoice Document from "1" to "1..Unbounded"?  Or is there another method?
    What is the standard process in PI for setting up an asynchronis web service? 
    Thanks,
    Matt

  • Could someone help me to clearly distinguish between SOAP and HTTP adapter?

    In which scenarios we can go for HTTP adapter and when to go for SOAP adapter?

    Hi Lekshmi !!
    A SOAP message will be bundled inside the soap envelope.HTTP is not an adapter in adapter engine whereas soap is an adapter i.e, HTTP doesn't require a communication channel where as SOAP requires.You can send soap messages using some SOAP client.
    SOAP Adapter is used to xchange SOAP messages bw remote clients and webservices....
    check this link for more differences..
    SOAP and HTTP adapter
    When you need to Send Data to XI from a Webservice , your SOAP adapter is used.
    HTTP adapter is used when you want to post a HTTP request message from a web application to XI.
    How can i make use of SOAP Sender Adapter without using any tools like XML Spy etc....
    XML SPy is used as a TEST tool when you are sending SOAP information to XI. TO actually send data , you need to configure a webservice and construct a SOAP request message and post the data .
    we use SOAP adapter when we need to connect to remote system or use Webservices in these cases we use SOAP adapter.
    HTTP Adapter is used by extenal systems to connect to Intergartin server using native HTTP Interface.
    the http adapter is a service which is directly connected to integration engine. Adapter Framework (Java) isnt involved. It is much more performant than SOAP adapter.
    The SOAP adapter is written in Java and is responsible for the SOAP envelope around the real XML message. You can build/remove that envelope as well in the mapping and use instead http adapter. But standard for webservices is using SOAP adapter.
    Check this thread....
    Difference between SOAP and Http Sender
    HTTP Adatpter Vs Soap Adapter
    HTPP Adatpter Vs Soap Adapter ????
    Difference between SOAP and Http Sender
    Difference between SOAP and Http Sender
    Plain HTTP Adapter vs SOAP Adapter with regards to SSL
    Plain HTTP Adapter vs SOAP Adapter with regards to SSL
    Hope it clears your doubt !!!!
    Questions are welcome here!!
    <b>Also mark helpful answers by rewarding points </b>
    Thanks,
    Abhishek Agrahari

  • SOAP Error: Unknown Application

    Hi.
    I'm facing a problem while calling a webservice from XI. One the sender side, I have a file and the SOAP is on the receiver side. The web service is deployed on our local EP server and I'm trying to call it from the XI server of our client. We have taken care of all the network connectivity etc,. When I execute the scenario, it is giving an error saying:
    <i>Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault.</i>
    But I have no problem calling the same web service from our local XI box.
    Could anyone provide me the solution for this.
    Thanks in advance.
    Regards,
    Hari.

    Check the soap configuration. Might be calling the web service requires a proxy and an authentication. Generally when you are calling from the local machine, the proxy is automaticlaly detected unless and untill specified. But in most cases, for a SOAP adapter the proxy needs to be specified (unless the network accepts anonymonous connections as XI will be running on admin domain and not on the network user domain).
    If that is not the problem then the adapter is not able to resoolve the hostname that you would have provided in the URL. try giving the IP address.
    Award if helpful,
    Sarath

Maybe you are looking for

  • JDeveloper performance

    I recently downloaded JDeveloper Studio 10.1.3 and what I am finding is that it is really slow. This is on a Dell laptop, XP Pro SP2 with an Intel Core Duo processor and 1GB RAM that is only a couple of months old, it is a quick machine. I have Oracl

  • Client can not fill out my Form in Adobe Acrobat

    I created a form, I hve no issue opening it up and filling it out personally. My co worker can do the same. However, when sent to a client, they can not fill out some of the fields when opening the form in adobe. Why is this?

  • Does anyone know which was the first version of Acrobat to offer electronic signatures?  Thank you.

    Trying to roll out a project that includes electronic signature (only... does not include digital certificate) in an organization with many older versions of software floating around. (It is a controlled environment, where not that easy to just have

  • Is it possible ?Change data capture from VSAM , DB2 , SQL Server  to Oracle

    Dear Professionals , We plan to build a warehouse project.Source systems are * VSAM files in zOS * SQL Server * DB2 Warehouse database is Oracle . Every night the changes in the source systems will be applied to Oracle warehouse DB. But only the chan

  • Photo to use for Album

    The album image seems to be the first photo in the album. Is there a way to select a different picture? My albums are shared from iPhoto and are kept in order by title. I know I can use a title for the cover picture that will make it sort first, but