Installing the Feature Pack for Web Services silently

Run the Feature Pack for Web Services installation program to silently install the feature pack on an existing installation of a WebSphere® Application Server Version 6.1 product.

Before you begin

The WebSphere Application Server Version 6.1 Feature Pack for Web Services extends the capabilities of WebSphere Application Server Version 6.1 to enable Web services messages to be sent asynchronously, reliably, and securely, focusing on interoperability with other vendors and to provide support for the Java API for XML Web Services (JAX-WS) 2.0 programming model.

Before starting this installation, do the following:
  1. Read Planning to install the Feature Pack for Web Services.
  2. Install a Version 6.1 WebSphere Application Server product if you have not done so already.
  3. Download and extract the Feature Pack for Web Services.

    For example, create two directories, wssrv_download and wsssrv_installation_image. Then, download the feature pack to the wssrv_download directory and then extract the downloaded file to the wsssrv_installation_image directory. Do not move any files out of the wsssrv_installation_image directory.

  4. The operating system requirements for a feature pack are the same as for a Version 6.1 application server installation. However, you need to ensure that you have enough free disk space to install the feature pack and the included maintenance onto the application server installation.
    • 1450 MB of free space available in your target installation directory for the feature pack and included maintenance. This is in addition to the required Version 6.1 application server product.
    • 600 MB of free space available in your temporary directory
Avoid trouble Avoid trouble: If you are planning to install multiple feature packs on the application server product, then there might be other steps to consider based on your topology. See Installing and configuring multiple feature packs for more information.gotcha

About this task

This topic describes how to install the Feature Pack for Web Services silently using a response file.

The installation program installs the following program files if they are not already installed:

Consider your current product topography before installing the feature pack because it installs maintenance packages that may affect the version of your application server product. If the application server is already at or above the levels of maintenance included with the feature pack, then the installation of these maintenance packages is skipped. If the application server is at a higher level than what the feature pack requires, then the feature pack installer will prompt you to upgrade the feature pack to the same version as the application server.

Procedure

  1. Log on as the user who installed the Version 6.1 WebSphere Application Server product.
    • [AIX] [HP-UX] [Linux] [Solaris] Log on using the same user ID that was used when the product was installed.

      Run the ls -al command at the root of the WebSphere Application Server installation to find the user ID that was used to install the product.

    • [Windows] Log on as a user who belongs to the administrator group or as the user who installed the product.
  2. Extract the downloaded product files. The WEBSV directory is the main directory of the Feature Pack for Web Services installation image. Save a backup copy of the response file responsefile.WEBSV.txt somewhere on your system.
  3. Edit responsefile.WEBSV.txt and customize it for your environment.
    Set values for the following options:
    Option Description
    -OPT silentInstallLicenseAcceptance="true"

    Accept the enclosed license agreement.

    -OPT disableNonBlockingPrereqChecking="true"

    This will notify the installer to continue with the installation and log the warnings even though the prerequisite checking has failed. This will also allow the installation to proceed if you are below the required level of maintenance. The feature pack installer will install the included maintenance packages.

    -OPT installLocation=app_server_root

    Set app_server_root to the root directory of your application server product.

    -OPT allowNonRootSilentInstall="true"

    You must uncomment this line if you are installing the product with a non-root or non-administrator ID.

    To override any option in the response file with command-line options, include the following option in the response file:

    -OPT overrideResponsefileOptions=true
  4. Optional:

    You can set values to create new application server and deployment manager profiles which are already augmented with the feature pack, or you can augment existing deployment manager profiles. You can also choose to create and augment profiles after installation. See "What to do next" on this page for more information. Change the following values in the response file to work with profiles during installation:

    Restriction: For the Feature Pack for Web Services you can only augment an existing deployment manager profile. It is recommended that you create a new deployment manager profile or a new application server profile that is already enabled with the feature pack functionality. Use the profile creation tasks to create these profiles. The deployment manager and application server are the only profile types which can be created with the feature pack functionality.
    • To create a new stand-alone application server or deployment manager profile already augmented with the feature pack:
      1. Uncomment the following line: -OPT createProfile="true"
      2. Uncomment and edit the following line: -OPT profileType="standAlone". You can choose standAlone or deploymentManager
      3. Go to either the stand-alone application server section or the deployment manager section near the bottom of the file and uncomment and edit the values as needed.
    • To augment an existing deployment manager profile, uncomment the following line and edit the values for <profile_name> and <WAS_HOME>:
      -OPT PROF_augment="-profileName <profile_name> -templatePath <WAS_HOME>/profileTemplates/WEBSERVICES/dmgr.wsfep"
      
  5. Stop all processes for the Version 6.1 product on which you are installing the feature pack.

    For example, for the Network Deployment product, stop all application server processes, the node agent, and the deployment manager. The installation will fail if the installer detects running Java processes associated with the target application server directory.

  6. Run the Feature Pack for Web Services installation program using the -silent option.

    At a command prompt for the WEBSV directory, enter the following command:

    install -options responsefile.WEBSV.txt -silent

    The installation program runs silently in the background.

Results

The installation wizard installs the feature pack and records installation events in the installation log files in the app_server_root/logs/install/webservices directory.
Tip: If you are logged in as non-root or non-admin user, you might not always find a log in the application server directory after a failed installation or uninstallation attempt. When the installer runs, a log file is created in your user home directory. If the installation fails, an attempt is made to move the log to the app_server_root directory; however, without the necessary permission to move the file to the app_server_root directory, the attempt to move fails and the log remains in your home directory. Look for the following log files in the user_home/webserviceslogs directory:
  • log.txt
  • trace.txt.gz
  • trace.xml.gz

Troubleshooting

If the installation program is interrupted for any reason while feature pack files are being installed, examine the messages that the installation program displays and the information in the installation logs. Correct the problems identified and try installing the product again. Since the feature pack installation contains the feature pack and various fix packs, an installation failure might occur at different points in the process.

Avoid trouble Avoid trouble: Certain events can prevent ISMP from starting the installation wizard. Such an event is not enough disk space to launch the installation wizard for example. If your installation fails and there is no information in the installation logs, use the -is:javaconsole parameter to record entries for events that cause the ISMP program to fail to start the installation wizard. The syntax of the install command for observing such events is:
[AIX] [HP-UX] [Linux] [Solaris]
./install -is:javaconsole
[Windows]
install.exe -is:javaconsole
Avoid trouble Avoid trouble: Although the usage of -is:javaconsole is supported, the usage of -console, for example install -console, is not supported.gotcha
gotcha

What to do next

Applying Maintenance

Use the Update Installer to install maintenance packages for any of the installable WebSphere software components in the product package. See Applying maintenance for the Feature Pack for Web Services with the Update Installer for more information.

Apply the current feature pack fix pack to Feature Pack for Web Services. You must synchronize the versions of any installed feature pack with the application server. For example, if your application server is at Version 6.1.0.9, then you must upgrade to 6.1.0.13 if you wish to upgrade the feature pack to 6.1.0.13.

If you have already installed Feature Pack for EJB 3.0, then you must apply the PK53084 interim fix before applying any feature pack fix packs to Feature Pack for Web Services, unless you originally installed Feature Pack for Web Services using a CIP created with the Installation Factory. See Installing and configuring multiple feature packs for more information.

Profiles

In order to use the feature pack functionality, you must first create a new profile enabled with the feature pack, or augment an existing deployment manager profile using the Profile Management tool.

For the Feature Pack for Web Services you can only augment an existing deployment manager profile. It is recommended that you create a new deployment manager profile or a new application server profile that is already enabled with the feature pack functionality. Use the profile creation tasks to create these profiles. The deployment manager and application server are the only profile types which can be created with the feature pack functionality. See Augmentation rules and limitations for feature packs on non-z/OS operating systems for more information.

Samples

The Feature Pack for Web Services provides several sample applications that you can install onto an application server profile that has been created with the feature pack functionality. See Installing Web Services Samples with the console.




In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 1:23:07 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-dist&topic=tins_runSilent_wbs
File name: tins_runSilent_wbs.html