Environment overview
The environment included the following items:
IBM WebSphere® Application Server Network Deployment version 7.0.0.11
IBM HTTP Server Version
IBM Tivoli® Directory Server
DB2 Enterprise Edition
Oracle Database
IBM Edge Caching Proxy Version
The following pictures show how the four environments used by RVT and IVT test are configured.
Notes: The product names in following charts are used during the test, you could pick up any of other supported products (database, LDAP, etc.) in your own environment.
Machine Specifications
The following tables show the specifications for the machines used by both RVT and IVT in this infrastructure:
RVT Machine Specifications:
Software | Machine Type | OS | # of CPUs | CPU Speed | RAM (GB) | Function |
WAS ND V7.0.0.11 | eServer BladeCenter JS22 | AIX V6.1 TL 4 | 4 | 4.5G | 15.5G | Deployment Manager |
X3650 | RedHat Enterprise Linux (RHEL) 5.4 | 8 | 2G | 3.6G |
WAS Base V7.0.0.11 | eServer BladeCenter JS22 | AIX V6.1 TL 4 | 4 | 4.5G | 15.5G | Mashups Server - Node1 |
X3650 | RedHat Enterprise Linux (RHEL) 5.4 | 8 | 2G | 3.6G |
WAS Base V7.0.0.11 | eServer BladeCenter JS22 | AIX V6.1 TL 4 | 4 | 4.5G | 15.5G | Mashups Server - Node2 |
X3650 | RedHat Enterprise Linux (RHEL) 5.4 | 8 | 2G | 3.6G |
WAS Base V7.0.0.11 | eServer BladeCenter JS22 | AIX V6.1 TL 4 | 4 | 4.5G | 15.5G | MashupHub Server |
X3650 | RedHat Enterprise Linux (RHEL) 5.4 | 8 | 2G | 3.6G |
IBM DB2 Enterprise Edition V9.7 | eServer BladeCenter JS22 | AIX V6.1 TL 4 | 4 | 4.5G | 15.5G | Database |
Oracle 11.2 | X3650 | RedHat Enterprise Linux (RHEL) 5.4 | 8 | 2G | 3.6G |
ITDS6.0 | X3650 | Windows 2003 SP2 | 8 | 2G | 3.6G | LDAP |
IHS 7.0.0.11 | eServer BladeCenter JS22 | AIX V6.1 TL 4 | 4 | 4.5G | 15.5G | Web Server |
X3650 | RedHat Enterprise Linux (RHEL) 5.4 | 8 | 2G | 3.6G |
Feed Server | X3650 | Windows 2003 SP2 | 8 | 2G | 3.6G | Feed Server |
IVT Machine Specifications:
Software | Machine Type | OS | # of CPUs | CPU Speed | RAM (GB) | Function |
WAS ND V7.0.0.11 | Power PC 5 | AIX V6.1 TL 4 | 2 | 2G | 4 | Deployment Manager |
VM | RedHat Enterprise Linux (RHEL) 5.4 | 1 | 2.66G | 4 |
WAS Base V7.0.0.11 | Power PC 5 | AIX V6.1 TL 4AIX V6.1 TL 4 | 2 | 2G | 4 | Mashups Server - Node1 |
VM | RedHat Enterprise Linux (RHEL) 5.4 | 1 | 2.66G | 4 |
WAS Base V7.0.0.11 | Power PC 4 | AIX V6.1 TL 4 | 2 | 1.5G | 4 | Mashups Server - Node2 |
VM | RedHat Enterprise Linux (RHEL) 5.4 | 1 | 2.66G | 4 |
WAS Base V7.0.0.11 | Power PC 5 | AIX V6.1 TL 4AIX V6.1 TL 4 | 2 | 2G | 4 | MashupHub Server |
VM | RedHat Enterprise Linux (RHEL) 5.4 | 1 | 2.66G | 4 |
IBM DB2 Enterprise Edition V9.5 | Power PC 5 | AIX V6.1 TL 4 | 2 | 2G | 4 | Database |
Oracle 11.1.0.6.0 | VM | RedHat Enterprise Linux (RHEL) 5.4 | 1 | 2.66G | 4 |
ITDS 6.1 | VM | Windows 2003 SP2 | 1 | 2.66G | 4 | LDAP |
IHS 7.0.0.11 | Power PC 5 | AIX V6.1 TL 4 | 2 | 2G | 4 | Web Server |
VM | RedHat Enterprise Linux (RHEL) 5.4 | 1 | 2.66G | 4 |
IBM Edge Caching Proxy 7.0 | X335 | Windows 2003 SP2 | 4 | 3.06 GHz | 4 | Reverse Proxy |
IBM Edge Caching Proxy 7.0 | VM | Windows 2003 SP2 | 1 | 2.66G | 2 | Forward Proxy |
IBM Edge Caching Proxy 7.0 | X3650 | SUSE Linux Enterprise Server 11 | 4 | 2G | 4 | Transparent Proxy |
Installation and configuration
Refer to the topics from the
IBM Mashup Center Infocenter listed in the steps below for more detailed instructions on the steps to install and configure the environment used for this test.
The environment was installed with the following steps:
1.0 Install Lotus mashups on ServerA and ServerB with same parameters settings.
2.0 Install WAS ND 7.0.0.0 as a DM Server, apply fixpack 7.0.0.11.
3.0 Install IHS. Here we just install DM and IHS in the same box.
4.0 Setup the MashupHub server on ServerC.
(1) Install IHS and MashupHub on ServerC.
(2) Configure the IHS on ServerC as the web server for Hub server.
(3) Configure the LDAP Server for Hub Server. (using the same user repository with mashups cluster.)
(4) Enable the SSL for the Hub server environment.
(5) Update server.config.ini file.
(6) Configure the DB persistence for Hub Server if required.
5.0 Configure two lotus Mashups Servers to share one common DB.
6.0 Update the preferences in DM Server:
(1) Enable "Synchronize changes with Nodes"
(2) Enable "application security"
(3) Security -> Global security -> Web and SIP security -> General settings, enable these two options:
"Use available authentication data when an unprotected URI is accessed"
"Default to basic authentication when certificate authentication for the HTTPS client fails"
7.0 Federate two mashups server as managed node servers.
8.0 Create the new cluster
9.0 Create Web Server:
(1) Federate the IHS server on ServerA as unmanaged node server
(2) Create the web server
(3) Enable the "Accept content for all requests" setting for web server
10.0 Start the cluster environment.
11.0 Configure LDAP Server on DM Server for the cluster environment. The LDAP should be the same one that's configured to Hub server.
12.0 If required, enable SSL for Lotus Mashups Cluster
(1) Enable SSL for the IHS server which is configured with cluster
(2) Enable SSL between IHS and Lotus Mashups Cluster
(3) Configure Cluster to connect to LDAP server by using "ldaps", 636 port.
13.0 Configure the Mashups server on primary node to connect to the remote Hub server
(1) Update the Hub connection
(2) Enable SSO
14.0 Specify the cluster name.
15.0 Configure content shelf for Louts Mashups Cluster to Hub mode.
16.0 Create "Administrators" group in DM admin console, and add your WAS admin user as its member.
17.0 Create "com.ibm.portal.auth.tai.HTTPBasicAuthTAI" interceptor manually in DM admin console.
18.0 Install mashups OOB widgets on the Hub server
19.0 Load Welcome Space in the Lotus Mashups Cluster.
20.0 Update gadget configuration files to make gadget work in cluster environment.
21.0 Restart all servers.
22.0 If required, setup the IBM edge caching proxy server for the Lotus Mashups cluster environment.
Test user configuration
In this deployment scenario, we focus on the both Reliability Verification Test (RVT) and Interoperability Verification Test (IVT).
For RVT, this environment was load and stress tested using RPT (Rational Performance Tester) with up to 1000 concurrent users doing basic actions (including CRUD page/space/widget and others) for 120 continuous hours, the Transactions per Second (TPS) is 83.
For IVT, we tested all basic functions to make sure that all the components functioned together properly with the customized configurations in the clustered environment.