A WSDL file describes a web service. The WSDL Import utility imports a WSDL file and generates TIBCO BusinessEvents project artifacts using elements in the WSDL. TIBCO BusinessEvents can import abstract and concrete WSDL files. The source of the WSDL could be, for example, a ActiveMatrix BusinessWorks
SOAPRequestReply activity.
The table following this example shows which WSDL elements and attributes are used to create TIBCO BusinessEvents project artifacts. Elements and attributes used in the import are highlighted in bold text. Differences between import from abstract and concrete WSDL files are also highlighted. See
Table 22, Imported WSDL Project Artifacts for more details.
Suppose you import the example WSDL above into a Studio project called Library. The imported and generated project artifact names would appear as shown in the Project Folders and Resources column in the table below. Folders that are added by TIBCO BusinessEvents are shown in bold. The example is a concrete WSDL. In the WSDL Source column the source of folder and resource names is given for abstract as well as concrete WSDL sources.
Given a concrete WSDL, folders are created for all the elements after the port, up to the last forward slash of the location URL. The text after the last forward slash is the channel name. For example, given the following location URL:
The folder structure would be /Service/Trial and the channel name would be
getBook.
In a concrete WSDL, the SOAPAction attribute of a
<soap:operation> element specifies the URL of a destination. It also becomes the destination name. Forward slashes (
/), colons (
:), and periods (
.) are converted to underscore characters (
_) to form the name. For example:
For each operation, the import utility creates a rule and a rule function. The rule has no body. The rule functions have
SoapEventOut as the return type. Null value is returned by default.
The <wsdl:input> element becomes a request event and the <wsdl:output> element becomes a response event. Each event type inherits from the
SoapEvent event type.
Event names come from the message attributes. In the example, the request event is
GetBookRequestMessage and the response event is
GetBookResponseMessage.