IHS多WAS集群负载均衡和会话同步架构的实现.doc

IBM Http Server + WebSphere集群的负载均衡和会话保持一.系统准备服务器1：IP1 & 服务器2：IP2OS: Linux AS 5.0 APP:IHS+WAS (V6.1)在两台服务器上/etc/hosts文件下相互添加ip地址和主机名p.s. 若安装WAS V6.1时安装界面无法打开，则需安装firefox浏览器 先安装WAS再安装IHS。二.系统架构最终模式图：因现有应用限制，现拓扑图如下三.集群安装1. 安装应用服务器1作为主服务器安装Cell（含DM和websphere）端口号： 服务器2创建单独的应用程序服务器(websphere)p.s. 为了搭建一个完整的WebSphere Application Server 运行环境，你至少要创建一个概要文件。该概要文件叫做缺省概要文件。缺省概要文件通常是在安装WebSphere Application Server 的时候创建的。但是，你也可以在安装好WebSphere Application Server 之后再另行创建概要文件。两种创建概要文件的方法的结果都是一样的，都可以完成搭建一个完整的WebSphere Application Server 运行环境。2.配置集群（1）启动节点1/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin 执行./startNode.sh 如下：rootus01 bin# ./startNode.shADMU0116I: Tool information is being logged in file /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/nodeagent/startServer.logADMU0128I: Starting tool with the AppSrv01 profileADMU3100I: Reading configuration for server: nodeagentADMU3200I: Server launched. Waiting for initialization status.ADMU3000I: Server nodeagent open for e-business; process id is 4124（2）启动DM/WebSphere/AppServer/profiles/Dmgr01/bin执行./startManager.sh如下：rootus01 bin# ./startManager.shADMU0116I: Tool information is being logged in file /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/dmgr/startServer.logADMU0128I: Starting tool with the Dmgr01 profileADMU3100I: Reading configuration for server: dmgrADMU3200I: Server launched. Waiting for initialization status.ADMU3000I: Server dmgr open for e-business; process id is 4338启动DM后，可访问http:/IP1:9060/admin（3）增加节点到主机中./addNode.sh IP1 8879 -username admin -password adminus51 (也可用./addNode.sh IP1 8879 系统会提示你输入DM的用户名和密码)对这个命令的解释如下：IP1 : DM服务器的IP8879:DM的SOAP端口号 Username:DM控制台的用户名 Password:DM控制台的密码如下：rootus01 bin# ./addNode.sh 1 8879 -username admin -password adminus51ADMU0116I: Tool information is being logged in file /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/addNode.logADMU0128I: Starting tool with the AppSrv01 profileCWPKI0308I: Adding signer alias dummyclientsigner to local keystore ClientDefaultTrustStore with the following SHA digest: 0B:3F:C9:E0:70:54:58:F7:FD:81:80:70:83:A6:D0:92:38:7A:54:CDCWPKI0308I: Adding signer alias dummyserversigner to local keystore ClientDefaultTrustStore with the following SHA digest: FB:38:FE:E6:CF:89:BA:01:67:8F:C2:30:74:84:E2:40:2C:B4:B5:65ADMU0001I: Begin federation of node us01Node01 with Deployment Manager at 1:8879.ADMU0001I: Begin federation of node us01Node01 with Deployment Manager at 1:8879.ADMU0009I: Successfully connected to Deployment Manager Server: 1:8879ADMU0033E: The node us01Node01 already has been added to the cell.ADMU0027E: An error occurred during federation ADMU0033E: The node us01Node01 already has been added to the cell.; rolling back to original configuration.ADMU0211I: Error details may be seen in the file: /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/addNode.logADMU0111E: Program exiting with error: com.ibm.ws.management.tools.DoNotDoAddNodeException: ADMU0033E: The node us01Node01 already has been added to the cell.ADMU1211I: To obtain a full trace of the failure, use the -trace option.ADMU0211I: Error details may be seen in the file: /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/addNode.log(4) 在服务器2中重复第(3)步，将服务器2节点加入DM./addNode.sh 1 8879 -username admin -password adminus51如下：rootus02 bin# ./addNode.sh 1 8879 -username admin -password adminus51ADMU0116I: Tool information is being logged in file /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/addNode.logADMU0128I: Starting tool with the AppSrv01 profileCWPKI0308I: Adding signer alias CN=us01, O=IBM, C=US to local keystore ClientDefaultTrustStore with the following SHA digest: F6:DD:0C:04:9D:33:69:FE:A1:4C:48:80:9E:95:6F:0F:99:39:CD:2BCWPKI0308I: Adding signer alias dummyclientsigner to local keystore ClientDefaultTrustStore with the following SHA digest: 0B:3F:C9:E0:70:54:58:F7:FD:81:80:70:83:A6:D0:92:38:7A:54:CDCWPKI0308I: Adding signer alias dummyserversigner to local keystore ClientDefaultTrustStore with the following SHA digest: FB:38:FE:E6:CF:89:BA:01:67:8F:C2:30:74:84:E2:40:2C:B4:B5:65ADMU0001I: Begin federation of node us02Node01 with Deployment Manager at 1:8879.ADMU0001I: Begin federation of node us02Node01 with Deployment Manager at 1:8879.ADMU0009I: Successfully connected to Deployment Manager Server: 1:8879ADMU0505I: Servers found in configuration:ADMU0506I: Server name: server1ADMU2010I: Stopping all server processes for node us02Node01ADMU0512I: Server server1 cannot be reached. It appears to be stopped.ADMU0024I: Deleting the old backup directory.ADMU0015I: Backing up the original cell repository.ADMU0012I: Creating Node Agent configuration for node: us02Node01ADMU0014I: Adding node us02Node01 configuration to cell: us01Cell01ADMU0016I: Synchronizing configuration between node and cell.ADMU0018I: Launching Node Agent process for node: us02Node01ADMU0020I: Reading configuration for Node Agent process: nodeagentADMU0022I: Node Agent launched. Waiting for initialization status.ADMU0030I: Node Agent initialization completed successfully. Process id is: 26001ADMU9990I: ADMU0300I: The node us02Node01 was successfully added to the us01Cell01 cell.ADMU9990I: ADMU0306I: Note:ADMU0302I: Any cell-level documents from the standalone us01Cell01 configuration have not been migrated to the new cell.ADMU0307I: You might want to:ADMU0303I: Update the configuration on the us01Cell01 Deployment Manager with values from the old cell-level documents.ADMU9990I: ADMU0306I: Note:ADMU0304I: Because -includeapps was not specified, applications installed on the standalone node were not installed on the new cell.ADMU0307I: You might want to:ADMU0305I: Install applications onto the us01Cell01 cell using wsadmin $AdminApp or the Administrative Console.ADMU9990I: ADMU0003I: Node us02Node01 has been successfully federated.（5）创建新集群 p.s.创建新集群的时候注意勾选”配置HTTP会话内存到内存复制”，这样就能使session在集群内共享(打个比方：用户A登录，假设被分配至NodeA节点来处理，用户的登录信息被保存至session中，如果此时NodeA宕机，A用户被分配到其他节点处理时就不会被要求重新登录)；如没有在创建集群时选择”配置HTTP会话内存到内存复制”也可以按如下方式操作：配置会话复制服务器 应用程序服务器 选择集群成员 容器设置：会话管理 其他属性：分发环境设置 确认分布式会话选择的是内存到内存复制，其他属性：定制调整参数 调整级别： 低（故障转移优化） 写频率 servlet 服务结束 写内容 所有会话属性 调度会话清除： false对集群的每个成员重复以上操作。（注：实际生产环境中如果设置为故障转移优化，需要考虑对性能的影响。）(6)加入服务器1节点p.s. 注意此处的权重：节点1 权重为2，节点2 权重为1则表示节点1 分流三分之二的流量，而主机2 分流三分之一的流量。(7) 加入服务器2节点(8)创建完毕p.s.若此时发布应用，可选择发布在集群，可通过：http:/IP1:9081/上下文/index.jsphttp:/IP2:9081/上下文/index.jsp访问。3.IBM Http Server的安装之前的操作仅是创建了集群，在集群上发布应用，此时并不能达到访问单个IP而后台实现负载均衡，而我们的目的是能通过集群提高系统的可用性和可靠性，故需要配置IHS来实现负载均衡。（1）在服务器1