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; web addresses 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 web addresses component.

web addresses, or Universal Resource Locators (URLs), have an important role when HTTP or SSL (HTTPS) protocols are used. In WebSphere® Message Broker, each HTTP or SOAP input node expects to receive requests from a specific web address, or web addresses when wildcard characters are used. The servlet container also uses the web address to locate the servlets that are going to process the HTTP or HTTPS requests received by the listener in the container.

The proxy servlet passes the requests from the servlet container to the broker and vice versa. web addresses have the dual function of locating servlets and locating HTTP or SOAP input nodes. This affects the format of the web addresses used for the broker.

A web address is made up of the following structure:

<schema>://<hostname>:<port>/<url_path>

web address structure definition:

<schema> is HTTP or HTTPS.

<hostname> is the hostname, or IP address, of the server where the servlet container is running.

<port> is the port number that the servlet container is listening on.

<url_path> is a series of tokens separated by slashes /. These are used to indicate the location of the servlet and the location of the HTTP or SOAP input nodes.

Because the <url_path> is used for mapping two resources (instead of one with the broker internal listener) the format of the web address will change when the proxy servlet is used.

The broker structure of the <url_path> is:

/<url_path>=/<context_root>/<node_url_path>

Broker <url_path> structure definition:

<context_root> is the <url_path> allocated to the proxy servlet by the container when the servlet is installed and deployed.

<node_url_path> is the part of the web address path that is added to make the web address unique to a specific HTTP or SOAP input node.

The entire <url_path> has to be configured in the properties of the HTTPInput node.

In some web servlet containers, it is possible to configure the proxy servlet to receive all the HTTP or HTTPS requests arriving to the container (<context_root> = “/*”). In this case, the existing web addresses in the HTTP nodes do not have to change when the proxy servlet is implemented.

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 | ac69370_