![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
This release supports SOAP version 1.1. Some understanding of SOAP protocol is required in order to work with this feature. See http://www.w3.org/TR/soap/ for details.
How Clients View the WSDL When TIBCO BusinessEvents acts as a web service server, clients of the service can view the exported concrete WSDL for the web service using the URL to the document root folder (see HTTP Channel Advanced Configuration Settings for details about the document root setting). You must place the WSDL file in that location.To create a SOAP event, create a SimpleEvent that inherits a SOAPEvent. It makes event configuration easier. Its payload has a message root element having an Envelope child element. The root element contains Header and Body elements, and the Body element has a Fault element. You can further configure these elements using the payload editor.
Also, ensure that the default destination for the SOAP event uses com.tibco.cep.driver.http.serializer.SOAPMessageSerializer.
•
•
• See Parsing and Building SOAP Messages for more details.For SOAP requests, the header property SOAPAction represents the destination name, and the requestURI represents the channel URI. TIBCO BusinessEvents combines the SOAPAction and requestURI to create a destination URI. It maps the request with a destination having same URI as the newly created URI.For example, if the requestURI of a request is /QueryBooks and the value of SOAPAcion is QueryBooksByAuthor, then TIBCO BusinessEvents engine maps the request with a destination having /QueryBooks/QueryBooksByAuthor URI if it exists.The section Creating Resources Using the WSDL Import Utility explains how to use the WSDL import feature to create the resources.Also see Understanding the WSDL to Project Resource Mapping for details about how the WSDL elements correspond to project resources.Configure an HTTP channel, an HTTP connection resource for the channel. See Working with HTTP Requests for details. Connection configuration is the same for SOAP and HTTP channels, except for the serializer. For SOAP destinations, use the following serializer:
2. In the Inherits From field, select SOAPEvent.In general the procedure of serving requests and sending requests to other servers is the same for SOAP services as for other HTTP interactions. See Working with HTTP Requests. One rule function is used as the event preprocessor.In addition, you must configure rules and rule functions to access information from the SOAP messages in the inbound events, and to populate outbound events with SOAP message details. Set two SOAPevents you configured in Task B as input and return arguments of the preprocessor. See Parsing and Building SOAP Messages for details.Open the project CDD for editing, and configure an event preprocessor for the destination you configured in Task A. Use the rule function you configured in Task C.
See Understanding the WSDL to Project Resource Mapping to understand which sections of the WSDL are used to create each resource.
a. In Studio Explorer, right-click the project folder (or the project root) where you want to store the WSDL file and select Import. You see the Import wizard.
b.
c. At the File system dialog, click Browse, select the directory that contains the WSDL file you want to use, and click OK.
a. In Studio Explorer, right-click anywhere in the project and select Import. You see the Import wizard.
b.
c. At the WSDL Import dialog, click Browse and select the WSDL file you imported in step 1, then click OK.
2.
3. In Studio Explorer, select the WSDL file and then select Edit > Delete from the top menus to delete the WSDL file.
4.
6. Open the mapper and click on the Mapper Check and Repair button and check only the mappings in red.
7. Click Ok to fix the mappings.
WSDL Filenames must conform to the NCName datatype. See the following page for more details:Table 21 shows how related project resources are exported as a WSDL file.
Table 21 Exporting Project Artifacts as WSDL Forms the <wsdl:operation> operation.
• SOAPEvent for the WSDL input argument
• SOAPEvent for the WSDL output argument 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. The name of the connection forms the <wsdl:port>. Host and port of the connection form the <soap:address> host and port. With SOAPMessageSerializer as the default serializer. Forms the soapAction attribute of the operation.The destination name becomes soapAction specified for that particular operation. In the Agent Classes tab, Input Destination Collections list, the Preprocessor specified for the input SOAPEvent’s default destination. Associates soapAction to the operation in the HTTP binding.
1. Right-click the project, and click Export...
2.
3. Select the WSDL location by specifying the path, and type a valid NCName for the WSDL file.
5. Click Finish.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |