Overview The following performance target was attempted on this deployment:
- 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 process, and each process runs under one WAS profile. For example:
- Activities on Server1
- Blogs on Server2
- Communities on Server3
- Dogear on Server4
- Profiles on Server5
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 CPU, 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 CPU, 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 CPU, 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 CPU, 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. See http://publib.boulder.ibm.com/infocenter/ltscnnct/v1r0/topic/com.ibm.help.lotus.connections.doc/t_config_ldap_102.html
.
2. Create the features databases. See http://publib.boulder.ibm.com/infocenter/ltscnnct/v1r0/topic/com.ibm.help.lotus.connections.doc/t_create_dbs_over_102.html
.
3. Create the profiles database. See http://publib.boulder.ibm.com/infocenter/ltscnnct/v1r0/topic/com.ibm.help.lotus.connections.doc/t_prof_install_profiles_db_102.html
.
4. Install WebSphere Deployment Manager. See http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tins_customn.html
.
5. Install IBM WebSphere Application Server (WAS). See http://publib.boulder.ibm.com/infocenter/ltscnnct/v1r0/topic/com.ibm.help.lotus.connections.doc/t_install_was_102.html
.
6. Install IBM HTTP Server (IHS). See http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.ihs.doc/info/ihs/ihs/tihs_installihs.html
.
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 server processes under one WAS profile, install each feature on both nodes, and then add the nodes to the Deployment Manager.
1. Create multiple server processes on Node 1:
- Create a JACL file named createConnectionsServer.jacl and copy the following code into the file:
#
* PLEASE READ THIS IMPORTANT NOTE REGARDING THE FOLLOWING CODE *
# In the lines of code below, the characters \r identify a carriage return.
#
These visual carriage returns were added to this document to prevent
# long lines of text from running off the printed page.
#
# DO NOT not include the \r in your file; instead, remove it and
#
add the line it identifies as a broken line to your file as a single
# line.
#
Create a server using the supplied server name and node
# createConnectionsServer.jacl
#
# Create the servers for Lotus Connections
#
About:
# This script uses the given node and server arguments to create
#
Lotus Connections servers on a Webphere Application Server.
#
#
Usage:
# wsadmin.sh -username system \
#
-password password \
# -f /createConnectionsServer.jacl server
#
# Parameters:
#
arg1 - server to create
#
#
Servers:
# Activities - ActivitiesServer
#
Blogs - BlogServer
# Communities - CommunitiesServer
#
Dogear - DogearServer
# Profiles - ProfilesServer
#
proc createserver {serverArg} {
#
#
Globals
#
global AdminConfig
global AdminControl
global AdminApp
set node [$AdminConfig list Node]
set nodeName [$AdminConfig showAttribute $node name]
#
# Is a server by this name already running on the node?
###
puts "createConnectionsServer: Checking to see if server $serverArg is \r
already running on node $nodeName"
set runningServer [$AdminControl completeObjectName \r
type=Server,node=$nodeName,process=$serverArg,*]
if {[llength $runningServer] > 0} {
puts "createConnectionsServer: Error -- Server $serverArg \r
already running on node $nodeName"
puts "createConnectionsServer: Error -- exiting script"
return
}
puts "createConnectionsServer: Creating the server $serverArg on \r
node $nodeName..."
set name_attribute [list name $serverArg]
set attributes [list $name_attribute]
set server [$AdminConfig create Server $node $attributes]
#
# Save the change
#
puts "createConnectionsServer: Saving the configuration"
$AdminConfig save
}
#
#
Main
#
puts "createConnectionsServer: Starting - Lotus Connections server creation"
if { !($argc == 1) } {
puts "createConnectionsServer: This script requires a parameter: \r
the server to create"
puts "e.g.: createConnectionsServer.jacl ActivitiesServer"
puts " createConnectionsServer.jacl BlogsServer"
puts " createConnectionsServer.jacl CommunitiesServer"
puts " createConnectionsServer.jacl DogearServer"
puts " createConnectionsServer.jacl ProfilesServer"
} else {
set serverArg [lindex $argv 0]
createserver $serverArg
}
puts "createConnectionsServer: Finished - Lotus Connections server creation"{{}}
- Copy the createConnectionsServer.jacl file into the bin directory of the WAS profile. The default location is:
- AIX: /usr/IBM/WebSphere/AppServer/profiles/AppSrv01/bin
- Linux: /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin
- Windows: C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\bin
- Start the WAS profile by running the following command:
- AIX/Linux: ./startServer.sh server1
- Windows: startServer.bat server1
- Launch the JACL file by running the following command:
- AIX/Linux: ./wsadmin.sh - - -f createConnectionsServer.jacl
- Windows: wsadmin.bat - - -f createConnectionsServer.jacl (where is the WebSphere administrator's user name, is the WebSphere administrator password, and is the name of the server that you want to create.)
- Repeat step d for each additional server in the current WAS profile, changing to the name of each of the other servers in the WAS profile.
2. Create multiple server processes on Node 2 of the cluster by repeating step 1. Remember to change
to the name of each server on Node 2. For example, if the servers on Node 1 are named Server1, Server2, Server3, and so on, then the servers on Node 2 should be named Server6, Server7, Server8, and so on..
3. Install Lotus Connections features on all the nodes. See http://publib.boulder.ibm.com/infocenter/ltscnnct/v1r0/topic/com.ibm.help.lotus.connections.doc/t_install_standalone_102.html
.
4. Add the nodes to the Deployment manager to create a cluster environment. See http://publib.boulder.ibm.com/infocenter/ltscnnct/v1r0/topic/com.ibm.help.lotus.connections.doc/c_install_cluster_over_102.html
.
5. Configure the IBM HTTP Server to manage connections to the product. See http://publib.boulder.ibm.com/infocenter/ltscnnct/v1r0/topic/com.ibm.help.lotus.connections.doc/c_add_ihs_over_102.html
.
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
.