JCO example for extern-extern-rfc communication

[Former Member]

Hi all,

a while ago i asked how to realize extern to extern rfc communication with jco 3.0:

At the time of posting this wasn't possible.

Now since jco 3.0.11 this feature has been added to jco.

Unfortunatly i'm unable to find a simple example for this.

I need help to get a connection to external rfc programs (in old RFC C SDK i use this settings: Type E, with GWServ, GWHost, TPNAMe and TPHOST).

Does anyone have a hint or a small code example?

thx a lot

[MarkusTolksdorf · Accepted solution]

Hi Tom,

You need to

specify the following parameters for your destination in order to communicate with some other non ABAP system:

jco.client.type=E

jco.client.gwhost=<host of gateway, on which RFC Server program is registered>

jco.client.gwserv=<service of this gateway>

jco.client.tpname=<program ID of the registered RFC server

jco.client.repository_destination=<destination from which to read metadata if needed>

However, only scenarios that are supported for such a setup are mentioned in note 756754.

Best regards,

Markus

[Former Member · Accepted solution]

Hi Markus,

thank's a lot for your reply.

My Problem is that i can't establish a second connection. So setting param jco.client.repository_destination ist not possible.

In the meantime SAP has stated this as a bug in JCO an is working on a hotfix.

Best regards,

Tom

[MarkusTolksdorf · Accepted solution]

Hi Tom,

the fix is ongoing, I know.

Best regards,

Markus

[Former Member · Accepted solution]

Hi Markus,

of course you know

As i'm really wainting for the fix, can you predict time til it is finished?

Just as a mark.

Will it be closer to two weeks or two month or is release half a year away?

Best Regards,

Tom

[MarkusTolksdorf · Accepted solution]

Hi Tom,

I guess you know that for legal reasons there are no timelines to communicate.

Best regards,

Markus

[MarkusTolksdorf · Accepted solution]

Hi,

One small correction: jco.client.type=R is the better choice as you need to connect to a registered server. E will also work, but will be adopted to R by JCo internally.

Best regards,

Markus

[HAL9000 · Accepted solution]

Hi Markus,

it is also allowed and even recommended in the JCo documentation not to specify the parameter jco.client.type at all. It will be determined and set automatically according to the other specified logon properties.

Best regards,

Stefan

[Former Member · Accepted solution]

Hi all,

thx for your assistence.

Best regards,

Tom