websphere linux 5.4 安装步骤

websphere linux 5.4 安装步骤
原文: http://hi.baidu.com/kennyrbj/blog/item/302456f6f935b1e37709d74a.html

可能出现的问题:

1:

今天在RHEL5上安装websphere6.1,运行install时没有反应,

最后发现linux少装了一个包:
compat-libstdc++-33-3.2.3-61.i386.rpm

把这个包装好后,安装界面终于出来了。


在rhel5 cd2的/server目录中,运行以下命令
rpm -ivh libXp-1.0.0-8.i386.rpm
rpm -ivh openmotif-2.3.0-0.3.el5.i386.rpm
rpm -ivh compat-db-4.2.52-5.1.i386.rpm -->这个包在我的光盘上没有。
rpm -ivh compat-gcc-34-3.4.6-4.i386.rpm
rpm -ivh compat-libf2c-34-3.4.6-4.i386.rpm
rpm -ivh compat-gcc-34-g77-3.4.6-4.i386.rpm
rpm -ivh compat-gcc-34-c++-3.4.6-4.i386.rpm
rpm -ivh compat-libstdc++-296-2.96-138.i386.rpm
rpm -ivh compat-libstdc++-33-3.2.3-61.i386.rpm

2

一、问题
同事说WebSphere Applicaiton Server 6.1死活就是在ReHat5.3上装不起来。直接运行install脚本没有任何反应。而环境需求方项目组要的很紧。
我大致看了一下硬件环境,操作系统是Red Hat Enterprise Linux Server release 5.3 (Tikanga),内核是Kernel 2.6.18-128.el5xen on an x86_64。软件环境,已经新建用户和用户组was和was,目的很明显,不想使用超级用户root而是另建WAS6.1的单独用户,以避免使用超级用户带来的不可预知的高风险、同时也有利于硬件和软件维护分工边界职责的厘清。

此前装的WAS5.1是32位的,WAS6.1也是32位的,64位的WAS6.1我是没有装过。当然硬件都是64位的。这时对我来说,倒是一个新的挑战。我也是一个装配WAS的熟练工了。应该不算是问题吧。于是我也是安装以前的经验,直接运行install脚本,跟同事运行的结果一样,毫无反应。难道是我的人品问题吗?不可能吧。

先检查一下安装包的jre。java -version都跑不起来,WAS6.1安装包抛出了如下的错误信息:
[root@test02 bin]# ./java -version
JVMJ9VM011W Unable to load j9jit23: /IBM/soft/C88TFML/JDK/jre.pak/repository/package.java.jre/java/jre/bin/libj9jit23.so: cannot restore segment prot after reloc: Permission denied
JVMJ9VM011W Unable to load jclscar_23: /IBM/soft/C88TFML/JDK/jre.pak/repository/package.java.jre/java/jre/bin/libjclscar_23.so: cannot restore segment prot after reloc: Permission denied
Could not create the Java virtual machine.

因无法加载libj9jit23.so和libjclscar_23.so,许可被拒绝,无法创建Java虚拟机。

二、求解
难道是安装包的jre有问题吗?似乎不大可能,毕竟64位的ReHat5.0以上的版本我是第一次使用,于是首先怀疑操作系统在支持上是不是存在有地雷必须绕行。果然到IBM的官网的补丁发布说明上的硬件需求特别说明上就有专门指出,问题症状如出一辙。
http://www-01.ibm.com/support/docview.wss?uid=swg21264941
Problems might occur when you attempt to run WebSphere Application Server on the Red Hat Enterprise Linux Version 5 operating system
Technote (troubleshooting)

Problem(Abstract)
You might have problems if you attempt to run IBM? WebSphere? Application Server versions 6.0 or 6.1 on the Red Hat Enterprise Linux? version 5 operating system.

For example, you might receive an error message such as the following:

pak/repository/package.java.jre/java/jre/bin/classic/libjvm.so: cannotrestore segment prot after reloc: PPermission denied

Cause
If you want to use WebSphere Application Server version 6.0 on the Red Hat Enterprise Linux Version 5 operating system, you must have WebSphere Application Server version 6.0.2.21 or later and IBM Software Development Kit (SDK) version 1.4.2 Service Release 8 or later installed.

If you want to use WebSphere Application Server version 6.1 on the Red Hat Enterprise Linux version 5 operating system, you must have WebSphere Application Server version 6.1.0.9 or later and IBM SDK version 1.5 Service Release 5 or later installed.

In addition, the Red Hat Enterprise Linux version 5 default policy for security-enhanced Linux (SELinux) prevents WebSphere Application Server versions 6.0 and 6.1 from installing and running properly.

Resolving the problem
Complete the following steps:

   1. Disable SELinux on the Red Hat Enterprise Linux version 5 operating system before installing WebSphere Application Server versions 6.0 or 6.1. For more information, see the Red Hat Enterprise Linux Deployment Guide.
   2. After installing WebSphere Application Server versions 6.0 or 6.1, perform. one of the following upgrade actions:
          * For WebSphere Application Server version 6.0, install WebSphere Application Server version 6.0.2.21 or later and IBM SDK version 1.4.2 Service Release 8 or later on your system. These updates are available through the following Web site: Recommended fixes for WebSphere Application Server.
          * For WebSphere Application Server version 6.1, install WebSphere Application Server version 6.1.0.9 or later and IBM SDK version 1.5 Service Release 5 or later on your system. These updates are available through the following Web site: Recommended fixes for WebSphere Application Server.

原因如下:
如果想在RHEL版本5以上的操作系统使用WAS6.0以及WAS6.1,那么必须使用WAS6.0.2.21或者以上的版本,同时必须安装IBM的SDK1.5.5或者以上的版本。
另外,红帽企业Linux版本5的增强安全 (SELinux) 的缺省策略阻止了WAS版本6.0 和6.1的正确安装和运行。

解决问题完成如下的步骤:
1、对症下药,在安装WAS6.0或者6.1之前,禁用红帽企业Linux版本5操作系统的SELinux。更多详情,就要参考“红帽企业Linux开发指南”。
2、在安装WASWAS6.0或者6.1之后,执行如下的升级动作其中之一:
对于WAS6.0,在你的系统上安装WAS 6.0.2.21及其以上版本并同时安装IBM的SDK1.4.2.8及其以上版本。
对于WAS6.1,在你的系统上安装WAS 6.1.0.9及其以上版本并同时安装IBM的SDK1.5.5及其以上版本。

三、正解
问题来了,如何禁用SELinux,又要动手搜索查看“红帽企业Linux开发指南”。再抛出如下的参考:
Deployment_Guide-en-US,所谓的“开发指南”:
http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Deployment_Guide-en-US/index.html
如何启用或者禁用SELinux,参考“开发指南”的章节“44.2.7. Enable or Disable SELinux”:
http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Deployment_Guide-en-US/sec-sel-enable-disable.html
禁用SELinux方法有两种:
1、命令方式下编辑/etc/sysconfig/selinux,把SELINUX=permissive改成SELINUX=disabled。需要提醒的是,修改SELINUX或者SELINUXTYPE后,只有在下次重启机器的时候修改方可生效。
[root@host2a ~]# cat /etc/sysconfig/selinux
# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
#       enforcing - SELinux security policy is enforced.
#       permissive - SELinux prints warnings instead of enforcing.
#       disabled - SELinux is fully disabled.
SELINUX=permissive
# SELINUXTYPE= type of policy in use. Possible values are:
#       targeted - Only targeted network daemons are protected.
#       strict - Full SELinux protection.
SELINUXTYPE=targeted

# SETLOCALDEFS= Check local definition changes
SETLOCALDEFS=0

2、图形界面方式修改SELinux
注意:图形界面方式修改SELinux需要administrator权限。操作步骤如下,我就不再赘述了。
   (1).On the System menu, point to Administration and then click Security Level and Firewall to display the Security Level Configuration dialog box.
   (2).Click the SELinux tab.
   (3).In the SELinux Setting select either Disabled, Enforcing or Permissive, and then click OK.
   (4).If you changed from Enabled to Disabled or vice versa, you need to restart the machine for the change to take effect.
   Changes made using this dialog box are immediately reflected in /etc/sysconfig/selinux.

经过以上的折腾,WAS安装包的install脚本终于运行起来,安装界面跳出来了。功夫真是不负啊。

   四、回顾
   最后我从硬件需求和软件需求(操作系统)方面对SELinux阻止WAS6.1正常安装的场景下如何解决问题总结如下:
   1、硬件是64位的,操作系统是64位,操作系统是RHEL 5.0+。
   2、不再使用超级用户,而是使用非root的用户和用户组安装WAS6.1。
   3、如何禁用SELinux,使得WAS6.1的图形化安装界面能够正确启动和安装进程能够顺利运行。

你可能感兴趣的:(linux,server,IBM,application,websphere,Deployment)