This procedure enables you to import WSDL documents into the SAP NetWeaver Developer Studio.
You need to import a WSDL document to be able to create Web services in outside-in mode or to generate Web service proxies. More information about creating outside-in Web services: Creating Outside-In Web Services. More information about generating Web service proxies: Creating Web Service Proxies.
You can import WSDL documents from the following sources:
● Enterprise Services Repository (ESR)
You import the WSDL document for a Service Interface (SI) modeled in the ESR.
● File system or a remote location, such as a URL
● Services Registry (SR)
You import the WSDL document of a Web service published in the SR.
● Importing from the ESR
○ The SAP NetWeaver Developer Studio is configured to connect to the ESR in Window à Preferences à Web Services à Enterprise Service Browser. More information: Browsing Enterprise Services from the SAP NetWeaver Developer Studio.
○ You have a user with sufficient permissions to log on to the ESR.
● Importing from the SR
○ The SAP NetWeaver Developer Studio is configured to connect to the SR in Window à Preferences à Web Services à Service Registry.
More information: Connecting the SAP NetWeaver Developer Studio to the Services Registry
○ If you are using a proxy to access the Internet, the proxy settings of the SAP NetWeaver Developer Studio are configured in Window → Preferences → General à NetWork Connections.
○ To download a WSDL document, you have a user with sufficient permissions to log on to the system providing the Web service whose WSDL document you want to import.
You can apply for credentials to download WSDL documents from the SR at the following Web address: http://www.sdn.sap.com/irj/sdn/esareg
To import a WSDL document from the ES Workplace, configure the SAP NetWeaver Developer Studio to connect to the ES Workplace. In the SAP NetWeaver Developer Studio, choose Window → Preferences → Web Services → Service Registry, and enter the following settings:
Option |
Value |
Server |
sr.esworkplace.sap.com |
Port |
80 |
HTTPs Port |
50043 |
1. Choose File à Import à Web services à Import WSDL.
The WSDL Import wizard starts.
2. In Output folder field, browse to the project where you want to import the WSDL document.
3. Under Available wsdl sources, choose location from which you want to import a WSDL document.
Depending on the option you choose, the wizard provides different options on the subsequent screens. The procedures below outline the steps you need to complete to import a WSDL document from each of the locations.
1. Choose Enterprise Services Repository, and then choose Next.
2. Enter your credentials to the ESR, and then choose OK.
The Import screen that opens shows the Process Components available in the ESR and lists them by version.
3. Navigate to the Service Interface you need, then choose it, and then choose Finish.
ESR Import Screen
1. Choose Remote Location / File System, and then choose Next.
2. In the URL field, provide the path to the WSDL document.
3. If the WSDL document which you provide is not accessible via a direct connection, you can enter connection proxy settings manually. Choose Network settings preference page and then provide the specific network connection settings.
4. Choose Finish.
1. Choose Services Registry, and then choose Next.
2. If prompted, log on to the SR.
Enter your credentials in the Username and Password fields under UDDI Service. The Username and Password fields under Classification Service are automatically populated with the credentials you specify under UDDI Service. Then choose OK.
3. Specify search criteria to find the Web service whose WSDL document you want to import.
You can use basic and advanced search criteria. By using the advanced search criteria, you additionally narrow your search results by specifying the classification of the Web service. The relation between the various search criteria you can use is a logical AND. More information about the classifications: Structuring of Services in the Registry.
○ Search by basic criteria:
i. In the Find box, enter the name of the Web service. You can use wildcard search (*, ?).
ii. In the Service State, choose the state of the Web service. The table below outlines the meaning of each state:
Service States
State |
Meaning |
Modelled |
The Service Interface is only modeled and does not have any implementation. The service definition does not have a callable service endpoint with runtime configuration settings. |
Activated / Deployed |
The service definition does not have a callable service endpoint with runtime configuration settings. However, the service operations already have an implementation. |
Configured |
The service definition has a callable service endpoint with runtime configuration settings. |
iii. In the System field, choose the SAP System ID <SAPSID> of the particular system which provides the Web service, or accept the default value. For AS ABAP systems, the client number of the physical system is displayed next to the System ID.
○ Search by advanced criteria.
i. Choose Show Advanced.
The classifications tree opens.
ii. Browse the classifications tree, and select the checkbox for each relevant classification.
When you select more than one classification from the same classification system, the relation between these classifications is a logical OR.
When you select classifications from different classification systems, the relation between them is a logical AND.
Advanced Search Criteria
iii. Choose Next.
The table under Found Service Definitions is populated with the list of Web services that match your search criteria.
iv. From the list, choose a service definition.
The table under Endpoints for selected Service Definition shows all endpoints configured for the selected service definition. Service endpoints are available for a service definition only if the selected service definition is in state Configured.
You can import the WSDL document of a service definition or of a service endpoint of the service definition (if a service endpoint is available).
v. Choose a service endpoint, if applicable.
vi. Log on to the system, which provides the Web service, and then choose OK.
The WSDL document is imported in the SAP NetWeaver Developer Studio.
Depending on the location from which you imported the WSDL document, the name of the imported file is as follows:
● The file is imported from a file system.
The original filename is preserved. If the WSDL document imports other WSDL documents or schemas, their filenames are preserved as well.
● The file is imported from the Enterprise Services Repository
The file name is constructed as follows: <Service Interface>.wsdl or <data type>.wsdl.
● The file is imported from the Services Registry or a remote location.
If the WSDL document you import, also called root WSDL, imports other WSDL documents or schemas, then the filenames are constructed as follows:
rootwsdl_<Service Name>.wsdl – the name of the WSDL document you import (the root WSDL)
importedwsdl_1_<Service Name>.wsdl – the name of a WSDL document imported by the root WSDL
importedwsdl_2_<Service Name>.wsdl – the name of a WSDL document imported by the root WSDL
importedschema_1_<Service Name>.xsd – the name of a schema imported by the root WSDL
importedschema_2_<Service Name>.xsd – the name of a schema imported by the root WSDL
If the WSDL document you import is that of a service definition, (as opposed to a service endpoint) it may not contain a service element. In this case, the file names of the WSDL and the schema is constructed by the absolute remote path of the WSDL. For example, you import the WSDL from http://www.ws-i.org/SampleApplications/SupplyChainManagement/2002-10/Manufacturer.wsdl, and the WSDL imports one more WSDL and four schemas, the file names of the imported files are:
rootwsdl_SampleApplications_SupplyChainManagement_2002-10_Manufacturer.wsdl.wsdl
importedwsdl_1_SampleApplications_SupplyChainManagement_2002-10_Manufacturer.wsdl.wsdl
importedschema_1_SampleApplications_SupplyChainManagement_2002-10_Manufacturer.wsdl.xsd
importedschema_2_SampleApplications_SupplyChainManagement_2002-10_Manufacturer.wsdl.xsd
importedschema_3_SampleApplications_SupplyChainManagement_2002-10_Manufacturer.wsdl.xsd
importedschema_4_SampleApplications_SupplyChainManagement_2002-10_Manufacturer.wsdl.xsd
The schema files are imported in a separate Schemas sub-folder.