IDOC sender Principal Propagation

Hi experts,
I've a scenario IDOC to JDBC, it give me a error. I could have seen in others threads this error can be relationed with 'Principal Propagation' but i don' understand this concept, also in this scenario i haven't a sender agreement (because it is a IDOC),
the error is:
- <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
  <Trace level="3" type="T">Channel for adapter engine: JDBC</Trace>
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
  <Trace level="2" type="T">return fresh values from cache</Trace>
  <Trace level="2" type="T">Get logon data for adapter engine (SAI_AE_DETAILS_GET):</Trace>
  <Trace level="3" type="T">URL = http://sapdes:50300/MessagingSystem/receive/AFW/XI</Trace>
  <Trace level="3" type="T">User = PIISUSER</Trace>
  <Trace level="3" type="T">Cached = X</Trace>
  <Trace level="3" type="T">Creating HTTP-client</Trace>
  <Trace level="3" type="T">HTTP-client: creation finished</Trace>
  <Trace level="3" type="T">Security: Basic authentication</Trace>
  <Trace level="3" type="T">Serializing message object...</Trace>
  <Trace level="1" type="T">HTTP Multipart document length: 5223</Trace>
  <Trace level="3" type="T">HTTP-client: sending http-request...</Trace>
  <Trace level="3" type="T">HTTP-client: request sent</Trace>
  <Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>
  <Trace level="3" type="T">HTTP-client: response received</Trace>
  <Trace level="3" type="T">HTTP-client: checking status code...</Trace>
  <Trace level="3" type="T">HTTP-client: status code = 503</Trace>
  <Trace level="3" type="System_Error">HTTP-client: error response= <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title>Error Report</title> <style> td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;} A:link A:visited A:active </style> </head> <body marginwidth="0" marginheight="0" leftmargin="0" topmargin="0" rightmargin="0"> <table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75"> <tr bgcolor="#FFFFFF"> <td align="left" colspan="2" height="48"><font face="Arial, Verdana, Helvetica" size="4" color="#666666"><b>  503 &nbsp Service Unavailable</b></font></td> </tr> <tr bgcolor="#3F73A3"> <td height="23" width="84"><img width=1 height=1 border=0 alt=""></td> <td height="23"><img width=1 height=1 border=0 alt=""></td> <td align="right" height="23"><font face="Arial, Verdana, Helvetica" size="2" color="#FFFFFF"><b>SAP J2EE Engine/7.00 </b></font></td> </tr> <tr bgcolor="#9DCDFD"> <td height="4" colspan="3"><img width=1 height=1 border=0 alt=""></td> </tr> </table> <br><br><br><br><br><br> <table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75"> <tr bgcolor="#FFFFFF"> <td align="left" colspan="2" height="48"><font face="Arial, Verdana, Helvetica" size="3" color="#000000"><b>  The requested application, AFW, is currently unavailable.</b></font></td> </tr> <tr bgcolor="#FFFFFF"> <td align="left" valign="top" height="48"><font face="Arial, Verdana, Helvetica" size="2" color="#000000"><b>  Details:</b></font></td> <td align="left" valign="top" height="48"><font face="Arial, Verdana, Helvetica" size="3" color="#000000"><pre>  No details available</pre></font></td> </tr> </body> </html></Trace>
  <Trace level="3" type="T">HTTP-client: closing...</Trace>
  </Trace>
  </Trace>
  </Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
  <Trace level="3" type="T">Persisting message after plsrv call</Trace>
  <Trace level="3" type="T">Message-Version = 007</Trace>
  <Trace level="3" type="T">Message version 007</Trace>
  <Trace level="3" type="T">Pipeline CENTRAL</Trace>
  </Trace>
  <Trace level="3" type="System_Error">Error exception return from pipeline processing!</Trace>
  <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!--  ************************************
  -->
  <Trace level="3" type="T">Persisting message Status = 014</Trace>
  <Trace level="3" type="T">Message version 008</Trace>
  <Trace level="3" type="T">Pipeline CENTRAL</Trace>
  </SAP:Trace>
very thanks,

Hi
  Check this blog & the SAP notes in it
/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
Regards
Vishnu

Similar Messages

  • 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

  • Principal Propagation - no checkbox in Sender/Receiver agreement

    My SAP XI version is NW04s SP11 (upgraded from sp09). I activated Principal Propagation in  RSXMB_CONFIG_PP (it's status is green) and made the settings according this blog:/people/alexander.bundschuh/blog/2007/01/16/principal-propagation-in-sap-xi , but there is no Principal Propagation checkbox in Sender/Receiver agreement of Integration Directory.
    Can anybody help me?
    SAPXIAF11P_1-10003482.SCA and SAPXIAFC11P_5-10003481.SCA were deployed, ABAP kernel patch level is 95.

    Did you import the SAP Basis Component in your IR after the Upgarede corresponding to your SP level in your IR?
    Regards
    Bhavesh

  • Principal Propagation with SOAP sender

    Hello
    I've already read some blogs and SAP help about configuring the principal propagation (PP), those blogs explains details about the configuration with SAP (ABAP and Java) system.
    However in my case I have the third party SOAP sender application. I jsut wonder how to configure or write the soap Java program. Basically 2 things need to be done for hte soap sender:
    1) Force the soap sender to send message along with a SAP assertion ticket
    2) Sign the assertion ticket with private key (Public key/certification will be installed in PI Java AE)
    I have no idea how step 1 works (Take Java soap client program as example)
    Once a private key / public key is generated, how to use it to sign the assertion ticket?
    Basically our soap sender could be from any platform (.net, java program, oracle, etc.), I need to know how to configure the soap sender for PP generally.
    Anybody configured PP for soap sender?
    Thank you so much

    Hi Jayson,
    With the amount of questions asked in one single question , i feel things are not clear at your end.
    i suggest you going through:
    Prinicipal propogation:
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/808d3048-638c-2a10-35a6-faa48e50ad59
    Principal Propagation in SAP XI
    /people/alexander.bundschuh/blog/2007/01/16/principal-propagation-in-sap-xi
    Configuring adapters for principal propogation
    http://help.sap.com/saphelp_nwpi711/helpdata/en/48/cf9e199bf23e49e10000000a421937/frameset.htm
    Regards
    joel

  • Principal Propagation SOAP Sender

    Hello,
    is it possible to use principal propagation for the following scenario:
    SOAP Sender (Basic auth) -> PI -> RFC
    so that the basic auth user from the incoming SOAP call is propagated to the RFC call
    br franz

    Hi Franz,
    Take a look at this: http://help.sap.com/saphelp_nw04/helpdata/EN/45/0f16bef65c7249e10000000a155369/frameset.htm
    Best Regards,
    Jose Nunes

  • "Ticket authentication failed" error in Principal Propagation scenario

    Hi All,
    I am working on Principal Propagation, where the scenario is sync RFC-PI-RFC. I have followed all steps mentioned in the below blog. When I execute the scenario (with Principal propagation box checked in the sender agreement) I get dump while executing the RFC from sender system. The dump is:
    "Ticket authentication failed"
    Scenario works fine if I don't check Principal propagation check box in the sender agreement.
    Principal Propagation blog: /people/alexander.bundschuh/blog/2007/01/16/principal-propagation-in-sap-xi
    Can anyone suggest what can be the reason for this dump?
    Thanks,
    Shweta.

    Hi All,
    Any inputs on this?
    Thanks,
    Shweta.

  • Avoid principal propagation in RFC_to_File scenario?

    Hi!
    I am facing with the following error in sxmb_moni by retrieving the message from business system A.
    Errror in part Call adapter
    System_Error: Error exception retnr from pipeline processing
    name = "CL_XMS_MAIN_WRITE_MESSAGE_TO_PERSIST"
    I also detected the following additional error text:
    <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.ConfigException: Unauthorized: J2EE AE rejected user. Reason: Principal propagation is not active, but technical IS service user was not used (J2EE_ADMIN).</SAP:AdditionalText>
    <SAP:ApplicationFaultMessage namespace="" /
    The error tell me that the principal propagation is missing.
    Unfortunately I cannot activate principal propagation on Sender system due to ABAP dump error.
    Question:
    Are there some alternative solutions without activating principal propagation?
    If yes hwo can these be realize?
    For example: is it possible to send messages as technical IS server user such as j2ee_admin from sender system without activating principal propagation?
    Any helpful information will be very appreciated.
    Thank you!
    Holger

    HI Holger
    Looking at the error we can see its authorization issue. You can try using user like PISUPER to create and use principal propagation
    Moreover other than this you have to go through normal RFC -> XI -> File procedure where you have different user involved at different services. No other choice
    Thanks
    Gaurav

  • SOAP to SOAP principal propagation with logon tickets

    I have configured a scenario using soap sender to soap receiver with an integrated configuration on PI 7.1. It is synchronous CE 7.11<->PI 7.10<->ECC 6.0. The scenario works with basic authentication. If I enable principal propagation on the sender side it still works fine. Now I have activated principal propagation on the receiver side and I get the following error in the message audit log:
    <p/>
    <pre>
    2010-05-07 09:01:50 Information MP: entering1
    2010-05-07 09:01:50 Information MP: processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
    2010-05-07 09:01:50 <b>Information SOAP: request message entering the adapter with user DAMZOG.JOCHE </b>
    2010-05-07 09:01:50 Information SOAP: request message leaving the adapter (call)
    2010-05-07 09:01:50 Information The application tries to send an XI message synchronously using connection SOAP_http://sap.com/xi/XI/System.
    2010-05-07 09:01:50 Information Trying to put the message into the call queue.
    2010-05-07 09:01:50 Information Message successfully put into the queue.
    2010-05-07 09:01:50 Information The message was successfully retrieved from the call queue.
    2010-05-07 09:01:50 Information The message status was set to DLNG.
    2010-05-07 09:01:50 Information Delivering to channel: SOAP_MRByID_In5_R
    2010-05-07 09:01:50 <b>Information SOAP: request message entering the adapter with user J2EE_GUEST</b>
    2010-05-07 09:01:50 Fehler SOAP: call failed: java.io.IOException: unable to get URLConnection: com.sap.security.core.server.destinations.api.ConfigurationException: [destination_0004] Unable to create URLConnection:No logged in user found.
    2010-05-07 09:01:50 Fehler SOAP: error occured: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: unable to get URLConnection: com.sap.security.core.server.destinations.api.ConfigurationException: [destination_0004] Unable to create URLConnection:No logged in user found.
    2010-05-07 09:01:50 Fehler Adapter Framework caught exception: java.io.IOException: unable to get URLConnection: com.sap.security.core.server.destinations.api.ConfigurationException: [destination_0004] Unable to create URLConnection:No logged in user found.
    2010-05-07 09:01:50 Fehler The message was successfully transmitted to endpoint com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: unable to get URLConnection: com.sap.security.core.server.destinations.api.ConfigurationException: [destination_0004] Unable to create URLConnection:No logged in user found. using connection SOAP_http://sap.com/xi/XI/System.
    2010-05-07 09:01:50 Fehler The message status was set to FAIL.
    </pre>
    <p/>
    Any ideas what could be wrong?
    Edited by: Jochen Damzog on May 7, 2010 9:02 AM
    Edited by: Jochen Damzog on May 7, 2010 9:06 AM
    Edited by: Jochen Damzog on May 7, 2010 9:22 AM

    The problem was due to the channels being not in the most recent state. A simple restart of the soap sender channel did the job.

  • Principal Propagation SOAP - XI - RFC Scenario

    Hi,
    I am developing a synchronous scenario whereby a SOAP request posted by a non SAP system should be forwarded to an ECC system using RFC. Challenge I am facing is that I want to use the user, which was used for basic user authentification to post to XI, dynamically in the RFC call. I have been reading about Principal Propagation using assertion tickets, however only SOAP receiver adapter is spoken about. I am trying to configure this using SOAP Sender adapter.
    As far as my understanding goes the sending system should be able to create these assertion tickets ?
    Has anyone developed a similar interface ?
    Scenario is: Non SAP SOAP Sending system = Client, Adapter engine = Server & Client, Integration Server = Server & client and Receiving ABAP system (ECC6.0) is Server.
    Any help would be appreciated and awarded if helpfull.
    Kind Regards, Jelmer Keuken
    Ps. XI is version 7.0 SP18, Alreay read the Blogs of Alexander Bundschuh
    Edited by: J. Keuken on Sep 9, 2009 4:04 PM

    Hi,
    This scenario is definately possible to implement with principal propagation.
    1. Enable the PP on Integration server
    2. Here you need not have to do anything on SOAP sender side to create the assertion ticket..
    The assertion ticket is required on SAP side which will act as Web AS ABAP Server.
    refer the settings --http://help.sap.com/saphelp_nw04/helpdata/en/61/42897de269cf44b35f9395978cc9cb/frameset.htm
    3. And then follow further steps as it mentioned the blogs...
    Thanks
    Swarup

  • Error to IDOC Sender

    Dear Experts,
    I have a requirement to send error information back to the IDOC Sender. The scenario is IDOC --> PI --> TargetSystem (ASYNCHRONOUS).
    If there is an error in processing within SAP PI, then the error should be propagated to the SAP system (IDOC), so that the Business can take note of the error.
    As far as I know, we can configure Alerts in SAP PI and in case of an error the recipient will get the alert message. But how to send the error message back to sender in case of an IDOC
    I do not want blogs on how to configure alerts in ALRTCATDEF
    Thanks.

    although I think you mean the person that triggered the IDoc, ie. someone who created a SalesOrder, which was then sent
    to PI.
    Yes, this is what is required.
    With this UserID you can do a lookup in the sender system, to retrieve the email-adress in the User Master Data record.
    Then use this email adress to send an alert,
    How exactly the lookup will be done? I have a message processing running in SAP PI, suddenly something goes wrong (lets say there is a mapping error) and the processing stops there. Now how to do a lookup (from where)? Configuring a fixed recipient in ALRTCATDEF wont work as we dont know who will trigger the IDOC!
    Any reference on how to perform lookup when message fails in XI/ PI will be helpful.
    Thanks.

  • Principal Propagation - Define interfaces button missing?

    Hi,
    I'm trying to configure PP in my PI 7.0 SP15 system with kernel version 146.
    I have completed all of the steps in the relevant guide but when I go to t.c. SXMB_ADM -> Configure Principal Propagation, there's no button/option for configuring interfaces for principal propagation as stated in the guide. Have I missed something?
    Regards,
    Gökhan

    Sorry, false alarm.
    This button is only valid in sender business systems, not the PI system and only needs to be configured for sender systems.

  • Principal Propagation Issue

    Hi,
    We are using PI 7.1 and have a SOAP - XI - ECC(RFC) scenario where we need to use Principal Propagation in order to send the user parameters who has invoked the webservice (using SOAP Adapter) on XI and the same user needs to be propagated to ECC system via RFC call.
    We did all the settings as per the guidelines setup in P.P guide. The issue here is once we enable Single Signon (P.P) on our XI server the local service user created in XI, which is given to Source system for invoking WS on XI stops working.
    In other words we have some other systems also which are sending webservice request to XI but with local service userid/pwd we have provided to them as they do not support Single Sign On. This stops working once we enable Single Sign On in XI. Does it mean at one time only one thing will work, either Service user/pwd or Single sign on user?
    Is there any alternate way of achieving the same? Has anyone used P.P feature? It does not seem to be working at Adapter Level.
    Thanks
    amit

    Dear Amit,
    Either of the one will work either SSO user or Service user . You cant have both working simultaneously. Because your SSO user is nothing but where one system logs on to another system using the user & pwd maintained on host system.
    The way out is to separate SSO user and Service users.
    Also refer https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/bc72b890-0201-0010-3a8d-e31e3e266893
    Rgds
    joel
    Edited by: joel trinidade on Mar 4, 2009 10:30 AM

  • Principal Propagation Issue - J2EE_GUEST being used in some messages

    Hi guys !
            I have the following situation, my customer have a SAP PI 7.1 Ehp 1 and, some interfaces are configured to run under Principal Propagation.
            What is occurring is, for an interface that uses principal propagation and works correctly, the message enters in PI using an authenticated user for principal propagation(for example, USER0001) and this authentication is propagated until the receiver system(eg, SAP ECC), but in some cases, this same interface shows the following behavior: the authenticated user USER0001 send a message, the message starts to be processed in the PI pipeline propagating this user but, when the message will be delivered to RFC Adapter, we receive the following error:
    Adapter Framework caught exception: failed to generate ClientPoolcom.sap.aii.adapter.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: could not create JCO Pool com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: could not get JCOProperties com.sap.security.core.server.destinations.api.DestinationException: [_DestinationServiceAuthorization1004] User-based destination service access denied to principal J2EE_GUEST. Assign the UME action Destination_Service_Write_Permission if the user should have the permission to save, update or remove destinations. The action is available already to the Administrator role.
          And after one message stop with the error above, any message of any interface using principal propagation starts to show the following error, that is only solved running a full cache refresh:
    Delivering the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: could not get functiontemplate from repository: com.sap.mw.jco.JCO$Exception: (106) JCO_ERROR_RESOURCE: Repository pool 'RfcRepository[RfcClient[RFCReceiverAutoCommit_ECC]]f0264787314535c0a27cf29d108f5860' does not exist or was removed..
          The question is, why do PI pipeline is trying to use J2EE_GUEST in some task for an interface configured to use Principal Propagation ? Why this occurs in some cases and not in anothers(for the same interface) ? Why the cache is being lost ?? And of course, how can I solve this annoyng situation ?
          All configurations needed to run Principal Propagation was done according the help.sap.com documentation(http://help.sap.com/saphelp_nwpi711/helpdata/en/48/a9bbb97e28674be10000000a421937/content.htm), and as I said, it works in most cases. All messages are sent using SOAP Adapter for the Sender System, and RFC Adapter for the receiver, and there are synchronous and asynchronous interfaces. Basically the interfaces that only read data from SAP, does not use principal propagation and, the ones that create/update/delete data in SAP, uses principal propagation.
          Somebody already saw something like this ?
          Thank you in advance, and best regards,
          Wilson

    Hi guys !
    I have continued with some tests in environment trying to understand what
    is happening and, I did the following, as the first error mentioned is
    "User-based destination service
    access denied to principal J2EE_GUEST. Assign the UME action
    Destination_Service_Write_Permission if the user should have the
    permission to save, update or remove destinations", I entered on UME Admin,
    created a new Role named J2EE_GUEST_ROLE, assigned the UME Action
    Destination_Service_Write_Permission to it, and assigned this new role to
    the user J2EE_GUEST, and ran new tests.
    After some executions, one message stopped with this error:
    Adapter Framework caught exception: error while processing message to
    remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException:
    could not get a client from JCO.Pool: com.sap.mw.jco.JCO$Exception: (101)
    RFC_ERROR_PROGRAM: 'user' missing
    I have observed that, in all messages that stops in error, we have the
    following line in Audit Log:
    Processing child message of multi-message with message Id
    000c2936-6a89-1ed0-aebe-c262ae7d412e.
    And this interface doesn´t have multi-message to be processed, is a
    single message only.
    I checked on configuration and see that the interface determinations for all interfaces has the flag "Maintain order at runtime", what is usefull basically when a Interface Determination has more than one interface,
    what is not my case, so I will unmark this flag in all interfaces and run
    new tests trying to identify if this solves the problem.
    Any idea for this annoyng issue ?
    Thank you and regards !

  • Principal Propagation / SAP Assertion Ticket

    Hi Experts,
    i m planning a synchronous scenario
    3rd party (SOAP) -> PI -> SAP ECC (RFC)
    PI is on 7.1, ECC on 7.00
    I would like to run Principal Propagation. At the moment i m struggling with Assertion Ticket to be issued by the SOAP sender. From [SAP Help: Princ Prop / Configuring the Sender|http://help.sap.com/saphelp_nw04/helpdata/EN/45/3418a0eabe072fe10000000a155369/content.htm]: "The SOAP client itself must be able to issue SAP assertion tickets."
    - Does that mean: if the sender is a non SAP system Principle Propagation cannot be implemented?
    - Or is there a way to issue the SAP assertion ticket from 3rd party SOAP sender?
    - If yes, how does that work?
    I found two interesting threads:
    [Principal Propagation SOAP - XI - RFC Scenario   |Re: Principal Propagation SOAP - XI - RFC Scenario]:
    I do not understand Swarups answer 100%. He wrote: "Here you need not have to do anything on SOAP sender side to create the assertion ticket.The assertion ticket is required on SAP side which will act as Web AS ABAP Server"
    Can anybody illuminate that? Is he right?
    [Issuing SAP assertion Tickets |Issuing SAP assertion Tickets]: The last post of Anthony stayed unansered, unfortunately. "How does the sender system do that? Is it somethign embedded in the header of the SOAP message? This really is unclear to me"
    Thanks for your help,
    Udo

    Hi Udo,
    > - Does that mean: if the sender is a non SAP system Principle Propagation cannot be implemented?
    Principle propagation supports XI, SOAP and RFC adapters.
    http://help.sap.com/saphelp_nw04/helpdata/en/45/0f16bef65c7249e10000000a155369/frameset.htm
    Before using the principle propagation you have to active the configuration, but you can only activate the configuration if you have kernel patch 149 installed.
    Regards
    Ramesh

  • Principal Propagation: User needs to be defined in PI???

    Hi All,
    We have a major SRM implementation using Principal Propagation(PP) for most of the interfaces. We are currently in design state. One of the things that were brought to my attention was that the user to be propagated from Sender needs to be maintained in both PI and Receiver System. As we have about 35000 users(Suppliers/internal Employees) that will be using the SRM funtionality. Does that mean i have to maintain all 35,000 users in PI also???
    Is there any other way that we can implement PP without creating these users in PI??? but create these in Receiver and Sender system only.
    Regards,
    XIer

    Hi ,
    I don't know much about PP, but was going through the [guide|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/808d3048-638c-2a10-35a6-faa48e50ad59?quicklink=index&overridelayout=true]
    which specifies that this model has weakness with respect to user credentials.(page4).
    When application users are propagated to the IS (ABAP proxies only), each application user must be maintained with the corresponding execution
    rights in the IS.
    I think  you might have  already referred this:)
    Regards,
    Srinivas

Maybe you are looking for