Importing Web Services
Use
In a composite application, you can import Web services, map them to the existing service operations, and consume these Web services. When designing your composite you can consume existing enterprise services and map them to customizable application services that fit your particular needs. You can edit the Web services in an entirely model-driven manner, which ensures flexibility, reusability, ease of development, and increased development productivity. You can browse the enterprise services that are offered in the Enterprise Service (ES) Workplace.
You cannot configure reliable messaging for Web services you have imported in your composite application. You can only find out which of the operation of the external service support reliable messaging in the Operations tab of the external service editor.
You can view the location of the WSDL file on the local file system. To do that, click the imported Web service with the secondary mouse button and from the context menu choose WSDL Document Location.
To check whether any of the operations of the service you have imported supports idempotency or reliable messaging, open the Operations tab page and check the Idempotency and WS-RM columns in the Existing Operations table.
Prerequisites
You have configured the Universal Description Discovery and Integration (UDDI) server.
To do that, in the SAP NetWeaver Developer Studio, choose Window → Preferences → Web Services → SAP Services Registry in the Server Name field enter name of the UDDI server.
Procedure
Importing Web Services Using Search Console
You can directly import the Web service with the Search Console using drag and drop. For more information about the search capabilities you can use in the Search Console, see Browsing Services in Search Console.
Importing Web Services Using Import Wizard
If in your development environment there is already a service interface, operation or type with the same qualified name but a differing definition, you will not be able to import your new service interface. When such collisions are detected, you will be presented with a detailed explanation for each of them and the import will be canceled. You have to delete the old definitions manually from your project before retrying the import.
Note that the same wizard is used when using the Composite Designer perspective.
1. In the Service Composer perspective of SAP NetWeaver Developer Studio, choose the CAF application in which you want to import a Web service.
2. Click the external node with the secondary mouse button and choose Import Web Service.
Choose the location from where you want to import the WSDL file. When ready, choose Next.
For more information about the information required for each option, see Importing WSDL Documents in the SAP NetWeaver Developer Studio.
3. (Optional) Choose an existing Service Group for the configuration of the imported Web service or create a new one. Choose Next.
For more information about using service reference or service group in your composite application, see Creating Service Groups.
4. (Optional) If you want to change the hierarchy of the Java packages or change the name of a particular Java file, you need to apply customization for the imported WSDL definition. To do that, mark the Apply JAX-WS external customization files checkbox.
The location of all xsd and wsdl files is displayed in a new window, so that you can write proper external customization bindings.
5. Choose Finish.
The imported Web service appears under the external package node in Composite Application Explorer. You can now create mappings for the Web service.
You need to configure the Service Groups in SAPNetWeaver Administrator, after you have assigned the imported Web service to it.
More Information
Configuring Consumer Applications