WHITE PAPER WEBSPHERE CLUSTER AND IBM HTTP SERVER CONFIGURATION FOR XCP ABSTRACT This white paper explains the best way to configure IBM WebSphere 8.5.5.2 in a cluster environment with IBM HTTP Server as the load balancer for EMC Documentum xCP. December, 2015
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
WHITE PAPER
WEBSPHERE CLUSTER AND IBM HTTP SERVER CONFIGURATION FOR XCP
ABSTRACT
This white paper explains the best way to configure IBM WebSphere 8.5.5.2 in a
cluster environment with IBM HTTP Server as the load balancer for EMC
Documentum xCP.
December, 2015
2
To learn more about how EMC products, services, and solutions can help solve your business and IT challenges, contact your
local representative or authorized reseller, visit www.emc.com, or explore and compare products in the EMC Store
Copyright © 2015 EMC Corporation. All Rights Reserved.
EMC believes the information in this publication is accurate as of its publication date. The information is subject to change
without notice.
The information in this publication is provided “as is.” EMC Corporation makes no representations or warranties of any kind with
respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a
particular purpose.
Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.
For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.
VMware is a registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions. All other
trademarks used herein are the property of their respective owners.
Part Number H14756
3
TABLE OF CONTENTS
EXECUTIVE SUMMARY .............................................................................. 4 AUDIENCE ....................................................................................................... 4
CONFIGURING IBM WEBSPHERE APPLICATION SERVER IN A CLUSTER .... 5
INSTALLING WEBSPHERE APPLICATION SERVER NETWORK DEPLOYER .. 6
INSTALLING WEBSPHERE APPLICATION SERVER .................................. 23
INSTALL AND CONFIGURE IBM HTTP SERVER AND PLUGINS ................. 34
ADDING NODES TO THE DEPLOYMENT MANAGER PROFILE .................... 62
CREATING A CLUSTER ............................................................................ 65
INTEGRATING IBM HTTP SERVER TO THE CLUSTER ENVIRONMENT ....... 71
GENERATING IBM HTTP SERVER PLUG-IN FILE AND ENABLING JAVA ... 75
PROVISIONING THE ENVIRONMENT FOR XCP AND VERIFICATION OF
DEPLOYMENT ......................................................................................... 77
FAILOVER IN WEBSPRHERE CLUSTER WITH XCP ................................... 79
CONCLUSION ......................................................................................... 79
4
EXECUTIVE SUMMARY
This guide explains the best way to successfully install and configure an IBM WebSphere Application Server 8.5.5.2 with EMC
Documentum xCP in a clustered environment to enable high availability and failover. WebSphere Application server needs
minimum 3 nodes for Memory-to-memory replication, which is required for WebSphere failover. Configure the cluster with the
widely used IBM HTTP Server as the Load balancer, through which users can access the xCP application.
AUDIENCE
This guide addresses the Customers, Tech Support Engineers, Developers and Testers who understand the process of installing
and configuring IBM WebSphere Application Server 8.5.5.2 on multiple machines in a clustered environment with load balancing
and the configurations needed to deploy the xCP application on a WebSphere cluster. We assume that you possess working
knowledge of Documentum xCP. The xCP Deployment Guide provides further details on the deployment procedures on xCP
stack.
5
CONFIGURING IBM WEBSPHERE APPLICATION SERVER IN A CLUSTER
The procedure of setting up WebSphere cluster includes the task of installation and configurations on multiple computers. You
will need four computers at minimum.
First machine will have Deployment manager and WebSphere AppServer instance (Node1).
Second and Third machine (Node2 and Node3 machines) will have WebSphere AppServer instance.
Fourth machine (LoadBalancer machine) will have IBM Http Server configured for load balancing.
You must perform the following tasks to configure the IBM WebSphere cluster on a 3 node clustered environment. Detailed steps
for each task are given in the next section.
First install IBM installation manager on Deployment manager, both WebSphere AppServer instance machines and load
balancer.
Install the WebSphere Application Server Network Deployment 8.5.5.2.
Install WebSphere Application Server 8.5.5.2.
Install the IBM HTTP Server 8.5.5.2.
Configure the XMS to the cluster set up and deploy the xCP application on cluster.
Note: Install the supported JAVA SDK in all the machines using the IBM installation manager if it’s different from the default
JAVA that gets installed.
High level diagram of WebSphere cluster with IBM HTTP Server can be seen in Fig 1:
Fig 1
WebSphere Network Deployment
Node 1 Node 3 Node 2
IBM HTTP Server
End User
6
INSTALLING WEBSPHERE APPLICATION SERVER NETWORK DEPLOYER
1. This section lists the instructions to install WebSphere Application Server Network Deployment. This document covers
WebSphere cluster setup for Windows 64 bit.
2. Log on to the Node1 machine.
3. Install the IBM Installation Manager. Start the instance once installed. Go to File > Preferences > Passport Advantage.
Enable the checkbox Connect to Passport Advantage to connect to IBM online repository and select Apply and click OK.
7
4. Now in the IBM Installation Manager click install. The installer will prompt you to enter credentials to connect to the IBM
download site. Enter valid credentials and click OK.
8
9
5. From the install packages, select “Show All versions”. Browse for all options and select IBM WebSphere Application Server
Network Deployment 8.5.5.2. Click Next.
10
6. Select the recommended fixes and click Next.
11
7. Then Software License Agreement page is displayed. Select the option “I accept the terms in the license agreement”.
Click Next.
12
13
14
8. Review the summary and install the IBM WebSphere Application Server Network Deployment.
15
9. Select None option for the next action to be performed and click Finish.
16
To Create Cell and profile:
1. To install Cell (Deployment Manager and a managed node) and Profile, navigate to
Start > All programs > IBM WebSphere > WebSphere Customization Toolbox. From the WebSphere customization tool box
8.5, select Profile Management Tool and click on ‘Launch Selected Tool’.
17
2. Click the Create button on the next page.
18
3. In the Environment Selection, select the Cell (deployment manager and a federated application server) and click Next.
19
4. In the Profile Creation Options wizard select default option “Typical profile creation” and click Next.
20
5. In the Administrative Security page clear the checkbox Enable administrative security and click Next.
21
6. In the Profile Creation Summary page, review the summary listing and click Create. The IBM WebSphere Application Server
Network Deployment Version 8.5.5.2 installation has started. When the installation is completed, the Installation Results
page appears indicating successful installation. Click on Finish and you can note the profiles being created.
22
23
INSTALLING WEBSPHERE APPLICATION SERVER
1. Now log in to the Node2 and install installation manager following the steps as in the above section.
2. From the Install Packages wizard, select the Show all versions checkbox option.
3. Browse through the options and select IBM WebSphere Application Sever 8.5.5.2 and click Next.
24
4. Select the required fixes from recommended fixes for the Application Server and click Next.
25
5. Now follow the instructions as shown.
26
27
28
29
6. Once the WebSphere Application Server installation is complete, navigate to WebSphere Customization Toolbox and create a
profile. Click on Create on the Profile Management Tool.
30
7. In the Environment Selection, select the Application Server and click Next. Follow the steps given below to proceed.
31
32
33
8. Once the above steps are completed, the application server profile gets created successfully on Node2.
9. Repeat the same steps on the other application server node (Node3) to complete the WebSphere cluster setup on 3 nodes.
34
INSTALL AND CONFIGURE IBM HTTP SERVER AND PLUGINS
1. Login to the Load Balancer machine.
2. Install the installation manager. Start the instance once installed.
3. In the Install Packages wizard select the following:
IBM HTTP Server for WebSphere Application Server, Web Server Plug-ins for IBM WebSphere Application Server, WebSphere
Customization Toolbox of the required version and click Next.
35
36
4. Accept the recommended fixes and click Next.
37
5. In the License agreement page accept the terms and click Next.
38
6. Follow the steps as given below.
39
40
7. In the configuration for IBM HTTP Server page, check the HTTP port values. Ensure that the port numbers are unique and do
not conflict with other services running on this host machine. On the same page The Windows Service Definition page is
displayed.
8. Select the checkbox Run IBM HTTP Server as a Windows Service.
9. Select the option Log on as a specified user account.
10. Enter the User name and Password details. (Windows user id/password) and click on Verify Password. Upon Successful
Authentication, click Next, The Installation summary page is displayed.
41
11. Review the summary information and click install.
42
12. When the installation is complete, the last page of the IBM HTTP Server installer indicates that packages were installed.
13. After Successful installation of IBM HTTP server, Webserver plugins and Customization Toolbox, select None and click Finish
in the dialog box.
43
14. Again launch IBM Installation Manager and select the Network Deployment repository and click to proceed.
15. Repeat the same steps to install Network deployment manager by selecting desired repository shown below.
16. Click on Next and further follow the same steps as shown in Network deployment installation section.
44
45
17. Upon Successful Installation, it will prompt you to create Profile.
18. Select Profile Management Tool to create a profile option and click Finish.
46
19. Click on Create button to create custom profile.
20. Select Custom profile and click Next. Profile creation options page is displayed.
47
21. Select the default option and click on Next. Federation Page is displayed.
48
22. Select Federate this node later using the addNode command. Click Next. Profile Creation Summary page is displayed.
49
23. Review the summary and click Create.
50
24. Profile Creation Complete page is displayed. Click Finish to complete the installation.
51
25. Now open the Customization Toolbox and select the Welcome tab to select Web Server Plug-ins Configuration Tool.
52
26. Click on Add button on the Web Server Plug-ins Configuration Tool dialog box.
27. Provide a name and location of the Web Server plug-ins.
53
28. Now click Create button.
54
29. Select the option IBM HTTP Sever V8.5 in the Web Server Selection and click Next.
55
30. Provide the location of the httpd.conf file of the IBM HTTP Server and specify the Web server port.
56
31. Review the information in Setup IBM HTTP Server Administration Server page and click Next.
57
32. Enable the IBM HTTP server service option if required and click Next.
58
33. Provide a unique name for the Web server and click Next.
59
34. In the Configuration Scenario Selection Page, select the remote option and provide the IP of the same machine where the
IBM HTTP server is being installed.
60
35. In the Summary page, review the configurations and click Configure.
61
36. Click Finish on successful installation.
62
ADDING NODES TO THE DEPLOYMENT MANAGER PROFILE
Once the individual application servers are created, they need to be mapped to the Deployment Manager. You need to add IBM
WebSphere Application Server nodes to the deployment manager prior you create the cluster.
To add nodes to the deployment manager:
1. Login to Deployment Manager (Node1) machine.
2. Open command prompt. Go to the location where Deployment Manager profile is located:
C:\IBM\WebSphere\AppServer\profiles\Dmgr01\bin
3. Execute the following command at the command prompt to start the Deployment Manager :
startManager.bat
4. Login to Node2 and Node3 machines.
5. Open command prompt. Go to the location where Application Server profile is located: :
C:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin
6. Execute the following command at the command prompt to add a new node to the Deployment Manager profile:
addNode.bat dmgr_host [dmgr_soap_connector_port].
For example, execute the following command:
addNode.bat <hostname/IP> 8879
Note: Add details of all the machines involved in the cluster to the hosts file, else execution of this command may fail
sometimes.
63
7. Login to Load Balancer (LB) machine.
8. Open command prompt. Go to location where the custom profile is located:
C:\Program Files(x86)\IBM\WebSphere\AppServer\profiles\Custom01\bin
9. Execute the following command at the command prompt to add a new node to the Deployment Manager profile:
addNode.bat dmgr_host [dmgr_soap_connector_port]
10. Open a Web browser and enter the following URL to access the WebSphere Network Deployment manager administrator
console:
http://<Depmnger IP>:9060/admin
11. Check whether the four nodes have been added to the relevant deployment manager profiles and are synchronized properly
as illustrated in the following two figures.
12. From the IBM console, go to System administration > Nodes & System administration > Node agents to verify the
functionality.
Note: If the nodes don’t get started by default use the command: startNode.bat from the respective profile location of
each machine.
64
65
CREATING A CLUSTER
Access the Deployment Manager Administrator console in the browser using the following URL to create a cluster:
http://<ip>:<port>/admin. Follow these to create a cluster:
1. In the left pane, expand the Servers node and expand Clusters and click WebSphere application server Cluster. The Server
clusters page is displayed in the right pane.
66
2. Click New. The Enter basic cluster information page is displayed.
3. In the Cluster name field, specify the cluster name.
4. Select the checkbox Configure HTTP session memory-to-memory replication. Click Next.
67
5. The Create new cluster member page is displayed.
6. In the Member name field, specify a unique member name.
7. In the Select node list, select the required node (First node-Node1).
8. Select the checkbox Generate unique HTTP ports. Accept the other default settings.
9. Click Next. The Create additional cluster member’s page is displayed.
68
10. Specify the member name, select the required node, and select the checkbox Generate unique HTTP ports.
11. Click Add Member to add the additional cluster member to the list below. Repeat steps 10 and 11 to add new cluster
members.
12. Click Next. The Summary page is displayed.
69
13. Review the Summary and click Finish. The WebSphere Application Server Clusters page is displayed with the cluster created.
70
71
INTEGRATING THE IBM HTTP SERVER TO THE CLUSTER ENVIRONMENT
IBM HTTP Server has to be integrated with the clustered environment to delegate incoming requests from the client to the
available application server instances. To integrate the IBM HTTP Server:
1. Go to the Deployment Manager Administrator Console. In the Deployment Manager Administrator Console, expand the
Servers node and access the Server Types node.
2. Select the Web Servers node, and click New. The Select a node for the Web server and select the Web server type page is
displayed.
3. Select the required node (Load Balancer Node) from the Select node list box.
4. In the Server name field, specify the name of the web server you are adding.
5. Select IBM HTTP Server from the Type list box.
6. Click Next. The Select a Web server template page is displayed.
72
7. Select a template that corresponds to the web server you want to add. Click Next. The Enter the properties for the new Web
server page is displayed.
73
8. In the Port field, accept the default port or specify the Web server port. In addition, specify the Web server installation path.
9. In the Service name field, accept the default name or specify the name of the HTTP service.
10. In the Plug-in installation location field, specify the Plug-in installation path.
11. Select All in the Application mapping to the Web server list box.
12. Click Next. The Confirm new Web server page is displayed.
74
13. Review the summary of the Web server selections.
14. Click Finish. The Web server page is displayed with the list of installed web servers.
75
15. Click Save in the Messages area.
GENERATING THE IBM HTTP SERVER PLUG-IN FILE AND ENABLING
JAVA
You must generate the IBM HTTP Server plug-in file and propagate it to the deployment manager location. To generate the plug-
in file:
1. In the Deployment Manager Administrator Console, expand the Servers > Server Types node.
2. Select the Web server’s node. The Web server’s page is displayed listing all the installed Web servers.
3. Select the web server you installed.
4. Click Generate Plug-in.
5. Select the web server.
6. Click Propagate Plug-in.
7. Select the web server.
8. Click Start.
9. Select Clusters in the Server node.
10. Click Start.
11. Verify all the appservers are running by navigating to Servers > Server Types > WebSphere application servers.
12. Enable the installed JAVA on all profiles by using command:
managesdk –enableProfileAll –sdkName <Java Vesion>
eg, managesdk –enableProfileAll –sdkName 1.7.1_64
76
13. Once the Java is enabled, set the default Java to be used from the WebSphere Console by navigating to Server > Server
Types > WebSphere application servers > clone1 > SDK. Ensure this is done on all the servers.
77
PROVISIONING THE ENVIRONMENT FOR XCP AND VERIFICATION OF
DEPLOYMENT
Once all the app server nodes on the cluster are started and all are accessible, the cluster environment has to be provisioned in
xMS to deploy the xCP application. Please follow the xCP Deployment Guide for provisioning the entire xCP stack . Here you will
look at registering the WebSphere nodes.
For the Apphost service websphereEndpoint provide details as given below:
WebSphere Connector Port:8879, obtained from WebSphere Console under System Administration > Deployment Manager
> Ports > Soap_Connector_Address (Please check the screenshot below).
WebSphere Cell Name: The cell name is obtained from System Administration > Deployment Manager, click Runtime tab
and take the value from Cell name.
WebSphere Node Name: The node name is obtained from System Administration > Deployment Manager, click Runtime tab
and take the value from Node name.
WebSphere server Name: This is the cluster name that was created under Creating Cluster section.
WebSphere Virtual Host: By default all nodes would be deployed with deafult_host as the virtual host.
WebSphere Shared Libraries: Name of the Shared library that is created. Please check xCP Deployment Guide for more info
on this.
Cluster Enabled: Check this to specify the cluster environment.
78
Once the environment is registered with xMS, the xCP Application can be deployed by specifying the xMS details in the designer.
After deploying the xCP application into the Cluster setup , we need to update the plugin-cfg.xml file of load balancer.
Login to the LoadBalancer Machine.
Navigate to the folder locations C:\Program Files (x86)\IBM\WebSphere\Plugins\config\webserver1 and C:\Program Files
(x86)\IBM\WebSphere\AppServer\profiles\Custom01\config\cells\node1Cell01\nodes\LBNode01\servers\webserver1.
Note: The paths might change based on your configurations.
Open the plugin-cfg.xml , under the element
<UriGroup Name="default_host_cluster01_URIs">
Add the element <Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/<Application Name>/*"/>
Do not restart the Load Balancer services or nodes.
Access the Application by Load Balancer url http://<LBNode IP>/<Application Name>/signin.jsp
In order to verify the deployment of xCP application in each of the nodes, open the WebSphere Console and navigate to
Servers > Server Types > WebSphere Application server > clone1 > Installed applications.
79
FAILOVER IN WEBSPRHERE CLUSTER WITH XCP
Webserver and Appserver Load balancing:
1. Access http://<LoadBalaner machine IP>:80/< xCP Application> and login to xCP Application.
2. Stop appserver1. User is able to perform ECM operation without any issue.
3. Start appserver1 and stop appserver2.
4. User is able to continue ECM operations on xCP app.
5. Even if one of the appserver machine is down, user is able to work with the app without any errors.
6. Check the appserver logs to verify request is going through other appserver, when one appserver is down.
CONCLUSION
This guide endeavors to provide detailed steps with screenshots across the various installation and deployment procedures for
WebSphere with xCP. You can use the information provided in this guide to set up IBM WebSphere Application Server 8.5.5.2 in
a clustered environment effortlessly, and integrate with Documentum xCP seamlessly.
Related Documents
