1. Install jdk 6.26
[Root @ localhost src] # chmod o + x jdk-6u26-dlj-linux-amd64.bin // Add the execution permission x to the jdk's other user, some versions will prompt for the next action after performing this step. There is no prompt for this version. We will perform the Next Step manually.
[Root @ localhost src] #./jdk-6u26-dlj-linux-amd64.bin // there will be a large heap prompt information after execution, the following will prompt you whether to execute the same:
Do you agree to the above license terms? [Yes or no]
Run yes.
After completion, a new directory is generated in the current directory: jdk1.6.0 _ 26
[Root @ localhost] # ls
Apache-tomcat-6.0.36.tar.gz jdk1.6.0 _ 26 kernels
Debug jdk-6u26-dlj-linux-amd64.bin
[Root @ localhost] # mkdir-p/usr/java // create a directory to build the jdk Environment
[Root @ localhost] # mv jdk1.6.0 _ 26/usr/java/
[Root @ localhost] # vim/etc/profile // modify the environment variables. Add the following content under the change file:
Export JAVA_HOME =/usr/java/jdk1.6.0 _ 26
Export CLASSPATH = $ CLASSPATH: $ JAVA_HOME/lib: $ JAVA_HOME/jre/lib
Export PATH = $ JAVA_HOME/bin: $ JAVA_HOME/jre/bin: $ PATH: $ HOMR/bin
Source/etc/profile // make the environment variable take effect immediately
Java-version // check the java version to check whether the jdk is successfully installed.
If an error is reported:
[Root @ websphere ~] # Java-version
Error occurred during initialization of VM
Java/lang/NoClassDefFoundError: java/lang/Object
Java 6.0.26 is not installed properly. The solution is as follows:
Cd/usr/java/jdk1.6.0 _ 26/lib/
[Root @ localhost lib] # unpack200 tools. pack tools. jar
[Root @ websphere lib] # cd/usr/java/jdk1.6.0 _ 26/jre/lib/
[Root @ websphere lib] # unpack200 rt. pack rt. jar
Run java-version again, and the prompt is as follows:
[Root @ websphere lib] # java-version
Java version "1.6.0 _ 26"
Java (TM) SE Runtime Environment (build 1.6.0 _ 26-b03)
Java HotSpot (TM) Client VM (build between 1-b02, mixed mode)
Ii. Install websphere 7.0
1: Download the trial version 7.0.0.9 of Websphere e_7009.trial.base.opt.linux.ia32.tar.gz
2: Decompress the file and run launchpad. sh to install it. During the installation process, select install three, and set the username and password to megasoft.
3: Check that the installation environment is appropriate. The result is fails. No matter, go to the next step.
4: After the installation is complete, start First steps.
Including:
· Installation check: Check the installation of WebSphere Application Server, confirm the installation is correct, and start the Application Server during this process.
· Start Server: Start WebSphere Application Server. In order to facilitate and help identify problems, the output of the startup process is displayed in a separate window. When the application server starts running, the link becomes the Stop the server link, which provides a simple way to Stop the server and displays the output of the server shutdown process in a separate window. The management password that needs to be set during the installation process to stop the server. This is an easy way to check the internal authentication mechanism of the application server.
· Management Console: Start the WebSphere Management Console in the browser window. You can perform configuration tasks that are not involved in the installation process on this console. To start the console, you also need to set the management password during installation.
· Configuration file management tool: You can create additional execution configuration files. Each configuration file can be configured for specific enterprise Web applications and ports. If the target Server environment is not specified during the installation process and the Server configuration information is not migrated from the existing WebSphere Application Server System, use this option to create at least one WebSphere Application Server configuration file. At least one configuration file is required to start WebSphere Application Server. Each configuration file provides the configuration information required to start the Application Server in a specific context.
· Example Library: access the sample application installed during installation.
· WebSphere Application Server Information Center: Open the WebSphere Application Server Library website in a browser. Detailed information about WebSphere Application Server is provided here, involving many different enterprise Application scenarios.
· Migration Wizard: this wizard helps you migrate configuration information and applications from previous WebSphere Application Server versions.
After the service is enabled, you can access it as follows:
Https: // 192.168.2.18: 9043/ibm/console
If the server is restarted, run the script to start the service:
/Opt/IBM/WebSphere/AppServer/bin/startServer. sh server1