Was6.1 after SELinux is installed on rhel5.3

I. Problems
Colleague saidWebSphereApplicaitonServer6.1 is unable to be installed on rehat5.3. Directly run the install script without any response. WhileEnvironmentDemand side project team needs to be tight.
I roughly looked at the hardware environment and operationsSystemIs Red Hat EnterpriseLinuxServer Release 5.3 (tikanga), kernel is kernel 2.6.18-128. el5xen on an x86_64.SoftwareEnvironment, new users and user groups have been createdWasAnd was, the purpose is very obvious, do not want to use Super User Root, but create a separate user of was6.1, this helps avoid unpredictable high risks brought by Super Users and clarify the division of responsibilities between hardware and software maintenance.

The previously installed was5.1 is 32-bit, and was6.1 is also 32-bit. I have not installed the 64-bit was6.1. Of course, the hardware is 64-bit. This is a new challenge for me. I am also a skilled engineer in assembling was. It should not be a problem. As a result, I used to run the install script directly, which is the same as that of my colleagues. Is it my character? Impossible.

Check the JRE of the installation package first.Java-Versions cannot run. The was6.1 installation package throws the following error message:
[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
Cocould not create the Java Virtual Machine.

Unable to load libj9jit23. So and libjclscar_23.so, the license is denied and the Java Virtual Machine cannot be created.

Ii. Solution
Is there a problem with the JRE of the installation package? It seems unlikely that I use a 64-bit rehat5.0 or later version for the first time. Therefore, I first doubt whether the operating system supports mines and must be bypassed. Sure enoughIBMThe hardware requirements on the patch release instructions on the official website are specifically pointed out that the symptoms of the problem are exactly the same.
Http://www-01.ibm.com/support/docview.wss? Uid = swg21264941
Problems might occur when you attempt to run WebSphereApplicationServer on the Red Hat Enterprise Linux version 5 Operating System
Te (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 followingWebSite: 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.

The reason is as follows:
If you want to use was6.0 and was6.1 for operating systems later than RHEL version 5, you must use was6.0.2.21 or later and install IBM sdk1.5.5 or later.
In addition, the default security enhancement (SELinux) policy of Red Hat Enterprise Linux version 5 blocks the correct installation and running of was versions 6.0 and 6.1.

SolutionComplete the following steps:
1. the right remedy: Disable SELinux of Red Hat Enterprise Linux version 5 before was6.0 or 6.1 is installed. For more details, refer to the Red Hat Enterprise Linux development guide ".
2. After waswas6.0 or 6.1 is installed, execute one of the following upgrade actions:
For was6.0, install was 6.0.2.21 and later on your system and install IBM sdk1.4.2.8 and later.
For was6.1, install was 6.1.0.9 and later on your system and install IBM sdk1.5.5 and later.

Iii. Positive Solution
The question is, how to disable SELinux, and how to search and view the Red Hat Enterprise Linux development guide ". Throw the following reference:
Deployment_Guide-en-US, the so-called"DevelopmentGuide ":
Http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Deployment_Guide-en-US/index.html
To enable or disable SELinux, see Chapter 44.2.7. enable or disable SELinux in the Development Guide ":
Http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Deployment_Guide-en-US/sec-sel-enable-disable.html
There are two ways to disable SELinux:
1. edit/etc/sysconfig/SELinux in command mode and change SELinux = permissive to SELinux = disabled. Note that after SELinux or selinuxtype is modified, the modification takes effect only when the machine is restarted next time.
[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. Modify SELinux in Gui Mode
Note: The Administrator permission is required to modify SELinux in Gui mode. The procedure is as follows.
(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.

The installation script of the was installation package finally runs, and the installation interface jumps out. Kung fu is really worth it.

Iv. Review
Finally, in terms of hardware requirements and software requirements (Operating Systems), I will summarize how SELinux can solve problems in scenarios where was6.1 is blocked from normal installation as follows:
1. The hardware is 64-bit, the operating system is 64-bit, and the operating system is RHEL 5.0 +.
2. No longer use superusers, but use non-root users and user groups to install was6.1.
3. How to disable SELinux so that the was6.1 graphical installation interface can correctly start and run the installation process smoothly.