SOAP adapter in gray color?

Hi guys,
When I go to RWB > Component Monitoring > Adapter engine > Adapter monitoring. I see all the adapters and my SOAP adapter appears in gray!
In ID when I try to create a test channel it appears available.
Anybody knows why it appears in gray?
Thnaks in advance,
Ricardo.

Hi,
untill you send the first message through this adapter is stays grey
but it's ok
when you send a first message it changes it's colour
Regards,
michal

Similar Messages

  • SOAP Adapter Startup

    Hi All,
             I have observed one thing that when we restart J2ee engine, all file, jdbc and jms adapters auto start however SOAP adapter needs a manual start in RWB.
    Could someone put some light on this, and is there a way that the adapter auto starts like others.
    Regards,
    XIer

    Hi Xier,
    There very rare references avaialble about this problem. Even I wil say this not the exact problem as the adapters like SOAP , Mail required 1st message to process. Once you had message processing the Adapter status get activated to either green, red based on the successful processing of that message. Unless the 1st message is activated you will find the status with gray color. I don't think you will require to do it manually each time. Have you tried to process a message even if the SOAP adapter status is gray after restarting the J2EE Engine. Please confirm if you are getting same results for Mail adapter also.
    Let me know if still you have any doubts about it.
    Thanks
    Swarup

  • Sender SOAP Adapter - problem

    Hi,
    After reading through the forums I understood that SOAP adapter turns green only with the first message.
    I have set everything up and sending a test message with XML Spy:
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
         <SOAP-ENV:Body>
              <m:SIMPLE_OUT_MI xmlns:m="http://test.com/soapTest">
                   <TEXT>TEST</TEXT>
              </m:SIMPLE_OUT_MI>
         </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    XMLSpy returns me an empty message back:
    <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
         <SOAP:Header/>
         <SOAP:Body/>
    </SOAP:Envelope>
    I can not see the message in SXMB_MONI and the adapter stays gray.
    Where do I look for the problem ?

    Hi Vick,
    Try like this......in ID from your sender agreement in which you have your sender SOAP comm channel, from menu select Display WSDL and then copy the WSDL URL and give it to source applications to use it.............create a service user for them to access PI 7.1 server while sending the SOAP req msg.............
    your source applications may have to generate proxy from this WSDL URL in their application and then they can send a SOAP req msg to your PI 7.1 server............
    Regards,
    Rajeev Gupta

  • SOAP adapter installation and activation

    We have installed XI 3.0 SR1 and wish to enable the sender SOAP adapter to receive SOAP messages from a different (PeopleSoft) system.  The documentation we have found really seems to be lacking in the area on installing and activating the SOAP adapter.  We are fine with the configuration pieces, but first activating the SOAP adapter is our problem.
    1) Is the SOAP adapter part of the Central Adapter Engine or do we need to install the Plain J2SE Adapter Engine on our XI server to get the SOAP adapter?
    2) If the SOAP adapter is part of the Central Adapter Engine, how do I 'activate' it?
    When I view the Adapter Monitor (http://<XIserver>:<J2EEport>/AdapterFramework/monitor/monitor.jsp) I see a line item for the SOAP adapter but it is grayed out.  Also, when browsing J2EE with the Visual Admin Tool, I find the following adapters, but no SOAP...
    SAP XI Adapter: BC
    SAP XI Adapter: File
    SAP XI Adapter: JDBC
    SAP XI Adapter: JMS
    SAP XI Adapter: Mail
    SAP XI Adapter: Marketplace
    SAP XI Adapter: RFC
    SAP XI Adapter: XI
    Any advice would be appreciated.  We see our next option as either applying XI Support Packages which will hopefully correctly deploy the SOAP adapter in case this was an installation problem, or to install the Plain J2SE Adapter Engine.  Thank you!

    Hi Jeff,
    XI 3.0 the SOAP Call goes to the Java Port 50000 plus instance number * 100. And the URL is different.
    It goes to a servlet and the URL is:
    http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
    without a party name it is:
    http://host:port/XISOAPAdapter/MessageServlet?channel=:service:channel
    Monitoring is in the SXMB_MONI or the Runtime workbench, the adpater monitor does not give you details.
    Here is the link to the help docu:
    http://help.sap.com/saphelp_nw04/helpdata/en/69/a6fb3fea9df028e10000000a1550b0/frameset.htm
    It is not too bad and as I said it works fine both ways.
    Cheers
    Stefan

  • Soap adapter communication channel problem

    Hi...
      While doing Webservices to file scenario, in component monitoring, the soap adapter communication channel is showing as (in small traiangle inyellow color) channel started but inactive

    Hi leelaratnam,
    Please check that you have only 1 communication channel active and running.
    This happens when more than 1 CC is pointing or waiting for the same incoming data.
    Also perform a dummy activate (i.e. write somthing in description and activate) in your message mapping and communication channel objects in case you are using PI 7.0
    Thanks,
    Varun

  • PE_Adapter status with gray colored arrow in sxmb_moni

    Hi ,
    I have one interesting problem to discuss,
    We are working in the production system and all archiving and deletion jobs are scheduled on weekly basis.
    Scenario is IDOC-->SOAP and BPM is also used. When checking in sxmb_moni the status of message is checkered flag but on the outbound side the status is green with scheduled for outbound processing. and when i display the message PE_ADAPTER's status is not checkered it is a gray colored arrow.and deletion and archiving job have not deleted only these messages.Also when i click on PE in sxmb_moni it doent take me to the BPM process steps it just refers to Inbound Queue.
    What i have done so far
    1. There is no entry in SMQ1,SMQ2,SWPR,SWPC,SWWL,SM58 for these messages.
    2. In message monitoring also when i check with the message ID as filtration criteria it is showing successful for integration engine.
    How to complete this PE_Adapter step of pipeline.
    or is that the case like new message was created for same process in sxmb_moni and the current messages are just to display.?
    Thanks in Advance.

    Hi Krishna,
    I have done everything related to queue, deregistering,registering and activating but still no luck, there is nothing in the queue and these messages are two months back. b'coz there status was incomplete , they were not deleted and in sap side Idoc dint get acknowlegement for these messages.

  • XIServer error raised: 503 Service Unavailable with SOAP Adapter

    Hi,
    We are getting a very strange error from a process that is working fine in 2 other environments.
    We are sending a message into the SOAP receiver adapter and are getting the following error at the Call Adapter part of the process :
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <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="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
      <SAP:P1>503</SAP:P1>
      <SAP:P2>Service Unavailable</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>&lt;!DOCTYPE HTML PUBLIC &quot;-//W3C//DTD HTML 4.0 Transitional//EN&quot;&gt; &lt;html&gt; &lt;head&gt; &lt;title&gt;Error Report&lt;/title&gt; &lt;style&gt; td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;} A:link A:visited A:active &lt;/style&gt; &lt;/head&gt; &lt;body marginwidth=&quot;0&quot; marginheight=&quot;0&quot; leftmargin=&quot;0&quot; topmargin=&quot;0&quot; rightmargin=&quot;0&quot;&gt; &lt;table width=&quot;100%&quot; cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; border=&quot;0&quot; align=&quot;left&quot; height=&quot;75&quot;&gt; &lt;tr bgcolor=&quot;#FFFFFF&quot;&gt; &lt;td align=&quot;left&quot; colspan=&quot;2&quot; height=&quot;48&quot;&gt;&lt;font face=&quot;Arial, Verdana, Helvetica&quot; size=&quot;4&quot; color=&quot;#666666&quot;&gt;&lt;b&gt;&amp;nbsp;&amp;nbsp;503 &amp;nbsp Service Unavailable&lt;/b&gt;&lt;/font&gt;&lt;/td&gt; &lt;/tr&gt; &lt;tr bgcolor=&quot;#3F73A3&quot;&gt; &lt;td height=&quot;23&quot; width=&quot;84&quot;&gt;&lt;img width=1 height=1 border=0 alt=&quot;&quot;&gt;&lt;/td&gt; &lt;td height=&quot;23&quot;&gt;&lt;img width=1 height=1 border=0 alt=&quot;&quot;&gt;&lt;/td&gt; &lt;td align=&quot;right&quot; height=&quot;23&quot;&gt;&lt;font face=&quot;Arial, Verdana, Helvetica&quot; size=&quot;2&quot; color=&quot;#FFFFFF&quot;&gt;&lt;b&gt;SAP J2EE Engine/6.40&amp;nbsp;&lt;/b&gt;&lt;/font&gt;&lt;/td&gt; &lt;/tr&gt; &lt;tr bgcolor=&quot;#9DCDFD&quot;&gt; &lt;td height=&quot;4&quot; colspan=&quot;3&quot;&gt;&lt;img width=1 height=1 border=0 alt=&quot;&quot;&gt;&lt;/td&gt; &lt;/tr&gt; &lt;/table&gt; &lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt; &lt;p&gt;&lt;font face=&quot;Arial, Verdana, Helvetica&quot; size=&quot;3&quot; color=&quot;#000000&quot;&gt;&lt;b&gt;&amp;nbsp;&amp;nbsp;The requested application, AFW, is currently unavailable.&lt;/b&gt;&lt;/font&gt;&lt;/p&gt; &lt;p&gt;&lt;font face=&quot;Arial, Verdana, Helvetica&quot; size=&quot;2&quot; color=&quot;#000000&quot;&gt;&lt;table&gt;&lt;tr&gt;&lt;td valign=&quot;top&quot;&gt;&lt;b&gt;&amp;nbsp;Details:&lt;/b&gt;&lt;/td&gt;&lt;td valign=&quot;top&quot;&gt;&lt;PRE&gt;No details available&lt;/PRE&gt;&lt;/font&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;&lt;/font&gt;&lt;/p&gt; &lt;/body&gt; &lt;/html&gt;</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>HTTP response contains status code 503 with the description Service Unavailable XML element Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    We are on XI 3.0 SP13.
    Any suggestions ?
    Kind regards
    Colin.

    Hi Colin,
    Quick look into these-
    1) Are you able to test the WebService, because the error tells about unavailable...
    For more-
    /people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
       /people/siva.maranani/blog/2005/03/01/testing-xi-exposed-web-services
    2) Is your SOAP Receiver COnfiguration is correct
       ~ http://help.sap.com/saphelp_nw2004s/helpdata/en/29/5bd93f130f9215e10000000a155106/content.htm
    3) Check the  wsdl is correct and try look into the input message for the Webservice(SOAP Adapter)
    Have a look into this thread-
    503 service unavailable
    Hope this helps,
    Regards,
    Moorthy

  • I'm unable to print in lightroom 5.4 . Macbook retina  OS X Version 10.9.2. Print button is in gray color.

    I'm unable to print in lightroom 5.4 . Macbook retina  OS X Version 10.9.2. Print button is in gray color.

    Pages v5 does not play nice with current Avery label templates in Word format. Pages v5 does not natively perform mail merge without adapting a third-party AppleScript solution.
    Labelist 8 is in the OS X App Store for USD $20. It is comprehensive, label software. Download button on their site gives you a free, full functional, 30-day trial. Recommend you consider Labelist over any Pages v5 kludge. Your time has a value.

  • Not able to see Message Content while using SOAP Adapter

    Hi freinds
    I am working on following scenario
    Web Application ---> SOAP Adapter ---> XI ---> RFC Adapter ---> SAP R/3
    Web application is using the WSDL file which I generated from XI.
    Now everything is going fine & I am even getting the XML data in SAP R/3 ( Order is getting created ) but in RWB under message monitoring I am getting " <b>Content of message deleted to save memory</b> " for message content.
    Even in SXMB_MONI for that timeframe it is showing " <b>No messages available for selection</b> ".
    Can you tell me why I am not getting the message content & the message itelf in SXMB_MONI. What I need to do in order to get the message content while monitoring.
    Best Regards
    Lalit
    P.S --> I am able to see the message content if I am using File Adapter in place of SOAP Adapter

    Hi
    After adding the LOGGING_SYNC parameter with value 1. I am able to see the messages in sxmb_moni but they have status as " System Error - Restart not possbile " with the following error ::
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <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="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
      <SAP:P1>402</SAP:P1>
      <SAP:P2>ICM_HTTP_TIMEOUT</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText><html><head><title>SAP Web Application Server Error</title> <style type="text/css"> body { font-family: arial, sans-serif;} </style> </head> <BODY text="#172972" link="#808080" vlink="#808080" alink="#8e236b" bgcolor=white leftmargin="0" topmargin="0" marginheight="0" marginwidth="0"> <table height="61" width="100%" border="0" cellspacing="0" cellpadding="0"><tr><td background="http://sapxidev:50000/sap/public/icman/img/bluebar_tile.gif" height="30"><table> <tr> <td width=5></td> <td width=20% nowrap><font face=arial size="-1" color=white>SAP Web Application Server </font></td><td width=75% align="right" nowrap><font face=arial size="-1" color="white"><a href="http://help.sap.com/">Help </font></td><td width=5% nowrap></font></td> </tr></table> </td><td rowspan=2 width=122 height=61 valign=top><img src= "http://sapxidev:50000/sap/public/icman/img/theme.jpg" width=122 height=61 border=0 alt="SAP"></td> </tr><tr><td background="http://sapxidev:50000/sap/public/icman/img/graybar_tile.jpg" height="31">  </td></tr> </table> <br><br> <table width=800> <tr><td width=50 nowrap> </td><td> <H2>500 Connection timed out</H2><br>Connection timed out (-5) <br><hr> <table border="0"> <tr><td>Error:</td><td>-5</td></tr> <tr><td>Version:</td><td>6040</td></tr> <tr><td>Component:</td><td>ICM</td></tr> <tr><td>Date/Time:</td><td>Wed Dec 21 13:59:55 2005 </td></tr> <tr><td>Module:</td><td>icxxthr_mt.c</td></tr> <tr><td>Line:</td><td>2559</td></tr> <tr><td>Server:</td><td>sapxidev_XID_00</td></tr> <tr><td>Detail:</td><td>Connection to partner timed out</td></tr> </table> <p></p> </td></tr></table> <table><tr><td width=50 nowrap></td> <td nowrap><FONT SIZE=-1><a href="http://www.sap.com/">&copy; 2001-2003, SAP AG</a></FONT></td></tr></table></SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error when receiving by HTTP (error code: 402, error text: ICM_HTTP_TIMEOUT)</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    As my payload was of 100 records with 15 fields I guessed that this can be the reason I am getting timed out. So next time I just send 2 records & this time no error & everything went fine.
    Now one thing I need to do is to increase the TIMEOUT value with the help of <b>OSS Note 824554</b>.
    But still in RWB ( with 2 records also ) under message monitoring I am getting " <b>Content of message deleted to save memory</b> " for message content.
    My objective now, is to display the payload which is coming from Web Application via SOAP Adapter in RWB. Can you help me in this.
    Best regards
    Lalit Chaudhary

  • Mapping related errors in SOAP Adapter scenario

    Hello Friends
    I have done this several times and in this particular case I am getting some errors.
    Here is the scenario
    External  --- (SOAP) ---  XI  -
    (RFC) -
    SAP TABLE.
    Program
    I have created an XSD (External definition) to get the data to XI using SOAP Adapter.
    I have done the mapping and everything looks Ok to me. I even restarted my XI server. All other scenarios are working except for this particular scenario in question.
    When I looked at <SXMB_MONI> I see the xml string coming in correctly with proper tags and data as expected.
    However, it is failing with some mapping errors.
    Here is the error message I got in SXMB_MONI
    Any help will be greatly appreciated.
      <Trace level="1" type="T">Interface Mapping http://cincom.com/config AddConfigDNA</Trace>
      <Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_AddConfigDNARequest_</Trace>
      <Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:403) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) 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:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy177.processFunction(Unknown Source) 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:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7701) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2376) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1700) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8061) at com.sap.mw.jco.JCO$Server.work(JCO.java:8181) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8128) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) 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) Root Cause: com.sap.aii.mappingtool.tf3.IllegalInstanceException: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:283) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:398) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) 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:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy177.processFunction(Unknown Source) 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:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7701) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2376) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1700) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8061) at com.sap.mw.jco.JCO$Server.work(JCO.java:8181) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8128) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) 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)</Trace>
      <Trace level="1" type="T">Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_AddConfigDNARequest_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd</Trace>
      <Trace level="1" type="T">com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_AddConfigDNARequest_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:73) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) 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:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy177.processFunction(Unknown Source) 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:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7701) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2376) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1700) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8061) at com.sap.mw.jco.JCO$Server.work(JCO.java:8181) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8128) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) 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) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:403) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) 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:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy177.processFunction(Unknown Source) 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:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7701) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2376) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1700) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8061) at com.sap.mw.jco.JCO$Server.work(JCO.java:8181) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8128) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) 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) Root Cause: com.sap.aii.mappingtool.tf3.IllegalInstanceException: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:283) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:398) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) 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:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy177.processFunction(Unknown Source) 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:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7701) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2376) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1700) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8061) at com.sap.mw.jco.JCO$Server.work(JCO.java:8181) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8128) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) 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)</Trace>
      <Trace level="1" type="E">CL_XMS_PLSRV_MAPPING~ENTER_PLSRV</Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      </SAP:Trace>
      </SOAP:Header>
    - <SOAP:Body>
    - <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
    - <SAP:Payload xlink:href="cid:[email protected]">
      <SAP:Name>MainDocument</SAP:Name>
      <SAP:Description>Main XML document</SAP:Description>
      <SAP:Type>Application</SAP:Type>
      </SAP:Payload>
      </SAP:Manifest>
      </SOAP:Body>
      </SOAP:Envelope>

    Hi Ram,
    This error is due to error in message mapping.The map rules you have specified for the Node: "ZBAPI_ADD_CONFIG_DNA" is not getting satisfies due to which it is unable to create the Node who occurance is mandatory.Check if map rule specified for this particular Node.
    Thanks,
    Bhargav.
    Note:Award Points if found useful

  • Why is my internet search page gray?  I am able to search a topic, but the 'results' part of the screen is a medium gray color and it won't respond.  Any ideas?

    Why is my internet search page gray?  I am able to search a topic, but the 'results' part of the screen is a medium gray color and it won't respond.  Any ideas?

    Try clearing Safari's cache : Settings > Safari > Clear Cache (and Clear History)
    If that doesn't work then try closing Safari completely and then re-open it : from the home screen (i.e. not with Safari 'open' on-screen) double-click the home button to bring up the taskbar, then press and hold any of the apps on the taskbar for a couple of seconds or so until they start shaking, then press the '-' in the top left of the Safari app to close it, and touch any part of the screen above the taskbar so as to stop the shaking and close the taskbar.
    A third option is a reset : press and hold both the sleep and home buttons for about 10 to 15 seconds (ignore the red slider), after which the Apple logo should appear - you won't lose any content, it's the iPad equivalent of a reboot.

  • Error in using XI-SOAP adapter, but no error  with SAP-BC

    Hi,
    I am working on RFC->XI->Webmethod (.asp) scenatio.
    I am using SOAP adapter.
    Whin I am not using "Do not use SOAP Envelop".
    I am getting "com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML" Error in SXMB_MONI.
    But when I am using "Do not use SOAP Envelop" then I am not getting any error. in SXMB_MONI status showing Successfully Processed. But the responce i am getting is "You are not authorized to view this page  // HTTP 401.1 - Unauthorized: Logon Failed"
    But same web-service is working fine while connected with SAP-BC.
    Please Help why scenario is working with BC, but not with XI.
    Thanks & Regards

    Hi Bhavesh,
    Thanks for reply.
    I am getting all success in message monitoring, but still web-services sying they are not getting any message.
    I am attaching all 4 logs for one synchronous communication of message monitoring.
    I am not able to understand where message going and why XI showing success every where.
    ********1st(Sent Messages)
    Success SOAP: response message leaving the adapter
    Success Application attempting to send an XI message asynchronously using connection AFW.
    Success Trying to put the message into the send queue.
    Success The response message for message cf4fd921-4a74-11db-9312-001279933263(INBOUND) was successfully transmitted to the calling application.
    Success The message status set to DLVD.
    Success The application sent the message asynchronously using connection AFW. Returning to application.
    ********2nd (Sent Messages)
    Success RFC adapter received sRFC for Z_PA_SAP_TO_Webservice from D02/230. Attempting to send message synchronously
    Success Application attempting to send an XI message synchronously using connection AFW.
    Success Trying to put the message into the call queue.
    Success Message successfully put into the queue.
    Success The message was successfully retrieved from the call queue.
    Success The message status set to DLNG.
    Success The message was successfully transmitted to endpoint http://XYZ.com:8000/sap/xi/engine?type=entry using connection AFW.
    Success The application sent the message synchronously using connection AFW. Returning to application.
    Success The message status set to DLVD
    **********3rd (Received Messages)
    Success Using connection AFW. Trying to put the message into the receive queue.
    Success The XI response message for message d0372be1-4a74-11db-91d7-001279933263(INBOUND) was successfully returned to the calling application.
    Success The message status set to DLVD.
    **********4th (Received Messages)
    Success The message was successfully received by the messaging system. Profile: XI URL: http://XYZ.com:50000/MessagingSystem/receive/AFW/XI
    Success Using connection AFW. Trying to put the message into the request queue.
    Success Message successfully put into the queue.
    Success The message was successfully retrieved from the request queue.
    Success The message status set to DLNG.
    Success Delivering to channel: IF_O_502_WebserviceBusService_SOAP_In_02
    Success SOAP: request message entering the adapter
    Success SOAP: completed the processing
    Success SOAP: response message received d0372be1-4a74-11db-91d7-001279933263
    Success The message status set to DLVD.
    Success The message was successfully delivered to the application using connection AFW.

  • Error while invoking the ABAP Proxy via SOAP Adapter

    Hi,
    My scenario involves SOAP Client invoking a webservice hosted in PI which in turn invokes the ABAP Proxy asyncronously.
    SOAP Client -> PI -> ECC (ABAP Proxy) . This works fine.
    Next , I have exposed the ECC Service Interface as webservice using SOA Manager transaction. Now, once the service is created using SOAManager, i replaced the XI Adapter with SOAP Adapter and provided the target URL as the URL provided by the SOAManager.
    SOAP Client -> PI -> ECC (ABAP Proxy via SOAP Adapter)
    With this approach, i am encountering the below error message
    2009-05-29 12:17:55 Error Adapter Framework caught exception: null
    2009-05-29 12:17:55 Error 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.
    Any ideas on the above errror message? Any pointers or inputs will be appreciated.
    Thanks,
    Vinayak Kamath

    > 2009-05-29 12:17:55 Error Adapter Framework caught exception: null
    > 2009-05-29 12:17:55 Error 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.
    This is a generic error message which does not have any information about the error which has occurred.
    Do you see any error messages in the SOAP client?
    Regards
    Stefan

  • Error while Testing SOAP Adapter In XI

    <b>Hi Frndz
    I am trying to test my SOAP adapter which i have exposed as a webservice. I testing this from the WSNavigator which throws the following error:</b>
    HTTP/1.1 500 Internal Server Error
    Connection: close
    Set-Cookie: <value is hidden>
    Set-Cookie: <value is hidden>
    Server: SAP J2EE Engine/6.40
    Content-Type: text/xml; charset=utf-8
    Date: Thu, 15 Dec 2005 12:24:19 GMT
    <?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>DeliveryException</code>
              <text><![CDATA[
    com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 404 : Not Found
         at com.sap.aii.af.ra.ms.impl.core.queue.CallConsumer.onMessage(CallConsumer.java:144)
         at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:512)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:74)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:141)
              ]]></text>
            </s:SystemError>
          </detail>
        </SOAP:Fault>
      </SOAP:Body>
    </SOAP:Envelope>
    <b>I have used this url for the Webservice:</b>
    <u>http://<host>:<port>/XISOAPAdapter/MessageServlet?channel=:CVXSABSR_TEST_SENDER:CVXSACC_TEST_SENDER</u>
    <b>I am unable to figure out where the problem is.
    Any ideas to solve this?
    Thanks in Advance
    DhanyaR Nair</b>

    <b>Hi Andrews and Ravi
    Thanks for the quick response.
    <u>Andrews</u> the Message Servlet is in OK status, as it reponded from checking the url given by you.
    What should i try next?
    <u>Ravi</u> i checked the url for checking the Comm Channel. There are two IDs associated with the Channel
    1>Object ID
    2> ObjectVersion ID
    with the ObjectVersionID , we are getting the following error and with ObjectID we got the proper response  </b>
    <b>with ObjectVersion ID</b>
    <u>http://<host>:<port>//XISOAPAdapter/HelperServlet?action=GetChannelInfo&channelID=<Object version ID></u>
    <b>response:</b>
    <?xml version="1.0" ?>
    - <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <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.SOAP_EXCEPTION</code>
    - <text>
    - <![CDATA[
    com.sap.aii.af.service.cpa.impl.exception.CPALookupException: Channel object with Id Channel:a9f7f390671e11daa2300012799e22c2 not available in CPA Cache.
         at com.sap.aii.af.service.cpa.LookupManager.getCPAObject(LookupManager.java:202)
         at com.sap.aii.af.mp.soap.web.HelperServlet.processGetChannelInfo(HelperServlet.java:455)
         at com.sap.aii.af.mp.soap.web.HelperServlet.doGet(HelperServlet.java:131)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java: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:95)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
                ]]>
      </text>
      </s:SystemError>
      </detail>
      </SOAP:Fault>
    <b>with the object id</b>
    <u>http://<host>:<port>/XISOAPAdapter/HelperServlet?action=GetChannelInfo&channelID=<Object  ID></u>
    <b>Response</b>
    <?xml version="1.0" ?>
    - <s:ChannelInfo xmlns:s="http://sap.com/xi/WebService/xi30">
      <channelID>ea30ed2ccc243fe49b7c2c5646ed3b2d</channelID>
      <name>CVXSACC_TEST_SENDER</name>
      <type xmlns:st="http://sap.com/xi/XI/System">st:SOAP</type>
      <direction>INBOUND</direction>
      <party />
      <service>CVXSABSR_TEST_SENDER</service>
      </s:ChannelInfo>
    <b>with the url</b>
    <u>http://<host>:<port>/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:CVXSABSR_TEST_SENDER:CVXSACC_TEST_SENDER</u>
    <b>Response</b>
    <?xml version="1.0" ?>
    - <s:ChannelInfo xmlns:s="http://sap.com/xi/WebService/xi30">
      <channelID>ea30ed2ccc243fe49b7c2c5646ed3b2d</channelID>
      <name>CVXSACC_TEST_SENDER</name>
      <type xmlns:st="http://sap.com/xi/XI/System">st:SOAP</type>
      <direction>INBOUND</direction>
      <party />
      <service>CVXSABSR_TEST_SENDER</service>
      </s:ChannelInfo>
    <b>How should i proceed ? Any idea frndz
    Thanks in Advance
    DhanyaR Nair</b>

  • Error in while calling a Soap Adapter using the UDF

    hi,
    i am trying to make a call to Soap Adapter using a UDF.
    The code of the UDF is as follows :
    InputStream isPayloadStream = null;
    AbstractTrace trace= container.getTrace();
    String sService="Business Component";
    String sChannelName="Soap Channel(Sender)";
    SystemAccessor accessor=null;
    trace.addInfo("entered UDF");
    StringBuffer sb = new StringBuffer(" ");
    trace.addInfo("creating the reference file");
    sb.append("<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n");
    sb.append("<ns0:MT_123082_UDF xmlns:ns0=\"http//infosys.com/pi/projects/png/n1\">\n");
    sb.append("<INTERCHANGECONTRLNOS>" + var1 + "</INTERCHANGECONTRLNOS>");
    sb.append("<PGPARTNERID>"var2"</PGPARTNERID>""\n""</ns0:MT_123082_UDF>");
    trace.addInfo("trigerring the SOAP channel ");
    try{
    Channel channel = LookupService.getChannel(sService,sChannelName);
    accessor = LookupService.getSystemAccessor(channel);
    isPayloadStream = new ByteArrayInputStream((sb.toString()).getBytes());
    trace.addInfo("creating the xml payload ");
    XmlPayload payload = LookupService.getXmlPayload(isPayloadStream);
    Payload result=accessor.call(payload);
    catch (Exception e){
    trace.addInfo(e.getMessage());
    finally{
    if ( accessor !=null) {
    accessor.close();
    return " ";
    The above code is throwing an error while end to end testing.
    the scenario is such,while graphical mapping a UDF will be used, which will create an Xml payload, and send this payload to another SOAP to file scenario.
    The error in the sxmb_moni is:  "Error when calling an adapter by using the communication channel CC_123085_UDF_SOAP_OUT (Party: , Service: BC_123082_REMADV_D96A, Object ID: fa9c6ee15efc30c68ec34b08034d87d1) XI AF API call failed. Module exception: 'failed to set up the channel fa9c6ee15efc30c68ec34b08034d87d1'. Cause Exception: 'Channel stopped by administrative task.'."
    Please can anyone suggest how this error can be rectified.
    regards,
    Meenakshi

    Hi,
    i have checked the communication channel and the XML. The following error occurs everytime i try to run the scenario.
    Error:
    Error when calling an adapter by using the communication channel CC_123082_UDFRECEIVER_SOAP_IN (Party: , Service: BC_123082_REMADV_D96A, Object ID: 2a895589066d30d4b2686e9d3a8d4c8d) XI AF API call failed. Module exception: 'SOAP Error'. Cause Exception: 'SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 400 Bad Request'
    Please let me know how this error can be resolved.
    Regards,
    Meenakshi

Maybe you are looking for

  • Glitch getting Mail to access my .Mac account

    Yesterday after I had had my powerbook on for a while, after Mail had opened on startup and automatically checked for and retrieved mail for my .mac account and a second separate account, Mail suddenly began asking me to log on. This was maybe about

  • How to resolve hang issue in  Iphone 4s with IOS 7

    how to resolve hang issue in  Iphone 4s with IOS 7

  • Generating DME format by executing F110

    Hi As per the bank requested, we have an developed and Data Medium Engine format using DMEE. After executing the payment run, I had downloaded the output of the file using Environment --> Payment Medium  --> DME Administration When i go into Environm

  • Logging WLDF

    Hi all, This had probably been answered so apologies. Can't seem to find out how I can grab a simple log of JDBC Connection Pool info, Session info, and THread Usage while we are stressing our system our system, without having to look at the admin co

  • Error-page encoding problem

    Hi all! I use AppServerPE9.0 and i need to custom error page web.xml:     <error-page>         <exception-type>java.lang.Throwable</exception-type>         <location>/error.jsp</location>     </error-page>     <error-page>         <error-code>403</er