TIBCO EBX® generates a WSDL that complies with the W3C Web Services Description Language 1.1 standard.
A WSDL can be generated for different types of operations:
| Operation type | WSDL description | 
|---|---|
| 
 | WSDL for EBX® add-ons. | 
| 
 | WSDL for dataset and replication operations. | 
| 
 | WSDL for default EBX® directory operations. It is also possible to filter data using the  | 
| 
 | WSDL for dataspace or snapshot management operations. | 
| 
 | WSDL for operations on the tables of a specific dataset. | 
| 
 |  Deprecated since version 5.8.1. This operation type has been replaced by  WSDL for user interface management operations (these operations can only be accessed by administrators). | 
| 
 | WSDL for administration operations like: 
 These operations can only be accessed by administrators. | 
| 
 | WSDL for EBX® workflow management operations. | 
EBX® supports the following methods:
from the user interface
from HTTP protocol
A WSDL can only be downloaded by authorized profiles:
| Operation type | Access right permissions | 
|---|---|
| 
 | All profiles, if at least one web service is registered. | 
| 
 | All profiles. | 
| 
 | All profiles, if the following conditions are valid: 
 
 | 
| 
 | All profiles. | 
| 
 | All profiles. | 
| 
 |  Deprecated since version 5.8.1. This operation type has been replaced by  Built-in administrator role or delegated administrator profiles, if all conditions are valid: 
 | 
| 
 | Built-in administrator role or delegated administrator profiles, if all conditions are valid: 
 | 
| 
 | All profiles. | 
An authorized user can download an EBX® WSDL from the data services administration area.
See Generating a WSDL for dataspace operations in the user guide for more information.
An application can download an EBX® WSDL using GET or POST HTTP method. The application has to be authenticated using a profile with appropriate rights.
http[s]://<host>[:<port>]/<ebx-dataservices>/{type}[/{dataspace}[/{dataset}]]?{queryParameters}
Where:
<ebx-dataservices> corresponds to the 'ebx-dataservices.war' web application's path. The path is composed by multiple, or none, URI segments followed by the web application's name. 
{type} corresponds to the operation type.
{dataspace} corresponds to the dataspace or snapshot identifier.
{dataset} corresponds to the dataset name.
{queryParameters} corresponds to common or dedicated operation parameters passed through the URL.
A request parameter can be specified by one of the following methods:
a PathParam which corresponds to a path segment from the URL (recommended)
a QueryParam which corresponds to a standard HTTP parameter with value.
| Parameter name | 
 | 
 | Required | Description | 
|---|---|---|---|---|
| 
 | no | yes | yes | Specifies the WSDL download operation. Empty value. | 
| 
 | no | yes | no | Specifies the user identifier. Required when the standard authentication method is used. 
 | 
| 
 | no | yes | no | Specifies the user password. Required when the standard authentication method is used. 
 | 
| 
 | yes | no | yes | Specifies the operation type. Possible values are:  
 | 
| 
 
 | yes | yes | (*) | Specifies the dataspace or the snapshot identifier. (*) required for  
 | 
| 
 | yes | yes | (*) | Specifies the dataset name. 
 | 
| 
 | no | yes | no | Specifies the list of table paths. Optional for  If not defined, all tables are selected. Each table path is separated by a comma character. 
 | 
| 
 | no | yes | no | Allows generating a WSDL for an operations subset. Optional for  This parameter's value is a concatenation of one or more of the following characters: 
 
 | 
| 
 | yes | yes | (**) | Specifies the unique name space URI of the custom web service. (**)Is required when  
 | 
| 
 | no | yes | (***) | Specifies the attachment file name. (***) optional if  
 | 
| 
 | no | yes | no | Specifies if the WSDL is downloaded as an attachment. 
 Default value is  | 
| 
 | no | yes | no | Overrides the target namespace URI of the WSDL. 
 Default value is  | 
No message body is required.
An HTTP code is always returned. Errors are indicated by a code above 400.
| Status code | Information | 
|---|---|
| 
 | The WSDL content was successfully generated and is returned by the request (optionally in an attachment). | 
| 
 | The request is incorrect. This occurs when: 
 | 
| 
 | Request requires an authenticated user. | 
| 
 | Request is not allowed for the authenticated user. | 
| 
 | Request is not allowed in this configuration. | 
| 
 | Request generates an error (a stack trace and a detailed error message are returned). | 
The response body depends on the returned status code and on the requested WSDL content.
200 (OK): the HTTP header Content-Type is set to text/xml;charset=UTF-8.
If the content is in attachment, the HTTP header Content-Disposition is set to attachment; filename*=UTF-8''<filename.wsdl>.
4xx: A detailed message is returned in the body. The HTTP header Content-Type is set to text/html;charset=utf-8.
Some of the following examples are displayed in two methods: PathParam and QueryParam. 
The WSDL will contain all repository operations, using standard authentication method.
http[s]://<host>[:<port>]/<ebx-dataservices>/repository?WSDL&login=<login>&password=<password>
The WSDL will contain all workflow operations.
http[s]://<host>[:<port>]/<ebx-dataservices>/workflow?WSDL
The WSDL will contain all tables operations for the 'dataset1' dataset in 'dataspace1' dataspace.
PathParam
http[s]://<host>[:<port>]/<ebx-dataservices>/tables/dataspace1/dataset1?WSDL
QueryParam
http[s]://<host>[:<port>]/<ebx-dataservices>/tables?WSDL&branch=<dataspace1>&instance=<dataset1>
The WSDL will contain all tables with only read operations for the 'dataset1' dataset in 'dataspace1' dataspace.
PathParam
http[s]://<host>[:<port>]/<ebx-dataservices>/tables/dataspace1/dataset1?WSDL&operations=R
QueryParam
http[s]://<host>[:<port>]/<ebx-dataservices>/tables?WSDL&branch=dataspace1&instance=dataset1&operations=R
The WSDL will contain the two selected tables operations for the 'dataset1' dataset in 'dataspace1' dataspace.
PathParam
http[s]://<host>[:<port>]/<ebx-dataservices>/tables/dataspace1/dataset1?WSDL&tablePaths=/root/table1,/root/table2
QueryParam
http[s]://<host>[:<port>]/<ebx-dataservices>/tables?WSDL&branch=dataspace1&instance=dataset1&tablePaths=/root/table1,/root/table2
The WSDL will contain custom web service operations for the dedicated URI.
PathParam
http[s]://<host>[:<port>]/<ebx-dataservices>/custom/urn:ebx-test:com.orchestranetworks.dataservices.WSDemo?WSDL
QueryParam
http[s]://<host>[:<port>]/<ebx-dataservices>/custom?WSDL&namespaceURI=urn:ebx-test:com.orchestranetworks.dataservices.WSDemo