| Home • Tips • Tutorials • Sample Specs • Certification Q's • Interview Q's • Jobs • Testimonials • Contact Us | ||
Document Categories:
Email a FriendWhat's New?
Contribute?What's Hot? |
Publishing Interface as Web Service (Web Service to RFC)By Neeraja Surapaneni, YASH Technologies This step-by-step document describes how to publish the
Interface as web service from XI. Business
process: In this example we are publishing
outbound interface as web service. When the interface is defined as web service
in the Integration directory, it will generate a WSDL document. Using this WSDL
we can create SOAP request with the help of third party tools like XML SPY or
Microsoft InfoPath. When this SOAP request is send to the XI system it will
invokes the RFC “ZSYNCGETSFLIGHTDET_E6S_800” in SAP R/3 system and this RFC
returns the response back to the SAP XI. The SAP XI collects the response and
maps to the WSDL response, which in turn is sent back to third party system XML
SPY or Microsoft InfoPath. About RFC The RFC
“ZSYNCGETSFLIGHTDET_E6S_800” when executed on E6S system client 800 with
import parameters CONNID and CARRID checks whether the combination exist in SAP
database table SFLIGHT or not? If the combination exists then it will return
FLAG as ‘0’ otherwise returns FLAG as ‘4’. 1.
Create
RFC in the R/3 system First we need to create the RFC
ZSYNCGETSFLIGHTDET_E6S_800 in R/3 system with import parameters as CONNID,
CARRID and export parameters as CONNID, CORRID and FLAG. Go to Transaction SE37 to create
RFC.
2.
Design
the interfaces in Integration Repository Start up the home page of the
Exchange Infrastructure Tools using transaction SXMB_IFR. Click on the
Integration Repository under Integration builder. 2.1
Import
RFC:- Import the RFC that we have created in the above step from
the corresponding R/3 system. To import RFC right click on RFC’s which is
under the Imported Objects under the Software component version.
When
we import RFC’s we will get both Request messages and Response messages. This
imported RFC can be used as Message Interface.
2.2
Define
Request and Response Data Types:- Define a new data types for each
Request and Response messages of imported RFC. The
structure of Request data type should resemble Import parameters of RFC
The
structure of Response data type should resemble Export parameters of RFC.
2.3
Define
Request and Response Message Types:- Create
Request Message Type by encapsulating Request data type.
Now
create Response Message Type by encapsulating Response data type.
2.4
Create
outbound synchronous Message Interface We
are going to publish this Outbound
Message Interface as Web service in Integration Directory. Once we define this
interface as web service it will generate WSDL file. Using this file we can
create a SOAP request using third party tools like XML SPY or Microsoft Info
path.
2.5
Create
Message mappings Here
we need to create two message mappings, the first mapping is between Request
message type and RFC Request message and the second mapping is between RFC
Response message and Response message type. Request message mapping
Response
message mapping
2.6
Create
Interface mapping As
the Interface is Synchronous it will ask for the Request and Response
Activate
all the changes by clicking on Change lists tab.
|
|
|
Please send us your feedback/suggestions at webmaster@SAPTechnical.COM Home • Contribute • About Us • Privacy • Terms Of Use • Disclaimer • Safe • Companies: Advertise on SAPTechnical.COM | Post Job • Contact Us ©2006-2007 SAPTechnical.COM. All rights reserved. All
product names are trademarks of their respective companies. SAPTechnical.COM,
Inc. is in no way affiliated with SAP AG. Graphic Design by Round the Bend Wizards |
||