cancel
Showing results for 
Search instead for 
Did you mean: 

Calling Remote enabled Function module in java using RFC Destination

former_member236708
Participant
0 Kudos

Hi

We are on Portal 7.3 ehp1 sp9.

Steps followed are :

RFC Destination called “SAP_RFC” has been created as below :

Configuration -> Destinations -> RFC Destinations

Connection and Transport:

-------------------------------------

Load balancing :Yes

Provided : SystemID / MS Server / MS Server Service / Logon Group / Gateway Host / Gateway Service

SNC : Inactive

Logon Data:

------------------

Authentication : Current User (Assertion Ticket)

Language : EN

Client : XXX

Repository Connection:

-----------------------------------

Destination Name : This Destination

Specific Data:

----------------------

pooled Connection Mode : Yes

Max : 5

Size : 10

Max. wait time : 10,000

Ping Destination results : Successfully connected to System XXX as per user XXXXXXX.

JAVA Code as Follows:

JCoDestination destination = JCoDestinationManager.getDestination("SAP_RFC");

//destination.ping();

JCoRepository repository = destination.getRepository();

JCoFunction function = repository.getFunction("FM_NAME");

function.execute(destination);

Lines highlighted in RED color throwing an error as below :

{"ERROR":"Initialization of destination JCO_RFC failed: Incomplete logon data. on <SID> mshost <MS_HOST>/ com.sap.conn.jco.JCoException: (103) JCO_ERROR_LOGON_FAILURE: Incomplete logon data. on SID mshost MS_HOST"}

And found that no COOKIE with the name “SAP_SESSIONID_<system>_<client>” was not found, I am afraid that “Assertion Ticket” was not created in above scenario.

To confirm SSO configuration working, i have followed below steps:

1) Created System Object pointing to R/3 and tests were successful for authentication type "SSOLOGONTICKET / ASSERTIONTICKET"

It's J2EE application, no references or any other additional configuration been made part from above.

Any help ?

Thanks

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member236708
Participant
0 Kudos

Here is log ..Assertion ticket could not be retrieved. Error was null

Log Record Details

Assertion ticket could not be retrieved. Error was null

Single Click Filter by SeverityNegative Single Click Filter by SeverityError
Single Click Filter by DateNegative Single Click Filter by Date2014-04-23
Single Click Filter by TimeNegative Single Click Filter by Time20:28:26:056
Single Click Filter by CategoryNegative Single Click Filter by Category/System/Security/destinations
Single Click Filter by LocationNegative Single Click Filter by Locationcom.sap.security.core.server.destinations.service.AssertionTicketRetriever
Single Click Filter by ThreadNegative Single Click Filter by ThreadSystem [2]
j2ee/cluster/server0/log/system/security_00.log
Single Click Filter by Passport User Activity IDNegative Single Click Filter by Passport User Activity ID3a7af5ddca8b11e384bd8adb6f484d33
Single Click Filter by Time ZoneNegative Single Click Filter by Time Zone+0800
Single Click Filter by Customer Message ComponentNegative Single Click Filter by Customer Message ComponentBC-JAS-SEC
Single Click Filter by Runtime ComponentNegative Single Click Filter by Runtime Componenttc~sec~destinations~service
Single Click Filter by Correlation IDNegative Single Click Filter by Correlation ID3643650000002747
Single Click Filter by Passport SessionNegative Single Click Filter by Passport Session3A7AF5DDCA8B11E384BD8ADB6F484D33
Single Click Filter by Passport ConnectionNegative Single Click Filter by Passport Connection3a7af5ddca8b11e384bd8adb6f484d33
Single Click Filter by Passport Connection CounterNegative Single Click Filter by Passport Connection Counter0
Single Click Filter by Log IDNegative Single Click Filter by Log IDC0000AD01D7B002200000EA5009800B2
Single Click Filter by HostNegative Single Click Filter by Hosthost
Single Click Filter by SystemNegative Single Click Filter by SystemXXX
Single Click Filter by InstanceNegative Single Click Filter by InstanceJ00
Single Click Filter by NodeNegative Single Click Filter by Nodeserver0
hemanth2
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Mohan,

Hope you are doing good.
The error shows that the parameters are missing. can you check the parameters with the backend details. If teh issue persists, enable the JCo trace (to level 5) as per note 628962. Check:

<https://wiki.sdn.sap.com/wiki/display/SI/Java+Connectivity>

(check JCo trace activation via Java system properties)

Thank you and have a nice day :).

_____________

Kind Regards,

Hemanth

SAP AGS
 

former_member236708
Participant
0 Kudos

Thanks for your reply.

Ping Destination results : Successfully connected to System XXX as per user XXXXXXX.

If anything missing / wrong, test would fail right ?

Before i proceed further, i would like to know whether the approach is correct or not ?

You can see above, an error message from trace file.

Error message from jco_rfc file : RfcGetException rc (7) message: Incomplete logon data.

Message from log viewer under NWA : Assertion ticket could not be retrieved. Error was null


Thanks

hemanth2
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Mohan,

I remember such an issue with a previous customer. There is a known issue with the assertion tickets. Please see note 1754939  No logged in user exception. Also, due to the intertwined dependencies, it is highly recommended  to deploy the latest patches for the other SCAs as well mentioned in note 1794179 when you do a SCA upgrade. Deploy using any tool mentioned in sap note 1715441.

___________

Kind Regards,

Hemanth

SAP AGS

former_member236708
Participant
0 Kudos

Hi

Error: Assertion ticket could not be retrieved, Error was null.

Info : Returned Destincation JCO_RFC, type RFC to user <Unknown User>.

Thanks

hemanth2
Product and Topic Expert
Product and Topic Expert
0 Kudos

Great, is the issue resolved then and was the issue with the s_rfc authorizations?

former_member236708
Participant
0 Kudos

Hi

Nope, not yet resolved.

It could not be authorization issue, because changing RFC Destination from "Assertion Ticket" to "Logon Method" works fine and FMs being called successfully.

Problem is when we set "Assertion Ticket"

Still finding for solution.

Thanks for helping ..

hemanth2
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi,

Then please apply the note 1754939 as i mentioned earlier. there is a bug that was found sometime back and should help in this case.

regards,
Hemanth

former_member236708
Participant
0 Kudos

Hi

Here is reply from our basis team, saying that note 1754939 is not applicable.

The component versions in the note does not apply to our system (ours is 731, not 711). Furthermore, we are already at the latest patches for SP9 (patches are current as of 14.04.2014).


Thanks

akash_ahuja
Explorer
0 Kudos

i am facing the same issue, can you please tell me the solution.

Regards:

Akash Ahuja

former_member236708
Participant
0 Kudos

Nope, I am still having that issue.

former_member1191927
Participant
0 Kudos

Were you able to find a solution for this issue? I am having the same issue. Any help is appreciated.