A WSDL (Web Service Definition Language) is the formal description of a Web Service; in ALSB, it describes a proxy service or a business service. A WSDL is used to describe what a Web Service can do, where it resides, and how to invoke it.
You can base SOAP and XML services on an existing WSDL resource. A WSDL document is available for proxy and business services for any transport. See Create/Edit a Proxy Service - General Configuration page and Creating and Configuring Business Services.
For more information, see How WSDL is Used in ALSB in the AquaLogic Service Bus User Guide.
The path is the project name and the name of the folder in which the WSDL resides.
The unique name assigned to the WSDL. The name is a link to the View WSDL Details page. See Editing WSDLs.
|
|
The path is the project name and the name of the folder in which the WSDL resides. It is a link to the project or folder that contains this resource. See Qualifying Resource Names Using Projects and Folders.
|
|
Click the Delete icon to delete a specific WSDL. See Deleting WSDLs.
|
When you click Save, if there any unresolved references for the new WSDL, the system displays them. See Viewing Unresolved WSDL References.
The date and time that the user created this WSDL or imported it into the configuration. Click the date and time link to view the change history of this resource. See View Change History page.
|
|
The number of objects that this WSDL references. If such references exist, click the numeric link to view a list of the objects. See Viewing References to Resources.
|
|
The number of objects that reference this WSDL. If such references exist, click the numeric link to view a list of the objects. For example, if you select this WSDLs port or binding as the service type for a specific business service or proxy service, the business service or proxy service is listed as a reference when you click the link. See Viewing References to Resources.
|
|
The structural view of the WSDL is displayed by default, which includes the information shown in Table 6-3.
All of the locations for XML schemas or WSDLs included by the current WSDL are specified and are valid. Furthermore, all of the locations for nested XML schemas or WSDLs (XML schemas or WSDLs subsequently included by the included WSDLs or XML schemas) are specified and are valid. One or more of the locations for XML schemas or WSDLs included by the current WSDL is not specified or is not valid. Additionally, the location for one or more of the nested XML schemas or WSDLs (XML schemas or WSDLs subsequently included by the included WSDLs or XML schemas) may not be specified or may not be valid.To resolve an invalid XML schema or WSDL, click Edit References. See Resolving Unresolved WSDL References. |
Note: | The View WSDL Details page may also include a Separate Callbacks button. This button is only displayed if the WSDL has port types with callback operations that can be rewritten. If you click this button, the WSDL is rewritten. |
The View Unresolved WSDL References page displays the information shown in Table 6-5.
To locate a specific reference:
Use the Edit the References of a WSDL Resource page to resolve unresolved WSDL references by configuring the mapping for WSDL references such as WSDL imports and XML schema imports. A WSDL may also have an unresolved reference to a WS-Policy.