The purpose of this experiment is to optimize the performance of the middleware for the two-time WebSphere internal anatomy.
1. Prepare relevant documents
which
The ISO file is the was primary image file (the location of the was file)
Instalmgr Installing the Bootstrapper Installation Manager for IBM
2. Related auxiliary procedures
A) Graphical installation of Xmanager
B) xftp File transfer
C) How to use Xmanager
Xmanager use Xstart to connect to the server after installation
According to the corresponding configuration, click Run will pop up the corresponding server command line input interface
The Xmanager-passive startup graphical interface is automatically called after executing the startup program, such as Installation Manager's install
3. Installation
A) preparatory work
(1) Load the image file into an empty folder mkdir was Mount-o loop ibm\ websphere\ applications\ server\ version\ 8.5\ for\ all\ wasv85_base.iso W As (2) Decompression Installation Manager Compression pack
A) Install Installation Manager
(1) In the unzip directory to execute./install will installation Manager Setup to follow the instructions for the next installation (2) after the installation is complete, Installation Manager starts the startup statement /opt/ibm/ Installationmanager/eclipse/launcher
c) Install was
1. Click on the file--preferences
1. Click Add Repository (select Repository.config in was under was image file)
2. After adding the success, OK to return to the installation main screen, click Install
3. Select was8.5 to start the installation
5. Next installation (was itself already installed)
6. The corresponding configuration process (below are some of the more critical points, the process is generally the default installation can be)
(
You can then also pass
Cd/opt/ibm/websphere/appserver/bin/profilemanagement
./pmt.sh Start
)
Default KeyStore Password: root
Installation is complete!
D) View information such as was version
cd/opt/ibm/websphere/appserver/bin/
./versioninfo.sh
was installation related steps (Linux)