Using silent installation on HP-UX

This article describes how to install WebSphere Application Server using the noninteractive, or silent, mode. To complete a silent installation, you use the default response file or create a customized one, and then execute the installation script for WebSphere Application Server, supplying the response file as a command-line parameter.

These instructions assume the following:

  • Your machine has enough memory and disk space for your installation. See the WebSphere Application Server Supported Hardware, Software, and APIs Web site at www.ibm.com/software/webservers/appserv/doc/latest/prereq.html for the proper requirements.
  • You do not have a previous version of WebSphere Application Server already installed. If you do have a previous version of WebSphere Application Server installed, do not follow these instructions. Instead, refer to the article "Migration overview."
  • You have installed and configured your database.
  • If you are using IBM HTTP Server as your Web server, you will install it at the same time and onto the same node as you install WebSphere Application Server. If you are using another supported Web server with WebSphere Application Server, you have already installed it onto the same node as WebSphere Application Server.

    Note: You must purchase and install any Web server except IBM HTTP Server before you install WebSphere Application Server. IBM HTTP Server is supplied with WebSphere Application Server.

Using the default response file

A default response file, named install.script, is supplied with WebSphere Application Server. You can use the default options in this file to install WebSphere Application Server or use the file as a template for creating a customized response file.

If you use the default options in the default response file to install WebSphere Application Server, the following software and other resources are installed:

  • Java 2 Software Development Kit (SDK) 1.3 (version supplied with WebSphere Application Server)
  • IBM HTTP Server 1.3.19
  • WebSphere Application Server 4.0
  • WebSphere Application Server application samples
  • WebSphere Application Server application assembly and deployment tools
  • Plug-in for IBM HTTP Server 1.3.19
  • Documentation in U.S. English

All files except IBM HTTP Server are installed into the directory /opt/WebSphere/AppServer; IBM HTTP Web Server is installed into the directory /opt/HTTPServer. In addition, WebSphere Application Server is configured for use with IBM HTTP Server.

Using a customized response file

You can also use the default response file as a template for creating a customized response file. You can edit the default response file to enable the configuration of WebSphere Application Server with a different supported Web server or database or to install the products into a different directory. Instructions for editing the default response file are included in the procedure Performing a silent installation.

Performing a silent installation

Perform the following steps to create a customized response file (if needed) and install WebSphere Application Server. These instructions assume that the installation is being performed from the product CD-ROM:

  1. Ensure that you are logged into the machine with superuser (root) privileges.
  2. Ensure that the swagentd daemon is running by entering the following command:
    # ps -ef | grep swagentd
    • If the swagentd daemon is running, output similar to the following is displayed:
      root   10431   10128   0   10:43:33 pts/0   0:00   grep swagentd
      root    1391       1   0    May  9  ?       0:00   /usr/sbin/swagentd -r
    • If the swagentd daemon is not running, start it by entering the following command:
      # swagentd -r 
  3. Change particular operating system kernel parameters to make WebSphere Application Server run effectively. To set kernel parameters, perform the following steps:

    1. Determine the machine's physical memory by doing the following. You will need this value when configuring kernel parameters:
      1. Start the HP-UX System Administration Manager (SAM) utility.
      2. Select Performance Monitors, then System Properties.
      3. Click the Memory tab and note the value for Physical Memory.
      4. Click OK and exit from the SAM utility.
    2. In order to set the maxfiles and maxfiles_lim parameters to at least 4096, you must first edit the file /usr/conf/master.d/core-hpux to allow values greater than 2048 to be set by using the SAM utility. Do the following:
      1. Open the file /usr/conf/master.d/core-hpux in a text editor.
      2. Change the line
        *range maxfiles<=2048
        to
        *range maxfiles<=60000
      3. Change the line
        *range maxfiles_lim<=2048
        to
        *range maxfiles_lim<=60000
      4. Save these changes and close the file. The old values for these parameters might still be stored in the file /var/sam/boot.config. To force the SAM utility to create a new boot.config file, do the following:

        1. Move the existing version of the boot.config file located in the directory /var/sam to another location (the /tmp directory, for instance).
        2. Start the SAM utility.
        3. Select Kernel Configuration, then Configurable Parameters. When the Kernel Configuration window opens, a new boot.config file exists.

          Alternatively, you can enter the following command to rebuild the boot.config file:

          # /usr/sam/lbin/getkinfo -b
    3. Set the parameters listed in Table 1 to the values listed by doing the following:
      1. Start the SAM utility.
      2. Select Kernel Configuration, then Configurable Parameters.
      3. Highlight a parameter that you want to change and select Actions, then Modify Configurable Parameter.
      4. Type the new value for the parameter in the Formula/Value field and click OK.
      5. Repeat these steps for each of the parameters listed in Table 1 .
      6. After you have set all of the parameters, select Actions, then Process New Kernel.
      7. An information window opens, confirming your decision to restart the machine. Click Yes.

        If other information windows open, requesting information particular to your installation, follow the on-screen instructions to restart your machine and to enable the new settings to take effect.

        Alternatively, use the HPjconfig configuration utility available from the Java products for HP-UX Web site at www.hp.com/go/java. This pure Java application provides kernel parameter recommendations tailored to your specific Java enterprise services and HP-UX hardware platform. It supports only selected machine types, however. Refer to the information on this Web site to verify that your machine is suppported and for instructions on downloading and installing the utility.

        Table 1

        Parameter
        Value
        maxfiles 4096
        maxfiles_lim 4096
        max_thread_proc 1024
        maxuprc 512
        nproc 1024
        nflocks 8192
        ninode 2048
        nfile 4 * ninode value
        msgseg 32767 (or less)
        msgmnb 65 535
        msgmax 65 535
        msgtql 1024
        msgmap 258
        msgmni 256
        msgssz 16
        semmni 512
        semmap 514
        semmns 1024
        semmnu 1020 (nproc value minus 4)
        shmmax 483 183 821 (Ensure that this parameter is set to 483 183 821 or 90% of the physical memory (in bytes), whichever is higher. For example, if you have 512 MB of physical memory in your system, set shmmax to 483 183 821 (512 * 0.9 * 1024 * 1024).
        shmseg 16
        shmmni 300

    4. If you plan to redirect displays to non-HP machines, do the following before running applications that have a graphical user interface, such as the WebSphere Application Server applications that are started with the scripts install.sh or adminclient.sh:
      1. Enter the following command to obtain information on all public locales accessible to your application:
        # locale -a
      2. Choose a value for your system from the output that is displayed and set the LANG environment variable to this value. Here is an example command that sets the value of LANG to en_US.iso88591:
        # export LANG=en_US.iso88591
  4. If a preexisting Web server on your system is running, stop the Web server. If you plan to install IBM HTTP Server 1.3.19 as part of the WebSphere Application Server installation and a version of IBM HTTP Server prior to 1.3.19 is already installed on your system, you must uninstall it in order for the WebSphere Application Server installation program to successfully install IBM HTTP Server 1.3.19.
  5. Mount the CD-ROM by following the instructions in the file "Mounting a CD-ROM on HP-UX." The following steps assume that the CD-ROM drive is mounted at /cdrom.
  6. Navigate to the correct directory on the WebSphere Application Server CD-ROM by entering the following command:
    # cd /cdrom/hp
  7. Create a copy of the default response file by using the cp command, as follows:
    # cp install.script new_install.script 
    In this command, new_install.script represents the full pathname of the copy of the default response file you are creating (for example, /tmp/new_install.script). The name of your response file must have a .script extension.
  8. If the supported Web server or database you plan to use with WebSphere Application Server is newer than the version currently required by WebSphere Application Server, you must update the prereq.properties file or disable the prerequisite checking functionality before installing WebSphere Application Server.

    To obtain an updated prereq.properties file, download the latest version from the WebSphere Application Server Tools Web site at www.ibm.com/software/webservers/appserv/tools.html. Ensure that the updated prereq.properties file is downloaded or copied into the local /tmp directory.

    To disable prerequisite checking functionality, perform the following steps:

    1. Copy the prereq.properties file from the /cdrom/hp directory to the /tmp directory on the machine on which you plan to install WebSphere Application Server.
    2. Open the prereq.properties file in a text editor and disable prerequisite checking for an individual component by changing the value of the specific key from 1 to 0.
    3. Save the edited prereq.properties file.

  9. If you plan to install WebSphere Application Server by using the default options included in the default response file, proceed to Step 10. If you plan to install WebSphere Application Server by creating and using a customized response file, create this file by performing the following steps:
    1. Open your copy of the default response file new_install.script in a text editor.
    2. Move to the editable area of the response file beginning with the property destinationDirectory. This area of the response file contains editable properties specific to WebSphere Application Server product installation. Use the detailed comments throughout the file and in the table below to guide you through the installation and configuration options available for performing a customized silent installation. The table describes the properties that can be modified and their default values. All values are case-sensitive and must be entered exactly as they appear in the table. Review especially the InstallOption property. Your choice for this property can eliminate the need to make changes to other properties within the response file.

      Property name Description Possible values Default value
      destinationDirectory Use the destinationDirectory property to specify the directory in which WebSphere Application Server is installed. A fully qualified pathname /opt/WebSphere/AppServer
      InstallOption Use the InstallOption property to specify whether to perform a Quick (Typical) or Custom installation. Set this property to the value QUICK if you want to install WebSphere Application Server by using the Typical (Quick) installation option. Set this property to the value CUSTOM to install WebSphere Application Server by using the Custom installation option.
      • If you set the InstallOption property to the value QUICK, the installer installs WebSphere Application Server by using the default options listed in the section Using the default response file. No other properties within the install.script file have to be edited. At this point, save the edited install.script file. You can now reference this customized response file during installation of WebSphere Application Server.
      • If you set the InstallOption property to the value CUSTOM, you must edit several additional properties within this file. Proceed through the rest of the properties listed below.
      QUICK or CUSTOM QUICK
      Install?WebSphere Use the Install?WebSphere property to specify whether to install WebSphere Application Server. true or false true
      Install?.apserv Use the Install?.apserv property to specify whether to install the application server runtime for hosting applications and an administrative server for managing configurations. true or false true
      Install?.admin Use the Install?.admin property to specify whether to install the WebSphere Administrative Console for managing application servers (includes help and documentation). true or false true
      Install?.sample Use the Install?.sample property to specify whether to install sample servlets and Web site applications demonstrating both simple and advanced techniques. If you install the samples, you must also install the application and administrative servers or have the WebSphere Application Server product already installed on your system. true or false true
      Install?.tools Use the Install?.tools property to specify whether to install the Application Assembly and Deployment tools. true or false true
      Install?.http Use the Install?.http property to specify whether to install IBM HTTP Server 1.3.19. true or false true
      Install?.olt Use the Install?.olt property to specify whether to install the IBM Distributed Debugger. The debugger provides object level trace. true or false false
      Install?.plugins Use the Install?.plugins property to specify whether to install a Web server plug-in. This property must be set to true to install any Web server plug-in. true or false true
      Install?.apserv.apache1312 Use the Install?.apserv.apache1312 property to specify whether to install the plug-in for Apache 1.3.20 HTTP Web Server. Also set the following properties to install the plug-in for this Web server:
      Select4.config.apserv.apache1312
      Enter the fully qualified path and file name of the Web server configuration file. The default value is blank.
      Select4.error.apserv.apache1312
      Enter the fully qualified path and file name of the Web server dialog error message file. The default value is blank.
      true or false false
      Install?.apserv.httpserv Use the Install?.apserv.httpserv property to specify whether to install the plug-in for IBM HTTP Server 1.3.19. Also set the following properties to install the plug-in for this Web server:
      Select4.config.apserv.httpserv
      Enter the fully qualified path and file name of the Web server configuration file. The default value is blank.
      Select4.error.apserv.httpserv
      Enter the fully qualified path and file name of the Web server dialog error message file. The default value is blank.
      true or false true
      Install?.apserv.ipl41 Use the Install?.apserv.ipl41 property to specify whether to install the plug-in for iPlanet Web Server Enterprise Edition Version 4.1. Also set the following properties to install the plug-in for this Web server:
      Select4.config.apserv.ipl41
      Enter the fully qualified path and file name of the Web server configuration file. The default value is blank.
      Select4.error.apserv.ipl41
      Enter the fully qualified path and file name of the Web server dialog error message file. The default value is blank.
      true or false false
      Install?.apserv.domino Use the Install?.apserv.domino property to specify whether to install the plug-in for Lotus Domino Enterprise Server 5.0. Also set the following properties to install the plug-in for this Web server:
      Select4.config.apserv.domino
      Enter the fully qualified path and file name of the names.nsf file, which is the Domino/Lotus Notes database modified by WebSphere Application Server to include the plug-in information. The default value is blank.
      Select4.error.apserv.domino
      Enter the fully qualified path and file name of the Web server dialog error message file. The default value is blank.
      Select4.jarfile.apserv.domino
      Enter the fully qualified path and file name of the Notes.jar file, which is a library that the configuration code needs to configure Domino with the WebSphere Application plug-in. The default value is blank.
      true or false false
      DBType Use the DBType property to specify the database type you will use as the administrative database. DB2
      Oracle
      Merant
      Sybase
      Informix
      DB2
      DBName Use the DBName property to specify the name of the database to use. This value is the name of the database that you created when you configured your database (for instance, orcl for Oracle or was40 for DB2 UDB). A database name blank
      DBUser Use the DBUser property to specify the database user name. Ensure that you specify the same user name that you specified when configuring your database for use with WebSphere Application Server. A database user name blank
      DBPassword Use the DBPassword property to specify the database password. Ensure that you specify the same password that you specified when installing your database. If you are using DB2 UDB, your password must be eight or fewer characters in length. If you are using Sybase, your password must be six or more characters in length. A database password blank
      DBHome Use the DBHome property to specify the directory where the database software is installed. A fully qualified pathname blank
      DBurl Use the DBurl property to specify the URL for accessing the database. (If you are using DB2, Sybase, Merant, or Informix, do not edit this field.) If you are using Oracle, set this property to jdbc:oracle:thin:@hostname:1521:DBName, where hostname is the name of the machine hosting the database and DBName is the name of the database that you want to use. A database URL blank
      DBServerName Use the DBServerName property to specify the name of the host machine on which the database is located. (Do not edit this property if you are using DB2. To edit this property when using another database type, the database must be installed remotely and you must have specified the value true for the RemoteDB property.) A database server name blank
      DBPort Use the DBPort property to specify the port number of the host machine on which the database is located. (Do not edit this property if you are using DB2. To edit this property when using another database type, the database must be installed remotely and you must have specified the value true for the RemoteDB property.) A database port number blank
      RemoteDB Use the RemoteDB property to specify whether your database is installed on a different machine than the current one. (Do not edit this property if you are using DB2.) true or false false
    3. When you have finished editing the response file, save it and exit the text editor. You can now reference this customized response file during installation of WebSphere Application Server.
  10. Run the installation script in one of the following ways depending on the actions you have taken in Step 8. In each case, the install.sh shell script uses the response file to install the components and options that you have selected. (Because the shell script performs some pre- and post-processing steps on the installation, do not use the SAM utility to run the script.) The value new_install.script represents the full pathname of the copy of the default response file or the customized reponse file you created (for example, /tmp/new_install.script).
    • If you have not downloaded a new prereq.properties file or disabled the prerequisite checking functionality as detailed in Step 8, run the installation script file by entering the following command:
      # /cdrom/hp/install.sh -silent -responseFile new_install.script
    • If you have downloaded a new prereq.properties file or disabled the prerequisite checking functionality as detailed in Step 8, run the installation script file by entering the following command:

      # /cdrom/hp/install.sh -prereqfile /tmp/prereq.properties -silent  \
      -responseFile new_install.script

    Note: If you choose to install the plug-in for IBM HTTP Server, the installation process checks whether you have the correct version of the Web server on your machine. If you do not have IBM HTTP Server installed on your machine, the installation process performs one of the following actions, based on whether you have indicated in your response file to install IBM HTTP Server:

    • If you indicated in your response file that you do want to have IBM HTTP Server installed, the installation process installs the plug-in for it.
    • If you indicated in your response file that you do not want to have IBM HTTP Server installed, the script exits without installing the plug-in.
  11. After installation is complete, refer to the log file named install.log located in the /tmp directory to determine whether the silent installation was successful.
  12. Unmount the CD-ROM before removing it from the CD-ROM drive by following the instructions in the file "Mounting a CD-ROM on HP-UX."
  13. If you are using a Web server other than IBM HTTP Server, start the server. If you installed IBM HTTP Server as part of the WebSphere Application Server silent installation, you might need to configure it. Perform the following steps to verify that IBM HTTP Server is installed correctly:
    1. Ensure that the Web server is running or start it by entering the following command:
       # /opt/HTTPServer/bin/apachectl start
    2. Open a Web browser window and type the name of the host machine as the URL (http://host_machine or localhost). If you see the Welcome to the IBM HTTP Server page, the server has been installed correctly.
      Welcome to the IBM HTTP Server

      Note that you might need to make configuration adjustments to the server in order to run it successfully on your system. See the IBM HTTP Web Server documentation at www.ibm.com/software/webservers/httpservers/library.html for more information.

      To enable the Secure Sockets Layer (SSL) on IBM HTTP Server, see the IBM HTTP Server documentation at www.ibm.com/software/webservers/httpservers/doc/v1319/9atstart.htm for more information.

To test your resulting installation, proceed to the following articles: