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

Similar Messages

  • I need to secure SOAP message sent into SOAP adapter, how to?

    Hi guys,
    My scenario uses SOAP and I need to secure this SOAP message sent into SOAP adapter. As I have read in the documentation, HTTPS is possible only on the SOAP receiver adapter. But my is SENDER.
    COuld you help me please, how to solve it? Or post some link? Or, if you have your own approach, to let me know?
    Thanx, Peter

    Hi,
    you can use SSL with the sender adapter. Please see the extract of the SOAP Adapter FAQ (Note #856597) below:
    <b>Q:</b> Can I use SSL for my sender adapter?
    <b>A:</b> Yes. Normally, the SOAP adapter servlet runs on the engines HTTP port. But you can activate the engine's HTTPS port so that this servlet can receive messages sent to the HTTPS port. See the documentation about the J2EE engine's security configuration.
    I am afraid, I haven't yet tried this myself, so you will need to consult the J2EE documentation.
    Regards,
    HC

  • Generate Message Interface for SOAP Adapter

    Hi All,
    I want to implement a scenario like this:
      ABAP System -> RFC Adapter -> XI -> SOAP Adapter -> Web Service
    Currently the WSDL of the web service is known. It is http://www.abysal.com/soap/AbysalEmail.wsdl
    How can I generate the inbound message interface in XI according to the WSDL?
    Thanks
    Jerome
    Message was edited by: Jerome Zhao
    Message was edited by: Jerome Zhao

    Hi Jerome,
    Import the WSDL as an external definition and then you can create a inbound Message interface based on that external definition.
    Regards,
    Sridhar

  • Using adapter specific message attributes in SOAP adapter configuration

    Hi,
    Can you please let me know how to use adapter specific message attributes in receiver and sender SOAP adapter configuration. If possible , with example.

    See here:
    Adapter-Specific Message Attributes in the Message Header
    http://help.sap.com/saphelp_nw04/helpdata/en/43/0a7d1be4e622f3e10000000a1553f7/frameset.htm
    Sender Soap Adapter:
    http://help.sap.com/saphelp_nw04/helpdata/en/fc/5ad93f130f9215e10000000a155106/frameset.htm
    Receiver Soap Adapter
    http://help.sap.com/saphelp_nw04/helpdata/en/29/5bd93f130f9215e10000000a155106/frameset.htm

  • Adapter specific message attributes for SOAP adapter

    Hi all,
    I  have gone through the SAP Help Documents for configuring SOAP Communication Channel. I am unable to understand how to implement ASMA for Soap adapter.
    Please provide some links to help me understand the same
    Many Thanks,
    Neha

    Hi Neha,
    pls do chk the below links for SOAP adapter message attributes
    http://help.sap.com/saphelp_nwpi71/helpdata/en/fc/5ad93f130f9215e10000000a155106/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/43/0a7d1be4e622f3e10000000a1553f7/content.htm
    http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.wbia_adapters.doc/doc/sap_xi/sapximst38.htm
    http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.wbia_adapters.doc/doc/webservices/webservices16.htm
    Regards
    Sampath

  • Problem with the SOAP adapter !

    Hi!
    We are trying to use a WebServices from XI.
    In the WSDL file that we have imported and use'd in
    our mapping the information about the soap header look's
    like this :
    <wsdlsoap:header message="impl:serviceRequest" part="toCountry" use="literal" />
    <wsdlsoap:header message="impl:serviceRequest" part="fromCountry" use="literal" />
    <wsdlsoap:header message="impl:serviceRequest" part="language" use="literal" />
    <wsdlsoap:header message="impl:serviceRequest" part="customerCodeOwner" use="literal" />
    <wsdlsoap:header message="impl:serviceRequest" part="customerCode" use="literal" />
    <wsdlsoap:header message="impl:serviceRequest" part="userId" use="literal" />
    <wsdlsoap:header message="impl:serviceRequest" part="userPassword" use="literal" />
    But then the message leave the SOAP adapter
    it looks like this:
    <SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
    <SOAP:Header/>
    <SOAP:Body>
    <ns1:serviceRequest xmlns:ns1='http://www.dnbnordic.com/brg/NRGDecisionSupportDSC/wsdl'>
    <nRGDecisionSupportDSCRequest>
    <ns2:criteria xmlns:ns2='http://www.dnbnordic.com/brg/NRGDecisionSupportDSC/request'>
    <ns2:socialSecurityNumberApplicant>XXXXXXXXXX</ns2:socialSecurityNumberApplicant>
    <ns2:conversationCode>X</ns2:conversationCode>
    </ns2:criteria>
    </nRGDecisionSupportDSCRequest>
    <toCountry>XX</toCountry>
    <fromCountry>XX</fromCountry>
    <language>XX</language>
    <customerCodeOwner>SYD9001</customerCodeOwner>
    <customerCode>XXXXXXX</customerCode>
    <userId>XXXX</userId>
    <userPassword>XXXXXX</userPassword>
    </ns1:serviceRequest>
    </SOAP:Body>
    </SOAP:Envelope>
    The SOAP header info. is in the body !
    Ofcourse the message fails !!
    Any ideas ??
    //Stig

    Hi Stig,
    Although specified in the WSDL 1.1 spec, the use of soap:header is quite rare.
    And having a soap header consisting of multiple parts and not referring to single XSDL element is a bit in conflict with the document/literal approach.
    Bottom line: please try and convince your business partner to not use the soap:header trick and stick to standard document/literal web services.
    Kind regards, Guy Cretgs

  • SOAP adapter URL causing problems

    Hi gurus,
    As of PI 7.1, SAP is recommending to use:
    http://host:port/XISOAPAdapter/MessageServlet?senderParty=FP&senderService=FS&interface=IF&receiverParty=TP&receiverService=TS&interfaceNamespace=IFNamespace
    instead of
    http://<serverhost>:<port>/XISOAPAdapter/MessageServlet?channel=<party>:<ServiceName>:<ChannelName>
    while sending messages to the SOAP adapter. BUT, the new format is causing problems when the developers are trying to import the WSDL (to Webdynpro, eclipse, etc). Also, XMLSpy complains that the xml is not well-formed because of the soap address field.
    So I removed the & signs and replaced them with the escape equivalent of &amp; for the new format and tried to use:
    http://host:port/XISOAPAdapter/MessageServlet?senderParty=FP&senderService=FS&interface=IF&receiverParty=TP&receiverService=TS&interfaceNamespace=IFNamespace
    But this time, SOAP adapter replies saying there is no binding. How to overcome this?
    Thanks
    Gokhan

    try this format:
    http://<hostname OR IP addr>:<portno>/XISOAPAdapter/MessageServlet?channel=:<SenderService>:<SenderSOAPCC>&version=3.0&Sender.Service=<senderService>&Interface=<senderNamespace>%5E<senderMI>

  • 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

  • Error in Sender SOAP Adapter on XI 3.0 SP13

    Hi All.
    I have an application that sends a SOAP message to XI SOAP Adapter, to reach a synchronous interface. I've generated the .wsdl file from the Integration Directory, within the URL:
    http://sapbox:59800/XISOAPAdapter/MessageServlet?channel=:BS_PORTAL:CC_S_SOAP_CREDITO
    When I try to reach this URL, I get the successful response:
    <i>Message Servlet is in Status OK</i>
    I've also created the sender SOAP communication channel, fullfilling the default namespace and default interface correctly.
    However, when I use wsnavigator client provided by SAP to prove the scenario, the SOAP message doesn't achieve XI, as the XISOAPAdapter EJB throws some exceptions:
    <i>HTTP/1.1 500 Internal Server Error
    Connection: close
    Server: SAP J2EE Engine/6.40
    Content-Type: text/xml; charset=utf-8
    Date: Sat, 17 Sep 2005 02:59:12 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>BaseEJBException</code>
              <text><![CDATA[
    com.sap.aii.af.mp.processor.ModuleProcessorException
         at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:278)
         at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process(ModuleProcessorLocalLocalObjectImpl0.java:103)
         at com.sap.aii.af.mp.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:162)
         at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:508)
         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: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:159)
    Caused by: com.sap.engine.services.ejb.exceptions.BaseEJBException: Exception in method process.
         at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:121)
         at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:227)
         ... 19 more
    Caused by: java.lang.NoSuchMethodError: com.sap.aii.messaging.srt.xmb.XMBWebServiceExtension.setDynamicConfigurationMode(I)V
         at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.createXMBWSBubble(XISOAPAdapterBean.java:1129)
         at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.setup(XISOAPAdapterBean.java:265)
         at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:562)
         at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:103)
         ... 20 more
              ]]></text>
            </s:SystemError>
          </detail>
        </SOAP:Fault>
      </SOAP:Body>
    </SOAP:Envelope></i>
    I've already done something really similar on SP 9. Can it be a new problem from SP13? Does anyone has any idea?
    Thanks in advance.
    Deise Lima.

    Hi Naveen,
    I have configured a SOAP sender adapter in XI 3.0 and is using the URL
    http://host:port/XISOAPAdapter/MessageServlet?channel=:BS_WEBSERVICE:CC_WEBSERVICE_SOAP to post the messages. When I open the URL in the browser I am getting the error.
    Message Servlet is in Status ERROR
    Status information:
    Servlet com.sap.aii.af.mp.soap.web.MessageServlet (Version $Id: //tc/aii/30_VAL_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#5 $) bound to /MessageServlet
    Classname ModuleProcessor: null
    Lookupname for localModuleProcessorLookupName: localejbs/ModuleProcessorBean
    Lookupname for remoteModuleProcessorLookupName: null
    ModuleProcessorClass not instantiated
    ModuleProcessorLocal not instantiated
    ModuleProcessorRemote not instantiated
    But when I test the URL http://host:port/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:BS_WEBSERVICE:CC_WEBSERVICE_SOAP to check the communication channel I am getting the right response as below.
    <?xml version="1.0" ?>
    http://host:port/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:BS_WEBSERVICE:CC_WEBSERVICE_SOAP <s:ChannelInfo xmlns:s="http://sap.com/xi/WebService/xi30">
    <channelID>e7ac884596ea3d088cbfd8b434f942f2</channelID>
    <name>CC_WEBSERVICE_SOAP</name>
    <type xmlns:st="http://sap.com/xi/XI/System">st:SOAP</type>
    <direction>INBOUND</direction>
    <party />
    <service>BS_WEBSERVICE</service>
    </s:ChannelInfo
    I used the http capture to debug, In the 1st case though I am getting "Message Servlet in status error" I am seeing a 200 OK code in the http capture tool. When the message is posted from .net client proxy or Altova XML Spy we are getting a 500 internal server error.
    Am not sure what causes the error

  • Sender SOAP Adapter problem in PI 7.1

    Hello Everyone,
    I have a problem with Sender SOAP  Adapter
    In PI 7.0 i am able to receive the messages through sender SOAP Adapter for both HTTP and HTTPS. But when i am testing in PI 7.1 i am unable to receive any messages at Adapter level for both HTTP and HTTPS
    All sender leagcy system are getting different error messages like
    1. 400 HTTP Bad request.
    2. Invalid request.
    3. BAPI  error message
    Could any one please assist me in this problem.
    Thanks
    Vick

    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

  • Sender SOAP Adapter Modules!

    Hi Can anyone guide me how to write a Sender SOAP adapter module ?

    Hi Pooja, thanks for the reply I have seen that.
    Please look at the below forum.
    SOAP Adapter and plain HTTP
    It  says "When you write a module for sender SOAP adapter, you have to deal with the incoming message, as the SOAP adapter first calls the customer module, then creates the XI message."

  • SOAP Adapter and plain HTTP

    Hello,
    what does the option
    "Do not use SOAP envelope" on a SOAP SENDER adapter mean?
    Does this mean, that only the payload from the soap message is sent to the integration server? (without the soap envelope)
    Or does this mean, that I can send a XML message without SOAP envelope to the adapter from a HTTP client?
    Which means, I can use the SOAP adapter like the standard PLAIN HTTP adapter, but I can implement a adapter module!
    How knows more details on that?
    Best regards
    Werner Magerl

    Hi Werner,
    > When I use the option nosoap=true and the setting "Do
    > not use SOAP envelope" then it works.
    > So both things must be used together.
    > Is this correct?
    Yes. In your scenario you need both parameters.
    > What does this mean, that the XI message is created
    > after the self-defined modules?
    When you write a module for sender file-adapter, you have to deal with an XI message, as the file adapter fisrt creates the XI message, then calls the customer module.
    When you write a module for sender SOAP adapter, you have to deal with the incoming message, as the SOAP adapter first calls the customer module, then creates the XI message.
    > We just want to check the incoming XML message
    > against a local XSD. If there is an error against the
    > XSD, we do not want to receive the message, we want
    > to send back a specific HTTP error code.
    > This is the reason, why we just want to send a
    > plainHTTP message and not a SOAP Message.
    > In my opinion this should work?!
    > We do not want to use other modules.
    Yes, that should work.
    > Do you have experience on adapter modules for SOAP
    > adapter?
    No, I have no experience with adapter modules for sender SOAP adapter.
    Regards
    Stefan

  • Changing data structure in the receiver SOAP adapter

    I was wondering whether it is possible to have changing data structure in terms of one receiver SOAP adapter so I could sent data type 1 and 2 to a single XI web service enabled URL and make conditional parsing in terms of the received message ?
    I have a receiver SOAP adapter that ideally should be able to receive two different types of messages. But SOAP adapter is fixed to a sigle message interface that naturally has it's data structure set to just one type. I can just create conditions in terms of the data type 1 message that has been defined in the design side.
    Is it possible achieve this with just one SOAP receiver adapter?

    Henri,
    Please go through the note: 856597 (Quesiton NO 9)
    -Naveen.

  • SOAP adapter problems

    Hello,
    we are trying to use the SOAP adapter to send several RFCs
    to the backend, our client uses Apache Axis.
    We first tried the url http://
    AxisFault
    faultCode: Server
    faultSubcode:
    faultString: Application Error
    faultActor:
    faultNode:
    faultDetail:
    QIRF_SEND_REQUIRMENTS_GET_DAT2.Exception:
    /code
    It seems the message is sent to the backend (because
    NO_SUBSYS_DEFINED is one of the exceptions defined for
    QIRF_SEND_REQUIRMENTS_GET_DAT2 and I see successful
    delivery in the RWB) but the content is not recognized.
    The almost identical message sent via the HTTP-adapter
    works without problems:
    <?xml version="1.0" encoding="iso-8859-1" ?>
    <rfc:QIRF_SEND_REQUIRMENTS_GET_DAT2 xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
    <rfc:T_QAIVCTAB />
    <rfc:T_QAIMVTAB />
    <rfc:T_QAICATAB />
    <rfc:T_QIERRTAB />
    <rfc:I_IND_EVALUATE_CHARACTERISTIC>X</rfc:I_IND_EVALUATE_CHARACTERISTIC>
    <rfc:I_IND_SET_BLOCK_INDICATORS>X</rfc:I_IND_SET_BLOCK_INDICATORS>
    <rfc:I_IND_TRANSFER_USAGE_DEC_CODES>X</rfc:I_IND_TRANSFER_USAGE_DEC_CODES>
    <rfc:I_IND_MULTI_TRANSFER_POSSIBLE>X</rfc:I_IND_MULTI_TRANSFER_POSSIBLE>
    <rfc:I_QAILS>
    <rfc:SATZART>Q40</rfc:SATZART>
    <rfc:SUBSYS>ICD564</rfc:SUBSYS>
    </rfc:I_QAILS>
    </rfc:QIRF_SEND_REQUIRMENTS_GET_DAT2>
    Can anyone help ?
    Thanks in advance.
    PS: What is the technical difference between the two SOAP
    URLs and why are they on different ports? Is there
    documentation explaining these issues? And what exactly
    does "Use query" string" in the configuration tab for a
    SOAP Sender communication channel mean? Which parameters
    are allowed for this query string?

    Hi!!!
    The first url you use when you want to send a message to your SOAP adapter.
    The second one you use with a plain HTTP adapter - you send a message directly to a pipeline.
    Check this link:
    http://help.sap.com/saphelp_nw04s/helpdata/en/fc/5ad93f130f9215e10000000a155106/frameset.htm
    Regards,
    Andrzej

  • SOAP Adapter status stay "Channel started but inactive"

    Hi, Folks:
    We have a couple of SOAP adapters that I have not used for a while, so I put them in inactive status.
    Now we need to switch SOAP Scenario, I activate them, however, in Communication Monitoring Page, The status is Yellow Triangle: "Channel started but inactive"
    I have tried to inactivate and reactivate them for a couple of times, it does not help.
    Any ideas are welcomed !
    Liang

    Hi Guys
    As suggested by you guys, after I sent first message, all the SOAP adapter get active now. I believe I fogort how I setup it up initially. That is the value stay with your guy
    Thanks everyone !
    Liang
    Edited by: Liang Ji on Feb 29, 2008 8:48 PM

Maybe you are looking for

  • Unable to establish Network using WRT54GS V 6.0

    I have had problems with this router since yesterday. I downloaded the new firmware V1.52.2 and that's when my problems started. I was losing my internet connection intermittantly. I plugged everything directly into my cable modem and I didn't lose m

  • Mail Adapter - Attachments

    How to get Mail Attachments using "Mail Adapter" in XI? I will receive email with some files (with defined format). I need to put the data of file in a RFC. When I use "Mail Adapter", the XI send the attachments to XML?

  • Version A of ODS object 0FIAP_O03 does not exist

    I am installing this ODS and when i hit simulate , I am getting this message and only the cube is getting installed and nothing else. Version A of ODS object 0FIAP_O03 does not exist Thanks

  • Merging 5 schema to one schema

    Hi All we have 5 company codes & 5 PY Schemas, to avoid user confusion we need to use One schema for all 5 company codes/schemas. How we can create a custom schema to merge all , means each schemas will b a sub schema in one main schema,  should ref

  • ECM or CM

    Hi, Can anyone let me know whether ECM module can be used for Compensation procedure without portal. Regards, Sekhar.