Using an options file when importing a WSDL service
When you create an API definition, or add a target WSDL service to an API definition, by importing a .zip file, you can specify additional directives by including an options file in the .zip file.
You can use an options file when importing a .zip file while performing any of the following tasks:
- Creating a REST proxy API; see Creating a REST proxy API from an existing WSDL service.
- Creating a SOAP proxy API; see Creating a SOAP proxy API from an existing WSDL service.
- Adding a target WSDL service to an API definition; see Editing an API definition.
The options file is a YAML file, and must have the file name apiconnect.yaml.
You can include the following fields in the file:
||Suppress auto-generation of examples.|
||Enable generation of definitions for WS-Security headers.|
||Array of XSD file locations||Additional schema files, not referenced in the WSDL, that are used to define additional SOAP headers.|
||Create the API by using the information for the specified port.
If the specified port does not exist, or refers to a REST/XML port rather than a SOAP port, the API creation fails.
suppressExamples: true wssecurity: false implicitHeaderFiles: - xsdDir/schema1.xsd - xsdDir/schema2.xsd