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 proxy servlet; proxy servlet component

The HTTP proxy servlet requires a number of components such as message flows, a proxy servlet, a servlet container, web addresses, the Broker component, and web services clients. Ensure that you are familiar with the proxy servlet component.

A Proxy servlet is a Java™ Web Application Archive (WAR) file that is part of the runtime environment in WebSphere® Message Broker Version 6.1 Fix Pack 3 (6.1.0.3) and above, and can be found in the following directory:

WMB61_runtime_install_path/tools. Where WMB61_runtime_install_path specifies the name of your runtime installation directory.

The proxy servlet is a Java servlet that receives HTTP requests. The proxy servlet matches the received web address with the web address that the HTTP or SOAP input nodes are monitoring, then passes the HTTPRequest to the correct HTTP or SOAP input node flow using WebSphere MQ.

The proxy servlet receives response messages from the HTTP or SOAP reply nodes and sends them back to the client applications over HTTP or HTTPS. The message broker has several internal WebSphere MQ queues, SYSTEM.BROKER.WS.* queues, that are used for the communication between the proxy servlet and the HTTP or SOAP input and reply nodes.

Each HTTP or SOAP input node monitors the arrival of requests associated to specific web addresses. The message broker has internal configuration files, and an internal WebSphere MQ queue SYSTEM.BROKER.WS.ACK, that contain the list of web addresses that are monitored by the different HTTP or SOAP input nodes in message flows deployed on any execution groups. The proxy servlet accesses the internal file, or queue, to match the web addresses received in HTTP or HTTPS requests with the web addresses that the HTTP or SOAP input nodes that are waiting for.

The configuration files, or queue, have a unique correlation ID associated with each web address. The HTTP or SOAP input node uses this correlation ID to get the messages from the internal queue SYSTEM.BROKER.WS.INPUT, and the proxy servlet uses the same correlation ID to put the messages on this queue. This is the mechanism used to correlate the incoming HTTP or HTTPS requests and the HTTP or SOAP input nodes in the message flows.

The HTTP or SOAP input node copies the WebSphere MQ input message ID in the LocalEnvironment.Destination.HTTP.RequestIdentifier to be used by the HTTP or SOAP reply node for WebSphere MQ output message correlation ID. The proxy servlet does a selective GET by correlation ID to the reply queue SYSTEM.BROKER.WS.REPLY, and receives the response messages.

The proxy servlet accepts GET and POST HTTP or HTTPS requests.

When you have gained an understanding of the proxy servlet concept, read the following topics to help you 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 | ac69350_