More technical info on registered program ID and RFC sender

[Former Member]

Hi All,

I was configuring the RFC sender adapter performed the following steps and everythings looks fine.

1. Enter information like, gateway host, gateway service which you can find using transaction smgw.

2. Select Registered Program Id option button and enter any string as a program id.

3. Now go for configuring communication channel. Provide same parameters for Gateway, Gateway Service and Program Id.

Provide rest all required info like application server, system number, user name , password etc.

4. Now activate your communication channel.

5. Go back to your RFC Destination and now test your connection. It should be working.

Before testing your RFC destination, don't forget to ACTIVATE your communication channel.

But Iam curious to know some more detail,

The RFC destination of type T , pointing to itself (saphost and gateway pointing to itself) and if it is tested the RFC it gives me an error that the program ID does not exists.

But only after I have configured the RFC sender comm channel, and then test on the above created RFC , it works..!!!!

Could any of the experts help me what actually happens in background.

i have referred to Shabarish Vijayakumar & Michal Krawczyk, blogs but could not find more details on this..!

many thanks!

Regards

Edited by: gururaj ravindra on Oct 9, 2009 12:34 PM

[former_member187339 · Accepted solution]

Hi Gururaj,

>>The RFC destination of type T , pointing to itself (saphost and gateway pointing to itself) and if it is tested the RFC it gives me an error that the program ID does not exists. But only after I have configured the RFC sender comm channel, and then test on the above created RFC , it works..!!!!

I think I didn't get your question completely. Are you asking that after creating the RFC Destination (pointing to XI) you tried testing it and it got failed (with the program id error) and then when you made the RFC Sender channel it got successful??

Is this the question? If yes then when you created a RFC destination with a Program ID and tried testing it, it failed because there was no listener configured to listen the requests coming from this Destination

When you created the RFC Sender channel, that listener came into existence and the test got successful

Regards

Suraj

[Former Member · Accepted solution]

Thanks for your explanation, was quite helpful..!

Referring to listeners , what actually happens internally when I provide the Program ID in RFC sender comm chan and activate it. Does it open any Jco connection on the PI server?

Like the way we have to define the RFC LCRSAPRFC & SAPSLDAPI in abap stack n then create corresponding Jco in PI Java stack?

Many thank again!

Guru

[former_member187339 · Accepted solution]

Hi Guru,

>>Referring to listeners , what actually happens internally when I provide the Program ID in RFC sender comm chan and activate it. Does it open any Jco connection on the PI server?

Yes it opens a jco connection check this hlp.sap link too

http://help.sap.com/saphelp_nwmobile71/helpdata/en/d1/6a6f3a55c1404cb24e37fb9bb22011/content.htm

We reuire these RFC detination for our interfaces to run. But ABAP stack of PI requires some more RFC destinations which they use to connect with SL and Java stack. they are the LCRSAPRFC, SAPSLDAPI, AI_RUNTIME_JCOSERVER, AI_DIRECTORY_JCOSERVER

Check this lnk to know what each RFC connection does

http://help.sap.com/saphelp_nw2004s/helpdata/en/be/6e0f41218ff023e10000000a155106/content.htm

Regards

Suraj

[prateek · Accepted solution]

As soon as you activate the sender channel, the channel information is moved to PI CPACache. From there an RFC call is made to the SAP system having the same Program ID. SAP Gateway then search within its registration list for the same Program ID. If found, the communication setup gets completed and the route is used whenever there is call of RFC destination using the same Program ID.

Regards,

Prateek

[Former Member · Accepted solution]

Hi Prateek/ Raj,

Thanks for the explanation!

So this means a JCO destination is automatically created in the PI stack , and is visible in NWA ?

Correct me if wrong!

regards

guru

[Former Member]

Hi,

Your analysis clears say that

1. There should be two progids one is server and other is client

in your case you have created progids ,but not established the connection between server and client

i.e R/3 (server)and PI (client/listener)

as a result you got the error

2 .once you have established the connection using CC then R/3 server identified the listeners with the help of established connections through gateway monitor..

As a result green ..success...

HTH

Rajesh

[Former Member]

This question (about the Program Id ) has been discussed in the forum many times

please refer this

and this