Importing WSDL Documents in the SAP NetWeaver Developer Studio

Prerequisites

When importing from Enterprise Services Workplace (ES Workplace):

You have applied for credentials for ES Workplace at the following Web address: http://www.sdn.sap.com/irj/sdn/soareg

For more information about ES Workplace, see: http://www.sdn.sap.com/irj/sdn/esworkplace
SAP NetWeaver Developer Studio is configured to connect to the ES Workplace.

You can do this in Window Preferences Web Services Service Registry . Enter sr.esworkplace.sap.com for server, 80 for port, and 50043 for HTTPS port.

Context

You need to import a WSDL document into SAP NetWeaver Developer Studio so that you can create Web services in outside-in mode, or to generate Web service proxies. For more information about these procedures, see Creating Outside-In Web Services and Creating Web Service Proxies , respectively.

You can import WSDL documents from the following sources:

Enterprise Services Repository (ES Repository) where a Service Interface (SI) is modeled.
File system or a remote location such as a URL.
Services Registry (SR) where the Web service is published.

Procedure

Choose File Import Web services Import WSDL .
In the Output folder field, browse to the project where you want to import the WSDL document.
Under Available wsdl sources , choose the 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. To complete the importing process, proceed with one of the following:

Results

The WSDL document is imported into SAP NetWeaver Developer Studio. Depending on the location from which you imported the WSDL document, the name of the imported file is as follows:

When the file is imported from a file system, the original file name is preserved. If the WSDL document imports other WSDL documents or schemas, their file names are preserved as well.
When the file is imported from the Enterprise Services Repository the file name is constructed as follows: <Service Interface>.wsdl or service Interface>.wsdl or <data type>.wsdl.
When 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 file names 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
  Note
  The schema files are imported to a separate Schemas subfolder.