WebSphere安装部署手册

1、WebSphere安装手册1. 安装IBM Installation Manager需要安装IBM Installation Manager的效劳器为tims1 、tims2、tims3、tims4。1.1. 安装以root用户登录。(1) 将安装包agent.installer.linux.gtk.x86_64_1.6.2000.20210301_2248.zip复制或上传到/WAS目录下。(2) 进入WAS目录，解压IBM Installation Manager的安装包。roottims1 #cd /WASroottims1 WAS# unzip agent.installer.linu

2、x.gtk.x86_64_1.6.2000.20210301_2248.zip -d installer(3) 安装。roottims1 WAS# cd installerroottims1 installer# ./install这时候，将会出现安装的图形界面。点击Next。选中I accept the terms in the license agreement，点击Next。这里显示了默认的安装目录，不用更改，点击Next。确认信息无误后，点击Install。等待一会，安装完成后将显示如下界面。点击Restart Installation Manager，重启Installation M

3、anager。1.2. 启动roottims1 #cd /opt/IBM/InstallationManager/eclipseroottims1 eclipse#./IBMIM这时候，将出现IBM Installation Manager的图形界面。1.3. 停止在图形界面上直接关闭窗口即可。2. 安装IBM Server需要安装IBM Server的效劳器为tims1。需要先安装好IBM Installation Manager。2.1. 安装以root用户登录。(1) 将安装包unzip was.repo.8550.ihs.ilan_all.zip复制或上传到/WAS目录下。(2) 进入

4、WAS目录，解压IBM Server的安装包。roottims1 #cd /WASroottims1 WAS# unzip was.repo.8550.ihs.ilan_all.zip -d was.repo.8550.ihs.ilan_all(3) 翻开IBM Installation Manager界面，开始安装。进入菜单File Preferences点击Add Repository，添加存储库。点击Browse，弹出选择存储库配置文件的窗口。在这里选择/WAS/was.repo.8550.ihs.ilan_all/repository.config，点击OK。确认路径正确后，点击OK。

5、这样，IBM Installation Manager的存储库将显示在Respositories区域内。点击OK。点击Install。请等待一小会。界面中显示了IBM Server的安装包，选中它，点击Next。选中I accept the terms in the license agreement，点击Next。默认的共享资源路径/opt/IBM/IMShared不需要修改，点击Next。选中Create a new package group，默认的安装目录/opt/IBM/ Server不需要修改，点击Next。这里显示了两个IBM Server，一个是32位的，一个是64位的。64位

6、操作系统请选择64位的IBM Server。点击Next。默认的 端口是80，一般不需要修改。如果80端口号被占用，可修改成其他端口号。点击Next。确认信息无误后，点击Install。等待一会，安装完成后将显示如下界面。点击Finish，关闭窗口。2.2. 启动进入/opt/IBM/ Server/bin目录roottims1cd /opt/IBM/ Server/bin查看一下 d依赖的动态库roottims1 bin# ldd dlinux-vdso.so.1 => (0x00007fff2e467000)libm.so.6 => /lib64/libm.so.6 (0x00

7、0000350a200000)libaprutil-1.so.0 => /usr/lib64/libaprutil-1.so.0 (0x00007f84f65f5000)librt.so.1 => /lib64/librt.so.1 (0x0000003509e00000)libcrypt.so.1 => /lib64/libcrypt.so.1 (0x0000003515600000)libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003509a00000)libdl.so.2 => /lib64/libdl.s

8、o.2 (0x0000003509200000)libexpat.so.0 => not foundlibapr-1.so.0 => /usr/lib64/libapr-1.so.0 (0x00007f84f63c7000)libc.so.6 => /lib64/libc.so.6 (0x0000003509600000)libuuid.so.1 => /lib64/libuuid.so.1 (0x0000003514200000)libexpat.so.1 => /lib64/libexpat.so.1 (0x000000350d600000)libdb-4.7

9、.so => /lib64/libdb-4.7.so (0x0000003515200000)/lib64/ld-linux-x86-64.so.2 (0x0000003508e00000)libfreebl3.so => /lib64/libfreebl3.so (0x0000003514e00000)如果出现libexpat.so.0 => not found，那么创立一个指向/lib64/libexpat.so.1的链接roottims1 bin# ln -s /lib64/libexpat.so.1 /lib64/libexpat.so.0再次查看一下 d依赖的动态库

10、，这里显示所有的动态库都可以找到了。roottims1 bin# ldd dlinux-vdso.so.1 => (0x00007fffb29ff000)libm.so.6 => /lib64/libm.so.6 (0x000000350a200000)libaprutil-1.so.0 => /usr/lib64/libaprutil-1.so.0 (0x00007f87ab1ae000)librt.so.1 => /lib64/librt.so.1 (0x0000003509e00000)libcrypt.so.1 => /lib64/libcrypt.so.

11、1 (0x0000003515600000)libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003509a00000)libdl.so.2 => /lib64/libdl.so.2 (0x0000003509200000)libexpat.so.0 => /lib64/libexpat.so.0 (0x000000350d600000)libapr-1.so.0 => /usr/lib64/libapr-1.so.0 (0x00007f87aaf80000)libc.so.6 => /lib64/libc.so.6

12、 (0x0000003509600000)libuuid.so.1 => /lib64/libuuid.so.1 (0x0000003514200000)libdb-4.7.so => /lib64/libdb-4.7.so (0x0000003515200000)/lib64/ld-linux-x86-64.so.2 (0x0000003508e00000)libfreebl3.so => /lib64/libfreebl3.so (0x0000003514e00000)启动roottims1 bin# ./apachectl start启动后系统将出现以下进程。roott

13、ims1 bin# ps -ef|grep droot 26063 1 0 05:29 ? 00:00:00 /opt/IBM/ Server/bin/ d -d /opt/IBM/ Server -k startnobody 26064 26063 0 05:29 ? 00:00:00 /opt/IBM/ Server/bin/ d -d /opt/IBM/ Server -k startnobody 26065 26063 0 05:29 ? 00:00:00 /opt/IBM/ Server/bin/ d -d /opt/IBM/ Server -k startnobody 26066

14、26063 0 05:29 ? 00:00:00 /opt/IBM/ Server/bin/ d -d /opt/IBM/ Server -k startroot 26095 2528 0 05:29 pts/0 00:00:00 grep d启动后，在浏览器中输入 :/localhost或 :/如果是在其他机器上访问，需要将localhost或换成IBM Server的IP地址，将显示IBM Server的欢送页面，这说明启动正常了。2.3. 停止roottims1 cd /opt/IBM/ Server/binroottims1 bin# ./apach

15、ectl stop3. 安装Web Server Plugin-ins需要安装Web Server Plugin-ins的效劳器为tims1。需要先安装好IBM Installation Manager。以root用户登录。(1) 将安装包was.repo.8550.plg.ilan_all.zip复制或上传到/WAS目录下。(2) 进入WAS目录，解压安装包。roottims1 #cd /WASroottims1 WAS# unzip was.repo.8550.plg.ilan_all.zip -d was.repo.8550.plg.ilan_all(3) 翻开IBM Installat

16、ion Manager界面。进入菜单File Preferences点击Add Repository，添加存储库。点击Browse，弹出选择存储库配置文件的窗口。在这里选择/WAS/was.repo.8550.plg.ilan_all/repository.config，点击OK。确认路径正确后，点击OK。这样，IBM Installation Manager的存储库将显示在Respositories区域内。点击OK。点击Install。请等待一小会。界面中显示了Web Server Plug-ins的的安装包，选中它，点击Next。选中I accept the terms in the li

17、cense agreement，点击Next。选中Create a new package group，默认的安装目录/opt/IBM/WebSphere/Plugins不需要修改，点击Next。这里显示了两个IBM WebSphere SDK for Java，一个是32位的，一个是64位的。64位操作系统请选择64位的IBM Server。点击Next。确认信息无误后，点击Install。等待一会，安装完成后将显示如下界面。点击Finish，关闭窗口。4. 安装WebSphere Application Server需要安装WebSphere Application Server的效劳器为

18、tims2、tims3、tims4。需要先安装好IBM Installation Manager。以root用户登录。(1) 将安装包WASND_v8.5.5_1of3.zip、WASND_v8.5.5_2of3.zip、WASND_v8.5.5_3of3.zip复制或上传到/WAS目录下。(2) 进入WAS目录，解压安装包。roottims2 #cd /WASroottims2 WAS# unzip WASND_v8.5.5_1of3.zip -d WASND_v8.5.5_1of3roottims2 WAS# unzip WASND_v8.5.5_2of3.zip -d WASND_v8.

19、5.5_2of3roottims2 WAS# unzip WASND_v8.5.5_3of3.zip -d WASND_v8.5.5_3of3(3) 翻开IBM Installation Manager界面。进入菜单File Preferences点击Add Repository，添加存储库。点击Browse，弹出选择存储库配置文件的窗口。在这里选择/WAS/WASND_v8.5.5_1of3/repository.config，点击OK。确认路径正确后，点击OK。这样，WebSphere Application Server的存储库将显示在Respositories区域内。点击OK。点击In

20、stall。请等待一小会。界面中显示了WebSphere Application Server的安装包，选中它，点击Next。选中I accept the terms in the license agreement，点击Next。默认的共享资源目录/opt/IBM/IMShared不需要修改，点击Next。选中Create a new package group，默认的安装目录/opt/IBM/WebSphere/AppServer不需要修改，点击Next。这里显示了支持的语言，默认选中了English，可以选中Simplified Chinese添加简体中文语言包。点击Next。EJB的三

21、个选项不需要选中，Sample applications也不需要选中；对于64位的操作系统，最后的IBM WebSphere SDK请选择64位的。点击Next。这里要求插入盘2，盘2的目录是/WAS/WASND_v8.5.5_2of3/disk2，请输入或通过Browse选择，然后点击OK。这里要求插入盘3，盘3的目录是/WAS/WASND_v8.5.5_3of3/disk3，请输入或通过Browse选择，然后点击OK。等待一会，安装完成后将显示如下界面。选择None，点击Finish，关闭窗口。5. 创立部署管理器需要创立部署管理器的效劳器为tims2。需要先安装好IBM WebSpher

22、e Application Server。5.1. 创立部署管理器以root用户登录。翻开概要文件管理工具。翻开方式1：菜单：Applications IBM WebSphere IBM WebSphere Application Server v8.5 Tools Profile Management Tool翻开方式2：roottims2 # cd /opt/IBM/WebSphere/AppServer/bin/ProfileManagementroottims2 ProfileManagement# ./pmt.sh点击Create。选择Management，点击Next。选择Depl

23、oyment manager，点击Next。选择Advanced profile creatiojn，点击Next。选中Deploy the administrative console (recommended)，点击Next。默认的概要文件名称Dmgr01和目录/opt/IBM/WebSphere/AppServer/profiles/Dmgr01不需要修改，点击Next。输入节点名称tims2CellManage01，主机名称tims2，单元名称tims2Cell01，点击Next。选中Enable administrative security，输入用户名和密码。这个用户名和密码由安装

24、者自己确定，需要牢记。点击Next。选中Create a new default personal certificate，点击Next。将两个Expiration period in years都设置为15，其他不变，点击Next。各端口号不需要修改，点击Next。不要选中Run the deployment manager process as a Linux service，直接点击Next。确认信息无误后，点击Create。等待一会。选中Launch the First steps console，点击Finish。点击Installation verification验证。上面出现了

25、The Installation Verification Tool verification succeeded说明安装成功了。这时候，在浏览器里输入 s:/localhost:9043/ibm/console/，将会出现管理控制台的登录页面。输入前面指定的用户名和密码即可登录。5.2. 启动部署管理器roottims2 # cd /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/binroottims2 bin# ./startManager.shADMU0116I: Tool information is being logged in file

26、/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/dmgr/startServer.logADMU0128I: Starting tool with the Dmgr01 profileADMU3100I: Reading configuration for server: dmgrADMU3200I: Server launched. Waiting for initialization status.ADMU3000I: Server dmgr open for e-business; process id is 43875.3. 停止部署

27、管理器roottims2 # cd /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/binroottims2 bin# ./stopManager.sh -username wasadmin -password 123456ADMU0116I: Tool information is being logged in file /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/dmgr/stopServer.logADMU0128I: Starting tool with the Dmgr01 profi

28、leADMU3100I: Reading configuration for server: dmgrADMU3201I: Server stop request issued. Waiting for stop status.ADMU4000I: Server dmgr stop completed.执行stopManager.sh时要指定用户名和密码，这个用户名和密码是前面安装过程中输入的。需要先安装好IBM WebSphere Application Server。6. 创立节点需要创立结点的效劳器为tims3、tims4。需要先安装好IBM WebSphere Application

29、Server。6.1. 创立结点以root用户登录。翻开概要文件管理工具。翻开方式1：菜单：Applications IBM WebSphere IBM WebSphere Application Server v8.5 Tools Profile Management Tool翻开方式2：roottims3 # cd /opt/IBM/WebSphere/AppServer/bin/ProfileManagementroottims3 ProfileManagement# ./pmt.sh点击Create。选择Application server，点击Next。选择Advanced prof

30、ile creatiojn，点击Next。取消选中Deploy the default application，点击Next。默认的概要文件名称AppSrv01和目录/opt/IBM/WebSphere/AppServer/profiles/AppSrv01不需要修改，点击Next。在tims3效劳器上安装时，输入节点名称tims3Node01，效劳器名称server1，主机名称tims3；在tims4效劳器上安装时，输入结点名称tims4Node01，效劳器名称server1，主机名称tims4。点击Next。选中Enable administrative security，输入用户名和密码

31、。这个用户名和密码由安装者自己确定，需要牢记。点击Next。选中Create a new default personal certificate，点击Next。将两个Expiration period in years都设置为15，其他不变，点击Next。各端口号不需要修改，点击Next。不要选中Run the application server process as a Linux service，直接点击Next。不要选中Create a Web server definition，直接点击Next。确认信息无误后，点击Create。等待一会。选中Launch the First st

32、eps console，点击Finish。点击Installation verification验证。上面出现了The Installation Verification Tool verification succeeded说明安装成功了。6.2. 将节点联合到部署管理器roottims3 # cd /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin下面这个命令中02是部署管理器所在效劳器tims2的IP地址，8879是部署管理器的SOAP connector port，wasadmin和123456分别是部署管理器的

33、用户名和密码。roottims3 bin# ./addNode.sh 02 8879 -username wasadmin -password 123456ADMU0116I: Tool information is being logged in file /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/addNode.logADMU0128I: Starting tool with the AppSrv01 profileCWPKI0309I: All signers from remote keystore

34、already exist in local keystore.ADMU0001I: Begin federation of node tims3Node01 with Deployment Manager at 02:8879.ADMU0009I: Successfully connected to Deployment Manager Server: 02:8879ADMU0505I: Servers found in configuration:ADMU0506I: Server name: server1ADMU2021I: Stoppi

35、ng all server processes for node tims3Node01ADMU0512I: Server server1 cannot be reached. It appears to be stopped.ADMU0024I: Deleting the old backup directory.ADMU0015I: Backing up the original cell repository.ADMU0012I: Creating Node Agent configuration for node: tims3Node01ADMU0014I: Adding node t

36、ims3Node01 configuration to cell: tims2Cell01ADMU0016I: Synchronizing configuration between node and cell.ADMU0018I: Launching Node Agent process for node: tims3Node01ADMU0020I: Reading configuration for Node Agent process: nodeagentADMU0022I: Node Agent launched. Waiting for initialization status.A

37、DMU0030I: Node Agent initialization completed successfully. Process id is: 4433ADMU0300I: The node tims3Node01 was successfully added to the tims2Cell01 cell.ADMU0306I: Note:ADMU0302I: Any cell-level documents from the standalone tims2Cell01 configuration have not been migrated to the new cell.ADMU0

38、307I: You might want to:ADMU0303I: Update the configuration on the tims2Cell01 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.ADMU0307

39、I: You might want to:ADMU0305I: Install applications onto the tims2Cell01 cell using wsadmin $AdminApp or the Administrative Console.ADMU0003I: Node tims3Node01 has been successfully federated.按照上述方法分别在tims3和tims4上创立一个结点并将结点联合到部署管理器后，需要重启一下部署管理器。6.3. 常见错误6.3.1. 错误1roottims3 # cd /opt/IBM/WebSphere/A

40、ppServer/profiles/AppSrv01/binroottims3 bin# ./addNode.sh 02 8879 -username wasadmin -password 123456ADMU0116I: Tool information is being logged in file /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/addNode.logADMU0128I: Starting tool with the AppSrv01 profileCWPKI0314E: The follow

41、ing error is returned from an exception: ADMC0016E: The system cannot create a SOAP connector to connect to host 02 at port 8879.ADMU0113E: Program exiting with error: com.ibm.websphere.management.exception.ConnectorException: ADMC0016E: The system cannot create a SOAP connector to conne

42、ct to host 02 at port 8879., resulting from: SOAPException: faultCode=SOAP-ENV:Protocol; msg=; targetException=.MalformedURLExceptionADMU4123E: Ensure that the Deployment Manager is running on the specified host and port. Also ensure that the security configuration in ps on

43、 the node is compatible with the Deployment Manager. ADMU1211I: To obtain a full trace of the failure, use the -trace option.ADMU0211I: Error details may be seen in the file: /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/addNode.log解决方法：关闭部署管理器所在效劳器tims2的防火墙。这个在总体说明一节已经说明。6.3.2. 错误2roottims3 b

44、in# ./addNode.sh 02 8879 -username wasadmin -password 123456ADMU0116I: Tool information is being logged in file /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/addNode.logADMU0128I: Starting tool with the AppSrv01 profileCWPKI0308I: Adding signer alias "CN=tims2, OU=Root Certifi

45、cate," to local keystore "ClientDefaultTrustStore" with the following SHA digest: 79:B3:0E:1B:C7:1E:14:34:4F:D0:53:CB:FD:04:98:99:B2:02:9B:37CWPKI0309I: All signers from remote keystore already exist in local keystore.ADMU0001I: Begin federation of node tims3Node01 with Deployment Man

46、ager at 02:8879.ADMU0009I: Successfully connected to Deployment Manager Server: 02:8879ADMU0505I: Servers found in configuration:ADMU0506I: Server name: server1ADMU2021I: Stopping all server processes for node tims3Node01ADMU0512I: Server server1 cannot be reached. It appears

47、 to be stopped.ADMU0024I: Deleting the old backup directory.ADMU0015I: Backing up the original cell repository.ADMU0012I: Creating Node Agent configuration for node: tims3Node01ADMU0027E: An error occurred during federation ADMU0036E: The Deployment Manager cannot lookup by name host tims3 at addres

48、s ; rolling back to original configuration.ADMU0211I: Error details may be seen in the file: /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/addNode.logADMU0026I: An error occurred during federation; rolling back to original configuration.ADMU0111E: Program exiting with error: com.ibm.w

49、ebsphere.management.exception.AdminException: ADMU0036E: The Deployment Manager cannot lookup by name host tims3 at address ADMU1211I: To obtain a full trace of the failure, use the -trace option.ADMU0211I: Error details may be seen in the file: /opt/IBM/WebSphere/AppServer/profiles/AppSrv0

50、1/logs/addNode.log解决方法：请确保节点所在的效劳器的/etc/hosts中有自己的IP和主机名的对应。例如节点所在效劳器为tims3，那么/etc/hosts要有这样一行：03tims3这个在总体说明一节已经说明。6.3.3. 错误3roottims3 bin# ./addNode.sh 02 8879 -username wasadmin -password 123456ADMU0116I: Tool information is being logged in file /opt/IBM/WebSphere/AppServe

51、r/profiles/AppSrv01/logs/addNode.logADMU0128I: Starting tool with the AppSrv01 profileCWPKI0309I: All signers from remote keystore already exist in local keystore.ADMU0001I: Begin federation of node tims3Node01 with Deployment Manager at 02:8879.ADMU0009I: Successfully connected to Deplo

52、yment Manager Server: 02:8879ADMU0505I: Servers found in configuration:ADMU0506I: Server name: server1ADMU2021I: Stopping all server processes for node tims3Node01ADMU0512I: Server server1 cannot be reached. It appears to be stopped.ADMU0024I: Deleting the old backup directory.ADMU0015I:

53、 Backing up the original cell repository.ADMU0012I: Creating Node Agent configuration for node: tims3Node01ADMU0014I: Adding node tims3Node01 configuration to cell: tims2Cell01ADMU0027E: An error occurred during federation tims2; rolling back to original configuration.ADMU0211I: Error details may be

54、 seen in the file: /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/addNode.logADMU0026I: An error occurred during federation; rolling back to original configuration.ADMU0113E: Program exiting with error: com.ibm.websphere.management.exception.AdminException: com.ibm.websphere.management.filetransfer.client.TransferFailedException: Upload retry limi