RFC destination Java => ABAP system to wrong system

[Former Member]

Hello everyone,

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?

Regards,

Cornelia

[Former Member]

Hi,

First of all you should always use fully-qualified name.

Secondly this RFC is of type 3 so you should provide the the URL for the messahe server along with the router information.

This should be able to help you.

Regards and reward with suitable points if helpful

[Former Member]

Hi Mantosh,

it's an RFC connection entered in Visual Administrator of the Java System (service Destinations), so there's no possibility to set an RFC type like in SM59.

Of course you're right concerning the hostnames, but I was wondering how that could happen. Normally, it should read the data which I configured in the RFC connetion and use that.

We deleted temporary files and cookies and all from the workstation were we started the browser, even rebooted the workstation, but no effect.

Do you know any cache were the java system could have the old data left?

Regards,

Cornelia