In Part one of this weblog we looked at Design in the Integration builder. Now let us continue on to the configuration and the testing of the end to end scenario.
1. We have a Business system or a Business service ready to use.
2. The Sender agreement, Receiver agreement , Receiver determination and interface deterimination steps will be done by the reader.
There are two adapters we need to configure for this scenario, a RFC sender adapter and a SOAP receiver adapter.
For configuring your RFC sender adapter refer this blog which gives you a detailed step by step procedure.
The SOAP receiver adapter needs to be configured as follows:
We need to specify the following;
1. Target Url : http://webservices.imacination.com/distance/Distance.jws
2. Configure Proxy : If your network has a proxy setup you need to provide the detaisl of the same.
3. Configure proxy User Authentication : to be specified in case.
4. SOAP Action : Provide getDistance since that is the operation the webservice will use in our case.
Once all of the configuration is done and the objects are activated, we proceed to the testing part of the scenario.
I have written a small ABAP code for test purpose.
REPORT Z_TEST_RFC_XI_WEBSERVICE.data: lv_distance type char10.CALL FUNCTION ‘Z_WEBSERVICE_TEST_SHABZ’ destination ‘Z_WEBSERVICE’ EXPORTING FROMZIP = ‘12222’ TOZIP = ‘22222’ IMPORTING DISTANCE = lv_distance.write : ‘Distance is : ‘ , lv_distance.
Once this program is executed we get the reply from the Webservice.
A screenshot of SXMB_MONI shows the request and response XML:
and thus this brings us to the end of a successful implementation of a RFC -> XI-> Webservice scenario. 🙂