on 08-26-2008 7:57 PM
we followed the documentation from OSS Note 974873 and the blog Principal Propagation in XI from Alexander Bundschuh.
we already successfully configured principal propogation for PI 7.0 Soap Adapter and R/3 4.6C.
Now we are configuring principal propogation between PI 7.0 Soap Adapter and ECC6 SP14 RFC Adapter.
We are getting the following error:
com.sap.aii.af.ra.ms.api.DeliveryException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: could not get a client from JCO.Pool: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Assertion ticket received is not meant for this system
Please suggest if anyone has already done this
Srinivas
Please check if note 1159962 is applicable for your landscape.
KK
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you very much for your response.
The Note specified is not relevant for our issue. we do have the ume.configuration.active=true for CreateAssertionTicketLoginModule.
we are importing Client side (PI) Java Certificate, ABAP Certificate to Server side (ECC) and ECC ABAP Certificate to PI.
1. Is there any difference between R/3 4.6C and ECC 6 in the way they interpret the certificates. (because in ECC 6 there is an additional option to specify Binary, Base 64 format of the cert file while importing)
we looked at the default trace and xi log and st11 dev_rfc trace. Is there any other way to get additional trace information on the Error: Assertion ticket received is not meant for this system
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.