Principal Propagation Using Sender SOAP adapter in PI7.1

Hi,
I am trying to configure principal propagation using SOAP sender adapter. In that, I am trying to generate the assertion ticket in SAP only but it is using PIAFUSER as the user that is being passed and not the user which we are using to logon.
Please tell me how an assertion ticket can be generated in this case , and the User that is being used for logging on is propagated. Is there any other way in which SOAP adapter can be used to propagate principally.

Hi,
  Have you come across this link?
http://help.sap.com/saphelp_nwpi711/helpdata/en/48/ce95b718d3424be10000000a421937/content.htm
Regards,
Ravi

Similar Messages

  • IOException: invalid content type for SOAP: TEXT/ using Sender SOAP adapter

    Hi all,
    When I am using Sender SOAP adapter, i am getting (MessagingException: Could not parse XMBMessage. Reason: java.io.IOException: invalid content type for SOAP: TEXT/HTML using connection SOAP_http://sap.com/xi/XI/System) exception.
    From my RWB I can see:
    2009-05-25 16:18:39 Information The message was successfully retrieved from the call queue.
    2009-05-25 16:18:39 Information The message status was set to DLNG.
    2009-05-25 16:18:39 Error Failed to parse the XI system response.
    2009-05-25 16:18:39 Error The message was successfully transmitted to endpoint com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIMessage creation failed (inbound). Reason: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Could not parse XMBMessage. Reason: java.io.IOException: invalid content type for SOAP: TEXT/HTML using connection SOAP_http://sap.com/xi/XI/System.
    2009-05-25 16:18:39 Error The message status was set to FAIL.
    2009-05-25 16:18:39 Error Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIMessage creation failed (inbound). Reason: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Could not parse XMBMessage. Reason: java.io.IOException: invalid content type for SOAP: TEXT/HTML
    Please help if possible! Thanks!
    Mayank

    Hi,
    Check in SLD your integration engine business system have the following
    pipeline url : http://server:httpport/sap/xi/engine?type=entry
    check Http port also
    After that go to TCODE - SXMB_ADM - integrationn engine configuration and check if your server is configured as HUB with the same url or not.
    Thanks
    Kasturika Phukan

  • Enabling HTTPS with Client Authentication for Sender SOAP Adapter on PI7.1

    Hello All,
    We are currently building up a HTTPS message exchange with an external client.
    Our PI 7.1 recieved over HTTPS messages on an already configured Sender SOAP Adapter.
    The HTTPS (SSL) connectivity works fine and was completely configured on the ABAP Stack at Trust Manager (TC=STRUSTSSO2)
    Login to Message Servlet "com.sap.aii.adapter.soap.web.MessageServlet is required and works fine with user ID and password.
    Now we have to configure the addtional Client Authentication.
    At SOAP Adapter (Sender Communication Channel) under "HTTP Security Level"you are able to configure "HTTPS with Client Authentication".
    But what are the next steps to get this scenario successfully in place?
    Many thanks in advance!
    Jochen

    Hi Colleagues,
    following Steps still have to be done:
    - Mapping public key to technical user at Java Stack
      As preparation you have to activate value "ume.logon.allow.cert" with true under "com.sap.security.core.ume.service" under Config Tool. At NWA under Identity Management at for repecively technical user the public key certificate
    - Be sure CA root certivicate at Database under STRUSTSSO2
    - Import intermediate Certificate under Certificate List at Trast Manager for the Respecive Server Note
    - use Login Module "client_cert" which you have to configure under NWA\Configuration Management\Authentication for Components "sap.com/com.sap.aii.adapter.soap.app*XISOAPAdapter".
    Many thanks to all for support!
    Regards,
    Jochen

  • Communication using Sender soap adapter using secured certificates

    Hi All,
    For sender soap scenario,
    We have installed 3rd party certificate on XI and we have give them XI SSL certificate to 3rd party.
    We are getting handshake error when they send message using XI URL.Can you please tell me in which location on webserver where 3rd party has to install certificate and what all settings
    I need to give in communication channel and sender agreement?
    thanks a lot.
    Best Regards,
    Harleen Kaur Chadha

    Can you please tell me in which location on webserver where 3rd party has to install
    certificate and what all settings I need to give in communication channel and sender agreement?
    Check this link to know more:
    http://help.sap.com/saphelp_nwpi71/helpdata/en/32/1c1041a0f6f16fe10000000a1550b0/frameset.htm
    Also there is a Blog by Alexander on Principal Propagation....you can refer it to know more on how, where to include the certificates..
    Regards,
    Abhishek.

  • Error using Sender SOAP adapter over HTTPS

    Hi experts,
    Few weeks ago, i developed an interface as follows: SOAP <-> XI <-> RFC.
    I tested the functionality using Altova and everything went well, with HTTP.
    However, when i use HTTPS it fails throwing these error messages (pop ups):
    <i>"HTTP error: could not post file"......
    "Error sending the soap data"</i>
    I have reviewed the SSL certificates installation and everything seems to be ok, but currently i am stuck and do not know how to fix this.
    I have also change the ID comm channel from HTTP to HTTPS with client aut.
    Is there any special service i have to activate? (XI services and SPIGATE are already done)
    Could you please assist?
    Thanks in advance and best regards,
    David

    David,
    have a look @ these threads...u may get some help!!!
    Sender Soap with HTTPS
    https Soap Adapter
    Regards
    Biplab

  • Use of SOAP adapter in PI7.11 - migration from PI7.0

    Hello everybody,
    We are migrating from PI7.0 to PI7.11.
    we have a scenario RFC => PI => SOAP
    in PI 7.0 that work perfectly for 2 years
    in PI 7.11 that doesn'"t work. That gives the error message "com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.EOFException: Connection closed by remote host" .
    the SOAP is under https with a certifcate  X509 imported  by visual admin for PI7.0 and imported by NWA in 7.11.
    The output message from the 2 environments are the same.
    I intercept them in clear format ( non crypted) thru a gateway except for the PI 7.11  there is a line more before the soap envelop. (CallingType: SJM).
    The certificates are places in TrustedCAs for the 2 environments
    In log there is the message:
    #2.0 #2010 03 01 09:56:10:788#+0100#Error#com.sap.aii.af.sdk.xi.net.HTTPClientConnection#
    #BC-XI-CON-AFW#com.sap.aii.af.lib#0026B9737AE51CA50000000100001090#5022851000000004#sap.com/com.sap.aii.adapter.soap.app#com.sap.aii.af.sdk.xi.net.HTTPClientConnection.getInputStream(Socket)#J2EE_GUEST#0##4EEA9DA0250F11DFBBEC0026B9737AE5#4eea9da0250f11dfbbec0026b9737ae5#4eea9da0250f11dfbbec0026b9737ae5#0#XI SOAP[rcv_SOAP_Login/SV_TME/*]_16058#Plain##
    failed to get the input stream from socket: java.io.EOFException: Connection closed by remote host.#
    #2.0 #2010 03 01 09:56:10:788#+0100#Error#com.sap.aii.af.sdk.xi.net.HTTPClientConnection#
    #BC-XI-CON-AFW#com.sap.aii.af.lib#0026B9737AE51CA50000000300001090#5022851000000004#sap.com/com.sap.aii.adapter.soap.app#com.sap.aii.af.sdk.xi.net.HTTPClientConnection.call(Object)#J2EE_GUEST#0##4EEA9DA0250F11DFBBEC0026B9737AE5#4eea9da0250f11dfbbec0026b9737ae5#4eea9da0250f11dfbbec0026b9737ae5#0#XI SOAP[rcv_SOAP_Login/SV_TME/*]_16058#Plain##
    additional info ssl_debug(6): Starting handshake (iSaSiLk 4.1)...
    ssl_debug(6): Sending v3 client_hello message, requesting version 3.2...
    ssl_debug(6): IOException while handshaking: Connection closed by remote host.
    ssl_debug(6): Sending alert: Alert Fatal: handshake failure
    ssl_debug(6): Shutting down SSL layer...
    PI7.0 is installed on windeows  server 2003  32 bits
    PI 7.11 is installed on windows server 2008  64 bits
    Is there someone who can help me ?
    Thanks in advance.
    E. Koralewski.
    Edited by: Eric Koralewski on Mar 1, 2010 12:04 PM
    Edited by: Eric Koralewski on Mar 1, 2010 12:04 PM

    Hi Christain,
    Thanks for the information
    I received a new version of that certificate to be sure that was not a problem of version .
    I imported it in old system ( version 7.0 ) in a new keystore , I did the same thing on the new system ( PI 7.11).
    The scenario works  in the old system with that keystore and not in the new system (7.11).
    The only one log I found is the log which is in the begining of my post. 
    Kind Regards

  • What would be the web servendpoint for a scenario using sender SOAP adapter

    Hi,
    I have setup a scenario to consume a Service interface in SAP namespace. This is a asynch inbound SI which is not point to point enabled which means the WSDL we get are only the definitions with no endpoints. So I exported it as an external definition which I will then use as sender interface so the scenario looks like this:
    Third Party -> SOAP Sender Adapter -> Outbound SI(Imported WSDL) -> XI Box (Mapping etc) -> Inbound SI -> XI Receiver Adapter -> ABAP box
    Once all has been setup, for SOAP sender adapter for third party to send data the URL looks like this.
    http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
    But I dont think so this is the endpoint beacuse if I give this in browser I only get an OK status from XI box, what should I give to third party they can use as WSDL endpoint to generate the proxy/stub on their side to send data to SAP.
    Regards, Shadab

    This is a asynch inbound SI which is not point to point enabled which means the WSDL we get are only the definitions with
    no endpoints. So I exported it as an external definition which I will then use as sender interface so the scenario looks like this:
    Third Party -> SOAP Sender Adapter -> Outbound SI(Imported WSDL) -> XI Box (Mapping etc) -> Inbound SI -> XI Receiver
    Adapter -> ABAP box
    Inbound (receiver-end) Service Interface is to be developed from an imported WSDL......not the Outbound (Sender-end) Service Interface.....you actually did the procedure which needs to be done when SOAP is at receiver-end.
    If you are clicking the WSDL tab in Service Interface and then taking it as the required WSDL then note that this is not the one.....it is to be generated from ID --> Tools --> Display WSDL (it will be based on the outbound SI)......this will have the end-point which you you mentioned
    Now you give this WSDL to the sender application (it will have the end-point) and ask them to develop their coding accordingly.
    If you need to view that WSDL in explorer, then you have to publish it somewhere....like in Service Registry (or WSnavigator)
    Regards,
    Abhishek.

  • Principal Propagation using SOAP Adapter

    Hi,
    Can anybody please explain Principal Propagation concept in SOAP adapter?
    I have no idea at all about this, so it will be good if you can explain with an example scenario.
    Thankyou.

    Hi Anita,
    Did you check the below doc and blog?
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/50d07121-07a5-2c10-5280-a081de9b851c?QuickLink=index&…
    Principal Propagation in SAP XI
    sap help page
    https://help.sap.com/saphelp_nw73ehp1/helpdata/en/49/fe95b02f2e4d2baddc39196c827c51/content.htm
    regards,
    Harish

  • Dynamic sender SOAP Adapter

    Hi,
    i need to define a web service that could be consumed by any sender system, how could i do this if i need to define the BS in the URL when i create the WSLD undel menu tool-->Define web service
    http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
    in case its migth be possible, how could i identify which system consume the service, is there any system information where i could get at least the host name or the IP???
    Thanks
    Rodrigo

    >> how could i do this if i need to define the BS in the URL when i create the WSLD undel menu tool-->Define web service
    http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel in case its migth be possible
    Create Webservice using Sender SOAP adapter. Go to sender agreeement, click display wsdl. Save the file . That is your wsdl and it contains all your webservice details that includes sender business system, interface, URL etc.
    >>how could i identify which system consume the service, is there any system information where i could get at least the host name or the IP???
    You create valid service users of PI to communicate and distribute for different consuming systems. When they invoke your webservice they have to use your login credentials. Also you can go with client authentication certifcate(SSL) so that only trusted partners with client certificate can communicate your webservice.
    >>where i could get at least the host name or the IP???
    You dont get those informations. You allow only trusted trading partners to consume your webservice using client authentication and certificate credentials.

  • What is the maximum size a sender SOAP adapter can handle?

    Hi,
    I am using sender SOAP adapter and receiver RFC adapter.
    What is the maximum size of request message it can handle efficiently.
    In the current scenario which I need to design , the request XML file could be up to 24 MB.
    Also if you could comment on which would be the best to use as the sender side - SOAP or File Adapter
    when the request message/file is of such size?
    regards
    Arun G

    hi,
    >What is the maximum size of request message it can handle efficiently.
    it totally depends on your hardware and flow design inside XI/PI
    >In the current scenario which I need to design , the request XML file could be up to 24 MB.
    this size is not a lot for a "normal" XI machine but it also depends on the
    volume of those messages - that is if you need to send
    one message like that per day or 1000 per half an hour...
    >Also if you could comment on which would be the best to use as the sender side - SOAP or File Adapter
    when the request message/file is of such size?
    SAP's general recommendation is to use messages around 5mb
    but it heavily depends on other factors so don't threat it as a must
    Regards,
    michal Krawczyk

  • How to use Basis Authentication in Sender SOAP Adapter

    We implemented one Sender SOAP Adapter and we had to implement the modified WEB.XML method to remove the security specification.  We have now asked the developer to correct this situation so we can remove this modification.  The Interface developer would like to use Basic Authentication. If you have an automated interface sending in a SOAP Message, how do you do Basic Authentication? 
    I've tried using:
    http://host:port/XISOAPAdapter/MessageServlet?channel=:<Service>:<Channel>&sap-user=xiappluser&sap-password=<Password>&sap-language=EN&sap-client=<Client>
    When I do this, I still get the Authentication Pop-Up Window.
    How does the Sending Interface either supply the ID and Password on the incoming SOAP Message or respond to the Authentication Pop-Up?
    Thanks,
    Anne

    By Defualt the web service exposed by you will use Basic Authentication mode only.
    But the way you do Basic Authentication in the web client is platfrom dependent.
    This is not the way to do Basic authentication
    http://host:port/XISOAPAdapter/MessageServlet?channel=:<Service>:<Channel>&sap-user=xiappluser&sap-password=<Password>&sap-language=EN&sap-client=<Client>
    I am providing you a code snippet on how to Basic Authentication in Java when making the Web Service Call.
    If the client is on some other platform just look for the corresponding api.
    Please award points if you find this answer useful.
    Code Snippet
    URL url = new URL(URL);
    URLConnection connection = url.openConnection();
    if( connection instanceof HttpURLConnection )
    ((HttpURLConnection)connection).setRequestMethod("POST");
         //connection.setRequestProperty("Content-Length",Integer.toString(content.length()) );
         connection.setRequestProperty("Content-Type","text/xml");
         connection.setDoOutput(true);
         String password = User + ":" + Password ;
          //Where con is a URLConnection 
         connection.setRequestProperty ("Authorization", "Basic " + encode(User + ":"+ Password));
         connection.connect();
    Encode Method
    public static String encode (String source) {
    BASE64Encoder enc = new sun.misc.BASE64Encoder();
    return(enc.encode(source.getBytes()));

  • WHAT IS THE BEST WAY TO CREATE AN XSD FILE (TO BE USED BY SOAP ADAPTER)

    Dear friends
    I have a simple scenario.
    OUTBOUND DATA  -->  SOAP ADAPTER  --> ( XI )  -->  RFC ADAPTER  --> INBOUND DATA
    The XML file that I got from mapping area of IR (Design) is as follows
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:MT_NAME_SOURCE xmlns:ns0="http://test3.com">
       <FIRSTNAME>DAVE</FIRSTNAME>
       <LASTNAME>SMITH</LASTNAME>
    </ns0:MT_NAME_SOURCE>
    If you notice, there are only 2 fields.
    I need to create an XSD file and import it as an external object, which I can use for SOAP Adapter.
    Which is the best way to create it.
    Also, I need to know if there is any step by step of sending a message from XML SPY. I have downloaded this software, but am not able to undertand how to use this.
    Hope to hear from any experts on this forum.
    Thanks in advance
    Ram

    Hi Ram,
    See the below blog..
    It shows how to send SOAP message using XML Spy.
    It also shows how to generate wsdl.
    /people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
    Regards,
    Sumit

  • ABAP Proxy without SOAP adapter in PI7.3

    Hi All,
    We have dual stack implementation of PI7.3 but we do not wish to use the SOAP adapter for configuring an ABAP proxy scenario.
    Is this possible? Is the Javastack only configuration in NW Admin available for use in dual stack implementation also?
    Thanks and Regards,
    Diptee

    Hi All,
    So it essetially means that only the below 2 options are available for ABAP proxy scenarios in PI7.3 for a ABAP+Javastack installation
    - use of SOAP adapter over XI protocol
    - use of conventional proxy configuration of the ABAP Integration Server
    And the only Javastack config cannot be used for a dual stack implementation.
    Please confirm if above is correct.
    Regards,
    Diptee
    Edited by: diptee s on Sep 21, 2011 4:48 PM

  • Remove authentication in sender soap adapter pi 7.1

    Hello
    Did anyone manged to remove authentication in PI 7.1 sender soap adapter?
    I have updated file web.xml in the file com.sap.aii.adapter.soap.war
    and now I want to deploy it,but I dont have any sda in the folder
    thx
    Shai

    hi Shai,
    just something to try in case:
    you don't need any java parameters of SOAP sender
    you can try approach from Stefan:
    /people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
    and then:
    1. in SICF copy the engine service to a new one
    2. put the credentials for this new service inside SICF
    then you will have sender SOAP adapter without a password right?
    I didn't try it but I guess it would work without
    crashing the whole original SOAP sender adapter by
    making changes into web.xml
    Regards,
    Michal Krawczyk

  • SMIME in sender soap adapter

    Hi,
    I'd like to know the proper format of the POST request to a sender soap adapter with SMIME activated. I've found almost no documentation about it.
    I'm trying to send a document ciphered to PI via soap adapter (HTTP POST). I've done the following steps
    1. I activate SMIME in the sender soap adapter, and I specify "Decrypt" as the security procedure in the sender agreement. I also incorporate the private key in the keystore DEFAULT and reference to it in the sender agreement.
    2. I use OpenSSL to cipher an xml document like this (I use the public certificate associated to the previous private key) :
    --> openssl smime -encrypt -in fich.txt -out fich_encrypted.txt certTesting.pem
    What I get is:
    MIME-Version: 1.0
    Content-Disposition: attachment; filename="smime.p7m"
    Content-Type: application/x-pkcs7-mime; smime-type=enveloped-data; name="smime.p7m"
    Content-Transfer-Encoding: base64
    MIIC....[base64 content of the file encrypted]
    3. I use CURL to send the HTTP POST request to PI. Previously I get the binary file from the base64 content.
    > POST /XISOAPAdapter/MessageServlet?senderParty=&senderService=BC_1[...]
    > Authorization: Basic c2U[...]
    > Host: pi.[...].com:50000
    > Accept: /
    > Content-Type: application/pkcs7-mime; smime-type=enveloped-data; name=fich_encrypted.der
    > User-Agent: Jakarta Commons-HttpClient/3.1
    > Accept-Encoding: text/xml
    > Content-Disposition: attachment; filename=fich_encrypted.der
    > Content-Length: 620
    > Expect: 100-continue
    but I get this error from the SOAP Adapter:
    --> java.io.IOException: invalid content type for SOAP: APPLICATION/PKCS7-MIME.
    I also get the same error if I remove the header Content-Disposition.
    4. If I send the xml file without ciphering (header Content-Type: text/xml;charset=UTF-8) I get the error:
    com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: call failed: java.lang.SecurityException: Exception in Method: VerifySMIME.run(). LocalizedMessage: SecurityException in method: verifySMIME( MessageContext, CPALookupObject ). Message: IllegalArgumentException in method: verifyEnvelopedData( ISsfProfile ). Wrong Content-Type: text/xml;charset=UTF-8. *Expected Content-Type: application/pkcs7-mime or application/x-pkcs7-mime*. Please verify your configuration and partner agreement
    PROBLEM --> I really don't know what the SOAP sender channel is expecting when SMIME is activated. I've tried to send the binary file encripted as an attachment and also directly, but the soap adapter complains.
    Thanks

    HI,
    for XI EP
    Please see the below links so that you can have clear Idea..
    /people/saravanakumar.kuppusamy2/blog/2005/02/07/interfacing-to-xi-from-webdynpro
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webas/java/integrating%20web%20dynpro%20and%20sap%20xi%20using%20jaxb%20part%20ii.article
    Consuming XI Web Services using Web Dynpro – Part II-/people/riyaz.sayyad/blog/2006/05/08/consuming-xi-web-services-using-web-dynpro-150-part-ii
    Consuming XI Web Services using Web Dynpro – Part I -/people/riyaz.sayyad/blog/2006/05/07/consuming-xi-web-services-using-web-dynpro-150-part-i
    /people/sap.user72/blog/2005/09/15/creating-a-web-service-and-consuming-it-in-web-dynpro
    /people/sap.user72/blog/2005/09/15/connecting-to-xi-server-from-web-dynpro
    Regards
    Chilla..

Maybe you are looking for