RFC connection error

[Former Member]

hi experts,

trying to create an inbound rfc connection into SAP system. with a registered server program and program ID , along with the gatewayhost n service .....but when i test the connection it says that

Logon -- cancel

error details - connection closed [no data ]

we confirmed that their gateway is up and running

My question is , do we have to register the program Id what was provided by the third party . in our SAP sys by our basis team.

if it has to be registered .where shuld it be done by basis

I appreciate ur look into this

thx n rgrds

ganga

[Former Member]

Im trying to do this in the R/3 system to connect to an external system, plz go through the error ive posted...

logon -

---

cancel

error details ---connection closed [ no data ]

Edited by: N.Ganga on Nov 23, 2010 10:05 AM

[former_member207622]

Yes for the sender system you need to g register the program and the same PROGRAMID we have to give in sender RFC channel

To register the program login into the OS level as sudo su u2013 <sid>adm and execute the following command.

rfcexec u2013g<program id> -a<gateway host name> -x<gateway service>

rfcexec is the server program name, the <program id> can be obtained from SM59, it is case sensitive and should match with the entry in SM59. The <gateway host name> and <gateway service> can be obtained from the transaction SMGW. When this command is executed it goes to a hanging loop.

The connection will fail once this command is terminated or the user executing this command logs off

To avoid this, instead of using the above mentioned command an entry should be made in the file saprfc.ini

To do this, execute the following command

sudo su u2013 <sid>adm

rfcexec u2013D<destination name>

<destination name> is the RFC destination name in SM59

So now we are done with registering the server program, but how do we check it is registered, once a server program is registered it is displayed in the Logged on clients in SMGW.

In transaction SMGW choose GOTO-> Logged on clients. There should be an entry for the server program in the screen that is displayed with system type Registered_TP (which indicates that the program is registered)

[Former Member]

Go to sm59 and check out if your RFC is still running. This might be the problem.

[Former Member]

this is a connection of SAP R/3 syatem to a third party biztalk server , and what are the inputs that we have to take from the third party who is totally unaware of the sap system....and any role of basis in this ...

[former_member207622]

SInce this is aconnection to third party , Do we have PI here in our landscape as middleware ?

Or you are trying to do a direct connection to biztalk ?

If PI is there what the bIztalk people require , Do they require File as in taget or webservice ?

whenever configurations are going to get created BASIS team will be required

Please specify your requirements

regards

Ninad

[Former Member]

Hi Ninad,

The third party wants to connect throught the PI or webservice...wht if they chose PI and wht if they chose webservices

[former_member207622]

Process integration provides the infrastructure for business applications, that run in distributed systems. Process integration acts as the messaging middleware for service communication(both SAP and Non-SAP), connectivity, transformation and portability.

Applications can also be connected directly with Web services (including the Web Service Reliable Messaging standard).

Its a Pretty good option for communication between an SAP and Non SAP application systems, we can attain this by the adapters provided by PI.

So If PI is choosen as a middleware by your clients then we have three types of scenario possible

RFC /Proxy/IDoc -

---

>>> PI -

---

>>>> Webservice/ File / JDBC

So confirm with your client what they wish to have at there side , web service or file or direct updation of there database through JDBC

Depending on their reply we can suggest the scenario to be build In all the three cases we have adapters in PI to take care of receiver message format

Hope this helps

Regards

Ninad

[Former Member]

Hey Ninad,

I really appreciate the quick updates from you. The scenario here is they are trying to movie their entire model into our landscape so what ever this connection we are trying to do is a one time connection and after migrating all the data or the models into our system or SAP there is no need of the connection for the transactions any further.....so there is no mapping part also . once the connection is established then everything will be parked into the our SAP system. we thought of establishing an RFC connection with the biztalk server [outbound] and as it is going to be an inbound [ SAP ] system. while doing they gave an program ID , sap gateway host and a gateway which when we are trying to do is throwing an error of connection closed or no data. they say the gateway is open .ive seen in the SMGW monitoring where ive havent found the gateway given in the RFC connection.so do we have to register in BASIS. thanks for ur patience

rgrds

Ganga

[former_member207622]

If I understood correctly now ? your Biztalk will be sender and SAP will be the receiver system

Now I am not sure how will you integrate the two without any mappings as you said .

Since SAP will have different data structure and Biz talk will have differnt data structure that is why te gateways provided by them will not be able to point to SAP directly

You will have to have some middleware which will consume the biz talk web service and then through transformation into RFCdata format it will pass the data to SAP

Design a webservice >> PI >>> RFC scenario , Dont use any gateways or anything from Biz talk directly because it will not be understood by SAP

If you follow this approach , you dont need any RFC connections and the program Id registration

Hpe this helps

Edited by: Ninad Sane on Nov 23, 2010 12:56 PM

[Former Member]

thnx folks

Edited by: N.Ganga on Dec 5, 2010 9:22 AM

[Former Member]

Hi Ganga,

Not required to register the program ID.

It creates the connection automatically based on your receiver RFC adapter's parameters. it works on the same concept as when you try to import any IDOC or RFC in your Integration Repository. If you remember you just give the IP address, system ID, user name & password there and it connects to respective R3 system automatically to import the IDOC or RFC.

http://help.sap.com/saphelp_sm40/helpdata/en/b3/05a63babb49547e10000000a114084/content.htm

Thanks,

[former_member207622]

I believe you dont need to create that

regards

Ninad