The installation of Websphere is essentially broken into two steps:
- Installation of binaries: the binaries include the executable files and shell scripts which are part of the distribution.
- Profile Creation: a profile corresponds to an application server configuration: as a matter of fact you can have several profiles for every installation each one corresponding to a different server configuration.
In this book we will use the official WAS track, although you can perform the same steps for the WAS for developers. In order to install WAS you need to download first the Installation Manager which is an IBM technology used to install many IBM products, including WAS. Download the Installation Manager from http://www.ibm.com/developerworks/downloads/ws/was/
When you click the Download button, you will be prompted to enter your IBM ID and, after that, you can choose to download the IBM Installation Manager (IIM) for your specific OS. Once downloaded the IIM, uncompress it using a tool available on your OS.
Installing WAS is a two-step procedure which requires running at first the IBM Installation Manager (IIM) software, which will then guide you through the application server installation.
It is also possible to install WAS using automated silent installation that can be run silently using a special file called response file where we can preset installation settings so that it is not required any user input. Check the section “How to perform WAS silent installation”.
Running the IBM Installation Manager (IIM)
In order to execute the IIM, move to the folder where you have uncompressed it and run it using the following command (on Windows launch “install.exe”):
The installation of the IIM is a wizard guided procedure which just requires accepting the license agreement, specifying the IIM installation directory and reviewing the packages you are going to install. The following diagram summarizes these simple steps:
Installing the IIM will take some time; once completed move to the next step.
Installing Websphere Application Server
Once that you have installed the IIM, move to the installation directory and issue the following command (On Windows execute IBMIM.exe):
The following screen will be displayed:
Choose to Install software packages. In order to install WAS you need to provide your IBM username and password (IBM ID). Once you have entered your IBM ID username and password click OK.
By default the wizard fetches data from the IBM repository. If you are not able to contact the IBM repository then you need to add a repository location by clicking on the Add Repository button. In the Add a repository pop-up dialog, type the following URL in the Repository field: http://www.ibm.com/software/repositorymanager/V8WASDeveloperILAN.
At this point the WAS installation will start, guided again by an intuitive wizard. The only inputs expected from the wizard are the Shared Resource directory which is the folder where multiple WAS installation can share data and the WAS installation directory, often referred to as WAS_ROOT in the rest of the book:
By default, the wizard will select to install the Websphere Full Profile which provides large-scale admin capabilities and full Java EE 6 support. On the other hand you might consider trying the Liberty profile that is included in all the commercial editions of the server, providing a lightweight profile of the server for web, mobile and OSGi applications. It is a functional subset of the full WAS profile with an install size of under 50 MB, a startup time of around 3 seconds and a new XML-based server configuration which can be treated as a development artifact to aid developer productivity. The Liberty profile does not include all the features contained in the full profile (such as JMS) therefore we will focus on the Websphere Full profile on this book.
At the end of the server installation you will be prompted to start the Profile Management Tool. You can either check the “Profile management Tool to create a profile” option or just move to the next section, where the Profile Management Tool is started from a shell.