Open topic with navigation

TIBCO BusinessEvents® Enterprise Edition 6.3.1

# Exporting Resources as a WSDL File

The WSDL export utility allows you to export rules and rule functions that have a SOAPEvent as a parameter, as a WSDL file.

Note:

- TIBCO BusinessEvents supports WSDL 1.1 specification. See the following page for more details:

  http://www.w3.org/TR/wsdl

- WSDL Filenames must conform to the `NCName` datatype. See the following page for more details:

  http://www.w3.org/TR/REC-xml-names/#NT-NCName

- Some Japanese characters, such as half-width Katakana, have issues when they are used in XML names. See the following document for more details:

  http://www.w3.org/Submission/japanese-xml/

The following table shows how related project resources are exported as a WSDL file.

Exporting Project Artifacts as WSDL
Project Folders and Resources | WSDL Artifact after Exporting
--- | ---
RuleFunction Use the rule function specified as the input event’s default destination as the SOAPEvent’s preprocessor. That rule function must have the “SOAPEvent for input” as the input and the “SOAPEvent for output” as the return type. | Forms the `<wsdl:operation>` operation.
SOAPEvent `SOAPEvent` for the WSDL input argument OR `SOAPEvent` for the WSDL output argument Use the event you configured in Add a SOAPEvent (and Other Ontology as Needed) . | Creates a message. The contents of Envelope > Header > Body become message parts.
HTTP Channel Channel with HTTP as the Driver, Resource as the Method of Configuration, with a pointer to the HTTP Connection. | The URI of the channel forms the `<soap:address>` URI.
HTTP Connection for HTTP Channel Host and port are used. | The name of the connection forms the `<wsdl:port>`. Host and port of the connection form the `<soap:address>` host and port.
Destination for HTTP Channel With `SOAPMessageSerializer` as the default serializer. The destination used is the default destination of the SOAPevent. | Forms the `soapAction` attribute of the operation. The destination name becomes `soapAction` specified for that particular operation.
CDD In the Agent Classes tab, Input Destination Collections list, the Preprocessor specified for the input SOAPEvent’s default destination. Place the input destination directly under the agent class input destination collections, and not under Collections > Input destination. | Associates `soapAction` to the operation in the HTTP binding.

Subtopics

Did you find this helpful?

YesNo
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO BusinessEvents® Enterprise Edition

Copyright © 2004-2024. Cloud Software Group, Inc. All Rights Reserved.