White Paper DEPLOYING WDK APPLICATIONS ON WEBLOGIC AND APACHE WEBSERVER CLUSTER CONFIGURED FOR HIGH AVAILABILITY AND LOAD BALANCE

Transcription

1 White Paper DEPLOYING WDK APPLICATIONS ON WEBLOGIC AND APACHE WEBSERVER CLUSTER CONFIGURED FOR HIGH AVAILABILITY AND LOAD BALANCE

2 Abstract This White Paper provides information to deploy WDK based applications on Distributed Oracle WebLogic Application Server Cluster. This document explains how to install and configure Oracle WebLogic Application Server in cluster mode and also to setup Apache WebServer in Load Balance mode. October 2012 Copyright 2012 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 are 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: h

3 Table of Contents About this document...4 Audience:...4 Overview:...4 Prerequisites...5 Installing the Oracle WebLogic on both physical machines...5 Deploying Documentum Webtop on a distributed WebLogic Cluster: Installing an Apache 2.2.x web server in Cluster mode and enabling Load Balance.. 24 Conclusion: References:

4 About this document This document outlines the ideal way to successfully install and configure an Oracle WebLogic cluster consisting of two Managed Servers running on a separate physical machine each with EMC Documentum WDK based applications in a clustered environment to enable high availability and Load Balancing. The volume of incoming requests is high in a production environment. This can be handled in an efficient manner if the web application is deployed in a clustered environment Audience: This White Paper is intended for EMC customers, partners, internal developers and testers who want to understand the process of installing and configuring an Oracle WebLogic/WebServer cluster which is configured. It is organized in step by step procedure which is easy to follow. If required, a reference to other published guide is provided in order to avoid the duplication of information. Overview: This document describes how to deploy WDK components on distributed Oracle WebLogic application server and Apache WebServer which is enabled for high availability and Load Balance. The process of installing and configuring an Oracle WebLogic application server and Apache WebServer in a clustered environment involves the following steps: Install WebLogic application server instances on both the physical machines. Create the WebLogic Domain on one physical machine. Copy the domain file structure to the other physical machine and enroll it to the WebLogic Domain. Ensure that both WebLogic machines are operational. Create and configure the Cluster. Ensure that the Cluster is operational. Deploy the WAR file to the application server. Install an Apache 2.2.x Web Server. Install the Apache HTTP server plug-in. Configure Load Balance setup. 4

5 Prerequisites The following are the environment details where this setup was configured and tested. This is one of the working scenarios. Application Server Machines: Windows Server 2008 R2 - Need 2 VM s Install the desired Application Server version and configure the WDK/Webtop applications in the respective Application Server according to CRD recommendation. Apache WebServer Machines: Windows Server 2008 R2 Need 2 VM s Install the desired Apache Webserver version and configure it to work with WebLogic Cluster. Load Balance Server Machine: Windows Server 2008 R2 Need 1 VM Install the desired Apache Webserver and configure it as Load Balancer between the 2 Apache WebServer machines. Installing the Oracle WebLogic on both physical machines You can setup WebLogic Cluster in different configuration methods. A WebLogic domain in fact is comprised of a combination of WebLogic Clusters and Managed Servers. The same version of WebLogic must be installed on both the physical machines. Also, WebLogic must be installed on the same Middleware Home in all the machines. This is essential since we copy the domain file structure from one physical machine to the other. Download the latest version of Oracle BEA WebLogic 10.3.x application server installer from the following location: To install the Oracle WebLogic Application Server: 1. Start the Oracle WebLogic Server installer on the first physical machine. The following Welcome page of the Oracle Installer WebLogic Platform is displayed: 5

6 2. Click Next. The following BEA Home Directory page is displayed: 6

7 3. On Choose Middleware Home Directory page, accept the default option Create a new Middleware Home and Middleware Home Directory as C:\Oracle\Middleware and click Next. This default selection appears during fresh installation. 4. On Choose Install Type page, by default, the Typical option is selected. 5. Click Next. The following Choose Product Installation Directories page is displayed: 7

8 6. Accept the defaults and click Next. The Choose Shortcut Location page is displayed. 7. The option All Users Start Menu folder is selected by default, which is recommended. 8. Click Next. The Installation Summary page is displayed. 9. Click Next to continue with the installation. The installation of the Oracle WebLogic Server is started. Creating Weblogic Domain in one of the physical machines: After the completion of the WebLogic installations on both the machines, proceed with the creation of WebLogic Domain. This is performed only on one of the two machines. 1. Start the Fusion Middleware Configuration Wizard utility config.cmd located in C:\Oracle\Middleware\wlserver_10.3\common\bin directory to create a new Weblogic domain. 2. On the Welcome page, select Create a new WebLogic domain. 8

9 3. Click Next. The following Select Domain Source page is displayed: 4. Ensure that the default option Generate a domain configured automatically to support the following products is selected. 5. Click Next to Specify the Domain Name and Location. 9

10 6. Accept the default options and click Next. 10

11 7. Enter the User name and Password of the user to whom you are assigning the Administrator role. By default, the Username is weblogic. You can choose to have weblogic as the Password, or provide a different password. 8. Click Next. The following Configure Server Start Mode and JDK page is displayed: 9. Select the default Sun SDK 1.6.0_18 JDK that is shipped with Oracle BEA WebLogic Server The JDK selection area lists all the JDKs available on the machine. 10. Click Next. The following Select Optional Configuration settings page is displayed: 11

12 11. Select Administration Server and Managed Server, Clusters and Machines options 0n Select Optional Configuration Page and click Next. The following Configure the Administration Server page is displayed: 12. Click Next to Configure Administration Server. 13. By default, the Name, Listen Address, Listen Port is displayed. You can change these details. However, you must ensure that the Listen Port is unique and is not used by any other process. 14. Click Next to Configure Managed Servers. 12

13 15. Click Add to add two Managed Servers and ensure that you provide a unique port for each new Managed Server. 16. After adding the required Managed Servers, click Next. The following Configure Clusters page is displayed. 13

14 17. Click Add to create one or more clusters and provide configuration information for each new cluster. Select the following while adding cluster details: Cluster Messaging mode = multicast Cluster address= (First machine ip: <Listen Port>, Second machine ip: <Listen Port>) 18. The new Managed Servers are assigned to the clusters you create. Specify the details of the new cluster. The combination of multicast address and multicast port must be unique for each cluster on a network. If the two clusters on a network use the same multicast address, they should use different ports. Note: You must identify the address and port you dedicate to multicast communications for your cluster. A multicast address is an IP address between and The default multicast value used by WebLogic Server is You should not use any multicast address with the value x You can change the cluster name and Multicast address, if required. You must change the Multicast port from 7001 to a unique port in the local entire network. You must specify the Cluster address, which is a combination of the IP address of the local machine and the Listen port specified for the Managed Servers. If you have configured more than one Managed Server, the values must be separated by a comma, e.g., IP Address:7003,IP Address:7004,IP Address: Click Next. The Assign Servers to Clusters page is displayed. Select a Managed Server from the Server list and assign it to the relevant cluster selected in the Cluster list. 14

15 20.Click Next. The following Configure Machines page is displayed: 21. Click Next. The following Configuration Summary page is displayed: 15

16 22. Review the Configuration Summary to verify the contents of your domain and click Create to create domain. 23. Click Done to finish. Copy the domain file structure to the other physical machine and enroll it to the WebLogic Domain WebLogic comes with a pack utility that allows you to pack a domain and move it from one place to another. We will instead use plain pack our WebLogic domain directory file structure and move it from one physical machine to the other. Note: Before copying the domain file structure to other machine, it is required to shut down the domain and node manager, if they are running on the first machine. Once the packing is done, we will restart them. On first machine, go to the Middleware Home i.e. C:\Oracle\Middleware\ directory and copy the user_projects folder directory to other physical machine. Start the Adminserver, Managed server on First host machine and Managed Server on the second host machine. You must perform the following steps after the cluster domain is created: On Primary host machine: 1. Browse to the following path: 16

17 C:\Oracle\Middleware\user_projects\domains\base_domain\bin 2. Execute startweblogic.cmd to start the admin server. 3. Open a command prompt and start the Managed Server i.e. ManagedServer_1 in the domain. Navigate to the following path C:\Oracle\Middleware\wlserver_10.3\common\bin and execute startmanagedweblogic.cmd ManagedServer_ Open a separate command prompt to execute the command to start Node Manager and navigate to the following path: C:\Oracle\Middleware\wlserver_10.3\server\bin 5. Execute startnodemanager.cmd to start Node Manager. Note: Before starting it, go over the start-up parameters specified in the nodemanager.properties configuration file in the wlserver_10.3/common/nodemanager directory and verify that it is not configured for SSL by ensuring that the SecureListener parameter is set to false. Once started the terminal window should indicate that the node manager is running and listening to the port configured. On Second Host Machine: 1. Navigate to the following path: C:\Oracle\Middleware\wlserver_10.3\common\bin 2. Execute following commands to start each of the Managed Server on the second host machine: startmanagedweblogic.cmd ManagedServer_2 IP :7001 The second machine is successfully enrolled into the WebLogic Domain. You can start the Node Manager on the second machine and verify that it is Reachable by the WebLogic Machine. We have already verified that the node manager on the first machine is reachable back. 3. You can start the Node Manager by running the startnodemanager.cmd in the wlserver_10.3/server/bin directory Note: Again, ensure that the node manager is not started in SSL mode by setting the SecureListener parameter to false in the nodemanager.properties configuration file in wlserver_10.3/common/nodemanager. nodemanager.properties might not exist until you first run start NodeManager.cmd. Now, with the node managers running on both physical machines return to the Administration Console and verify that the node managers are Reachable for both Machines. Ensure that the Cluster is operational The Cluster is setup; now ensure that the Cluster is operational through Administrator Console. Both Managed Servers should be displayed on the Servers table with a RUNNING state. 17

18 Now with both Managed Servers running, take a look at our Cluster status. Return to the Summary of Clusters page via Environment and then Clusters on the navigation tree and click Cluster in the Clusters table. Then click the Monitoring tab and observe the Cluster Server status on the Summery tab. Click the Health and Failover tabs to see other monitoring information and status. 18

19 This concludes our Cluster setup. Deploying Documentum Webtop on a distributed WebLogic Cluster: You must perform the following steps before deploying the WAR file or the expanded structure: 1. Modify dfc.properties file available in the following path with the valid credentials: \webtop\web-inf\classes 2. Browse to the following path and uncomment the <session-descriptor> tag in the weblogic.xml file: \webtop\web-inf 3. (Optional) If you are using the Apache WebServer, add the following lines to the ucf.server.config.xml file available in the \webtop\web-inf folder: <option name="http11.chunked.transfer.encoding"> <value>disabled</value> </option> Deploying the WAR file to the Application Server: J2EE application servers vary when you deploy the WAR file and create the expanded directory structure. 19

20 Typically, one of the following methods is used: Deploy the compressed WAR file to a working directory On some J2EE application servers (such as IBM WebSphere), the deployment process expands the WAR file into a working directory, and from that point forward, the expanded directory is considered to be the application. For these application servers, you deploy the compressed WAR file and work in the resulting directory structure. Expand the WAR file and deploy the expanded structure as the working directory On other application servers (such as JRun 4 and BEA WebLogic), you expand the WAR file manually, and then deploy the expanded directory structure, which becomes you re working directory. The deployment method you use depends on your application server. Note: Refer to your Java application server documentation for information on deploying a WAR file. To deploy the application on a distributed Oracle WebLogic Cluster: Access the weblogic admin console using 1. Log in to the Admin Console using the relevant credentials. You are logged into the WebLogic Servers Administration Console. 2. Select the Deployments node in the Domain Structure tree. The Summary of Deployments page is displayed on the right pane. 20

21 3. Click Install in the Deployments area of the Control tab to deploy an application on a cluster domain. The Install Application Assistant page is displayed on the right pane. 4. Browse to the current location of the WAR file or expanded directory structure. If you are deploying the compressed WAR file, the compressed WAR file you copied to the working directory is displayed as webtop.war with a unique icon in the Install Application Assistant page. Alternatively, if you expand the WAR file manually and then deploy the expanded directory structure, the expanded directory structure is displayed as Webtop with a unique icon in the Install Application Assistant page. 21

22 Alternatively, if you expand the WAR file manually and then deploy the expanded directory structure, the expanded directory structure is displayed as Webtop with a unique icon in the Install Application Assistant page. Note: You must select an application to continue with the installation. 5. Click Next. The Choose targeting style page is displayed. 6. By default, Install this deployment as an application option is selected which is used to target the application and its components to the same location. 7. Click Next. The following select deployment targets page is displayed: 22

23 8. In the Clusters list, select the cluster you created, and select the required Managed Servers on which you want to deploy the application. In our scenario, select the cluster Cluster_1 and managed servers ManagedServer_1 and ManagedServer_2 9. Click Next. The Optional Settings page is displayed. 10. In the Name field, Webtop is displayed as the application name by default. You can change the name. 23

24 11. Select option to Copy this application onto every target for me in the Source accessibility area. 12. Click Next. The following page is displayed: Installing an Apache 2.2.x web server in Cluster mode and enabling Load Balance Download the Apache 2.0.xx or 2.2.x web server installer from the following location for Windows: You can download the WebServer for any operating system to install and configure the web server. The steps involved in setting up two-node Apache WebServer cluster provide high availability. 1. Install the Apache HTTP Server on all three machines. 2. Configure Apache WebServer Cluster on two machines. 3. Ensure that the Cluster is operational. 4. On the Third host machine, configure the Apache WebServer Load Balancer. This Configuration shows how to set up a two-node Apache WebServer cluster that provides highavailability. In-front of the Apache WebServer cluster, we create a Load Balancer that splits up incoming requests between the two Apache nodes. Install an Apache WebServer plug-in on Machine 1 and configure it with Weblogic Cluster: The following procedure to install an Apache WebServer plug-in is applicable across operating systems. 1. Extract server103_apacheplugins.zip. 2. Browse to the server103_apacheplugins folder in the following path: win\32. 24

25 3. Copy mod_wl_22.so for the Apache 2.2.x web server file, to the following location of the WebServer: C:\Program Files\Apache Software Foundation\Apache2.x.x\modules 4. Open httpd.conf available in the following path: C:\Program Files\Apache Group\Apache2\conf 5. Depending on the Apache WebServer version with which you are working, add one of the following entries in httpd.conf LoadModule weblogic_module modules/mod_wl_22.so (for apache webserver 2.2.x) Next, add the following lines in httpd.conf : <IfModule mod_weblogic.c> WebLogicCluster IP:port1, IP:port2 </IfModule> <Location /> SetHandler weblogic-handler </Location> 6. Start the Apache WebServer. 7. Access Documentum Webtop using the following URL: Note: It should redirect the request to appropriate back end WebLogic application server in the cluster and Webtop login page should be displayed. Install an Apache WebServer plug-in on Machine 2 and configure it with WebLogic Cluster : Repeat from Step 1 to Step 7) on Apache WebServer machine 2 and check that the request is redirected to the appropriate back-end the above steps (WebLogic application server in the cluster and Webtop login page should be displayed when we access Documentum Webtop using the following URL: Configure WebServer Load Balancer on Machine 3: 1. Extract server103_apacheplugins.zip. 2. Browse to the server103_apacheplugins folder in the following path: win\ Copy mod_wl_22.so for the Apache 2.2.x web server file, to the following location of the WebServer: C:\Program Files\Apache Software Foundation\Apache2.x.x\modules 4. Browse httpd.conf from the following path: C:\Program Files\Apache Group\Apache2\conf and perform the following changes. a. Enable the following modules: LoadModule proxy_balancer_module modules/mod_proxy_balancer.so 25

26 LoadModule proxy_connect_module modules/mod_proxy_connect.so LoadModule proxy_ftp_module modules/mod_proxy_ftp.so LoadModule proxy_http_module modules/mod_proxy_http.so LoadModule setenvif_module modules/mod_setenvif.so b. Add the below ones to configure the Load Balance between the 2 WebServers(Apache WebServer1 & Apache WebServer 2) <IfModule mod_proxy.c> # set ProxyRequests off since we're only using the ProxyPass and ProxyPassReverse # directives. this keeps the server secure from # spammers trying to use your proxy to send . ProxyRequests Off <Proxy *> AddDefaultCharset off Order deny,allow Allow from all #Allow from.example.com </Proxy> # Enable/disable the handling of HTTP/1.1 "Via:" headers. # ("Full" adds the server version; "Block" removes all outgoing Via: headers) # Set to one of: Off On Full Block ProxyVia On </IfModule> #configure mod_proxy and mod_proxy_balancer on httpd.conf file <Location /balancer-manager> SetHandler balancer-manager Order Deny,Allow Deny from all Allow from 10.8.*.* </Location> <Proxy balancer://mycluster> # cluster member 1 BalancerMember route=lb1 # cluster member 2 BalancerMember route=lb2 </Proxy> ProxyPass /balancer-manager! ProxyPass / balancer://mycluster/ lbmethod=byrequests ProxyPassReverse / webserver1:80/ ProxyPassReverse / webserver2:80/ 26

27 5. Check that the Load Balancer redirects the request through WebServer cluster to the appropriate backend WebLogic application server in the cluster and Webtop login page is displayed when we access Documentum Webtop using the following URL: Note: I am allowing access to the balancer manager (the web UI) from any IP matching 10.8.*.* Enabling the load balance between 2 servers (webserver1, webserver2) running on port 80. Defining two routes for these servers called lb1 and lb2. Excluding (!) the balancer-manager directory from the ProxyPass to allow access to the Manager UI on the Load Balancing server. Expecting a cookie called BALANCEID to be available to manage sticky sessions. Conclusion: This whitepaper provides detailed information about how to install and configure Oracle WebLogic Application Server cluster in distributed environment. This document also provides detailed information on setting up Apache Webserver cluster and Load Balance configuration between two Web Servers. Through that we can conclude accessing Documentum WDK based Application i.e. Webtop from Apache WebServer Load Balancer works fine. References: