Beruflich Dokumente
Kultur Dokumente
Table of Contents
1.
2.
1.
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:
Domain
Administrator Server
Managed Server
Node Manager
1.1.1 Domain
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
WebLogic Server Node Manager: A Java program that lets you start and stop server
instancesboth Administration Servers and Managed Serversremotely, and to monitor
and automatically restart them after an unexpected failure.
1-2
1.2
Domain Creation
The following sections provides step-by-step WebLogic Server configuration for Oracle FCUBS
covering:
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-3
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-5
1-6
1-7
1-8
Click on Next,
1-9
1-10
1-11
Select the options Administration Server and Managed Servers, Clusters and Machines. Click
next,
1-12
Note: The default Listen port is 7001. This could be changed to any other free port. Please make
a note of this port; its 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
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
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
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
1-20
1.3
1-21
./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.
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
1-24
1.5
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
1.6
1-28
1.7
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
Domain structure -> Machines -> machine2 -> Monitoring -> node Manager Status
1-32
1.8
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
1-33
1-34
1-35
1-36
1-37
1-38
Choose driver
Oracles Driver (Thin XA) for instance connections; Versions 9.0.1 and later
1-39
Test configuration,
1-40
1-41
Click on activate Changes to activate the changes. Data sources are created as follows,
1-42
1.9
1-43
Choose driver
Oracles Driver (Thin) for RAC service-instance connections; Versions:10 and later
1-44
Click Test Configuration and check if the database connectivity is successful. Click Next on
success.
1-45
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,
1-49
1-50
PARAMETER
VALUE
30 Secs
900
Test Frequency
60
30
Initial Capacity
15
Max capacity
15
Shrink Frequency
900
Navigate To
1-51
Checked
Session Timeout
900
1-52
1-53
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
1-55
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
<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-58
1-59
Click on Next
1-60
1-62
2.
2.1
Appendix A
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,
2-1
Error2
Solutions
To solve the above errors,
2-2
2-3
This will recreate the ldap setting with new password and start the admin server.
2-4