Overview
This deployment had the following performance target:
- 15 TPS (Transactions Per Second)
with 300 concurrent users.
Infrastructure
The following figure illustrates the topology used in this deployment:
This deployment installs each feature on a separate WAS profile. For example:
- Activities on Server 1 on WAS Profile
1
- Blogs on Server 1 on WAS Profile
2
- Communities on Server 1 on WAS
Profile 3
- Dogear on Server 1 on WAS Profile
4
- Profiles on Server 1 on WAS Profile
5
Specifications
The following table lists the specifications of the systems used in this
deployment:
| Component
| Software
| OS
| Specs
|
| Web Server
| IBM HTTP Server 6.1.0.3
| AIX
Linux, Windows
| 2 Dual-Core CPUs,
2.0 GHz, 8 GB RAM
1 Quad-Core CPU, 1.6 GHz, 4 GB RAM
|
| Deployment Manager
| IBM WebSphere Application
Server 6.1.0.3
| AIX
Linux, Windows
| 2 Dual-Core CPUs,
2.0 GHz, 8 GB RAM
1 Quad-Core CPU, 1.6 GHz, 4 GB RAM
|
| Cluster Node 1
| IBM WebSphere Application
Server 6.1.0.3
| AIX
Linux, Windows
| 2 Dual-Core CPUs,
2.0 GHz, 8 GB RAM
2 Quad-Core CPUs, 1.6 GHz, 4 GB RAM
|
| Cluster Node 2
| IBM WebSphere Application
Server 6.1.0.3
| AIX
Linux, Windows
| 2 Dual-Core CPUs,
2.0 GHz, 8 GB RAM
2 Quad-Core CPUs, 1.6 GHz, 4 GB RAM
|
| Database
| DB2 9.1
| AIX
Linux, Windows
| 2 Dual-Core CPUs,
2.0 GHz, 8 GB RAM
2 Quad-Core CPUs, 1.6 GHz, 4 GB RAM
|
| LDAP
| IBM Directory Server
6.0, Domino 7/8, Active Directory 2003, or Sun One iPlanet 5.2
| AIX
Linux, Windows
| 2 Dual-Core CPUs,
2.0 GHz, 8 GB RAM
2 Quad-Core CPUs, 1.6 GHz, 4 GB RAM |
Notes
- Linux versions used in this deployment:
Red Hat Enterprise Linux ES release 4 (Nahant Update 4); SUSE Linux Enterprise
Server 10.
- Windows version: Microsoft Windows
2003 Server, Standard Edition
- AIX: 5.3.0.6, 64-bit
Step-by-Step instructions
Before deploying this infrastructure, the product and all related components
must be installed.
Installation
1. Prepare
LDAP .
2. Create
the features databases .
3. Create
the profiles database .
4. Install
WebSphere Deployment Manager .
5. Install
IBM WebSphere Application Server (WAS). .
6. Install
IBM HTTP Server (IHS). .
7. Prepare
content storage: configure network share directories for the activities
and blogs clusters. See http://publib.boulder.ibm.com/infocenter/ltscnnct/v1r0/topic/com.ibm.help.lotus.connections.doc/t_activities_install_102.html
and http://publib.boulder.ibm.com/infocenter/ltscnnct/v1r0/topic/com.ibm.help.lotus.connections.doc/t_blogs_snapshot_dir.html .
Deployment
To enable this deployment, you need to create multiple WAS profiles, install
each feature on a WAS profile on both nodes, and then add the nodes to
the Deployment Manager.
1. Create
multiple profiles on Node 1 .
If you install all five features, you will need to create five WAS profiles
and one server process for each profile.
2. Create
multiple profiles on Node 2 by repeating step 1 to create five profiles
on Node 2 and one server process for each profile.
3. Install
Lotus Connections features on the nodes. .
4. Add
the nodes to the Deployment manager to create a cluster environment. .
5. Configure
the IBM HTTP Server to manage connections to the product. .
6. Verify
the configuration. Copy the following URLs into your browser to verify
that you can access each feature:
- http: ///activities
- http: ///blogs
- http: ///communities
- http: ///dogear
- http: ///profiles
Recommended reading
For more information, please see: http://publib.boulder.ibm.com/infocenter/ltscnnct/v1r0/index.jsp .
|
|
|
|
| This Version: |
0 |
August 19, 2008 |
10:36:43 AM |
by developerWorks Lotus Team |
| Originally Added: |
Version 1 |
January 16, 2008 |
3:19:41 PM |
by Jun He |
|
|
|