The path to the architect Nineth Day cluster and configuration 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:

The 2 Tomcat cluster is implemented as two physically different Tomcat, two node, no master control, no console available (only through the http://localhost:8080/manager/html, or the 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 cluster of 2 WebLogic 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 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 to implement WebLogic must:

• Install WebLogic

• Create a AdminServer domain

• Establish a cluster master control on the AdminServer

You create each node that you want to join the total control of this cluster, and it is also a domain

First, to create a WebLogic cluster planning

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 end)

L Logical Name

L Physical Name (system path in domain)

L Port number

L-meter name (IP)

L Login information (Username/password)

Ücluster Node1 (cluster node 1)

L Logical Name

L Physical Name (system path in domain)

L Port number

L-meter name (IP)

L Login information (Username/password)

Ücluster Node2 (cluster Node 2)

L Logical Name

L Physical Name (system path in domain)

L Port number

L-meter name (IP)

L Login information (Username/password)

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

Physical name	Logical name	Port number	Host name (IP)	Login information
\bea\user_projects\domains\adminserver	AdminServer	7001	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.