WebLogic Cluster Environment __web

HTTP Proxy method

1. Configure WebLogic Cluster environment

WebLogic cluster is mainly divided into three modules, a cluster Management Server, followed by the cluster Management Server, and then there is Access Proxy server.

.. All servers in the cluster must be in the same network segment and must be reachable by IP broadcast (UDP)
.. All servers in the cluster must use the same version, including service packs
.. The server in the cluster must use a permanent static IP address. Dynamic IP address assignment cannot be used in a clustered environment. Such as
If the server is behind a firewall and the client is outside the firewall, then the server must have a public static IP
Address, only in this way can clients access the server
.. To run as cluster, you must have license that contains the cluster license

weblogic10.3

jdk1.6

Operating system: rh6.0

Host: 192.168.1.6, 192.168.1.7, 192.168.1.8, 192.168.1.50

2. Single-layer hybrid model

This architecture places all Web applications and related service applications in a single WLS instance of the cluster,
The advantage of this architecture is that:
.. Easy to manage
.. Flexible load-balancing mechanism
.. Stronger security controls

2.1 Create domain: script is located in ${weblogic_home}/weblogic92/common/bin/config.sh

Unlike the following creation, the server 192.168.1.6 creates a managed server s1:192.168.1.7:7003, s2:192.168.1.8:7004, agent:192.168.1.50, creates a cluster mycluster, chooses S1, S2, do not create a computer, select the HTTP proxy agent, create a management service complete

2.2 Managed Server 192.168.1.7 Ibid (script is located in ${weblogic_home}/weblogic92/common/bin/config.sh) Create domain, only create managed machine s1:192.168.1.7:7003, Other for default, create complete; S2 with S1

3. Multi-layer hybrid model

This architecture uses two WLS clusters, one to place the table static content and the cluster servlet, and the other to place the cluster EJB.
This is generally applied to the following situations:
.. When the load balancing mechanism needs to invoke methods in the cluster EJB;
.. The need for greater mobility between the provision of content and the services provided to the object;
.. When a higher system stability is required;

4. Edit Start WebLogic Service file
.. Edit Password file
Create the Boot.properties file under the domain directory you just created, which reads:
Username=weblogic
Password=weblogic
.. Edit files to start the Management Server
Create a startadminserver.sh in the bin directory under the domain directory you just created, which reads:
./startweblogic.sh
.. To edit a file that initiates a proxy server
Create a startproxyserver.sh in the bin directory under the domain directory you just created, which reads:
./startmanagedweblogic.sh ProxyServer http://10.0.10.149:7001
.. To edit a file that starts a managed server (managedserver_1)
Create a startmanagedserver_1.sh in the bin directory under the domain directory you just created, which reads:
./startmanagedweblogic.sh managedserver_1 http://10.0.10.149:7001
(Note: Start managed Server using the Startmanagedweblogic command, which has the following command format:
./startmanagedweblogic.sh Managed Server name Administrator server address)

5, start the service, deploy the program

6, test the cluster distribution function

Session sharing problem Test
The edit weblogic.xml configuration file is placed in the Web-inf directory of the Web application, which reads as follows:
<?xml version= "1.0" encoding= "UTF-8"?>
<wls:weblogic-web-app xmlns:xsi= "Http://www.w3.org/2001/XMLSchema-instance"
Xmlns:wls= "Http://www.bea.com/ns/weblogic/90"
Xsi:schemalocation= "Http://java.sun.com/xml/ns/j2ee
Http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd http://www.bea.com/ns/weblogic/90
Http://www.bea.com/ns/weblogic/90/weblogic-web-app.xsd ">
<session-descriptor>
<persistent-store-type>replicated</persistent-store-type>
<sharing-enabled>true</sharing-enabled>
</session-descriptor>
<wls:context-root>/</wls:context-root>
</wls:weblogic-web-app>

--------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------------------- ---------

SSL:T3 Certification

1 Overview

This article mainly describes how to configure the WebLogic cluster environment. Primary includes domain creation, cluster creation, server creation, WTC creation, program Publishing, service outage maintenance.

This article explains the sample environment:

WebLogic 9.2.3

Jdk150_12

Operating system: SunOS 5.10

Host ip:135.10.26.64 Name: NGWEB14

Host ip:135.10.26.65 Name: NGWEB15

Host ip:135.10.26.66 Name: NGWEB16

2 Concept explanation

Domains: Domain is the largest snap-in for WebLogic server instances, containing all WebLogic service resources. The following figure, Gzyzweb is a domain that contains all the WebLogic resources.

Service (Servers): A collection of externally delivered services, usually called servers.

Cluster (clusters): a grouping of servers.

Deployments (Deployment): publishes the application and makes the application run to that servers.

3 Domain Creation

3.1 Running the Create script

Script located in ${weblogic_home}/weblogic92/common/bin/config.sh

3.2 Select domain mode

Development mode and product model, according to the actual need to make a choice. Development mode when the service is started, the user name and password are not required, and the product mode requires the user name and password to be configured when the service is started.

3.3 Select a domain path

Configure the path to the new domain and customize a domain name, depending on the actual needs.

4 Configuration domain

4.1 Configuration Instructions

When domain creation is complete, a Config.xml file can be found in the domain's config directory, which is the configuration file for the entire domain environment. I'm not here to describe directly if you write Config.xml to implement the configuration, or you can configure it through the WebLogic console console.

4.2 Configuration Management Listening port

The default listening port is 7001, and usually we don't use the port, so we still need to be in the Config.xml.

<server>

<name>AdminServer</name>

<listen-port>8003</listen-port>

</server

4.3 Start the Management Server

In the domain directory./gzyzweb/bin, execute startweblogic.sh.

4.4 Access to the management console

Wait for admin server to start, enter address in browser: http://135.10.26.64:8003/console

5 Configuring the host

I want to configure the service on 3 hosts Unix, as needed.

5.1 Creating a Host

5.2 Configuring Node Properties

6 Configuration Cluster

Cluster can be said to be a collection of servers, so I mainly based on the actual application, the establishment of clusters.

6.1 Cluster creation

multicast address (multicast addresses): Usually after two digits of the cost machine IP two-bit address.

7 Configuring the server

The number of configuration servers is related to the actual application plan and performance, and a few or even dozens of servers can be started on one machine.

7.1 Server Creation

8 Configuration WTC

WTC: Is the WebLogic and tuxedo private connection method.

8.1 Server Creation

8.2 WTC Local Tuxedo Access point configuration

8.3 WTC Remote Tuxedo Access Point Configuration

9 Regulated Service certification

As the example above, the 135.10.26.66 host is the Management Server, then the host of the 135.10.26.64/65 need to launch certification to 66 to obtain the authorized authority.

9.1 Execute the authentication command

./weblogic92/common/bin/wlst.sh

9.2 Execute connect () command

Wls:/offline> Connect ()

Please enter your username [WebLogic]: WebLogic

Please enter your password [WebLogic]:

Please enter your server URL [t3://localhost:7001]: t3://135.10.26.66:8003

Connecting to t3://135.10.26.66:8003 with UserID WebLogic ...

Successfully connected to Admin Server ' AdminServer ', belongs to domain ' Gzyzweb '.

Warning:an insecure protocol is used to connect to the

Server. To ensure On-the-wire security, the SSL port or

Admin port should be used instead.

9.3 Let the domain of 65 machine pass 66 machine authentication

Wls:/gzyzweb/serverconfig> nmenroll ('/export/home/weblogic/domains/gzyzweb ', '/export/home/weblogic/ Weblogic92/common/nodemanager ')

Enrolling this machine with the domain directory At/export/home/weblogic/domains/gzyzweb ...

Successfully enrolled this machine with the domain directory at/export/home/weblogic/domains/gzyzweb.

9.4 Start the Nodemanger Manager on the 65 machine

When you start 65 on a 66 machine, the server runs on B.

10 Management Service Secure Communication settings

A CA signature is required to manage security (via Nodemanger forwarding) that is used to service communication between managed services. Since all are internal subnet traffic, we set the signature to none when using SSL for communication.

Set by: Enter the admin server's Configuration > SSL, Select Advanced, set hostname verification to None .