Linux WAS installation and preparation environment

Linux WAS can improve the ease of use performance. Next we will talk about Linux WAS. Recently, I plan to move the development platform to Linux WAS. I just installed the new Fedora 12 two days ago and installed Websphere 7 on it by the way. Record the installation process here for future reference.

Linux WAS preparation environment

First, make sure that the following components have been installed in the system: kernel and the latest or compatible version of the C ++ Runtime Library X Windows library and Environment (Gnome, KDE ...) GTK Runtime Library

1. log on to the system. We recommend that you use root users for installation to reduce installation complexity ). Check umask settings: 0022 is recommended for root users; 0002 is recommended for non-root users

2. Install FireFox by default). It is used to run the Launchpad program during installation and to use the shortcut menu created for Linux WAS in Gnome or KDE after installation.

3. If you have installed Linux WAS in the system before, stop all related Java processes and ibm http Server processes.

4. Ensure sufficient disk space. Basic installation does not include HTTP Server) requires the following disk space:
/Opt/IBM/WebSphere ~ 930 M
/Tmp ~ 100 M
WAS profile ~ that contains the example ~ 200 M, usually under the/opt/IBM/WebSphere directory

5. Increase the ulimit value to avoid problems during addNode and importWasprofile: the user's bash login script (~ /. Bashrc) add the last row: ulimit-n 8192

6. If the software with the cp command is installed, ensure that the software paths are removed from the PATH environment variable to use the shell cp command. After installing Linux WAS, restore the PATH settings.

Install Linux WAS

1. Run the launchpad. sh command in the root directory of the installation package as the root user to start the Launchpad.

2. on the displayed page, click "Launch the installation wizard for Websphere Application Server" to bring up the welcome page of the Linux WAS installation wizard.

3. On the System Prerequisite Check page, you will be warned that the supported operating System is not detected. Click Next to ignore it.

4. On the WebSphere Application Server Environments page, select "Application Server"

5. On the Enable Administrative Security Page, uncheck this option and Enable it after installation)

6. After the installation is complete, click Finish and the First Steps Console will pop up.

7. optional steps: Click Installation verification to verify the Installation. Then, you can click the Administrative console to open the Management console page http: // servername: 9060/ibm/console) to view the configuration information of Linux WAS. Finally, click Stop the server to Stop Linux WAS.

8. optional. Install the patch installation program updateinstaller2.167.0.0.0-ws-updi-linuxia32.zip, decompress the package, cd It To The unzipped directory, and run java-jar setup as root. jar. After/opt/IBM/WebSphere/UpdateaInstaller is installed by default, UpdateInstaller runs automatically, for example, put 7.0.0-WS-WAS-LinuxX32-FP0000005.pak under/opt/IBM/WebSphere/UpdateaInstaller/maintenance), one way to Next.

9. if SELinux is enabled, you need to change the java command programs related to Linux WAS and the security context of the linked libraries and jar packages. Otherwise, startServer is used. sh will encounter an error message similar to the following when starting Linux WAS/opt/IBM/WebSphere/AppServer/bin/startServer. sh: line 145:/opt/IBM/WebSphere/AppServer/java/bin/java: permission denied Linux WAS itself provides ready-made scripts/opt/IBM/WebSphere/AppServer/properties/version/nif/config/script/relabel_was.sh) to automatically complete these modifications. However, this script is customized for RHEL 5 and will check whether the system is RHEL5. so let's make a simple modification and comment out the final check statement of the script, as shown below:

 
 

  
  
view plaincopy to clipboardprint?  
  
  
#if [ -r /etc/redhat-release ]; then    
  
  
#    release=`cat /etc/redhat-release | awk '{print $7}'`    
  
  
#    version=${release%%\.*}    
  
  
#    if [ $version -ge 5 ]; then     
  
  
if [ -x /usr/sbin/selinuxenabled ] && /usr/sbin/selinuxenabled; then     
  
  
INSTALL_PATH=$1     
  
  
JAVA_PATH=$INSTALL_PATH/java/jre     
  
  
 set_java_contexts     
  
  
set_lib_contexts     
  
  
 fi    
  
  
# fi    
  
  
#fi     
  
  
exit $rc    
  
  
#if [ -r /etc/redhat-release ]; then  
  
  
# release=`cat /etc/redhat-release | awk '{print $7}'`  
  
  
# version=${release%%\.*}  
  
  
#if [ $version -ge 5 ]; then  
  
  
if [ -x /usr/sbin/selinuxenabled ] && /usr/sbin/selinuxenabled; then  
  
  
INSTALL_PATH=$1  
  
  
JAVA_PATH=$INSTALL_PATH/java/jre  
  
  
set_java_contexts  
  
  
set_lib_contexts  
  
  
fi  
  
  
#fi  
  
  
#fi  
  
  
exit $rc 
 
 

Save the modified script as relabel_was_fedora.sh, and then execute:

Sudo setenforce 0
Sudo./relabel_was_fedora.sh/opt/IBM/WebSphere/AppServer/
Sudo setenforce 1

10. If the firewall is enabled, open the WAS-related ports in Linux, such as ports 9080 and 9060.

11. Run sudo/opt/IBM/WebSphere/AppServer/profiles/cmdrv01/bin/startServer. sh server1 to start Linux WAS and check whether everything is normal.

1. Linux yum powerful basic operations
2. Partitioning and formatting Linux USB flash disks and creating Linux File Systems
3. Execute export and use man bash in Linux shell System
4. Start the installation and configuration of Linux Samba server to build
5. Install and create an account file in Linux Trac