Installation process for WebSphere Process Server (WPS) v7.0 by a non-root user using the silent install method

Technote (FAQ)


Question

How do you install WebSphere Process Server v7.0 silently (no GUI) with non-root access?

Answer

The IBM Installation Manager is the method to use to manage WebSphere Process Server V7.0 installations. You can use IBM Installation Manager to install WebSphere Process Server, update existing WebSphere Process Server installations, and also apply fixes. It supports both GUI and non-GUI modes of installation.
If you do not have access to the GUI, you can use this document to silently install the following products:
- WebSphere Application server
- Installation Manager
- WebSphere Process Server

This document assumes that you have already reviewed the following topics in the product documentation:



Brief outline of the silent installation process with Installation Manager

WebSphere Process Server V7.0 includes a run_template script and a template_response.xml file to enable silent installation. The following information is a brief outline of the four-step process that happens when you use the script and file to silently install the product:

  1. An install action in the run_template script installs WebSphere Application Server to the location that you specify. Ensure that, as a non-root user, you have appropriate access to install in this location.
  2. Another install action in the run_template script installs the IBM Installation Manager if it is not already installed, or updates it to the appropriate level as required.
  3. IBM Installation Manager imports the WebSphere Application Server Network Deployment installation from Step 1.
  4. WebSphere Process Server is installed over the WebSphere Application Server location that Installation Manager imported in Step 3.

Silently installing WebSphere Process Server as a non-root user

Complete the following tasks to install the software silently as a non-root user.

Step 1: Download the appropriate product image for your operating system, and then extract the product image. For example, for a Solaris 64bit image, WPS_v7_Solaris_SPARC_64_Install.tar.gz:


    mkdir < extract_root >

    cd <extract_root>

    gunzip -c WPS_v7_Solaris_SPARC_64_Install.tar.gz | tar xvf -


The response file and script that you use to install WebSphere Process Server are located in the following location: extract_root/responsefiles/WBI


Step 2: Back up the original run_templates script and template_response.xml response file. For example:


    cp run_templates run_templates.org

    cp template_response.xml my_response.xml file



Step 3. Edit the run_templates script as follows:


    Step 3a. In the script, specify where you want to install WebSphere Application Server.

    Note: For the purpose of discussion, the rest of this document assumes WebSphere Application Server and IBM Installation Manager are installed under the following locations:

    WebSphere Application Server: /export/home/wps/wpsv7/ProcServer

    Installation Manager: /export/home/wps/wpsv7/IM/eclipse

    Example:

    WAS_LOCATION=/export/home/wps/wpsv7/ProcServer

    Install command for WebSphere Application Server:

    "${WAS_IMAGE}"/install -silent -OPT silentInstallLicenseAcceptance=true -OPT allowNonRootSilentInstall=true -OPT disableOSPrereqChecking=true -OPT disableNonBlockingPrereqChecking=true -OPT installType=installNew -OPT profileType=none -OPT feature=samplesSelected -OPT feature=languagepack.console.all -OPT feature=languagepack.server.all -OPT installLocation="${WAS_LOCATION}"


    The previous example installs WebSphere Application Server in the location that is specified by WAS_LOCATION, but it does not create any profiles. You must complete the WebSphere Process Server installation and then create profiles as a post-installation task.

    If you have already installed WebSphere Application Server, edit the run_templates script to comment out the install command that is listed in the previous example.

    Step 3b. Change the command that is used for installing the IBM Installation Manager. You can install Installation Manager installation using both root and non-root users. You can define the installation location in the my_response.xml file (see Step 4a).

    If you are a non-root user, use the following command to install Installation Manager with the run_templates script:

    Installation Manager install command for non-root user:

    "${IM_IMAGE}"/userinst  --launcher.ini "${IM_IMAGE}"/user-silent-install.ini -input "${PROGDIR}"/my_response.xml -log ${WAS_LOCATION}"/logs/wps//silent_install.log

    If you are a root user, you can use the following command:

    Installation Manager install command for root user:

    "${IM_IMAGE}"/install  --launcher.ini "${IM_IMAGE}"/silent-install.ini -input "${PROGDIR}"/my_response.xml -log "${WAS_LOCATION}"/logs/wps/silent_install.log

    Important notes on Installation Manager installation:

    • The "${WAS_LOCATION}"/logs/wps/silent_install.log file used with -log option contains the results of all the actions in the response file. Review this log file to see the results.
      • If you install Installation Manager as a non-root user, the /var/ibm/InstallationManager directory is created under the home directory for the user (/home/<user>/var/ibm/InstallationManager). If you install as a root user, this directory is created directly under /var/ibm/InstallationManager. This location is the 'Agent Data Location' (more info) that holds information about Installation Manager and the different packages it handles. If you prefer a different location for this directory, you can use a -dataLocation parameter in the install action for Installation Manager in the run_templates script, as shown in the following example:
          "${IM_IMAGE}"/install  --launcher.ini "${IM_IMAGE}"/silent-install.ini -dataLocation <path_IBMIM_dataLocationFolder> -input "${PROGDIR}"/my_response.xml -log "${WAS_LOCATION}"/logs/wps/silent_install.log



      Step 4. Edit the copy of the response file (for example, my_response.xml) as follows. This file contains all of the responses to the install actions that install Installation Manager and WebSphere Process Server.


        Step 4a. Edit the Installation manager installation location.
        <!-- #########
        This profile node defines where IBM Installation Manager (IM) is/or will be installed. If you want to modify where IM is installed modify both the installLocation and eclipseLocation values to specify the correct directory
        ##########-->
        <profile kind='self' installLocation='/export/home/wps/wpsv7/IM/eclipse' id='IBM Installation Manager'>
        <data key='eclipseLocation' value='/export/home/wps/wpsv7/IM/eclipse'/>
        </profile>

        <!-- #######
        Modify to change the location of the eclipseCache (only if no cache has been created yet). eclipseCache is the Shared Resources Directory.
        #########-->
        <preference value="/export/home/wps/wpsv7/IM/eclipseCache" name="com.ibm.cic.common.core.preferences.eclipseCache" />
        In the previous example, the response file has been modified to specify that the Installation Manager should be installed in the /export/home/wps/wpsv7/IM/eclipse directory and the cache should be installed in the  /export/home/wps/wpsv7/IM/eclipseCache directory.

        If you are a non-root user, you need to ensure that you have write access to the directory where you intend to do your installation.
        Step 4b. Edit the WebSphere Application Server installation location. This section in the response file notifies Installation Manager to the location where WebSphere Application Server is installed.

        Note: The profile in Installation Manager refers to the binary installation location (do not get confused with the WebSphere Application Server profiles).

        <profile installLocation='/export/home/wps/wpsv7/ProcServer' id=' IBM WebSphere Application Server - ND'>
        <data key='eclipseLocation' value='/export/home/wps/wpsv7/ProcServer'/>
        The id field ( IBM WebSphere Application Server - ND) is what identifies this particular WebSphere Application Server installation to Installation Manager. You can change this to anything you prefer, but make sure to use the same value further down in the response file while importing the WAS location and updating other packages.

        Step 4c. Specify that you want to import the WebSphere Application Server location.

        This command directs Installation Manager to import WebSphere Application Server Network Deployment, the location of which you specified in Step 4b. If you changed the profile ID in the previous step, you must also change the profile ID here.

        <import profile=" IBM WebSphere Application Server - ND" type="WAS" />

        Step 4d. Specify that you want to install the required prerequisites and WebSphere Process Server.

        The following lines direct Installation Manager to install the IM-based offering. If you changed the profile ID previously, you must also change the profile ID here. Note that profile in Installation Manager refers to the binary installation location.

        <install>
        <offering profile=" IBM WebSphere Application Server - ND" id="com.ibm.websphere.XML.v10" />
        <offering profile=" IBM WebSphere Application Server - ND" id="com.ibm.websphere.SCA.v10" />
        <offering profile=" IBM WebSphere Application Server - ND" id="com.ibm.ws.WPS" />
        </install>


      Step 5. Run the run_templates script:

      The following code is a sample of the run_templates script along with the console output for a non-root user:
      bash-3.00$ ./run_templates
      /home/wpsuser/WPS70/responsefiles/WBI/../../WAS/install -silent -OPT silentInstallLicenseAcceptance=true -OPT allowNonRootSilentInstall=true -OPT disableOSPrereqChecking=true -OPT disableNonBlockingPrereqChecking=true -OPT installType=installNew -OPT profileType=none -OPT feature=samplesSelected -OPT feature=languagepack.console.all -OPT feature=languagepack.server.all -OPT installLocation=/export/home/wps/wpsv7/ProcServer
      WAS rc: 0
      /home/wpsuser/WPS70/responsefiles/WBI/../../IM/userinst --launcher.ini /home/wpsuser/WPS70/responsefiles/WBI/../../IM/user-silent-install.ini -input /home/wpsuser/WPS70/responsefiles/WBI/my_response.xml -log
      /export/home/wps/wpsv7/ProcServer/logs/wps/silent_install.log
      The next step is to use the manageProfiles command or the Profile Management Tool to augment existing profiles or create a new profile to enable the functionality provided by the feature pack. See the Information Center articles on creating, deleting, and augmenting profiles. Additionally, Network Deployment customers should read the profile rules and limitations topic.


      The output 'WAS rc:0' indicates that WebSphere Application Server was successfully installed. You can also check in the WAS_LOCATION/logs/install/log.txt file for an INSTCONFSUCCESS message to confirm.

      The output 'The next step...' indicates that WebSphere Process Server was successfully installed.




      Step 6. Complete post-installation tasks and verify the installation:
      • Verify that the INSTCONFSUCCESS message exists in the WAS_LOCATION/logs/install/log.txt file to indicate that WebSphere Application Server was installed.
      • Check the WAS_LOCATION//logs/wps/silent_install.log file to verify that WebSphere Process Server was installed. You will see a message similar to the following text if the installation was successful:

        The next step is to use the manageProfiles command or the Profile Management Tool to augment existing profiles or create a new profile to enable the functionality provided by the feature pack. See the Information Center articles on creating, deleting, and augmenting profiles. Additionally, Network Deployment customers should read the profile rules and limitations topic.

        You will also see the same message in the shell you used to run the run_templates script.


      Additional tips:

      Refer to the WebSphere Process Server support site on information about applying fix packs.

      At the time of writing this document, WebSphere Process Server V7.0.0 Fix Pack 1 is available for download.

      Also, note that you still need to use WebSphere Application Server Update Installer to apply any required fixes to your WebSphere Application Server installation.

      Related information

      WebSphere Process Server install in an isolated environ
      Installing WebSphere Process Server silently
      Installing interim Fixes (iFixes) manually
      Installing as an administrator or nonadministrator
      Installing updating and scripting installation

      Rate this page:

      (0 users)Average rating

      Add comments

      Document information


      More support for:

      WebSphere Process Server
      Installer

      Software version:

      7.0, 7.0.0.1

      Operating system(s):

      AIX, HP-UX, Linux, Solaris, Windows

      Reference #:

      1417628

      Modified date:

      2011-01-05

      Translate my page

      Machine Translation

      Content navigation