Tutorials

  1. Home
  2. Dokumente
  3. Tutorials
  4. 47. How to export the Metadata in different format as xsd, XSD (Response for V3 Inbound), json schema, WSDL 1.1, swagger 2.0/OpenAPI 2.0 and openApi 3?
  5. 47.1 How to export WSDL 1.1?

47.1 How to export WSDL 1.1?

Introduction

This tutorial will show you how the export WSDL 1.1 file. It guides you why we need it and what we do on file after generating it.

For exporting the message Type of WSDL 1.1 Format as following:

  • The interface could be Request, Response, and Fault.
  • The Request/outbound interface will get the IStructure/MessageTye based on the interface and get extra fields as SKYVVA__MessageId field. The SKYVVA__MessageId field will generate for all levels of messageType.
  • The Response/inbound interface will get the IStructure/MessageTye based on the interface and get extra fields such as SKYVVA__MessageId, SKYVVA__MESSAGE, and SKYVVA__Response_Code field. The SKYVVA fields generate only the parent level with messageType.
  • The Fault will get the IStructure/MessageTye based on the interface and get extra fields such as SKYVVA__MessageId, SKYVVA__MESSAGE, and SKYVVA__Response_Code field. The SKYVVA fields generate only the parent level with messageType.
  • When the interface doesn’t link with Request Interface, it will automatically generate as Request. If the interface link with Request Interface, it will generate as Response.
  • When the interface link with the Request and Response Interface, it will generate as Fault.
  • The interface link Request, Response, and Fault Interface, it will alert message error “ Error While Processing. This is might be the Interface Structure Configuration issue“.
  • The SKYVVA field will not generate from Interface ISturcture that upload from the file.
  • The old ways checkbox will generate old or new ways of file format.
  • It will export the normal message type and SOAP template in the generic page and interface page.
  • It will generate only the SOAP template in the message type of repository.

Pre-required

First, you need to do some prerequisite steps before you can use the function “Generate Metadata“:

  1. Create Integration
  2. Create Inbound/Outbound Interface
  3. Create IStructure/Message type add into the interface

How to get message type in WSDL 1.1 File?

The WSDL 1.1 can be generated at three places e.g. in the custom link of Integration and directly on the interface details page. We pick up one for sample using the inbound interface and having Message Type. Before getting the message type, we need to have a MetaData provider, a Repository.

This is the Message Type sample:

Inbound interface using with Message Type

Checking structure message type in mapping tool at the left side because we are using an inbound interface.

Now you are able to generate MetaData. we will show you how to generate metadata on the generic page (the customs link of Integration Details Page). Please enter the integration details page and you will able to see the “Generate MetaData“ in the Custom Links section. Please click the Generate MetaData link:

Generate metadata in new ways of WSDL 1.1. Please choose the interface name on “Create WSDL For Interface”, Choose file format WSDL 1.1 in “Chose a format file”, uncheck the checkbox “As old ways?” and click the “Export” button.

Note
If your interface link to message type as WSDL template, so Combobox ‘Chose a format file’ will display only ‘WSDL 1.1’ option.

You will get a WSDL 1.1 file format under the “Outbound Interfaces (Related List)” section. You can download it by clicking the link “View”. You will able to see the file after download in download folder or download bar chrome browser.

This is the second way to generate WSDL 1.1 format, you can go to Interface Details Page that you want to generate. You will see the “Generate MetaData” button in the header section page. Please click this button to see the pop-up screen.

Please choose WSDL 1.1 in “Chose a format file” picklist and click the “Export” button.

You will get WSDL 1.1 file in the download bar section or you can check on the download folder on your local pc.

After you get the WSDL 1.1 file you can import it for example into the SAP PO system side as the screenshot below.

This is the third way to generate WSDL 1.1 format from the message type. Please enter the repository. Then you will see the “Generate MetaData” Action button in the message type section.

Note: if you want to generate the WSDL 1.0 file format on the message type, your message type has to SOAP template. For example, you can generate WSDL Service only. It has three-part in WSDL such as Request, Response, and Fault Message type depend on your business message type.

Here is the SOAP message type template:

We will show you to export the “SOAP Service” message type. Please click the MetaData button

It will pop-up to export metadata, then please choose the WSDL1.1 file format.

You will get WSDL 1.1 file in the download bar section or you can check on the download folder on your local pc.

After you get the WSDL 1.1 file you can import it for example into the SAP PO system side as the screenshot below.

Summary

Finally, you have learned how to generate metadata with a WSDL 1.1 file format was in the generic page, Interface details page, and message type.

Fandest du diesen Artikel hilfreich? Ja Nein

Wie können wir helfen?