Cluster and configuration __web of WebLogic

One, the WebLogic cluster

Remember the cluster of Tomcat we talked about on the fifth day tutorial?

Two tomcat to do node that is TOMCAT1, TOMCAT2, using Apache httpserver to do a request for distribution.

Now look at the WebLogic cluster, in fact, it is similar.

The difference is that Tomcat's cluster is implemented as two physically different Tomcat, two node, no master control, no console available (only through the more humble http://localhost:8080/manager/html, or http://localhost:9090/manager/html) to monitor each Tomcat node (only monitor has no control here);

If we're going to be using our web apps, we need to manually copy files to each tomcat's WebApp directory individually. the WebLogic cluster must have a total control, as can be seen from the figure above, and then the master control we call it AdminServer, and then under it we can hang WebLogic's cluster node, which is not a physically different two weblogic, Instead of domain, we assume that domain1, domain2, is a node of two weblogic clusters.

if we want to distribute our web apps, we just need to do it once in the master-side, then the node that hangs on the master-side will automatically publish our web application to every node.

Therefore, the cluster that implements the WebLogic must: Install WebLogic create a adminserver domain on the adminserver set up the cluster master to create each node to join the total control end of the cluster, and also one of the domain Ii. planning before creating a WebLogic cluster

Based on the contents of the first section, we plan our WebLogic for experiments into 3 domain, each of which contains the following essential attributes: Adminconsole (Total control)

Logical name

Physical name (System path in domain)

Port number

Meter name (IP)

Login information (Username/password) Cluster Node1 (cluster node 1)

Logical name

Physical name (System path in domain)

Port number

Meter name (IP)

Login information (Username/password) Cluster Node2 (cluster Node 2)

Logical name

Physical name (System path in domain)

Port number

Meter name (IP)

Login information (Username/password)

We use tables to list the aggregate control and each node in the cluster we will create:

7001

[

physical names	logical name	Port number	host name (IP)	logon information
\bea\user_projects\domains\adminserver	AdminServer	localhost	weblogic/password_1
\bea\user_projects\domains\server1	Mycluster1	7011	localhost	weblogic/password_1
bea\user_projects\domains\ Server2	Mycluster2	7012	localhost	weblogic/password_1

With the plan ready, you can start to create our cluster. third, start to create our WebLogic cluster 3.1 Create the total control side of the cluster (aminserver)

Windows:

Windows starts Creating Domain Wizard by menu->oracleweblogic->weblogic Server 11gr1->tools->configuration Wizard.

Unix/linux:

Unix/linux through the

Cd/bea/wlserver/common/bin ./config.sh

To start the wizard that created domain.

Select "Create a new WebLogic domain", choose Next ( all following my steps and interface with the selection of parameters to go, all the user name, password, port number, IP, please fill in according to the first section of the table in the parameters)

The next step is similar to the interface, but there is a difference, attention oh, don't do it too soon

The above is called the Cluster broadcast address interface.

Because the cluster is broadcast (with unicast and multicast two kinds) to synchronize nodes in the cluster, and the session in each node through the broadcast address for replication and synchronization, that is, the main control domain constantly and its sub nodes under the communication between, Often to ask each child node. Name: can be any cluster information transfer mode: There are two kinds of unitcast and multicast, before the 11G version of the multicast10g began to support the unicast protocol. If you specify multicast, you must specify a multicast address, which can be weblogic default.

If you are in a domain environment, you also need to configure this multicast address and multicast port in the firewall so that it is opened in the firewall and the protocol is both of TCP and UDP.

Look, this piece on the right we call it "the logical extension of the cluster."

This is where the nodes in each cluster are assigned the corresponding "Computer name/IP", because our experiment is based on the same machine, that is, the vertical cluster, so this step does not need to fill in any, direct next .

You can start adminserver when you are done

And then through the http://localhost:7001/console to view our cluster planning, the following figure:

In this way, we have completed the creation of a new domain and will be expanded into a cluster of total control-side servers, at the same time, we have created a "cluster Topology", so here's what to do: Create node 1 in the cluster topology to create nodes in the cluster topology 2 3.2 Creating nodes in a cluster (Mycluster1, Mycluster2)

Start the WebLogic configuration Wizard

According to the normal domain, is a common domain to create ( for the experiment to facilitate our user name and password are all weblogic/password_1): user_projects\domains\ Server1 (logical name: Mycluster1, Port: 7011) User_projects\domains\server2 (logical name: Mycluster2, Port: 7012)

Next, Next, create, finish.

The same steps above allow you to create SERVER2 (the logical name is Mycluster2, Port: 7012).

3.3 How to start a cluster

[

physical names	logical name	Port number	host name (IP)	logon information
\bea\user_projects\domains\adminserver	AdminServer