WSDL Analyzer
- Last Updated: January 22, 2026
- 3 minute read
- OpenEdge
- Version 12.8
- Documentation
Runs the WSDL Analyzer, which provides HTML documentation on the interface that a web service Description Language (WSDL) describes. This HTML documentation describes how an ABL developer can access the web service and its operations in ABL.
| Operating system | Syntax |
|---|---|
| UNIX Windows |
|
- -h
- Displays a help message on the usage of this command.
- -b
-
Forces documentation of binding names. A web service can offer two options for a web service client to connect (or bind) to it:
- Using services with ports (most common)
- Using binding names (the names of the WSDL
<binding>elements) with SOAP endpoints that you must obtain separately (sometimes used to bind a SOAP viewer)
Normally, if a WSDL defines services, the Analyzer includes only the service and port names in the generated documentation. If the WSDL does not define any services, the Analyzer documents the binding names. This option tells the Analyzer to document the binding names even when services are defined in the WSDL.
- -nohostverify
- Turns off host verification for a Transport Layer Security (TLS) connection using HTTPS.
- -WSDLUserid username
- Specifies a username for accessing the WSDL file.
- -WSDLPassword password
- Specifies a password for accessing the WSDL file.
- -WSDLAuth password
- Specifies if the access to a WSDL file requires TLS client
authentication. Set this to
sslto enable TLS client authentication for WSDL access. If you set this toBasic, the connect method ignores client authentication for WSDL access. - -WSDLKeyFile password
- Specifies the location of the client certificate. If
you do not specify an absolute path of the client certificate file, the
connection operation searches the $DLC/keys folder for the client-certificate-file-name.pem
file. This option must be updated only if
-WSDLAuthparameter is set tossl. - -WSDLKeyPwd password
- Specifies, in clear text or encoded format, the password of the client
certificate. This option must be updated only if
-WSDLAuthparameter is set tossl. For more information on password encoding, see Password encoding in OpenEdge Programming Interfaces. - -proxyhost host
- Specifies the name or IP address of the host where an HTTP-based proxy server required to access the WSDL file is located.
- -proxyport port
- Specifies the port on which the HTTP-based proxy server is listening for requests to download WSDL files.
- -proxyUserid username
- Specifies a username for accessing an HTTP-based proxy server.
- -proxyPassword password
- Specifies a password for accessing an HTTP-based proxy server.
- -show100style
- Shows procedure and function signatures as documented in the 10.0x releases of OpenEdge. With the release of 10.1A, some procedure signatures are changed for ease of use. For more information, see "Analyzing wrapped document literal" in OpenEdge Development: Web Services (11.7 documentation).
- -noint64
- Prior to OpenEdge Version 10.1B, the ABL
INT64data type did not exist and the WDSL Analyzer mapped XML Schema types ofxsd:longto the ABLDECIMALdata type. Use this option if you want to use thexsd:longto ABLDECIMALmapping. Otherwise,xsd:longmaps toINT64. The current version of OpenEdge continues to recognize existing mappings ofxsd:longtoDECIMALas valid whether or not this option is specified. - wsdl-url-or-filename
- Specifies a URL, Microsoft Uniform Naming Convention
(UNC), or local pathname to the WSDL file. If the string does not
specify a URL protocol ("
file://", "http://", or "https://") or start with a UNC prefix ("\\"), it is assumed to be a a local file pathname. - target-directory
- Specifies the target directory (to be created if necessary) where the Analyzer will write the generated documents. If not specified, the Analyzer assumes the current working directory. Choose a directory dedicated for the specified WSDL file, as some generated document filenames are the same for multiple WSDL files.
- –servername
- Specifies the server name in TLS connection initialization for client that it sends to the server as part of the TLS negotiation.