on 12-18-2014 4:36 PM
Hi all,
We have a WDJ application which is failing because there's a problem with a destination to access ABAP RFC.
The WDJ app is using a JCO named ZWD_MODELDATA_DEST, this JCO uses SSO as authentication method. A test on this JCO results successfull "JCo destination 'ZWD_GV_MODELDATA_DEST' was sucessfully tested with user 'GMAYORGA'".
Through NWA -> Configuration -> Destinations, we defined an RFC destination named ZWD_MODELDATA_DEST (same as JCO) and this destination uses "Current User (Assertion Ticket)" as authentication method. Doing a ping to the destination we get the error message "Error during ping operation: Initialization of repository destination ZWD_MODELDATA_DEST failed: System received an expired SSO ticket on gala.empresasyv.com sysnr 00".
Looking for a solution I changed the destination's authentication method to "Technical User" with this both the ping to the destination and WDJ app worked successfully. So the problem is with the destination.
On the other two enviroments (QAS and PRD) the configuration is the same and the app doesn't fail. All the portal landscape is on NW 7.4 SP06 and has patched the same components on the same version.
Best regards,
Gregory.
Hi Gregory, For fixing the issue, maintain the JCO destination in the location below: Go to http://:/nwa - Configuration - Destination and create new and give the ZWD_MODELDATA_DEST and WD_METADATA_DEST. Once done it will fix the issue. Hope this helps. Cheers- Pramod
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Pramod,
The destination ZWD_MODELDATA_DEST (named same as JCO) was already created and is the one with which the ping fails.
Also both the JCO and Destination named ZWD_RFC_METADATA_DEST were already created with "Technical User" as authentication method and both test/ping fine.
Regards,
Gregory.
Hi Pramod,
On my first post I said "Through NWA -> Configuration -> Destinations, we defined an RFC destination namedZWD_MODELDATA_DEST (same as JCO) and this destination uses "Current User (Assertion Ticket)" as authentication method." so yes, the authentication method I used to configure the destination is Current User with assertion ticket.
The following image shows the error occurred when I do a ping to the destination:
Best regards,
Gregory.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
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.