Linux application development: create WebSphere (2)

Article title: Linux Application Development fuel: create WebSphere (2 ). Linux is a technology channel of the IT lab in China. Includes basic categories such as desktop applications, Linux system management, kernel research, embedded systems, and open source.
In the next window, accept the default value (in our example, the Node Name is TP1Manager, the Host Name is TP1, and the Cell Name is TP1Network ). Click Next.
　　 Figure 9. Installation Wizard -- Node, host, and unit name
　　 　
The next window displays your installation options. Confirm the selection and click Next.
　　 Figure 10. Installation Wizard -- select Installation
　　 　
The next window allows you to register online. You can register now or in the future. Click Next and then click Finish to complete Deployment Manager installation.
　　
After the installation wizard is complete, the First Steps window will automatically open.
In First Steps, click Verify Installation. This option runs the Installation Verification Test tool to confirm that the Deployment Manager server is correctly installed and can be started properly. It may take several minutes to run the validation installation test for the first time.
　　
After the message is displayed, scroll down to the confirm message area. The confirmation message shows that the dmgr server is available for e-commerce. You will see the final "IVT Verification Succeeded" and "Installation Verification is complete" messages.
　　
　　 Figure 11. First Steps
　　 　
Click Exit to disable First Steps.
　　
Click Exit to disable WebSphere Application Server Network Deployment LaunchPad.
Create a Deployment Manager Unit
After the installation is complete, your configuration will be:
　　
Computer 1:
　　
Basic WebSphere Application Server installed
The WebSphere Application Server Deployment Manager is installed.
Installed ibm http Server
　　
Computer 2:
　　
Basic WebSphere Application Server installed
　　
Deployment Manager unit creation
The two WebSphere nodes must be added to the Deployment Manager unit. We will use the addNode command to complete this task. this command can be found in the bin directory installed by WebSphere Application Server on each node (TP1 and TP2. You cannot execute this command on both nodes at the same time.
　　
Run addNode on TP1, wait for the command to end, and then run it on TP2. This command requires the computer name that runs the Deployment Manager process as the parameter. In addition, because you configure Deployment Manager and Application Server to coexist on the same computer, you must specify another parameter for the SOAP ctor Address of Deployment Manager. In this example, the host name is TP1 and the SOAP Connector Address is 8889. Listing 2 illustrates the use of the addNode command.
　　
Listing 2. addNode command
　　
TP1 :~ #/Opt/WebSphere/AppServer/addNode. sh TP1 8889
　　
The addNode command uses the specified SOAP ctor Address to connect to the Deployment Manager on the specified host. After the command is complete, you will get a message that the node has been successfully added, as shown in 12.
　　
　　 Figure 12. addNode
　　 　
Now run the same addNode command on TP2 to add TP2 to the unit.
　　
Now, we run a Deployment Manager and a Node Agent on TP1, and a Node Agent on TP2. Check the following logs to confirm that the installation has reached this step:
　　
/Opt/WebSphere/AppServer/logs/nodeagent/SystemOut. log (on TP1 and TP2)
/Opt/WebSphere/DeploymentManager/logs/dmgr/SystemOut. log (on TP1)
The message "Server xxx open for e-business" indicates that the process has been started (xxx, dmgr, or Node Agent ).
　　
　　 Create a cluster
As mentioned above, a cluster is a group of application servers running the same application. In a cluster, each application server is usually called a clone ). In Figure 13, there are three clones: two on TP2 and one on TP1. In WebSphere Application Server Version 5, the weights assigned to the clone are used to achieve load balancing. Weight is the relative value of all clones in the group.
　　
　　 Figure 13. cluster configuration
　　 　
In our example, we want to set the weight of Clone 3 to the same as the weight of clone 1 plus the weight of Clone 2. For example, you can set clone 1 to 2, Clone 2 to 2, and Clone 3 to 4. Use other values, such as 3 and 6, with the same result. Avoid using large numbers as the relative weight of the clone.
　　
Use the WebSphere Administrative Console to create an application server cluster. Start a Web browser (such as Mozilla or Netscape) in the background ):
　　
# Mozilla &
　　
Enter URL http: // tp1: 9091/admin to open the Deployment Manager Administrative Console. Because Deployment Manager and Application Server are configured on the same host, the port you specify is 9091 instead of 9090. Enter the user ID admin (or any administrator ID you select) and click OK:
　　
　　 Figure 14. logon to the Administrative Console
　　 　
The Administrative Console is displayed. In the Administrative Console, click + to expand Servers, and then select Clusters (Servers> Clusters ). In Server Cluster, Click New to create a New Cluster.
　　
　　 Figure 15. Administrative Console
　　 　
Now we will perform the following steps:
　　
Create a cluster
Create clone 1
Create clone 2
Create clone 3
Install an enterprise application
In step 1, enter cluster1 as the cluster name. Do not select "prefer local ". Select Create Replication Domain for this cluster. Click Next to step 2.
　　
　　 Figure 16. enter basic cluster information