cancel
Showing results for 
Search instead for 
Did you mean: 

RFC WSDL file

Former Member
0 Kudos

Hi,

I have an SAP system which sends an RFC call to XI, XI sends that call to Database. Now I want to get a WSDL file , I tried this:

http://<sapserver>:<8000>/sap/bs/bsp/webservicebrowser/search.html.

But its gives '403 Not available error'. Can you please tell me how can i proceed with or without that?.

Can I proceed without the wsdl file of RFC for an RFC call?

Thanks in advance,

Raj.

Accepted Solutions (1)

Accepted Solutions (1)

former_member185846
Active Participant
0 Kudos

Hi Raj,

Check the following links for webservices.

/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi

Rgds,

Jothivel.

Answers (5)

Answers (5)

Former Member
0 Kudos

i have a similar problem kindly some help with it :

i have a following scenario.

WS Clinet <> XI <> RFC . The RFC i am using is RFC_CUSTOMER_GET ; it has two inputs ( Not mandatory) No. and Name. The Request and response is sent through SOAP. I used option in SAP Xi to generate WSDL where the URL is following format :

http://host:port/XISOAPAdapter/MessageServlet?channel=:<service>:<channel>;

i am using Altova XML Spy to generate and send SOAP request using the WSDL generated from the above process.

When i am sending soap request using XML SPY , i am getting prompt to enter to Uname and passwd. But right across i am getting the following error:

HTTP Error : couldnot POST the file : ‘/XISOAPAdapter/MessageServlet?Channel=:WS2RFC_BS:WS_Sender&Version=3.0&Sender.Service=WS2RFC_BS&Interface=http%3A%2F%2Fwww.prosoftgroup.com%2Fws2rdc%5ERequest_MI’ on Server ‘nemo.prosofthq.com’(500).

and then an exception is generated. :

SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

<SOAP:Body>

<SOAP:Fault>

<faultcode>SOAP:Server</faultcode>

<faultstring>failed to call the adapter engine</faultstring>

<detail>

<s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">

<context>XIAdapter</context>

<code>DeliveryException</code>

<text><![CDATA[

com.sap.aii.af.mp.module.ModuleException

at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:697)

at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:103)

..

..

..

---

Now while configuring SOAP Adapter i used BE mode and i have a receiver determination. i also checked over this URL manually using IE and after entering Uname and password i got status OK ?

Dunno where the problem is ? Please suggest

Vara

former_member181955
Contributor
0 Kudos

Hi Raj,

Have you executed this scenario, if so can you please give me settings required in SAP.

How have you executed this RFC?. Please let me know.

I have done this but while i am executing this RFC in SAP it is throwing exception called "CALL_FUNCTION_REMOTE_ERROR".So please let me know how you have executed this RFC.

Thanks

N.P.Babu

Former Member
0 Kudos

Hi Prasad,

I have not executed it yet. I am not sure when I will do that, since we have SLD import problem, we have to fix that first.

Best Regards,

Raj.

Former Member
0 Kudos

Prasad,

I done this. I got it successful. If you are not done yet, please feel free to ask.

Rgds,

Raj.

former_member181955
Contributor
0 Kudos

Yes , please let me know

Former Member
0 Kudos

Hi Raj,

The given Scenario specifies that you are trying to make an RFC call to XI. There is no need for a WSDL file for the same.

WSDL file comes in picture, when we use SOAP as message communication protocol. SOAP is a basis to make web service calls.

I suggest you to create a RFC sender adapter for your scenario.

http://help.sap.com/saphelp_nw2004s/helpdata/en/7f/edef4149c8c517e10000000a155106/frameset.htm

Regards,

Ajay.

Former Member
0 Kudos

Thanks all of you for your kind help. Please let me if you are not rewarded.

Best regards,

Raj.

Former Member
0 Kudos

Hi Raj -

If you're trying to push data out of SAP using RFC, you need to import the RFC metadata into the Repository. You do this by drilling into your SWC<b>V</b> and then under <b>Interface Import</b>, you'll see <i>Import of RFC and IDoc... Permitted</i> option. After that, fill in your connection data to the SAP system from which you'll retrieve it.

Aside from that, you need to set up your Sender RFC adapter... blog link below:

/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step

The link (http://<sapserver>:<8000>/sap/bs/bsp/webservicebrowser/search.html)

you're trying to access provides you with delivered RFCs exposed as web services. This typically involves the SOAP adapter. Sam very well describes this above.

Regards,

Jin

Former Member
0 Kudos

How do we expose an RFC as webservice to be avilable as wsdl from R/3 system that I want to make an RFC call?. I have a tutorial with me which exactly fits into my scenario, thats why I want to know how do I expose RFC as Web Service?. Which host should I use, is it XI one or R/3 system?

Thanks Jin.

Best regards,

Raj.

Former Member
0 Kudos

Hi Raj -

Couple of options:

1. Expose the RFC as a service directly from the R/3(or other SAP app system), you need at least WebAS 6.20 or above. The RFC should be Remote-enabled in the Attributes. Then you can get the WSDL for it by accessing the following link corresponding to your R/3/SAP app host:

http://<hostname>:<port_number>/sap/bc/bsp/sap/WebServiceBrowser/search.html?sap-client=<relevant_cl...;

Be sure to include the client and use a fully-qualified hostname.

With this option, assuming a web service client, you should be able to call the RFC as a web service directly or via XI (sender/receiver SOAP adapter). You can still use the receiver RFC adapter, of course, but then you wouldn't be asking for the WSDL.

2. If the RFC is developed on a SAP basis 46D system or below, it cannot directly be called as a web service from a web service client. XI has to "front" as the web service for the RFC. In this case, it would be a a SOAP->XI->RFC scenario only.

>>><i>Which host should I use, is it XI one or R/3 system?</i>

For your particular case here, given that you have a WebAS 6.20 or above system, the WSDL is available on the R/3 host.

Regards,

Jin

Former Member
0 Kudos

Do I need any extra setups for that? I got the errors:

Service cannot be reached.

Note

The termination occurred in system SBU with error code 403 and for the reason Forbidden.

The selected virtual host was 0 .

Thanks-a-lot Jin.

Warm regards,

Raj.

Former Member
0 Kudos

raj , this is vara, you could even expose the same as webservice using soap adapter and then publish wsdl from option in integration directory (define webservice to get wsdl) i am doing a similar scenario but i am getting some errors i also posted. lemme know.

Vara

Former Member
0 Kudos

Hi Raj -

Probably services in txn SICF (in R/3) have to be activated. Definitely the following and others:

default_host->sap->bc->soap->rfc

Probably need others. Looks like the WebServiceBrowser one is not directly listed. But at least try activating the one above if not already.

Also, make sure you're using the ABAP/ICM http port. You can confirm this in txn SMICM, then Goto->Services.

Regards,

Jin

Message was edited by: Jin Shin

sam_raju
Contributor
0 Kudos

Hi Raj,

You can generate the WSDL file from XI Itself. Finish your integration Scenario and in the IR Go to Tools-->Define Web Service and specify all the parameters to generate and save the WSDL to a local file.

But make sure you specify the URL for Web Service as follows:

In the Step “Specify the URL of the Web Server” of the Define Web Service Screen, specify the URL. The inbound address for SOAP Message should be http://host:port/XISOAPAdapter?MessageServlet?channel=party:service:channel

Under party:service:channel enter the party name, the service name, and the name of the communication channel. If no party has been created, enter the following: channel=:service:channel

Note: For more details on this topic, refer to help.sap.com documentation at the following URL http://help.sap.com/saphelp_nw04/helpdata/en/fc/5ad93f130f9215e10000000a155106/content.htm

Rgds,

Sam Raju