JCo 3rd party client - PI RFC Receiver - TP FOO not registered

[szymon_bolek]

Hi there PI-PO gurus!

In order to test the following scenario:

JCo 3rd party client -> SAP PI -> SAP R/3

i have created a local JCo Client in Java with the following FOO.jcoDestination file:

jco.client.type=E
jco.client.gwhost=SAP-PI-HOST

#instance is 00

jco.client.gwserv=sapgw01

jco.client.tpname=FOO
jco.client.user=MY-USER-ID

jco.client.passwd=MY-PASSWD

jco.client.snc_mode=0
jco.client.snc_partnername=SNC-STRING

jco.client.snc_qop=9
jco.client.snc_lib=C:\\Program Files (x86)\\SAP\\FrontEnd\\SecureLogin\\lib\\secgss.dll

I am starting the client using

JCoDestination destination = JCoDestinationManager.getDestination(FOO);

where FOO points to FOO.jcoDestination file.

It gives me "TP FOO not registered"

I also created an RFC Receiver in the SAP PI with:

Application Server (Gateway): SAP-PI-HOST

Application Server Service: sapgw01

Program ID: FOO

Do you have any suggestions for me, what might be wrong? Maybe there is something else in the PI to be configured?

Or maybe you have already some step-by-step guides for such scenarios?

thank you & best regards

simon 🙂

[szymon_bolek · Accepted solution]

Here is what worked:

Scenario: 3rd party JCo Client (jco 2.1.10) -> SAP PO Single stack 7.4

jco.properties

jco.client.type=E

jco.client.gwhost=<sap-po-host>

jco.client.gwserv=<sap-po-gateway> e.g. sapgw01

jco.client.tpname=FOOBAR

RFC sender channel:

Application server: <sap-po-host>

Application server service: sapgw01

Program ID: FOOBAR

in Advanced Mode uncheck Verify Sender System

"RFC Metadata Repository Parameter" of SAP R/3 MUST be valid, so channel is activated.

cheers

simon 🙂

[iaki_vila]

Hi Szymon,

You need to create the sender agrement and  the sender RFC channel with the program ID set and to activate these objects before to test the connectivity.

Regards.

[szymon_bolek]

Hi Inaki,

I am terribly sorry, yes I meant the sender RFC channel is there, not the receiver (as i wrote previously). Yes I did that and activated them objects fine. So, any other suggestions?

It seemes in the whole SCN there is NO single scenario like this?! How this is possible?

Or this is so obvoius, that noone really has any problems with JCo third party connections to SAP PI/PO.

thank you & best regards

Simon 🙂

[Former Member]

You need to register the program Id FOO in sap pi. To do that you have yo Create rfc destination

[szymon_bolek]

Alberto, thank you, but what exactly I would enter in rfc destination for 3rd party jco client, which is my local computer at the moment? Could you elaborate?

br

simon 🙂

[Former Member]

Check if you have register your program ID in SAP PI. I do not know if you have single stack or dual, anyway:

dual stack: execute SMGW---Go to---Logged on Client. Check TP Name column, it must be your Program Id (the same that you put in your RFC Sender channel)

Single Stack you can check the program ID directly in Comunication Channel monitor.

[szymon_bolek]

Alberto, thank you, it is a single stack. You mean Program ID in Communication Channel. It is maintained and .jcoDestination has the same

jco.client.tpname=FOO

So, that matches so far.

cheers

simon 🙂