Copyright Notice: This article can be reproduced, please be sure to indicate the original source and author information in hyperlink when reprint. Original Source: http://www.aiview.com/notes/was_cluster_deploy.htm Author: Zhang Yang Alex_doesAThotmail.com Last Updated: 2004-12-3
table of Contents
Server Software and Hardware Environment Deployment Steps WAS and Linux Compatibility Reference Resources
According to the practice of the author in the project, this article describes the general steps to deploy IBM WebSphere5.0 Cluster on the Redhat Linux Enterprise. If you are interested, welcome to letter.
Server hardware and software environment
Linux operating system version: RHEL 2.1 (Red Hat Enterprise Linux) Application Server version: IBM WebSphere Application Server 5.0 Database Version: IBM DB2 UDB V8.1
4 XSeries 335, dual SCSI hard drives, a temporary unused. 1 XSeries 345, a dual SCSI hard disk, a mirror, a disk array, using a 345 RAID card. Disk arrays, 6 SCSI disks, 5 pieces have made RAID 5, and the remaining SPARE disc.
Four 335 hosts are used for WebSphere clusters, which will be installed in one of the WASPhere Network Deployment, called management nodes, other three-installed WAS service and DB2 client, called business nodes, one one The node installs IHS (IBM HTTP Server).
Deployment steps
To install RHEL 2.1 for 5 servers, if you are processed, you need to select language pack support during the installation process; install DB2 service on the 345 host, create a database; install WAS 5.0 on the three business nodes, then install WAS FP2; At the business node installed IHS; in order to access the database, the above three business nodes need to install the DB2 V8.1 runtime client, after the installation is complete, run /opt/ibm/db2/v8.1/instance/db2icrt creation instance, catalog Remote data host node, cataloging remote database; install the WAS ND version on the rest of the management node, then install WAS ND FP2; configure the WAS service:
The following statement is added to the startServer.sh file:. / Home / DB2 / SQLLIB / DB2PROFILE The path in front of the DB2 instance is different from the DB2 instance installation location; configuring the WAS environment variable DB2_JDBC_DRIVER_PATH as: /opt/ibm/db2/v8.1 / Java establishes a secure username and password, which needs to access the remote database; set the data source, the driver uses '{db2_jdbc_driver_path} /db2java.zip', the database name uses the above-mentioned remote database alias, select the authentication alias; Once you can use the test data source function test whether you can access the database (only if you have FIX PACK 2 to provide test function); start the WAS, access the http: // localhost: 9090 / admin Deployment application, deploy the application, by the following address Visit: http:// localhost: 9080 / appname
The above is the general step of the configuration. After the configuration is successful, the deployment can be accessed by the business node installed in IHS, and the load will be distributed on three business nodes, and the WAS ND is transferred to the company. High availability, and load balancing of business processing. With the expansion of enterprise business scale, it can easily handle a large number of requests by adding nodes. For network configurations of the above host, just install the business node of the IHS requires a public IP address for external release of Web services. Other nodes are configured inside address, which can be placed in a secure area, especially database servers, which can set a stricter security policy, which is not discussed in depth.
WAS and Linux compatibility
According to IBM and Redhat's official information, WAS and RH Linux correspondence is as follows:
WAS 5.0 RHEL 2.0 As WAS 5.1 RHEL 3.0 AS UPDATE Level 1
RHEL 3.0 official statement can support IBM WAS 5.1, but you need to upgrade to RHEL UPDATE Level 1 upgrade package, you also need to install some other patches.
WAS 5.0 is unable to install success on RHEL 3.0, because RHEL uses JDK1.4, while WAS 5.0 is JDK1.3.1. If installing in such an environment, the installation process will report the following error:
Segment fault.
Try to set the following environment variables, and cannot resolve this issue, so version selection, you must understand when planning, and can be done in order to deploy trouble.
LD_assume_kernel = 2.2.5 or ld_assume_kernel = 2.4.19 rpm_force_nptl = 1
Reference resource
IBM WebSphere Developer Garden http://www-900.ibm.com/developerWorks/cn/wsdd/
