In this recipe, we will see how we can create a client proxy based on a given Web service (using its WSDL document). As an example, we will use the Web service that we created earlier in this chapter. We will use the Web service wizard from the transaction SE80. This will generate the class and other necessary objects that are needed to call the Web service.
We will now follow the steps as shown:
- Go to transaction
SE80, and select the menu option Edit Other Object. - On the dialog box that appears, choose the Enterprise Services tab and in the Client Proxy field enter a suitable name. Then click on the Create button.
- The wizard will then start. The first step will ask for the Source of the Web service. Choose the option URL/HTTP Destination and click on Continue.
- For the next step of the wizard, enter the WSDL URL of our Web service binding. This is the same URL as shown in the Service Definition Overview tab in the
SOAMANAGERtransaction.
- Enter the URL in the URL field and then click on Continue.
- You will then be asked to specify the Package and Request number. Choose the Local Object checkbox and enter a suitable Prefix of the class to be generated. We will use the prefix
ZST8_. Then click on Continue.
- Finally, the screen appears where it is specified that clicking the complete button will generate the proxy class. Press the Confirm button to complete the action.
This will create the service consumer proxy as shown in the following screenshot. The proxy by the name ZST8_CO_ZST8_MYSERVICE is created. The relevant class corresponding to the proxy is also generated and activated along with the necessary methods.
The method contains the necessary logic for converting the amount based on the function module used while defining. The input structure corresponds to the importing parameters, whereas the output structure corresponds to the exporting parameters of the function module used for generating the Web service. All the necessary objects are generated. In addition, the relevant structures needed for the Web service call (consumer proxy method call) are also generated.
In the next recipe, we will see how to create a logical port for the Web service consumer. After this, the service may be called from a program using the proxy class methods.
Apart from WSDL URL, you may use other options as the source of your web service. You may use a local file that contains the WSDL document pertaining to the service or the enterprise service repository of a PI instance. In addition, a UDDI registry (maintained on the SAP server that provides access to information about published Web services) may also be specified.
Alternatively, a more sophisticated Service Registry may be used as the source. The service registry is a UDDI v3 complaint registry within an SOA landscape. It may have services published from activated service interfaces from ESR, or from sender agreements from Integration Directory. Also, it may be used on ABAP or Java services definitions from AS, ABAP, or Java, respectively. They provide important information about services along with the reference to WSDL data. After entering the name of the UDDI registry or service registry the name of the relevant service may then be specified on the next screen.
- http://help.sap.com/saphelp_nwpi711/helpdata/en/fa/82f552b492495d8961df56c0fa2dde/content.htm
- http://help.sap.com/saphelp_nw70ehp2/helpdata/en/69/8a1e9553dc4baba6026a3db510cadb/frameset.htm
- http://help.sap.com/saphelp_nwpi71/helpdata/en/47/0ae6a14ddb0e8ae10000000a155369/frameset.htm
- http://www.netweavercentral.com/index.php/2011/consume-a-web-service-in-abap/old link
- http://sapignite.com/consuming-a-web-service-in-abap/
- http://help.sap.com/saphelp_nw04/helpdata/en/81/845f3c31727d59e10000000a114084/frameset.htm
- http://help.sap.com/saphelp_nwpi71/helpdata/en/e6/6d0f3fb35c48fa9fdf5f4e70d9f37d/frameset.htm