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 listeners

You can choose between broker-wide listeners and execution group (embedded) listeners to manage HTTP messages in your HTTP or SOAP flows. Learn about the two types of listener, how ports are assigned to them, and how you can switch from one to the other for individual execution groups.

Your choice of listener affects message flows that handle inbound Web service requests by using SOAPInput, SOAPReply, SOAPAsyncResponse , HTTPInput, or HTTPReply nodes. Message flows that do not handle inbound requests but that instigate outbound requests by using SOAPRequest , SOAPAsyncRequest, or HTTPRequest nodes are not affected.

For more information about how your choice of listener relates to your HTTP topology, see Configuring your HTTP topology.

Execution group (embedded) listeners

Each execution group has an embedded listener. The listener is associated with an HTTPConnector object and an HTTPSConnector object. The HTTPConnector object controls the runtime properties that affect the handling of HTTP messages. For example, run the following command to change the port on which the embedded listener for execution group default on broker myBroker listens for HTTP messages:
mqsichangeproperties myBroker -e default -o HTTPConnector 
  -n explicitlySetPortNumber -v 8085 

The HTTPSConnector object controls the runtime properties that affect the handling of HTTPS (HTTP Secure) messages. Run the following command to display these properties for execution group default on broker myBroker:

mqsireportproperties myBroker -e default -o HTTPSConnector -r

For further details, including more examples, see Execution group HTTP listener parameters (SOAP and HTTP nodes).

By default, SOAPInput, SOAPReply, and SOAPAsyncResponse nodes use the execution group listener. If execution group default on broker myBroker is using the broker-wide listener, the following command returns a value of false:
mqsireportproperties myBroker -e default -o ExecutionGroup -n soapNodesUseEmbeddedListener

Each connector has its own assigned port, which is allocated from a range of numbers, as required. The default range for the HTTPConnector is 7800 - 7842; the default range for the HTTPSConnector is 7843 - 7884. The first execution group to start an embedded listener is allocated port 7800, the second is allocated 7801, and so on.

If you deploy a message flow to multiple execution groups, the port number is incremented by one for each successive deployment. Assume that no embedded listeners have as yet been started for these execution groups. In this case, the message flow that is deployed to the first execution group receives requests on port 7800. The next message flow uses port 7801, and so on, up to the specified limit of 7842. In this scenario, you typically use an intermediary router that listens on one port, then distributes the requests across the range of ports that you are using.

You can change these port number ranges, and you can allocate a specific port to an execution group, by using the mqsichangeproperties command.

If you restart an execution group, the embedded listeners continue to use the same ports as before the restart.

Broker-wide listeners

The broker-wide listener is associated with an HTTPConnector object for properties related to handling HTTP messages, and an HTTPSConnector object for properties related to handling HTTPS messages. For example, run the following command to change the port on which the broker-wide listener for myBroker listens for HTTP messages:
mqsichangeproperties myBroker -b httplistener -o HTTPConnector 
  -n port -v 8085 
Broker-wide listener properties that apply to HTTP and HTTPS messages are controlled by the HTTPListener object. For example, to disable the broker-wide listener for myBroker, run the following command:
mqsichangeproperties myBroker -b httplistener -o HTTPListener 
  -n startListener -v false 

Each connector has its own assigned port; default values are 7080 for HTTP and 7083 for HTTPS. You can change these port numbers by using the mqsichangeproperties command.

By default, HTTPInput and HTTPReply nodes use the broker-wide listener.

You can configure one or more execution groups so that HTTP nodes that you deploy to those execution groups use the embedded listener, or so that SOAP nodes that you deploy to those execution groups use the broker-wide listener.

Using both broker-wide and embedded listeners

Because the option to use the embedded listener is at the execution group level, you can change your configuration such that some execution groups use the broker-wide listener for HTTP nodes, SOAP nodes, or both, and other execution groups use the embedded listener for HTTP nodes, SOAP nodes, or both.

However, if you disable the broker-wide listener, the execution group listeners are used for all HTTP and SOAP nodes, even if you have not explicitly enabled support for them. Therefore, if you set all relevant broker and execution group properties to false, the execution group listeners handle all HTTP messages.

The HTTPRequest node communicates directly with the HTTP transport, and is therefore unaffected by your choice.

If you change the listener and port that are processing your HTTP or HTTPS messages, you must ensure that you also update your applications to use the updated configuration.

Configuring listeners

When you have decided on the configuration that you want:

  • If you want to use the broker-wide listener for HTTP nodes in all execution groups, and the embedded listener for SOAP nodes in all execution groups, you do not have to change your configuration.
  • If you are currently using the broker listener for one or more execution groups, and want to switch to using embedded listeners, follow the instructions in Switching from a broker-wide listener to embedded listeners.
  • If you are currently using the execution group listener for one or more execution groups, and want to switch to using the broker-wise listener, follow the instructions in Switching from embedded listeners to a broker-wide listener.
Notices | Trademarks | Downloads | Library | Support | Feedback

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

        
        Last updated:
        
        Last updated: 2016-05-23 14:48:00


Concept topicConcept topic | Version 8.0.0.7 | bc43700_