IIB High Availability

IBM HTTP Servers (IHS) Tier

High Level Architecture
GTM
NEMESB
No affinity
required All New Tr
affic
nothing lo
st
SWINDON NEWBURY

LTM LTM
NEMESBSTC NEMESBNDC

F5 Config for F5 Config for

Network Network
Load Balancing Load Balancing

IHS1 IHS2 IHS3 IHS4

IHS Config for IHS Config for

balancing app balancing app
instances instances

ESB1 ESB2 ESB3 ESB4

ESB21 ESB11 ESB41 ESB31

GPFS Share GPFS Share

MQ Shared Storage MQ Shared Storage
Across FCIP DB2 Primary Across FCIP
DB1 Primary

SY
NC

NC
SY

DB1 Principal DB2 Principal

Standby Standby

2
 Detailed Clustered Architecture

IHS IHS

Active
Cluster IIB IIB
Standby

Cluster IIB IIB

3
2 Options using
fixed IP ports
Broker-wide listeners
Integration Server (embedded)
listeners
Broker-wide or embedded listeners
By default, the SOAP nodes that you deploy to an integration server all use the embedded
listener. You can change the configuration of some or all of your integration servers so that
they use the broker-wide listener.

5 Sources:
http://www.ibm.com/support/knowledgecenter/en/SSMKHH_9.0.0/com.ibm.etools.mft.doc/an09148_.htm
http://www.ibm.com/support/knowledgecenter/en/SSMKHH_9.0.0/com.ibm.etools.mft.doc/ac56650_.htm
Broker-wide or embedded listeners
You can allocate a specific port to an integration
server listener, by using the mqsichangeproperties
command.

Each integration server has an embedded listener. The listener is

associated with an HTTPConnector object and an HTTPSConnector
object. They controls the runtime properties that affect the handling of
HTTP(S) messages.

mqsichangeproperties myBroker -e default -o HTTPConnector

-n explicitlySetPortNumber -v 8085

6 Source:
http://www.ibm.com/support/knowledgecenter/en/SSMKHH_9.0.0/com.ibm.etools.mft.doc/bc43700_.htm
Broker-wide or embedded listeners

Broker-wide
Embedded listeners
listeners
Throughput High* Highest
Endpoint integration Lower Complexity Higher Complexity
* Considering the topology with 2 active integration nodes

7 Source:
http://www.ibm.com/support/knowledgecenter/en/SSMKHH_9.0.0/com.ibm.etools.mft.doc/bc43700_.htm
Configuring your
HTTP topology
 Using external web servers with IBM
Integration Bus

HTTP traffic is handled by broker-wide listeners on both systems in this example.

9 Source:
http://www.ibm.com/support/knowledgecenter/en/SSMKHH_9.0.0/com.ibm.etools.mft.doc/be55180_.htm
Generating an HTTP server config in
Integration Explorer
Complete the following steps to generate a
configuration file:
•In the Navigator view, select the brokers for which you
want to generate a configuration file. If you want to work
with multiple brokers, hold down the Ctrl key while selecting
the brokers.
•Right-click the selected brokers and select Export Port
Configuration.
•Select the configuration that you want to export.
– If you want to use the WebSphere Application Server plug-in,
select WebSphere Application Server Plugin Configuration.
– Click Save to save the file.

10 Source:
http://www.ibm.com/support/knowledgecenter/en/SSMKHH_9.0.0/com.ibm.etools.mft.doc/be55220_.htm
Generating an HTTP server config
programmatically
Generate a configuration file for either the
WebSphere® Application Server plug-in or the
Apache mod_proxy module to use for connecting
to a web server such as IBM® HTTP Server (IHS).

11 Source:
http://www.ibm.com/support/knowledgecenter/en/SSMKHH_9.0.0/com.ibm.etools.mft.doc/be55220_.htm
 Thank you

12