10.3 Installing WAS
WAS is supplied with an installation wizard and the Installation Factory. We used the installation wizard so we would be able to install and bring up the WebSphere Server in a repeatable and automated fashion.
WAS 6.1 is structured so there is a single binary installation, but it supports multiple profiles (for example, deployment managers and appserver). Consequently, the IBM Installer can install binary files and create profiles in one step.
We optimized the installation step by using silent installation. Installing WAS Network Deployment using silent installation refers to using a file to supply installation options without user interaction. To configure the installation, change the options in the response file before you issue the installation command. Silent installation mode does not accept interactive installation options. To specify non-default options during a silent installation, use the response file.
Using silent installation offers you the following benefits:
| 1. | 
|
| You can automate the installation tasks. |
| 2. |
|
| You can avoid prerequisite checking, which could fail for environments on a newer fix level. |
| 3. |
|
| You can avoid manual configuration tasks. |
| 4. |
|
| You can ensure repeatable and consistent installation. |
Because the WAS install image is exported on a NFS filesystem and mounted under the /exports directory, we further optimized the installation process by invoking the installation wizard remotely by using the dsh command as shown in Example 10-2.
Example 10-2 Silent installation of WAS remotely
# dsh -s -n pt /exports/was_install/was61/WAS /install -options "/exports/systemfiles/was_response/pt.responsefile.txt" -silent
The response file is customized for each node, depending on the topology. Refer to WebSphere: responsefile.nd.txt in Appendix A, Sample files, for the response file we used for the installation of our sample scenario. Example 10-3 highlights the changes made in our response file with comments.
Example 10-3 WAS response file
################################################################################ # # License Acceptance # # This must be set to "true" so that you accept all IBM license terms associated with # this product, which is necessary for installing WAS -OPT silentInstallLicenseAcceptance="true" ################################################################################ # Operating System Prerequisite Checking # # The operating system prerequisite checking was disabled because of the higher # level fixes installed on the system # -OPT disableOSPrereqChecking="true" ################################################################################ # Non-blocking Prerequisite Checking # # The non blocking prerequisite checking was disabled to allow the installer to # continue with the installation and log the warnings even though the prerequisite # checking has failed. # -OPT disableNonBlockingPrereqChecking="true" ################################################################################ # Install a New Copy # # For a new WAS installation, the installType must be set to "installNew" -OPT installType="installNew" ################################################################################ # The selection state of the "Application Server samples" feature. # # We do not require the installation of the sample application. # -OPT feature="noFeature" ################################################################################ # AIX Default Install Location: # We used the default installation path for WAS # -OPT installLocation="/usr/IBM/WAS/AppServer"################################################################################ # Profile Creation Selection # # By setting the profileType to "cell" we imply both the Dmgr and AppSrv will be hosted # on the same system. This will create a Dmgr profile and AppSrv profile on the same # system. # -OPT profileType="cell" ################################################################################ # Administrative Security # # We do not want to enable AdminConsole security # -OPT PROF_enableAdminSecurity="false" ################################################################################ # # Deployment Manager Profile name # # The Dmgr profile name must be specified # -OPT PROF_dmgrProfileName=Dmgr ################################################################################ # # Application Server Profile name # # The AppSrv profile name must be specified # -OPT PROF_appServerProfileName=AppSrv ################################################################################ # # Host name # # The host name must be specified # -OPT PROF_hostName=pt ################################################################################ # # Deployment Manager Node name # # The Dmgr node name must be specified # -OPT PROF_nodeName=ITSOCellManager ################################################################################ # # Application Server Node name # # The AppSrv node name must be specified # -OPT PROF_appServerNodeName=PTNode ################################################################################ # # Cell name # # The cell name must be specified # -OPT PROF_cellName=ITSOCell ################################################################################ # # Default Ports # # Use WAS default ports # -OPT PROF_defaultPorts="true" ################################################################################ # # Validate Ports # # This is set to true to ensure they are not reserved or in use. # Otherwise, no port validation checking will occur. # # Valid value: # true - enables port validation. # -OPT PROF_validatePorts="true"
