HTTP and SOAP Channels : Overview of HTTP and SOAP Channels

Overview of HTTP and SOAP Channels
An HTTP channel is an internal HTTP server. When the BusinessEvents engine starts, it starts the internal HTTP server, which listens to the requests on the port specified in the HTTP Connection resource.
Selecting the Server Type
BusinessEvents uses a built-in server to serve HTTP requests by default. You can also use a TOMCAT server integrated with BusinessEvents.
SOAP Support
SOAP version 1.1 is supported. BusinessEvents supports only document/literal type of encoding of SOAP requests.
A SOAP event is an extension of a SimpleEvent. To create a SOAP event, create a SimpleEvent that inherits from a SOAPEvent. This creates a default schema in the event payload. Edit the schema and introduce header and body elements as necessary.
Using an HTTP channel and a destination configured to use the SOAP serializer and deserializer, BusinessEvents can act as a web services platform that sends and receives SOAP requests, and performs whatever operations are provided by the web service.
BusinessEvents can import a WSDL file and create the required project artifacts based on it, such as events, rules, rule functions, channels, and destinations. For more details, see Using the WSDL Import Utility.
BusinessEvents can also export a SOAP based rule function to a WSDL. The export utility scans the project for rule functions that take a SOAP event as the input, and generates a WSDL operation for it. For more details, see Using the WSDL Export Utility.
See Configuring BusinessEvents as a SOAP Server and Client for more details.