Clarifications on JCo Destinations

[Former Member]

Hi All,

I need some clarifications on the Jco destination concept..i tried to create a simple WD Java application that retrieves info from ECC by calling an RFC. I created and maintained the JCo destinations. the scenario at the dev system is as follows:

I was informed that java was installed or points to client 001, and im trying to pull data from rfc on client 800. In this case, the Jco destination for application data should be configured for client 800.

But what should be the client for the rfc metadata JCo destination? i tried configuring for both 800 and 001 and both worked, so im a little confused here..

Also, how can i determine which client does java point to? In addition, i dont understand why does java have to point to only 1 client? the same is not true for the abap engine.multiple clients exist on the abap engine..so why not for java? also, would there not be a scenario on portal where i have multiple applications retrieving data from multiple clients of the same ECC backend?

I'm quite confused on this and hv had no leads on explaining the above,..would really appreciate if anyone can answer some of my doubts here..thanks in advance!!

[Former Member]

Hey novice both the metadata and modeldata destinations has to point to the same client number.As metadata holds the information about the data(dictionary data)and modeldata is going to hold the actual data so they have to point out to the same client numbers.In ECC data may be client dependent or independent..if its client dependent then if you are providing metadata and modeldata of 2 different clients then how will you get the data from the ECC.You can create any number of logical systems to any clients but the thing is you must have proper credentials on the ECC system as well as on the EP server too.Becoz these clients will be created and maintained by the basis people.These destinations are used only when communicating with SAP system only(Like ECC).