Was6.1 Silent Installation and troubleshooting on linux (redhat5)

Was6.1 Silent Installation and troubleshooting on linux (redhat5)

I. environment conditions:
Remote RHL5 Linux Server
Local Win7 System
Smooth Network
Ii. Software conditions:
WAS6.1 program installation package
Xmanger remote SSH logon tool (Other ssh logon tools can be used)

A lot of problems may occur after the firewall is shut down: It is executing the following commands:
A. Enabling/disabling the service takes effect immediately and becomes invalid after restart.
Service iptables start
Service iptables stop
A. Enabling/disabling services takes effect permanently
Chkconfig iptables on
Chkconfig iptables off

Install the was package
1. Upload the was6.1 installation package:
Use xshell in Xmanager for ssh Login
It is best to create a new folder to save the was installation package and run the rz command in the specified directory to select the file to upload (note that the number of server system digits must be consistent with the number of was digits)

Run the following command to decompress the installation package after the upload is complete:
Tar-xzvf C88TFML_WASND_61_LINUX_X86_64.tar.gz
Obtain the following directory:

2. Edit the configuration file responsefile.nd.txt
We use the Silent Installation Method. All configurations are loaded by reading the configuration file. Next we will configure the corresponding file.
The responsefile.nd.txt file is located in the installation disk/WAS/folder. The following describes the parameters to be modified:
-OPT silentInstallLicenseAcceptance = "true"-accept License
-OPT allowNonRootSilentInstall = "true" -- whether to allow installation by non-root users
-OPT disableOSPrereqChecking = "true" -- Cancel system detection
-OPT installType = "installNew" -- whether to install it completely (note that this configuration item cannot be configured during configuration-OPT createProfile = "true". The two parameters are mutually exclusive. Remember)
-OPT feature = "noFeature" -- no installation example
-OPT installLocation = "/opt/IBM/WebSphere/AppServer" -- the default installation path for HP-UX, Solaris or Linux.
If it is installed under AIX, the path is-OPT installLocation = "/usr/IBM/WebSphere/AppServer"
-OPT profileType = "cell" -- generate a standard summary table. If it is set to none, no summary file is created. You must use manageprofiles. THE sh command is used to manually create a summary file. You can create a cell summary file and a dm Summary File by specifying it as a cell;
-OPT PROF_enableAdminSecurity = "true" -- set administrator security and enter the user name and password in the following two items. For example, the user name is admin and the password is admin. If the value is "false", this parameter is not set. The following two items are not required.
-OPT PROF_adminUserName = "admin"
-OPT PROF_adminPassword = "admin"
Save the file.
4. Execute the command line installation (Silent Installation ):
Run the command as the root account, switch the directory to WAS/enter in the command line
#./Install-options "responsefile.nd.txt"-silent
Here, the location and name of the responsefile.nd.txt file are set by myself. I changed it directly in the corresponding file provided by was.
Wait for a while until the command execution is complete. Check whether the installation is successful.
(This step is prone to a problem: it takes about a few seconds to execute the command, and then observe that there is nothing in the/opt directory. This indicates that the error may occur due to the following factors:
First, the log file directory will be generated during installation and found in waslogs folder under the user's directory.

This is why the two options mentioned above are mutually exclusive. Just comment out the createProfile configuration item.
Second, was jdk1.5 cannot be used in the system. We can check the following command.
# ../JDK/jre. pak/repository/package. java. jre/java/jre/bin/java-version (my current directory is under the WAS directory)
If jdk 1.5 is displayed normally, this cause is excluded. If errors such as Permission Deny are reported, the problem must be solved.
Cause: If you want to use WAS6.0 and WAS6.1 for RHEL versions 5 and later, you must use WAS6.0.2.21 or later, and install IBM SDK1.5.5 or later versions.
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.
The solution is as follows:
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.
Disable SELinux:
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.
 
)
Switch the directory to/opt. If you run the following command in the opt path, the. ibm and IBM folders are displayed, indicating that the installation is complete.
# Ls-la
5. view the Installation Log
The log file is located in/opt/IBM/WebSphere/AppServer/logs/install/log.txt. If you are interested, check it yourself.

6. verify whether the installation is successful
Switch the directory to/opt/IBM/WebSphere/AppServer/bin to start WAS
# Sh startServer. sh server1
(There are also several problems in this area.
1. Execute the following command
Netstat-antp
Check whether the ports after was is started, such as 9043, 9060, and 9080, are listening normally. If these ports are not available, it means that was is not started successfully. Let's check the startup log.
Vi/opt/IBM/WebSphere/AppServer/profiles/**/logs/server1/SystemOut. log
Vi/opt/IBM/WebSphere/AppServer/profiles/**/logs/server1/startServer. log
Detected in SystemOut. log
Solution to this problem
1. Modify the/etc/sysconfig/networ File
# Vi/etc/sysconfig/network
NETWORKING = yes
HOSTNAME = yourname (modify hostname here and replace yourname with your desired name)

2. Modify the name in/etc/hosts.
# Vi/etc/hosts
127.0.0.1 localhost. localdomain localhost (modify the hostname here and replace the localhost at the end with the name you want to use)

3. Finally, run the following command on the terminal:
# Hostname ***** (***** is the modified hostname, that is, the name you want to use)

Note: The names of the three changes must be consistent; otherwise, problems may occur. Remember.

)
After startup, enter http: // ip: 9043/ibm/console on another machine. If the interface can be opened, the installation is successful. The Silent Installation of the WAS image is now complete.