
When a Web service client proxy definition is created in the SAP NetWeaver Developer Studio, a proxy is generated for the Web service on the client side on the basis of a WSDL document. Logical ports (LP) and service endpoint interfaces (SEI) are automatically created.
Service endpoint interfaces are created by the proxy generator in accordance with the <port type>- information in the WSDL document. SEIs are used by client applications for Web service calls. The actual structure of an SEI depends on whether an RPC-style or a document-style proxy was generated.
A proxy can be used for different applications.
In a Web project or an EJB project, a WS client proxy project can be referenced in each case.
To create a deployable proxy, proceed as follows:
We recommend that you create less than 20 Web service proxies in the proxy project. Creating many proxies in the same project may impact the system performance during the deployment.
In addition to the procedure described here, you can also use the Web Service Navigator view to create a deployable proxy.
Enter the required data. Select JAX-RPC Service Interface if you want JAX-RPC interface to be generated, and choose a WSDL source among Local Server, Local File System or URL, and UDDI or URL to find the WSDL document on which the WS proxy is to be based.
The J2EE Engine must be up and running.
For more information, see also Initial Configuring and Querying UDDI
Select the name of the proxy and choose Build EAR from the context menu. When the EAR file is generated, select it and choose Deploy from the context menu.
You can expose the created bean as a Web service so that it can be easily tested through the Web service's test page .
Now, you need to create a client application that uses this proxy.
See also: