Shulou(Shulou.com)06/02 Report--

What is the meaning of was in linux? In view of this problem, this article introduces the corresponding analysis and answers in detail, hoping to help more partners who want to solve this problem to find a more simple and feasible way.

The was command is a common command under linux.

1. Linux was command

Linux WAS can improve the performance of more convenient use. Let's talk about art, Linux WAS. Recently, I plan to gradually move the development platform to Linux WAS. Two days ago, I just installed the new Fedora 12, so I installed Websphere 7 on it.

2. Linux WAS command preparation environment

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

1. Login to the system, you can use root users or not (root user installation is recommended to reduce installation complexity). Check umask settings: 0022 is recommended for root users and 0002 is recommended for non-root users

two。 Install the FireFox browser (usually installed by default) to run the Launchpad program during installation and, after installation, use the shortcut menu created for Linux WAS in Gnome or KDE

3. If you have previously installed Linux WAS on your system, stop all relevant Java processes, as well as IBM HTTP Server processes

4. Make sure there is enough hard disk space. A basic installation (excluding HTTP Server) requires approximately the following amount of hard disk space:

/ opt/IBM/WebSphere ~ 930m / tmp ~ 100m

WAS profile ~ 200m containing examples, which is generally also in the / opt/IBM/WebSphere directory

5. Increase the ulimit value to avoid problems with addNode and importWasprofile: add a line at the end of the user's bash login script (~ / .bashrc): ulimit-n 8192

6. If you have installed software with the cp command, be sure to remove the path to the software from the PATH environment variable to ensure that you use the shell cp command. After installing Linux WAS, restore the PATH settings.

3. Installation of Linux was command Linux WAS

1. Start Launchpad as the root user runs the launchpad.sh command under the installation package root directory

two。 On the open page, click "Launch the installation wizard for Websphere Application Server" to bring up the welcome screen of the Linux WAS installation wizard

3. There will be a warning on the System Prerequisite Check page that no supported operating system has been 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 (enable after installation if necessary)

6. When the installation is complete, click the Finish button and pop up First Steps Console

7. Optional steps: click Installation verification to verify the installation, and then click Administrative console to open the administrative console page (http://servername:9060/ibm/console) to view the relevant configuration information of Linux WAS. Finally, click Stop the server to stop Linux WAS.

8. Optional: install the patch pack: install the patch pack installer (UpdateInstaller) 7.0.0.0-WS-UPDI-LinuxIA32.zip, unzip it, then cd to the unpacked directory and run java-jar setup.jar as root. By default, UpdateInstaller will run automatically after the / opt/IBM/WebSphere/UpdateaInstaller installation is completed. (manually put the downloaded patch pack, such as 7.0.0-WS-WAS-LinuxX32-FP0000005.pak, under / opt/IBM/WebSphere/UpdateaInstaller/maintenance) Just Next all the way.

9. If SELinux is enabled You need to change the java command programs related to Linux WAS and the security context of related link libraries and jar packages Otherwise, you will encounter an error message similar to the following when starting Linux WAS with startServer.sh / opt/IBM/WebSphere/AppServer/bin/startServer.sh: line 145: / opt/IBM/WebSphere/AppServer/java/bin/java: Permission denied Linux WAS itself provides a ready-made script (/ opt/IBM/WebSphere/AppServer/properties/version/nif/config/script/relabel_was.sh) to automatically complete these changes. However, this script is tailor-made for RHEL5 and will check whether the system is RHEL5. So we need to make a simple change to comment out the last check statement of the script, as follows:

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 execute:

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

10. If the firewall is enabled, open the ports related to Linux WAS, such as 9080, 9060, etc.

11. Run sudo / opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin/startServer.sh server1 to start Linux WAS and check that everything is all right.

The answer to the question about what was means in linux is shared here. I hope the above content can be of some help to you. If you still have a lot of doubts to be solved, you can follow the industry information channel to learn more about it.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.