WSDL Generation

How to generate WSDL files for your service and binding and what options are available.

Introduction

When creating a WSDL file for your web service or web service binding, you can determine various parameters and values in the WSDL file. Further, there are currently differing standards for WSDL, meaning WSDL is interpreted differently by different vendors. Therefore, SAP Web Services supports different "flavors" of WSDL, giving you the confidence that your web service will be consumed correctly. Selecting a flavor changes the structure and content of the following elements:

SAP Assertions
Security Assertions
WSDL Section
WSDL Version
WSP Version
WSP Style
SOAP Version
SOAP Style
SOAP Action

You can either use one of the two SAP flavors or specify your own. And you can save your flavor and define it as default so the same structure of the WSDL file will be used the next time you open the WSDL Generation view.

To open the WSDL Generation page, see Displaying a WSDL Document.

Parameters

Table 1:
Parameter	Description
Flavor	Determines which WSDL types are accepted by the web service: All possible combinations are allowed SAP default WSDL representation
SAP Assertions	Assertions are used to construct the policy expressions in the WSDL files. The describe how the web service can be consumed. For example, which protocols are supported. Policies are also used to define the bindings, for example, which security policies are supported. Service consumers may not support some policies/SAP assertions. Therefore, you can control here which are available in the Web Service and which not. All - all proprietary SAP assertions are included in the WSDL file. Only optional - only SAP assertions marked as optional (wsp:Optional="true">) are included. The WSDL file does not contain any mandatory operations. If the service consumer does not support the contained operations, they can disregard them without generating errors. Without - no SAP assertions are included in the WSDL file.
Security Assertions	Include platform-relevant security assertions: Standard ABAP 700/710 and Java 710/730 ABAP 702/730/740 and later
WSDL Section	Determines what sections are included in the WSDL file. You may want to use a single WSDL file or multiple ones, depending on your system and parser. AllInOne - Includes all required information in a single file, including the three following sections. PortType - Includes only this section. Defines the port and message types. Binding - Includes only this section. Defines the bindings that are supported (all are over SOAP via HTTP). Service - Includes only this section.
WSDL Version	Only 1.1 is available at present.
WSP Version	Web Services Policy version. Use policies to expand and modify the web service connection. The WSP(s) are formulated in the WSDL file according to the selected version here. If the consumers of your web service do not understand policies, select No Policy. However, for the following types of web services, you must use policies and select a WSP Version: configured and managed centrally use any authentication method apart from simple username/password. For example, SSO scenarios require the use of policies.
WSP Style	single-Binding multi-Binding
SOAP Version	The version of SOAP used to define the bindings. If you select SOAP 1.1 and SOAP 1.2, each binding will be defined twice in the WSDL file, one for each version.
SOAP Style	The method use to translate WSDL bindings to SOAP messages. Document RPC (Remote Procedure Call) Document Wrapped Note The style is not related to the programming model! You can use Document if your web service is translated from an RFC—you don't have to use RPC.
SOAP Action	SOAP Actions communicate what action is to be performed. You can With - Include SoapAction. Without - Do not include SoapAction. SoapAction is not mandatory in WSDL files. Therefore the option is given here to include it or not.
Options for WSDL Access and URLs	The following settings change the location (URL) of the web service.
Alternate Host	The domain name. By default, the WSDL file is published to the same server that you perform the configuration. As this is usually an internal server that is not accessible by service consumers outside your organization's network, you can specify the host where the WSDL file will be published. Note that the WSDL URL is also used inside the file as well.
Alt. Port (http)	The port to use for HTTP.
Alt. Port (https)	The port to use for HTTPS.
Meta Data Protocol	You can use either HTTP (default) or HTTPS.
WSDL Generation
Refresh	Generates a new WSDL document based on the values you set for the above parameters.
Open WS document	Displays the WSDL document.
Open WS navigator	Opens the service in the Web Service Navigator (where you can test the service). See Testing a Service
WSDL URL	The URL of the WSDL file.