WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

HTTP traffic handling in WebSphere Message Broker

Before reading about HTTP traffic handling using the proxy servlet in an external Web container, ensure that you understand the basic structure of HTTP traffic handling in WebSphere® Message Broker.

WebSphere Message Broker supports Web services requests over HTTP. Brokers have HTTP listeners that receive requests, which are propagated to message flows that contain the following nodes:
  • HTTPInput
  • HTTPReply
  • SOAPInput
  • SOAPReply
  • SOAPAsyncResponse

WebSphere Message Broker has two types of listeners:

The default behavior for HTTP traffic handling is based on node type:

For more details about these listeners, see Processing HTTP messages.

When you have gained an understanding of the proxy servlet concept, read the following topics to help you to install and test the HTTP proxy servlet:
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:46:35


Concept topicConcept topic | Version 8.0.0.7 | ac69310_