IBM WAS_V85安裝兩節(jié)點(diǎn)was負(fù)載均衡-詳細(xì)步驟

1、安裝兩節(jié)點(diǎn)was負(fù)載均衡一、 安裝IM 兩邊可同時進(jìn)行二、 安裝WAS -ND 兩邊可同時進(jìn)行、三、 配置WAS -ND 添加節(jié)點(diǎn)Node 1 PIM-prod:/opt/IBM/WebSphere/AppServer/bin # pwd/opt/IBM/WebSphere/AppServer/binPIM-prod:/opt/IBM/WebSphere/AppServer/bin # /opt/IBM/WebSphere/AppServer/bin/manageprofiles.sh -create -templatePath /opt/IBM/WebSphere/AppServer/pro

2、fileTemplates/dmgr -profileName Dmgr -nodeName dmgrnode -cellName WASClusterCWMBU0002I: The deployment manager profile template has been deprecated and replaced by the management profile template with a deployment manager server.INSTCONFSUCCESS: Success: Profile Dmgr now exists. Please consult /opt/

3、IBM/WebSphere/AppServer/profiles/Dmgr/logs/AboutThisProfile.txt for more information about this profile.PIM-prod:/opt/IBM/WebSphere/AppServer/bin # /opt/IBM/WebSphere/AppServer/bin/manageprofiles.sh -create -templatePath /opt/IBM/WebSphere/AppServer/profileTemplates/default -profileName APP1Node1 -n

4、odeName APP1Node1INSTCONFSUCCESS: Success: Profile APP1Node1 now exists. Please consult /opt/IBM/WebSphere/AppServer/profiles/APP1Node1/logs/AboutThisProfile.txt for more information about this profile.Node2 PIM-prod-2: # /opt/IBM/WebSphere/AppServer/bin/manageprofiles.sh -create -templatePath /opt/

5、IBM/WebSphere/AppServer/profileTemplates/default -profileName APP2Node1 -nodeName APP2Node1INSTCONFSUCCESS: Success: Profile APP2Node1 now exists. Please consult /opt/IBM/WebSphere/AppServer/profiles/APP2Node1/logs/AboutThisProfile.txt for more information about this profile.PIM-prod-2: #Node 1 PIM-

6、prod:/opt/IBM/WebSphere/AppServer/bin # /opt/IBM/WebSphere/AppServer/profiles/Dmgr/bin/startManager.shADMU0116I: Tool information is being logged in file /opt/IBM/WebSphere/AppServer/profiles/Dmgr/logs/dmgr/startServer.logADMU0128I: Starting tool with the Dmgr profileADMU3100I: Reading configuration

7、 for server: dmgrADMU3200I: Server launched. Waiting for initialization status.ADMU3000I: Server dmgr open for e-business; process id is 8082PIM-prod:/opt/IBM/WebSphere/AppServer/bin #PIM-prod:/opt/IBM/WebSphere/AppServer/bin # /opt/IBM/WebSphere/AppServer/profiles/APP1Node1/bin/startServer.sh serve

8、r1ADMU0116I: Tool information is being logged in file /opt/IBM/WebSphere/AppServer/profiles/APP1Node1/logs/server1/startServer.logADMU0128I: Starting tool with the APP1Node1 profileADMU3100I: Reading configuration for server: server1ADMU3200I: Server launched. Waiting for initialization status.ADMU3

9、000I: Server server1 open for e-business; process id is 8670Node 2PIM-prod-2: # /opt/IBM/WebSphere/AppServer/profiles/APP2Node1/bin/startServer.sh server1ADMU0116I: Tool information is being logged in file /opt/IBM/WebSphere/AppServer/profiles/APP2Node1/logs/server1/startServer.logADMU0128I: Startin

10、g tool with the APP2Node1 profileADMU3100I: Reading configuration for server: server1ADMU3200I: Server launched. Waiting for initialization status.ADMU3000I: Server server1 open for e-business; process id is 5137Node 1PIM-prod:/opt/IBM/WebSphere/AppServer/bin#/opt/IBM/WebSphere/AppServer/profiles/AP

11、P1Node1/bin/addNode.sh 192.168.231.55 8879ADMU0116I: Tool information is being logged in file /opt/IBM/WebSphere/AppServer/profiles/APP1Node1/logs/addNode.logADMU0128I: Starting tool with the APP1Node1 profileCWPKI0308I: Adding signer alias root_1 to local keystore ClientDefaultTrustStore with the f

12、ollowing SHA digest: 67:C6:F1:22:0F:7C:CD:A1:65:66:74:96:81:BD:AD:37:35:E3:7B:58ADMU0001I: Begin federation of node APP1Node1 with Deployment Manager at 192.168.231.55:8879.ADMU0009I: Successfully connected to Deployment Manager Server: 192.168.231.55:8879ADMU0505I: Servers found in configuration:AD

13、MU0506I: Server name: server1ADMU2010I: Stopping all server processes for node APP1Node1ADMU0510I: Server server1 is now STOPPEDADMU0024I: Deleting the old backup directory.ADMU0015I: Backing up the original cell repository.ADMU0012I: Creating Node Agent configuration for node: APP1Node1ADMU0014I: A

14、dding node APP1Node1 configuration to cell: WASClusterADMU0016I: Synchronizing configuration between node and cell.ADMU0018I: Launching Node Agent process for node: APP1Node1ADMU0020I: Reading configuration for Node Agent process: nodeagentADMU0022I: Node Agent launched. Waiting for initialization s

15、tatus.ADMU0030I: Node Agent initialization completed successfully. Process id is: 8989ADMU0300I: The node APP1Node1 was successfully added to the WASCluster cell.ADMU0306I: Note:ADMU0302I: Any cell-level documents from the standalone WASCluster configuration have not been migrated to the new cell.AD

16、MU0307I: You might want to:ADMU0303I: Update the configuration on the WASCluster Deployment Manager with values from the old cell-level documents.ADMU0306I: Note:ADMU0304I: Because -includeapps was not specified, applications installed on the standalone node were not installed on the new cell.ADMU03

17、07I: You might want to:ADMU0305I: Install applications onto the WASCluster cell using wsadmin $AdminApp or the Administrative Console.ADMU0003I: Node APP1Node1 has been successfully federated.Node 2 PIM-prod-2: # /opt/IBM/WebSphere/AppServer/profiles/APP2Node1/bin/addNode.sh 192.168.231.55 8879ADMU0

18、116I: Tool information is being logged in file /opt/IBM/WebSphere/AppServer/profiles/APP2Node1/logs/addNode.logADMU0128I: Starting tool with the APP2Node1 profileCWPKI0308I: Adding signer alias root_1 to local keystore ClientDefaultTrustStore with the following SHA digest: 67:C6:F1:22:0F:7C:CD:A1:65

19、:66:74:96:81:BD:AD:37:35:E3:7B:58ADMU0001I: Begin federation of node APP2Node1 with Deployment Manager at 192.168.231.55:8879.ADMU0009I: Successfully connected to Deployment Manager Server: 192.168.231.55:8879ADMU0505I: Servers found in configuration:ADMU0506I: Server name: server1ADMU2010I: Stoppin

20、g all server processes for node APP2Node1ADMU0510I: Server server1 is now STOPPEDADMU0024I: Deleting the old backup directory.ADMU0015I: Backing up the original cell repository.ADMU0012I: Creating Node Agent configuration for node: APP2Node1ADMU0014I: Adding node APP2Node1 configuration to cell: WAS

21、ClusterADMU0016I: Synchronizing configuration between node and cell.ADMU0018I: Launching Node Agent process for node: APP2Node1ADMU0020I: Reading configuration for Node Agent process: nodeagentADMU0022I: Node Agent launched. Waiting for initialization status.ADMU0030I: Node Agent initialization completed successfully. Process id is: 5340ADMU0300I: The node APP2Node1 was successfully added to the WASCluster cell.