weblogic10.3 single machine cluster configuration with multiple servers in a domain

First, knowledge understanding

Here, too, learn to speak briefly:

Domain: Is the basic snap-in for WebLogic Server instances. The so-called domain is the logical unit that is managed by the WebLogic server instance that is configured as Administrator server, which is a collection of all related resources.

Server: is a relatively antagonistic unit that is combined to achieve a specific function.

Domain and server relationships: A domain can contain one or more WebLogic server instances, or even a server cluster. One domain has one and only one server functions as a Management server, and the other server implements a specific logical function.

Second, the Environment preparation

1. UNIX server one, already installed WebLogic 10.3.5.0;

2, the server in the cluster must use static IP address;

Third, planning

There is a preliminary plan for the server that needs to be clustered before doing the WebLogic cluster:

Operating system	IP Address	Port	Role
Unix Aix	133.160.37.23	9025	AdminServer
Unix Aix	133.160.37.23	9026	Server-0 (Managed server)
Unix Aix	133.160.37.23	9028	Server-1 (Managed server)

Iv. steps

Can not upload pictures that is the text, reference: http://wenku.baidu.com/view/6f97e52f2af90242a895e599.html or http://langzhiwang888.iteye.com/blog/1528511

Step 1. Go to the Oracle_middleware_home/wlserver_10.3/common/bin directory and run the following command to start the Domain Configuration Wizard

./config.sh

....

Step N, complete the creation of domain, server, cluster, machine.

Log in to the console: Http://133.160.37.23:9025/console view or modify related creation information.

V. Edit the Startup file

Cannot go to the console to start the managed server directly, because that generally does not come up. Here is the preparation for verifying that the server is started: Edit the password file

Build the Boot.properties file under the domain directory (/app/tempbea/weblogic/user_projects/domains/sub_domain) that you just created (the user name password here is the user name and password configured earlier), The contents are:

Username=weblogic

password=weblogic123 Edit the command to start the Management Server you can also edit these commands into. sh or. cmd startup files

1. The startup of the domain console or Management Server can be started directly with (/app/tempbea/weblogic/user_projects/domains/sub_domain) the file:

./startweblogic.sh

2. Edit the startup command for the managed server:

133.160.37.23:9025 two managed server startup commands.

(/app/tempbea/weblogic/user_projects/domains/sub_domain/bin recording starts)

Nohup./startmanagedweblogic.sh server-1http://133.160.37.23:9025 >/app/tempbea/weblogic/user_projects/domains /sub_domain/server-1.out &

Nohup./startmanagedweblogic.sh server-0http://133.160.37.23:9025 >/app/tempbea/weblogic/user_projects/domains /sub_domain/server-0.out &

After executing the above command sequentially, you can log in to the console to see if the host is running by the state of the managed server, and if all running, that means the configuration is fine.

Vi. release of applications

Go to WebLogic's console and click on the left domain structure and deploy. Click Install on the list that appears on the right. Select your app. Select the server that you want to publish.

This is just a simple single-machine cluster application, the principle is similar.