RFC destination Java => ABAP system to wrong system
I have a NW04 Java system (WebAs 640, SP19), which has an RFC destination to an ABAP system.
The strange this is this: we changed the target system of the RFC connection to a different one (let's say from SID1 to SID2), they have different system numbers, different host names and different gateways. Only user and password we kept the same, as that's easier to maintain.
We have a self developed java application which uses this RFC connection.
When we call the application using only the <b>not</b>-fully-qualified hostname the RFC connection to the old (SID1) is used, but the destination is defined with SID2.
However, when we use the fully qualified hostname in the URL, it works with SID2 (which is correct).
Does anyone have an idea why that happens and what we can do to prevent that?