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

Using external web servers with WebSphere Message Broker

WebSphere® Message Broker is frequently a component in Service Oriented Architecture (SOA) patterns that include external web servers and other HTTP solutions. Learn about the facilities that WebSphere Message Broker provides to help you to configure your web server infrastructure, and which configuration option best fits your existing topology.

The following diagram shows a web server topology that uses a web server plug-in generated in WebSphere Application Server to handle HTTP and HTTPS connections with an application server. The web clients use HTTPS to communicate with the web server, and the WebSphere Application Server plug-in forwards traffic over HTTP to one of two application servers. This topology provides simplified administration: the clients connect to a single endpoint, and all client security is handled in a single place. The plug-in can be used to handle load-balancing and failover between the two application servers.

WebSphere Application Server plug-in with application servers
You can configure a WebSphere Application Server plug-in so that it can be used, without any loss of functionality, with WebSphere Message Broker in the place of the application server. You can then take advantage of the load-balancing and failover capabilities of the plug-in to:
  • Support many HTTP sessions
  • Enable access to the broker from multiple IP addresses and ports
  • Simplify the administration of your SOA topology

In the following diagram, WebSphere Message Broker takes the place of the application servers. HTTP traffic is handled by broker-wide listeners on both systems.

WebSphere Application Server plug-in with WebSphere Message Broker

The WebSphere Application Server plug-in can be used in the preceding cases, and in more complex scenarios, to:

You can use WebSphere Message Broker to achieve this type of configuration. Depending on your existing topology, use WebSphere Message Broker to generate the most appropriate type of configuration data:
  • If your existing topology incorporates WebSphere Application Server, generate a configuration file that can be read by a WebSphere Application Server web server plug-in
  • If your existing topology does not contain WebSphere Application Server, but uses an Apache web server, such as IBM® HTTP Server, generate a configuration file that can be merged into your Apache mod_proxy configuration
  • If your topology is not described by the previous options, you can use the Message Broker API to generate a per-broker list of port and URL data in CSV format, which you can use in your web server configuration
Refer to the following topics to help you to generate the appropriate configuration data for your web server topology:
Notices | Trademarks | Downloads | Library | Support | Feedback

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

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


Concept topicConcept topic | Version 8.0.0.7 | be55180_