Configuring Weblogic Server Oracle FLEXCUBE Universal Banking Release 12.0.2.0.0 [September] [2013] Part No. E49740-01
Configuring Weblogic Server Table of Contents 1. CONFIGURING WEBLOGIC SERVER... 1-1 1.1 INTRODUCTION... 1-1 1.1.1 Domain... 1-1 1.1.2 WebLogic Domain Structure... 1-1 1.1.3 Administration Server... 1-2 1.1.4 Managed Server... 1-2 1.1.5 Managed Server Cluster... 1-2 1.1.6 Node Manager... 1-2 1.2 DOMAIN CREATION... 1-3 1.2.1 Environment details... 1-3 1.2.2 Start Node Manager... 1-3 1.2.3 Enable Graphical User Interface (GUI)... 1-5 1.2.4 Fusion Middleware Configuration Wizard... 1-5 1.3 PACK AND UNPACK DOMAIN... 1-21 1.4 JVM TUNING... 1-22 1.5 MANAGED SERVER STARTUP USING SCRIPT (STARTWEBLOGIC.SH)... 1-25 1.6 STARTING ADMIN SERVER... 1-27 1.7 STARTING MANAGED SERVERS... 1-29 1.7.1 Verifying machine status... 1-31 1.8 DATA SOURCE CREATION AND JDBC CONFIGURATION FOR ORACLE DATABASE SINGLE INSTANCE... 1-33 1.9 MULTI DATA SOURCE CREATION AND JDBC CONFIGURATION FOR ORACLE RAC... 1-43 1.10 JDBC TUNING... 1-51 1.11 ORACLE WEBLOGIC PROXY... 1-52 1.11.1 Proxy Plug-in Deployment options... 1-52 1.11.2 Cluster Creation... 1-52 1.11.3 Managed Server Creation... 1-54 1.11.4 Creating proxy.war file... 1-56 1.11.5 Proxy Plug-in Deployment... 1-58 2. APPENDIX A:... 2-1 2.1 INTRODUCTION... 2-1
1. Configuring WebLogic Server 1.1 Introduction This chapter provides a step by step process to configure Weblogic Server. To start with, the chapter provides a brief description on the following: 1.1.1 Domain Domain Weblogic Domain Structure Administrator Server Managed Server Managed Server Cluster Node Manager A domain is the basic administration unit for WebLogic Server instances. A domain consists of one or more WebLogic Server instances (and their associated resources) that you manage with a single Administration Server. You can define multiple domains based on different system administrators' responsibilities, application boundaries, or geographical locations of servers. Conversely, a single domain can be used to centralize all WebLogic Server administration activities. Each WebLogic Server domain must have one server instance that acts as the Administration Server. You use the Administration Server, via the Administration Console or using the command line in order to configure all other server instances and resources in the domain. 1.1.2 WebLogic Domain Structure 1-1
1.1.3 Administration Server A domain includes one WebLogic Server instance that is configured as an Administration Server. All changes to configuration and deployment of applications are done through the Administration Server. The Administration Server provides a central point for managing the domain and providing access to the WebLogic Server administration tools. These tools include the following: 1.1.4 Managed Server WebLogic Server Administration Console: Graphical user interface to the Administration Server. WebLogic Server Node Manager: A Java program that lets you start and stop server instances both Administration Servers and Managed Servers remotely, and to monitor and automatically restart them after an unexpected failure. In a domain, server instances other than the Administration Server are referred to as Managed Servers. Managed servers host the components and associated resources that constitute your applications for example, JSPs and EJBs. When a Managed Server starts up, it connects to the domain's Administration Server to obtain configuration and deployment settings. In a domain with only a single WebLogic Server instance, that single server works as both the administration server and managed server. 1.1.5 Managed Server Cluster Two or more Managed Servers can be configured as a WebLogic Server cluster to increase application scalability and availability. In a WebLogic Server cluster, most resources and services are deployed to each Managed Server (as opposed to a single Managed Server,) enabling failover and load balancing. The servers within a cluster can either run on the same machine or reside in different machines. To the client, a cluster appears as a single WebLogic Server instance. 1.1.6 Node Manager The Managed Servers in a production WebLogic Server environment are often distributed across multiple machines and geographic locations. Node Manager is a Java utility that runs as separate process from WebLogic Server and allows you to perform common operations tasks for a Managed Server, regardless of its location with respect to its Administration Server. While use of Node Manager is optional, it provides valuable benefits if your WebLogic Server environment hosts applications with high availability requirements. If you run Node Manager on a machine that hosts Managed Servers, you can start and stop the Managed Servers remotely using the Administration Console or from the command line. Node Manager can also automatically restart a Managed Server after an unexpected failure. 1-2
1.2 Domain Creation The following sections provides step-by-step WebLogic Server configuration for Oracle FCUBS covering: Managed server Creation Cluster Creation Node Creation This example, helps you to create a domain with 2 managed servers. The managed servers are going to be created on 2 different physical servers (nodes). This requires Weblogic Server of same version to be installed on both the machines and services (Weblogic and node manager) should be up. 1.2.1 Environment details This document has been prepared based on a test conducted in Linux servers running Red Hat Enterprise Linux Server release 5.5 (Tikanga). The machine configuration is given below, Node1 Hostname: IPL187DOR IP Address: 10.184.74.187 CPU details: 8 core Intel(R) Xeon(R) CPU E5540 @ 2.53GHz Physical memory: 24GB Node2 Hostname: IPL186DOR IP Address: 10.184.74.186 CPU details: 8 core Intel(R) Xeon(R) CPU E5540 @ 2.53GHz Physical memory: 24GB 1.2.2 Start Node Manager Start node manager in both servers before creating domain. Any domain created before creation of Node Manager Service will not be accessible via node Manager (even after restarting node manager), solution is to run the WLST command nmenroll to enroll that domain with the Node Manager. If the domain is created after the Node Manager Service has been installed should not have to be enrolled against the Node Manager. The Node Manager should automatically be 'reachable' by the domain. 1-3
How to check whether nodemanager is already running? The way to verify the nodemanager status is to check whether node manager process is running. ps ef grep weblogic.nodemanager.javahome If the above command returns the process details then node manager is running. If nodemanager is not running in any of the server, start it using startnodemanager.sh script under $WLSHOME/server/bin directory to start Nodemanager. In IPL186DOR, In IPL187DOR, 1-4
1.2.3 Enable Graphical User Interface (GUI) Establish a telnet or SSH connection to 10.184.74.187 server. Start X-manager in windows desktop. Export DISPLAY environment variable to the machine IP where x-manager is running. Syntax: export DISPLAY=<ip-address>:<port> Example: export DISPLAY=10.184.86.240:0.0 Test using xclock, 1.2.4 Fusion Middleware Configuration Wizard Weblogic domain creation and configuration will be done from server 10.184.74.187. From server 10.184.74.187 launch fusion Middleware configuration wizard using config.sh under $WLS_HOME/common/bin directory, 1-5
1-6
Choose Create a new Weblogic domain option. Click on Next, 1-7
Select Domain Source. Click on Next, 1-8
Specify Domain Name and location. Click on Next, 1-9
Configure Administrator User Name and password Use this screen to define the default WebLogic Administrator account for the domain. This account is used to boot and connect to the domain's Administration Server. Note: This is the credentials used to access Administration console. Click on Next, Select Server Start Mode as production mode and choose JDK. Click on next, 1-10
1-11
Select the options Administration Server and Managed Servers, Clusters and Machines. Click next, 1-12
Configure Administration server Listen address and port Note: The default Listen port is 7001. This could be changed to any other free port. Please make a note of this port; it s essential for launching the Admin console post domain creation. In this configuration 8990 port is input. This completes Admin Server configuration. The next screen takes us to Managed Server configuration. 1-13
Configure Managed Server Note: Every 75 concurrent users require one managed server. I.e. for 300 concurrent FCUBS users, it is recommended to have 4 managed servers. Click on Add button to add the desired number of Managed Servers. This completes managed server configurations. The next screen takes us to Cluster creation and configuration. 1-14
Cluster configuration, Click on Add button to add a new cluster. Input the cluster name. Choose multicast option for Cluster messaging mode. Note: The default multicast address and port will be 239.192.0.0 and 7001 respectively. A different address and port can be chosen if it is already in use. 1-15
Select the managed servers in the left pane and assign them to the cluster by clicking the right arrow button. 1-16
After assigning managed servers to cluster, That completes Cluster configuration. On clicking next, the machine configuration screen is displayed. 1-17
Configure machines Click on Add button to add the desired number of nodes. 1-18
Assign managed servers to Nodes In this scenario, based on the host on which the managed server is created, the managed servers are assigned to respective Nodes. Select the managed Server(s) in the left pane and assign them to the desired Node by clicking the right arrow button. As per the above configuration, managed server fcubs1 will start in server 10.184.74.187 and listen to port 8991 & Managed server fcubs2 will start in server 10.184.74.186 and listen to port 8992. This completes the Machine creation and configuration. Click Next. Verify the details. Click on Create button to create domain, 1-19
This completes the domain creation. 1-20
The Admin Server console will be something like: http://<ip address>:<admin console port>/console <IP address >: Host on which domain was created. <admin console port> : The port specified at the Administration Server configuration page. In this case the Admin Console URL is: http://10.184.74.187:8990/console 1.3 Pack and unpack domain The domain structure is expected to be copied to the second server (IPL186DOR) during domain creation. In some cases the domain structure (domain directories and scripts) will not be copied to the second node (IPL186DOR) of the weblogic clusters. Use pack and unpack utility provided under $WLSHOME//common/bin, Pack: Domain in 10.184.74.187 server, 1-21
./pack.sh -managed=true - domain=/oraint2/middleware/wls1035/user_projects/domains/fcubscl - template=/tmp/fcubscl.jar -template_name="fcubscl" Unpack: FTP FCUBSCL.jar in binary mode to server 10.184.74.186 under /tmp area and unpack the domain using unpack utility provided under $WLSHOME//common/bin,./unpack.sh -domain=/oraint1/weblogic10.5/oracle/middleware/user_projects/domains/fcubscl -template=/tmp/fcubscl.jar 1.4 JVM Tuning This section of the document provides JVM optimization for Oracle FLEXCUBE UBS. Basically the JAVA minimum and maximum head size needs to be reset for 32 and 64 bit environments. Both the minimum and maximum heap size is set to 1.5GB and 2GB in case of 32 bit and 64 bit environments respectively. How to find whether the JVM is 32bit or 64bit? Go to $JAVA_HOME/bin directory. Check java version using, 1-22
./java d64 version 64 bit JVM shows the version details where as 32bit throws an error. To change the JVM heap parameters modify setdomainenv.sh under domain FCUBSCL in both servers. This file is located at $WL_HOME/user_projects/domains/$WLS_DOMAIN/bin Use USER_MEM_ARGS variable to override the standard memory arguments passed to java. 32 bit JVM: USER_MEM_ARGS= -Xms1536M Xmx1536M XX:MaxPermSize=512M export USER_MEM_ARGS 64 bit JVM: USER_MEM_ARGS= -Xms2048M Xmx2048M XX:MaxPermSize=512M export USER_MEM_ARGS In server IPL187DOR, File setdomain.sh under directory /oraint2/middleware/wls1035/user_projects/domains/fcubscl/bin 1-23
In server IPL186DOR, File setdomain.sh under directory /oraint1/weblogic10.5/oracle/middleware/user_projects/domains/fcubscl/bin Note: Take a backup of the file before editing the same. 1-24
1.5 Managed server startup using script (startweblogic.sh) It is recommended to start managed servers using scripts (startweblogic.sh) when the managed servers are started from weblogic console. To enable this set the following properties in Nodemanager.properties file in both servers, StartScriptEnabled=true StartScriptName=$DOMAIN_HOME/bin/startWebLogic.sh Example: StartScriptEnabled=true StartScriptName=/oraint2/middleware/wls1035/user_projects/domains/fcubs113/bin/startWebLogi c.sh Nodemanager.properties can be found under $WLSHOME/ common/ nodemanager In server 10.184.74.187 Nodemanager.properties location: /oraint2/middleware/wls1035/wlserver_10.3/common/nodemanager/ Nodemanager.properties Under 10.184.74.186 server, 1-25
Nodemanager.properties location: /oraint1/weblogic10.5/oracle/middleware/wlserver_10.3/common/nodemanager Note: Node manager must be restarted in all servers (10.184.74.187 & 10.184.74.186) to activate this setting 1-26
How to restart node manager? Find out node manager pid using ps -ef grep weblogic.nodemanager.javahome Change directory to $WLSHOME/server/bin Kill the unix process using kill -9 <pid> Verify that the node manager is killed by tail f nohup.out Start node manager using nohup./startnodemanager.sh & Verify nodemanager is started using tail f nohup.out Same way restart nodemanager in server 10.184.74.186. 1.6 Starting Admin server Use startweblogic.sh under $DOMAIN_HOME/bin to start admin server in 10.184.74.187 server, 1-27
In this example startweblogic.sh script is under /oraint2/middleware/wls1035/user_projects/domains/fcubscl/bin/ under server 10.184.74.187 Note: Refer Appendix A on possible admin server start-up problems. 1-28
1.7 Starting managed servers Login to Administration console using URL http://10.184.74.187:8990/console, User name and password is set during domain creation as follows, Username: weblogic Password: weblogic123 1-29
This screen provides details of both managed servers which are currently down. Both managed servers are part of FCUBSCL domain. Fcubs1 managed server is associated with machine1 that is 10.184.74.187 server. Machine for fcubs2 managed server is machine2 that is 10.184.74. 1-30
1.7.1 Verifying machine status Before starting the managed servers ensure that all the machines are reachable, Domain structure -> Machines -> machine1 -> Monitoring -> node Manager Status Domain structure -> Machines -> machine2 -> Monitoring -> node Manager Status Node manager Status should be Reachable Select the managed servers and click on start button to start the managed server, Domain structure -> Environment -> servers -> control 1-31
Managed server Status will be changed to running, 1-32
1.8 Data Source creation and JDBC Configuration for Oracle Database Single Instance 3 valid data sources are required to launch FLEXCUBE application. JNDI names of those are, 1. jdbc/fcjdevds 2. jdbc/fcjschedulerds 3. jdbc/fcjdevdsbranch Note: jdbc/fcjdevds and jdbc/fcjschedulerds should be NonXA. jdbc/fcjdevdsbranch should be XA Click on Services -> Data Sources on the left pane Click on Lock & edit button. Then click on New -> Generic data source 4. Data source: jdbc/fcjdevds Provide the following details, Name: FCUBSDS JNDI Name: jdbc/fcjdevds Database Type: Oracle 1-33
Choose Database Driver : Oracle Driver (Thin) for instance connections ; Versions:9.0.1 and later Uncheck Support Global Transaction option. Click on Next button, 1-34
Input the Oracle database details and click Next. 1-35
Click on Test Configuration 1-36
Select target as cluster FCCLUSTER. Click on Finish 1-37
Click on Activate Changes button to active the change, 1. Create data source jdbc/fcjschedulerds similar to jdbc/fcjdevds 2. Data source: jdbc/fcjdevdsbranch 1-38
Enter JDBC data Source Properties, Choose driver Oracle s Driver (Thin XA) for instance connections; Versions 9.0.1 and later 1-39
Enter database connection details, Test configuration, 1-40
Select target as cluster. Click on Finish 1-41
Click on activate Changes to activate the changes. Data sources are created as follows, 1-42
1.9 Multi Data Source creation and JDBC Configuration for Oracle RAC Create respective number of Data sources as the number of nodes in Oracle RAC. In this scenario, there are two nodes in Oracle RAC. Hence two data sources are created: FCUBS_DS1 and FCUBS_DS2 pointing to Node1 and Node of Oracle RAC respectively. 1-43
Enter name, JNDI name and database type, Choose driver Oracle s Driver (Thin) for RAC service-instance connections; Versions:10 and later Uncheck Support Global transactions 1-44
Input the Oracle database details and click Next. The Host Name should point to the VIP and NOT the PUBLIC IP of the Oracle RAC node. Click Test Configuration and check if the database connectivity is successful. Click Next on success. 1-45
Choose target as FCCLUSTER. Click on Finish Click on activate changes 1-46
Similarly another data source FCUBS_DS2 should be created for second node of Oracle RAC. As per the summary screen FCUBS_DS1 and FCUBS_DS2 JDBC connections have been created successfully. 1-47
Now click on Multi Data Sources option under Services -> JDBC on the left pane. Click on New button. 1-48
Enter multi data source name, JNDI name and database type, Select target for multi data source as FCCLUSTER, 1-49
Choose Non-XA driver Choose both data sources 1-50
Activate the changes Similarly create a multi datasource for jdbc/fcjdevdsbranch 1.10 JDBC Tuning PARAMETER VALUE Navigate To Connection Reserve time out 30 Secs JTA Time out seconds 900 1.Login to Weblogic Server console. 2.Click on the domain name (ex: FCUBS) which is under 'Domain Structure'. 3. Go to Configuration->JTA, parameter and values is found on the right side panel of console. Test Frequency 60 Inactive connection time out 30 Initial Capacity 15 Max capacity 15 It is preferred to be 150% of total concurrent users Shrink Frequency 0 Thread Max Time (Server- >Configuration->Tuning-> Stuck Thread Max Time) 900 1-51
Test Connection on Reserve (Connection Pool->Advance) Checked Session Timeout 900 1.Login to Weblogic Server console 2.Click on Deployments which is under 'Domain Structure'. 3. Click on the deployed FCJ application from right side panel. 4. Click on FCJNeoWeb from Modules and components 5. Go to Configuration General, the parameter values can be found here. 1.11 Oracle WebLogic Proxy 1.11.1 Proxy Plug-in Deployment options Proxy Plug-in could be deployed in Clustered or Non-Clustered mode based on Application server deployment architecture. In Active-Active deployment model, it is recommended to have separate WebLogic Cluster for Proxy. 1.11.2 Cluster Creation This step required only for Active-Active deployment model of Application servers. Launch the Application Server Admin URL and navigate to Domain -> Environment -> Clusters And then add New Cluster for Proxy as Proxy Plug-in could be deployed in Cluster mode. 1-52
Enter the following details, Name: Proxy-cluster Messaging Mode: Multicast Multicast Address: 239.192.0.10 Multicast port: 8909 Click OK to proceed with cluster creation. 1-53
1.11.3 Managed Server Creation Create the new Managed servers. And also assign to Proxy-Cluster [for Active-Active deployment model] Create 2 managed servers proxy-server1 & proxy-server2 Create first Managed server proxy-server1 which will start in server 10.184.74.187 Click on Finish Assign machine1 to proxy-server1 managed server, Home >Summary of Clusters >Summary of Servers >proxy-server1 1-54
Save and activate the changes. Create second Managed server named proxy-server2 which will start in server 10.184.74.186 Click on Finish to create managed server, 1-55
Assign machine2 to proxy-server2 managed server, Home >Summary of Clusters >Summary of Servers >proxy-server1 >Summary of Servers >proxy-server2 Save and activate changes. 1.11.4 Creating proxy.war file Prior to deploying application, you must create a proxy.war. Steps are as follows, 1. Create a WEB-INF directory under the Proxy directory ( ex: Proxy\WEB-INF ) 2. Copy the following web.xml and weblogic.xml into WEB-INF folder 1-56
Update the param-value of WeblogicCluster with your current Cluster Address i.e., with Managed server listen address and Ports ( <ip address>:<port> <ip address>:<port> ) Web.xml <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd"> <web-app> <servlet> <servlet-name>httpclusterservlet</servlet-name> <servlet-class>weblogic.servlet.proxy.httpclusterservlet</servlet-class> <init-param> <param-name>weblogiccluster</param-name> <param-value>10.184.74.187:8991 10.184.74.186:8992</param-value> </init-param> <init-param> <param-name>verbose</param-name> <param-value>true</param-value> </init-param> <init-param> <param-name>debugconfiginfo</param-name> <param-value>on</param-value> </init-param> </servlet> <servlet-mapping> <servlet-name>httpclusterservlet</servlet-name> <url-pattern>/</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>httpclusterservlet</servlet-name> <url-pattern>*.jsp</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>httpclusterservlet</servlet-name> <url-pattern>*.htm</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>httpclusterservlet</servlet-name> <url-pattern>*.html</url-pattern> </servlet-mapping> </web-app> Weblogic.xml 1-57
<!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN" "http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd"> <weblogic-web-app> <context-root>/</context-root> </weblogic-web-app> 1. Go to the parent folder of WEB-INF and run the below command to create proxy.war file jar cvf proxy.war WEB-INF 1.11.5 Proxy Plug-in Deployment Domain Structure -> Deployments Click on install and upload proxy.war 1-58
Proxy.war will be uploaded to server. Click Next Choose Install the deployment as application option. Click Next 1-59
Select target as proxy-cluster Click on Next 1-60
Click on Finish to complete deployment Save and activate the changes 1-61
Start the deployed application Application state should change to ACTIVE 1-62
2. Appendix A 2.1 Introduction This chapter details issues that might be faced during Admin server start-up and the solutions for the same. 1. Server is running in Production Mode and Native Library (terminalio) to read the password securely from commandline is not found. Solution: Add -Dweblogic.management.allowPasswordEcho=true in Startweblogic.sh as per Metalink doc Id 1354736.1, 1. Admin server failed to start with following error, Error1 2-1
Error2 Solutions To solve the above errors, 2-2
1. Create a new directory security under /oraint2/middleware/wls1035/user_projects/domains/fcubscl/servers/adminserver and create a file boot.properties. Add weblogic console username and password in it as follows, 2. If there is a directory ldap exists under /oraint2/middleware/wls1035/user_projects/domains/fcubscl/servers/adminserver/data then rename directory ldap to ldap_old under 2-3
3. Start the Admin server, This will recreate the ldap setting with new password and start the admin server. 2-4
Configuring Weblogic Server [September] [2013] Version 12.0.2.0.0 Oracle Financial Services Software Limited Oracle Park Off Western Express Highway Goregaon (East) Mumbai, Maharashtra 400 063 India Worldwide Inquiries: Phone: +91 22 6718 3000 Fax:+91 22 6718 3001 www.oracle.com/financialservices/ Copyright [2007], [2013], Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government. This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate failsafe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. This software or hardware and documentation may provide access to or information on content, products and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.