SOAP Adapter option is disabled in adapter monitoring

Hi
I am trying a simple SOAP to FTP scenario. I have done all the steps in the repository as well as the directory and i have even activated it, but in adapter monitoring the SOAP adapter option is disabled.
Hope someone could help me out on this.
Thanks & Regards
Rahul

Hi Rahul,
We have also faced this type of problem. But at that time we were calling XI from a ASP.Net page.Just a few suggestions which you can try out :
1) Using XMLSPY and your wsdl file, try sending a SOAP request to the XI. If you got the response then there is no problem with your scenario.
2) If you didn't get the response or any erro comes then try recreating a new scenario nad repeat 1) (we have to do this after that only we got success )
3) Check your webdynpro code which call the XI server. Have a look at this weblog :
/people/sap.user72/blog/2005/09/15/connecting-to-xi-server-from-web-dynpro
Hope this will be helpful.
Regards
Suraj

Similar Messages

  • Messages failing in the SOAP adapter with the errror

    HI 
    I am getting the below error in the SOAP adapter monitoring . can any body tell what does "No route to host: Connect" mean .
    could some one help us on resolving this .
    Error Exception caught by adapter framework: No route to host: connect
    Error 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: No route to host: connect: java.net.NoRouteToHostException: No route to host: connect. Setting message to status failed.
    Error The message status set to FAIL.
    Error Returning synchronous error message to calling application: com.sap.aii.af.ra.ms.api.RecoverableException: No route to host: connect: java.net.NoRouteToHostException: No route to host: connect.
    thanks and regards
    sandeep

    Hi!
    First please confirm whether you are working on XI or PI 7.1 ?
    because in XI you need to generate WSDL manaually via Tools>Define Web service-Giving Input..and in XI you need to test the SOAP scenario from external tool like Altova xml spy tool kit or else SOAP client tool.
    In PI 7.1::
    You can publish directly the web service in the SERVICE REGISTRY from sender agreement onwards.
    once it is published you can check the status on your interface in service registry as CONFIGURED..Okay
    Here you can test directly in service registry...
    According to your error check ocne agan even though you gone through all the steps..
    1. Check whether the SOAP service is active or not in SICF>SAP>bc>XI>Service-->SOAP.
    2. sicne after generating wSDL u can get one url right that URL itself acts as  a gateway to enter the source data into XI..
    lets give to the source team to try with XI super uID adn PWD as authentification.
    3. Also please STOP ur communication Channel and start once again.
    4. Please check whether the WEB Service is configured correctly or not.
    Regards::
    Amar Srinivas Eli

  • XI / PI SOAP Adapter - MessageServlet not found / not responding

    I am in trouble with XI SOAP Adapter. When I try to reach the <b>MessageServlet</b> ( http://host:port/XISOAPAdapter/MessageServlet ) I get the response that document dont exists. Why MessageServlet do not respond? Anyone can help me?
      In my Adapter Monitor ( http://host:port/mdt/amtServlet ) I see about the SOAP adapter a grey status and the information: "SOAP Adapter Monitoring is now part of Channel Monitoring". This is not a problem, according to Suraj: "SOAP Adapter will become active only when you sent a message through that for atleast one time.")
      See also these topics:
      SOAP adapter installation and activation
      Adapter monitoring: SOAP is grey although it is used?
    how can i enable SOAP Adapter?
    https://websmp208.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=012003146900000286382005 (<b>SAP Note 856597</b>)
    <i>  I have readed these topics (and others), but my problem seems to be a little different.
    </i>
      My XI runtime cache contents (SXI_CACHE) are up-to-date.
      <b>Information of some of my XI components:</b>
    Software Components 
    Vendor  Name  Version  Location  Applied 
    sap.com  SAP-JEE  6.40 SP17 (1000.6.40.17.0.20060516064307)  SAP AG  20060612185606 
    sap.com  SAP-JEECOR  6.40 SP17 (1000.6.40.17.0.20060516064111)  SAP AG  20060612185559 
    sap.com  NWMADMIN  6.40 SP17 (1000.6.40.17.0.20060515153837)  MAIN_APPL63VA_C  20060612185601 
    sap.com  SAP_XITOOL  3.0 SP17 (1000.3.0.17.0.20060504222004)  SAP AG  20060613105756 
    sap.com  SAP_XIPCK  3.0 SP16 (1000.3.0.16.0.20060220233019)  SAP AG  20060612185556 
    sap.com  LM-TOOLS  6.40 SP17 (1000.6.40.17.0.20060417111655)  MAIN_APPL63VA_C  20060612185603 
    sap.com  SAP-XICONS  3.0 SP16 (1000.3.0.16.0.20060220232901)  SAP AG  20060612185600 
    sap.com  SAP-XIAFC  3.0 SP12 (1000.3.0.12.5.20050712085155)  SAP AG  20060612185555 
    sap.com  SAP_XIAF  3.0 SP17 (1000.3.0.17.0.20060522230043)  SAP AG  20060613103623 
    sap.com  SAP_JTECHF  6.40 SP17 (1000.6.40.17.0.20060516064445)  SAP AG  20060612185559 
    sap.com  SAP_JTECHS  6.40 SP17 (1000.6.40.17.0.20060516064629)  SAP AG  20060612185606 
    <b>sap.com  com.sap.aii.af.mp  3.0 (3.0.1720060522104934.0000)  SAP AG  20060613102037  sap.com/SAP-XIAFC  </b>
    sap.com  com.sap.aii.af.soapadapter  3.0 (3.0.1720060522104934.0000)  SAP AG  20060613103506  sap.com/SAP_XIAF 
      Thanks a lot! If you need other information, please, let me know.
      <b><i>Ivan, from Brazil</i></b>

    <i>"https://websmp208.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=012003146900000286382005 (<b>SAP Note 856597</b>)
    I have readed these topics (and others), but my problem seems to be a little different."</i>

  • Using receiver SOAP Adapter

    Hi,
    I have the following Scenario:
    I want to send an AuthenticateUSer method request to a WebService using SOAP receiver adapter synchronusly, and receive the Response.
    I've found the following error in monitoring:
    <i> <?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>XIAdapter</SAP:Category>
      <SAP:Code area="PARSING">ADAPTER.SOAP_EXCEPTION</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>soap fault: Server was unable to process request. --> Object reference not set to an instance of an object.</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error></i>
    Any ideas?
    How do I say to the SOAP adapter wich method I want to Invoke?
    Thanks and Regards.

    Hi Moorthy,
    I've test the WebService with WebService Studio 2.0 and it is working.
    I've test the SOAP Adapter with
    http://<host>:<port>//XISOAPAdapter/HelperServlet?action=GetChannelInfo&channelID=<Object%20version%20ID>
    and others and found the following log:
    <i><?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:<Object version ID> not available in CPA Cache.
         at com.sap.aii.af.service.cpa.impl.lookup.AbstractLookupManager.getCPAObject(AbstractLookupManager.java:172)
         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:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
      ]]>
      </text>
      </s:SystemError>
      </detail>
      </SOAP:Fault></i>
    In RWB, the SOAP Adapter Monitoring looks green, and in http://<host>:<port>//XISOAPAdapter/MessageServlet
    <i>Message Servlet is in Status OK
    Status information:
    Servlet com.sap.aii.af.mp.soap.web.MessageServlet (Version $Id: //tc/aii/30_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#11 $) 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
    ModuleProcessorRemote not instantiated</i>
    Is the Adapter working properly?
    Thanks and Regards.

  • Adapter monitoring: SOAP is grey although it is used?

    Hello everybody,
    5 minutes ago I checked our SOAP receiver communication channel and send a message. But in adapter monitoring the SOAP adapter is shown in grey instead expected in green.
    So how can I see, if the SOAP adapter works correctly?
    Thanks a lot, regards Mario

    Hi Mario,
    SOAP channel will show either Green or Red only when atleast one message has been processed thru the SOAP channel,
    First, for this message, check the SXMB_MONI status? Is it showing Black Flag ??
    Else try to activate the adapter once again, just refresh the cache and the send the message once again..
    Also have a look into this thread-
    how can i enable SOAP Adapter?
    Regards,
    Moorthy

  • Commuication Channel monitoring for SOAP Adapter

    Hi friends,
    When i see Sender soap adapter status in Communication channel monitoring.I am getting the status as:
    Channel started but Inactive
    What does that indicate?
    Kindly update what i need to do..

    Check these links :
    SOAP adapter - Channel started but inactive (case inside)
    SOAP Adapter status stay "Channel started but inactive"
    it ll be solved by given solutions in these thread like send messages,cache refresh..

  • SOAP adapter - Module options...

    Hi,
    with a SOAP receiver, in tab "Module" we have "Module configuration". For instance, we can specify:
    Module Key        = soap
    Parameter name = XMBWS.Timeout     (found in oss note 856597)
    Parameter value  = 10000
    Where can I find all the others available parameters ?
    Thanks
    Mickael
    P.S: maybe with: http://help.sap.com/saphelp_nw2004s/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm
    Message was edited by:
            Mickael Huchet

    Huchet,
    In the receiver SOAP adapter, if you want to add your own modules to process the request message, you add them before the module specified below; if you want to add your own modules to process the response message, you add them after the following module:
    sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
    Also you can see a list of parameters in this link:
    http://help.sap.com/saphelp_nw04/helpdata/en/bf/27fd3b651f6a1ce10000000a11402f/content.htm
    Go through this help for some info:
    http://help.sap.com/saphelp_nw04/helpdata/en/a4/31d940f52f7e7fe10000000a1550b0/content.htm
    ---Satish

  • SOAP adapter in PI 7.1

    Hello, expert,
    I have made SOAP adpeter work in PI 7.0, however after upgrading to PI 7.1, I have issue with a test scenario as following.
    I've defined DT, MT and SI (Service Interface) in ESR (no mapping needed)
    In ID, I configured a scenario SOAP --> PI  --> File.
    I tested the scenario in RWB using the test tool for adapter engine using URL:
    http://host:port/XISOAPAdapter/MessageServlet?channel=:BC_comp:CC_Notification_SOAP_Sender
    the message is attached in the end of this post.
    The message was successfully send to PI and saved to file, however the message going into IE pipeline and finally saved to the file is not the one I sent.
    Message sent to SOAP adapter:
    <?xml version="1.0" encoding="UTF-8"?>   
    <ns0:MT_Notification xmlns:ns0="http://mynamespace/xi">
       <Notification>
          <Number>12345</Number>
          <Type>abc</Type>
          <Status/>
          <OrderNo/>
          <FunctionalLocation>qaz</FunctionalLocation>
          <StartDate/>
          <EndDate/>
       </Notification>
    </ns0:MT_Notification>
    Message going into IE pipeline and further saved to file:
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    <!--  Inbound Message   -->
    <sap:Manifest xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:sap="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink">
    <sap:Payload xlink:type="simple" xlink:href="cid:payload-29092409f6d11ddc4d982a0c41f100csap.com">
      <sap:Name>PayloadName</sap:Name>
      <sap:Description>PayloadDescription</sap:Description>
      <sap:Type>Application</sap:Type>
      </sap:Payload>
      </sap:Manifest>
    Also in sxmb_moni, there is a acknowledgement which do not expect.
    Does anybody have an idea how this happens?
    Thank you
    Jayson

    Hi!
    I want to answer this thread as 2 parts:
    1. First check all of your configuration whether you have done...correctly or not later please activate all of your objects...
    then try your Scenario once..if not do one thing..
    2:
    I my sugestion is Why don't you try yourr scenario by using either SOAP CLient Tool or else ALTOVA XML SPY TOOL...
    Here I am provding the Steps to be followed to use ALTOVA XML SPY Tool
    please make sure even though you have done correctly..
    Steps for Testing via ALTOVA>>
    1. Go to ID-> TOOLS-> Define Web Service
    2. Give following URL in following window
    For without Party:
    note: http://<HOST name:5<Port>00/XISOAPAdapter/MessageServlet?channel=:<Channel Name>:<Adapter Name>
    3. Give Message Interface Name of Scenario
    4. Give following details in following screens  Service Name, Message Interface Name,   Namespace
    5. Finish & Save the WSDL in local folder to give to web-services
    (Generated WSDLu2019s attached in Technical Design Document)
    NOTE: AFter generating you can observe the above SOAP URL with your objects name...
    6.Once the WSDL file is created. Use a SOAP client tool or else aither ALTOVA XML SPY Tool  to create the SOAP request.
    You can create SOAP Request from WSDL using the following tool
    Once you have created the SOAP request, use the same as the payload and test the scenario.
    7. Select the option in the SEND SOAP REQuest in the MENU present in the top list of ALTOVA XML SPy Tool and give inputs i.e., SOAP URL and also give server details and it will ask authentification details
    8. Now by giving Authentification details you can send successfully....
    9. Now Got SXMB_MONI and now check your scenario is success or not..
    10. IF not go to MEssage monitoring in RWB and check at both the INtegration Server Level and ADAter engine level and then Check the AUDIT LOG
    11. ALso you can check Audit log in COmmunication channel monitoring
    12. If your SOAP Channel is in Red check Errors and then stop that channel manually and start once again and try the scenario once again...
    http://help.sap.com/saphelp_erp2004/helpdata/en/ae/d03341771b4c0de10000000a1550b0/frameset.htm
    I hope it will be useful to you in final case...Suppose if it is useful to you please close this and award points to the repective contributors if it is useful to you..
    Regards:
    Amar Srinivas ELi

  • PI 7.0: Message prioritisation in adapter engine for SOAP adapter.

    Hi All,
    We have both high and low priority synchronous messages using the SOAP sender Channel of the Central AE.
    How can we make sure that High Prio messages ALWAYS get a thread right away when entering the AE? Installing a separate AE is not an option.
    When I look in RWB->Component Monitoring->Adapter Engine->Engine Status in the Queues tab, I see this:
    SOAP_http://sap.com/xi/XI/SystemCall Yes 5(5) 5
    SOAP_http://sap.com/xi/XI/SystemRqst Yes 5(5) 5
    When a new High Prio message enters, it can take more than one hour before it gets processed, because there are 1000 Low Prio messages also using the same 5 available Threads...
    This delay is of course unacceptable for High Prio messages.
    I checked in many other threads in SDN, looks like we cannot priortise for particular messages in PI 7.0, as we can do only at adapter level, not at interface level.
    I was thinking of going to the approach which was suggested by "Gr, Wout" in the below thread. 
    xi prioritization in adapter engine (ae, af, adapter framework, java, jca)
    Creating own adapter "MYSOAP" by copying the metadata of SOAP adapter. By that we can use our own adapter "MYSOAP" for high priority interfaces.
    what you think guys about this approach?
    Is there any thing I need to take care going through this approach apart from copying SOAP metadata into my own adapter.?
    Thanks
    Deepthi

    increased thread count for soap adapter

  • Mail Adapter to Soap Adapter keeping the attachments - How?

    Hi guys,
    I am working on a scenario where I should pull emails from an Exchange server and I should forward them (with their attachments) to a separate systems via a Web Service.
    So far I have been able to pull the emails using the Mail Adapter and I get to see them in the monitoring tool of PI with their attachment(s).  But what I am not sure of is how I should forward these emails to the external system using a web service.
    This system should expose this web service that should use something similar to SOAP with attachments (I guess) and then PI should forward these attachments using the receiver SOAP adapter with the "keep attachments" option selected.
    Is this something that could work as simply as this (by configuring these two adapters to keep their attachments) OR will I need to do some more fancy stuff?
    Thanks for any advice you can give me on this.
    Aldo

    Hi Stefan,
    thanks for your replay.
    Yes, I understand that the mail should be in an XML message.  And with that part we are doing OK.  We have managed to send the XML between the systems.
    However, what I don't understand is how to pass the attachments.
    How should the receiving system receive them?  if they are not in the XML message itself how are these going to be passed over?
    Will the SOAP envelop have some kind of link or reference to the attachments?
    The receiving system is a SAP CE system and it's based on Java.  Can they expose a service that will somehow handle these attachments?
    Could you explain this part to us?  this is where we get confused.
    Thanks for your help in advance,
    Aldo

  • Importance of Message ID in soap adapter

    Hi
    what is the importnace of message id in soap adapter ?? Are there any situations where we send it through query string or message payload ?? I know.......by default IE creates Message ID for any messages that passes through it. But still are there any chances of my said situation ??
    Similarly what is the importance of GUID in case of SOAP Adapter ??

    Hi,
    I never used sending messageid but it might be used
    to monitor messages
    let's say in one middleware the message id is xxx-yyy-zzz
    and in XI it's ttt-yyy-uuu
    and if you set mesid = xxx-yyy-zzz it should be xxx-yyy-zzz in both right ?
    also check out the description on :
    section
    <b>Message ID (optional) &msgguid=<msgguid></b>
    http://help.sap.com/saphelp_nw04/helpdata/en/43/64db4daf9f30b4e10000000a11466f/content.htm
    Regards,
    michal

  • 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

  • Connection issue between Data service(DQ) to PI through SOAP adapter.

    Hi Guys,
    We are trying to connect the data services(DQ) with SAP PI through SOAP adapter. I provided the wsdl file to data services team and they are trying to send messages to PI. Looks like the messages are showing successful in there system, but not showing up in PI system.
    I tried the same file using xmlspy and PI receiving the messages from XMLSPY. We are wondering whats going wrong?
    Any idea about this data services system? Is there any other better way to receive messages to PI apart from webservices?
    PS: Connection is working fine from PI to DQ thorugh SOAP adapter.
    Thanks
    Deepthi.

    >>>> We are trying to connect the data services(DQ) with SAP PI through SOAP adapter. I provided the wsdl file to data services team and they are trying to send messages to PI. Looks like the messages are showing successful in there system, but not showing up in PI system.
    You are using soap sender  adapter ... Hosting webservices and DQ team is able to access your webservice.  Also using XMLSPY you are able to see pi messages.
    If you are using advance adapter engine, Please check only in the RWB -> adapter engine.
    If you are not using AAE, check in both SXMB_MONI and RWB for the wide range... Something problem with filter query in your checking...
    Note  since XMLSPY testing goes through Pi and able to monitor means you dont need another webservice client tool. 
    Solution:
    use tcp monitor to monitor the soap message ... It is better option
    /people/stefan.grube/blog/2007/03/29/troubleshooting-soap-http-and-mail-adapter-scenarios-with-tcpgateway

  • No "Adapter monitoring" in runtime workbench

    We appear to having difficulties with our SOAP adapter in XI 3.0.
    I have searched through the forum, and most queries relate to SOAP Adapter being greyed out in adapterframework, but it is not even available in the list.
    We do no have the Adapter Monitoring as an option in our runtime workbench, either.  How can we add this?
    Any thoughts gratefully received!

    Hi Barry,
    have you tried: http://server:port/mdt/amtServlet   ?
    this is the address of the adapter monitoring
    the old address ( < sp4 as far as I remember) of the adapter monitor:
    http://hostname:portnumber/AdapterFramework/monitor/monitor.jsp
    regards,
    michal
    Message was edited by: Michal Krawczyk

  • Synchronous messages through Soap Adapter

    Hi XI Guru's
    In my scenario I am sending a synchronous soap message over soap adapter. Message flow is  like
    3rd Party Application --> XI --> SAP R/3.
    My message do get processed in SAP R/3 and I do get response in SXMB_MONI as well as in Message Monitoring in RWB.
    The return message for message f1bdf1d0-cec5-11de-a9c0-0050569626f6(OUTBOUND) was successfully passed to the waiting "call" thread.
    2009-11-11 05:27:26     Information     The message status was set to DLVD.
    2009-11-11 05:27:26     Information     SOAP: response message entering the adapter (call)
    2009-11-11 05:27:26     Information     SOAP: response message leaving the adapter
    But still the response from XI does not reaches 3rd party application.
    On digging the logs I found following message.  Can this be an issue in XI which is blocking the reponse message from reaching the 3rd Party Application.( I tried posting the message through XML spy and I do get the response in XML spy.)
    (Note : My XI Installation has central adapter engine)
    #1.5 #0050569626F6004200000D0B00000B5000F66675B4B8DEA5#1257401122698#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/com.sap.aii.adapter.soap.app#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#LOVEIN#25369##sapnw03_NPI_6935550#Guest#2fd59d51c9d111debb440050569626f6#HTTP Worker [4]##0#0#Warning##Plain###Cannot send an HTTP error response [500 "Application error occurred during the request procession." (details: &quot;The WebApplicationException log ID is [0050569626F6004200000D0800000B5000F66675B4B8DEA5].&quot;)]. The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: *The stream is closed.*
    +     at com.sap.engine.services.servlets_jsp.server.runtime.client.ServletOutputStreamImpl.ensureOpen(ServletOutputStreamImpl.java:354)+
    Any help in this regard is appreciated .
    Thanks
    Lovein

    Thanks for your reply Stephan / Abhishek.
    To add some more info on the issue. This issue is when I am using PI 7.1 version.
    I do not face the issue if I use XI 3.0 and end to end flow works fine and response message reaches 3rd party application.
    Only difference I have in 2 versions is that in XI 3.0 we have been able to disable the soap adapter authentication (by changing web.xml file) where as in PI 7.1 we have not been able to disable that authentication and userid/ password info has to be provided while sending the soap message from 3rd Party application.
    (Security if not disabled gives 401 message as described on following blog [SOAP Sender ADAPTER 401 No Authorisation|SOAP Sender ADAPTER 401 No Authorisation] )
    On the other note do you guys know a way to disable this authentication on PI 7.1 version.
    Thanks ,
    Lovein

Maybe you are looking for

  • Failed to install 64-bit Oracle client on Windows 8.1

    I just tried to install the 64-bit client on Windows 8.1 with 16GB of ram. First of all, I got the INS-13001 warning that my environment does not meet minimum requirements, even though I was just installing a client! I chose to ignore the warning and

  • How much does a slide weigh?

    Hi, weight means Kb size for this post....not sure what else to call it. I am wondering, is there is a source to find out what makes a slide/project "heavy" in terms of its published kb size. Meaning, if I create a single slide project, just for argu

  • Problem in Posting Messages to MDM from SAP XI

    Helloo Experts, First of all I want to tell you this is my first day working with SAP MDM. I donu2019t even know the basics of MDM. I am trying to Post the Message from XI to SAP MDM Console. When I am trying to post a test message it appears success

  • RO doesn't come out of 'provisioning' state even though tasks are Completed

    I'm having an issue where I provision a user to a RO. Both System Validation and Create User (which are the only two tasks marked as Required for Completion') are ok.. and both are marked Completed but instead of the resource object changing to a 'Pr

  • Unable to start Oracle Application Testing Suite Application service

    Hi , I have installed OATS 9.1 successfully on my machine , but there is some problem in starting Oracle Application Testing Suite Application Service . I am not able to access Oracle Test Manager , when i start the service manually it gives "Error 1