[AIX HP-UX Linux Solaris Windows]

Installing the Feature Pack for Web 2.0 and Mobile on distributed operating systems silently

You can use Installation Manager to install the Feature Pack for Web 2.0 and Mobile silently.

Before you begin

On each of the systems onto which you want to install the Feature Pack for Web 2.0 and Mobile, perform the following actions:
  1. Install IBM® WebSphere® Application Server Version 8.0.
  2. Use Installation Manager to connect to a repository containing up-to-date product files and update the product.
  3. Use Installation Manager to connect to a repository containing up-to-date Installation Manager files and update Installation Manager.
  4. Obtain the necessary feature-pack files from the web.
    There are three basic options for installing the feature pack.
    • Access the live repositories, and use web-based installation.
      You can use Installation Manager on your local system to install the feature pack from the web-based repository located at the following location:
      http://www.ibm.com/software/repositorymanager/com.ibm.websphere.WEB2MOBILE.v11
      Tip: These live repositories are accessed by using your IBM authentication. For information about registering for an IBM password, read Registration Help and FAQ.
    • Download files from the Feature Pack for Web 2.0 and Mobile website, and use local installation.

      You can download the compressed file containing the feature-pack repositories from the Feature Pack for Web 2.0 and Mobile website. You can then use Installation Manager to install the feature pack from the unpacked local feature-pack repositories.

    • Licensed customers can download files from the Passport Advantage website and use local installation.

      You can then use Installation Manager to install the feature pack from the unpacked local feature-pack repositories.

    Notes:
    • Whenever possible, you should use the remote web-based repositories so that you are accessing the most up-to-date feature-pack installation files.
    • If you use local repositories, you can leave in the remote repositories as well because they will provide post-shipment service updates when you are connected to the web.
  5. Add the feature-pack repository to your Installation Manager preferences.
    1. Start Installation Manager.
    2. In the top menu, click File > Preferences.
    3. Select Repositories.
    4. Perform the following actions:
      1. Click Add Repository.
      2. Enter the path to the repository.config file in the location containing the repository files.
        For example:
        • [Windows] C:\repositories\featurepack_name\local-repositories
        • [AIX] [HP-UX] [Linux] [Solaris] /var/repositories/featurepack_name/local-repositories
        or
        http://www.ibm.com/software/repositorymanager/com.ibm.websphere.WEB2MOBILE.v11
      3. Click OK.
    5. Clear the checkmarks from any locations listed in the Repositories window that you will not be using.
    6. Click Apply.
    7. Click OK.
    8. Click File > Exit to close Installation Manager.

About this task

Using Installation Manager, you can work with response files to install the Feature Pack for Web 2.0 and Mobile silently in a variety of ways. You can record a response file using the GUI as described in the following procedure, or you can generate a new response file by hand or by taking an example and modifying it.

Procedure

  1. Stop all servers on the WebSphere Application Server installations that are being upgraded.
  2. Optional: Record a response file to install the Feature Pack for Web 2.0 and Mobile.

    On one of your systems, perform the following actions to record a response file that will install the Feature Pack for Web 2.0 and Mobile.

    1. From a command line, change to the eclipse subdirectory in the directory where you installed Installation Manager.
    2. Start Installation Manager from the command line using the -record option.
      For example:
      • [Windows] Administrator or non-administrator:
        IBMIM.exe -skipInstall "C:\temp\imRegistry" 
          -record C:\temp\install_response_file.xml
      • [AIX] [HP-UX] [Linux] [Solaris] Administrator:
        ./IBMIM -skipInstall /var/temp/imRegistry 
          -record /var/temp/install_response_file.xml
      • [AIX] [HP-UX] [Linux] [Solaris] Non-administrator:
        ./IBMIM -skipInstall user_home/var/temp/imRegistry 
          -record user_home/var/temp/install_response_file.xml
      Tip: When you record a new response file, you can specify the -skipInstall parameter. Using this parameter has the following benefits:
      • No files are actually installed, and this speeds up the recording.
      • If you use a temporary data location with the -skipInstall parameter, Installation Manager writes the installation registry to the specified data location while recording the response file. When you start Installation Manager again without the -skipInstall parameter, you then can use your response file to install against the real installation registry.

        The -skipInstall operation should not be used on the actual agent data location used by Installation Manager This is unsupported. Use a clean writable location, and re-use that location for future recording sessions.

      For more information, read the IBM Installation Manager Information Center.

    3. Add the appropriate repositories to your Installation Manager preferences.
      1. In the top menu, click File > Preferences.
      2. Select Repositories.
      3. Perform the following actions for each repository:
        1. Click Add Repository.
        2. Enter the path to the repository.config file in the location containing the repository files.
          For example:
          • [Windows] C:\repositories\featurepack_name\local-repositories
          • [AIX] [HP-UX] [Linux] [Solaris] /var/repositories/featurepack_name/local-repositories
          or
          http://www.ibm.com/software/repositorymanager/com.ibm.websphere.WEB2MOBILE.v11
        3. Click OK.
      4. Click Apply.
      5. Click OK.
    4. Click Install.
    5. In the Install Packages window, perform the appropriate actions.
      1. Select IBM WebSphere Application Server Feature Pack for Web 2.0 and Mobile and the appropriate version.

        If you already have the Feature Pack for Web 2.0 and Mobile function installed on a WebSphere Application Server installation on your system, a message displays indicating that the Feature Pack for Web 2.0 and Mobile is already installed. To install the Feature Pack for Web 2.0 and Mobile function on a WebSphere Application Server installation where it is not yet installed, click Continue.

      2. Click Next.
    6. Accept the terms in the license agreements, and click Next.
    7. Select the appropriate WebSphere Application Server installation, and click Next.
    8. Review the feature-selection panel, and click Next.
    9. Review the summary information, and click Install.
    10. Click Finish.
    11. Click File > Exit to close Installation Manager.
    12. Optional: If you are using an authenticated remote repository, create a keyring file for silent installation.
      Note: In a keyring file, you can store credentials for URLs that require authentication, such as your remote repositories.
      1. From a command line, change to the eclipse subdirectory in the directory where you installed Installation Manager.
      2. Start Installation Manager from the command line using the -record option.
        For example:
        • [Windows] Administrator or non-administrator:
          IBMIM.exe -skipInstall "C:\temp\imRegistry" 
            -keyring C:\IM\im.keyring 
            -record C:\temp\keyring_response_file.xml
        • [AIX] [HP-UX] [Linux] [Solaris] Administrator:
          ./IBMIM -skipInstall /var/temp/imRegistry 
            -keyring /var/IM/im.keyring 
            -record /var/temp/keyring_response_file.xml
        • [AIX] [HP-UX] [Linux] [Solaris] Non-administrator:
          ./IBMIM -skipInstall user_home/var/temp/imRegistry 
            -keyring user_home/var/IM/im.keyring 
            -record user_home/var/temp/keyring_response_file.xml
      3. When a window opens that requests your credentials for the authenticated remote repository, enter the correct credentials and save them.
      4. Click File > Exit to close Installation Manager.
  3. Use the response files that you created to install the Feature Pack for Web 2.0 and Mobile silently.
    1. Optional: Use the response file to install the keyring file silently.
      Go to a command line on each of the systems on which you want to install the feature pack, change to the eclipse/tools subdirectory in the directory where you installed Installation Manager, and install the keyring file silently. For example:
      • [Windows] Administrator or non-administrator:
        imcl.exe -acceptLicense 
          input C:\temp\keyring_response_file.xml 
          -log C:\temp\keyring_log.xml
      • [AIX] [HP-UX] [Linux] [Solaris] Administrator:
        ./imcl -acceptLicense 
          input /var/temp/keyring_response_file.xml 
          -log /var/temp/keyring_log.xml
      • [AIX] [HP-UX] [Linux] [Solaris] Non-administrator:
        ./imcl -acceptLicense 
          input user_home/var/temp/keyring_response_file.xml 
          -log user_home/var/temp/keyring_log.xml

      For more information on keyring files, read the IBM Installation Manager Information Center.

    2. Use the response file to install the feature pack silently.
      Go to a command line on each of the systems on which you want to install the feature pack, change to the eclipse/tools subdirectory in the directory where you installed Installation Manager, and install the feature pack silently. For example:
      • [Windows] Administrator or non-administrator:
        imcl.exe -acceptLicense 
          input C:\temp\install_response_file.xml 
          -log C:\temp\install_log.xml 
          -keyring C:\IM\im.keyring
      • [AIX] [HP-UX] [Linux] [Solaris] Administrator:
        ./imcl -acceptLicense 
          input /var/temp/install_response_file.xml 
          -log /var/temp/install_log.xml 
          -keyring /var/IM/im.keyring
      • [AIX] [HP-UX] [Linux] [Solaris] Non-administrator:
        ./imcl -acceptLicense 
          input user_home/var/temp/install_response_file.xml 
          -log user_home/var/temp/install_log.xml 
          -keyring user_home/var/IM/im.keyring
      Notes:
      • The relevant terms and conditions, notices, and other information are provided in the license-agreement files in the lafiles or product_name/lafiles subdirectory of the installation image or repository for this product.
      • The program might write important post-installation instructions to standard output.

      Read the IBM Installation Manager Information Center for more information.

Example [Windows]

The following is an example of a response file for silently installing the Feature Pack for Web 2.0 and Mobile.
<?xml version="1.0" encoding="UTF-8"?>
<!-- ##### Copyright ######################################################
# Licensed Materials - Property of IBM (c) Copyright IBM Corp. 2011. 
# All Rights Reserved. US Government Users Restricted Rights-Use, duplication 
# or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
####################################################################### -->

<!-- ##### Agent Input ##############################################
#
# Note that the "acceptLicense" attribute has been deprecated. 
# Use "-acceptLicense" command line option to accept license agreements.
#
# The clean and temporary attributes specify the repositories and other
# preferences Installation Manager uses and whether those settings
# should persist after the installation finishes.
# 
# Valid values for clean:
#      true = only use the repositories and other preferences that are 
#           specified in the response file.
#      false = use the repositories and other preferences that are 
#           specified in the response file and Installation Manager.
# 
# Valid values for temporary:
#      true = repositories and other preferences specified in the 
#           response file do not persist in Installation Manager.
#      false = repositories and other preferences specified in the 
#           response file persist in Installation Manager.
# 
####################################################################### -->

<agent-input clean="true" temporary="true">
<server>
<!-- ##### Repositories ###################################################
# Repositories are locations that Installation Manager queries for 
# installable packages. Repositories can be local (on the machine
# with Installation Manager) or remote (on a corporate intranet or 
# hosted elsewhere on the internet). 
# 
# If the machine using this response file has access to the internet, 
# then include the IBM WebSphere Live Update Repositories in the list 
# of repository locations. 
# 
# If the machine using this response file cannot access the internet, 
# then comment out the IBM WebSphere Live Update Repositories and 
# specify the URL or UNC path to custom intranet repositories and 
# directory paths to local repositories to use.

 ##### IBM WebSphere Live Update Repositories ####################
     # These repositories contain WebSphere Application Server offerings, 
     # and updates for those offerings

####################################################################### -->

<repository location='http://www.ibm.com/software/repositorymanager/com.ibm.websphere.WEB2MOBILE.v11'/>

<!-- ##### Local Repositories ########################################
     # Uncomment and update the following line when using a local
     # repository located on your own machine to install a 
     # WebSphere Application Server offering.
     ############################################################# -->
    <!--<repository location='/home/padmashr/Padma/localRepo'/> -->

</server>

<!-- ##### Install Packages ##########################################
#
# Install Command
#
# Use the install command to inform Installation Manager of the 
# installation packages to install. 
# 
# The modify attribute is optional and can be paired with an install 
# command to add features or paired with an uninstall command to 
# remove commands. If omitted, the default value is set to false.
#    false = indicates not to modify an existing installation by adding 
#            or removing features.
#    true = indicates to modify an existing installation by adding or 
#           removing features.
# 
# The offering ID attribute is required because it specifies the 
# offering to be installed. The offering listed must be present in 
# at least one of the repositories listed earlier. The example 
# command below contains the offering ID for the Base edition of 
# WebSphere Application Server. 
# 
# The version attribute is optional. If a version number is provided, 
# then the offering will be installed at the version level specified 
# as long as it is available in the repositories. If the version 
# attribute is not provided, then the default behavior is to install 
# the latest version available in the repositories. The version number 
# can be found in the repository.xml file in the repositories.
# For example, <offering ... version='8.0.0.20110617_2222'>.
# 
# The profile attribute is required and typically is unique to the
# offering. If modifying or updating an existing installation, the 
# profile attribute must match the profile ID of the targeted installation 
# of WebSphere Application Server.
# 
# The features attribute is optional. Offerings always have at least
# one feature; a required core feature which is installed regardless 
# of whether it is explicitly specified. If other feature names 
# are provided, then only those features will be installed. 
# Features must be comma delimited without spaces.
#
####################################################################### -->

<install modify='false'>
<offering id='com.ibm.websphere.WEB2MOBILE.v11' version='1.1.0.20110427_2247' profile='IBM WebSphere Application Server V8.0' features='main' installFixes='none'/>
</install>
<!--
# Profile Command
# 
# A separate profile command must be included for each offering listed 
# in the install command. The profile command informs Installation
# Manager about offering specific properties or configuration values.
# 
# The installLocation specifies where the offering will be installed.
# If the response file is used to modify or update an existing 
# installation, then ensure the installLocation points to the 
# location where the offering was installed previously. 
# 
# The eclipseLocation data key should use the same directory path to 
# WebSphere Application Server as the installationLocation attribute.
# 
# Include data keys for product specific profile properties. 
# For instance, additional translations can be specified by including
# the cic.selector.nl data key and the language codes as values for
# the translations to install.
# 
#  Language code values: cs,de,en,es,fr,hu,it,ja,ko,pl,pt_BR,ro,ru,zh,zh_HK,zh_TW
# -->

<profile id='IBM WebSphere Application Server V8.0' installLocation='C:\Program Files\IBM\WebSphere\AppServer'>
<data key='eclipseLocation' value='C:\Program Files\IBM\WebSphere\AppServer'/>
<data key='user.import.profile' value='false'/>
<data key='cic.selector.nl' value='en'/>
</profile>

<!-- ##### Preferences Settings ###########################################
# Additional preferences for Installation Manager can be specified. 
# These preference correspond to those that are located in the graphical
# interface under File / Preferences. 
# 
# If a preference command is omitted from or commented out of the response 
# file, then Installation Manager uses the preference value that was 
# previously set or the default value for the preference. 
# 
# Preference settings might be added or deprecated in new versions of
# Installation Manager. Consult the online Installation Manager
# Information Center for the latest set of preferences and 
# descriptions about how to use them.
#
# http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp
# 
####################################################################### -->

<!--
<preference name='com.ibm.cic.common.core.preferences.eclipseCache' value='C:\Program Files\IBM\SDP70Shared'/>
<preference name='com.ibm.cic.common.core.preferences.connectTimeout' value='30'/>
<preference name='com.ibm.cic.common.core.preferences.readTimeout' value='45'/>
<preference name='com.ibm.cic.common.core.preferences.downloadAutoRetryCount' value='0'/>
<preference name='offering.service.repositories.areUsed' value='true'/>
<preference name='com.ibm.cic.common.core.preferences.ssl.nonsecureMode' value='false'/>
<preference name='com.ibm.cic.common.core.preferences.http.disablePreemptiveAuthentication' value='false'/>
<preference name='http.ntlm.auth.kind' value='NTLM'/>
<preference name='http.ntlm.auth.enableIntegrated.win32' value='true'/>
<preference name='com.ibm.cic.common.core.preferences.preserveDownloadedArtifacts' value='true'/>
<preference name='com.ibm.cic.common.core.preferences.keepFetchedFiles' value='false'/>
<preference name='PassportAdvantageIsEnabled' value='false'/>
<preference name='com.ibm.cic.common.core.preferences.searchForUpdates' value='false'/>
<preference name='com.ibm.cic.common.core.preferences.import.enabled' value='true'/>
<preference name='com.ibm.cic.agent.ui.displayInternalVersion' value='false'/>
-->
</agent-input>

What to do next

You can begin using the feature pack by working with the various included features and applications.




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 product documentation | Feedback

Last updatedLast updated: Apr 22, 2018 11:06:25 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v800webmob&product=was-nd-mp&topic=tweb_ins_install_dist_silent
File name: tweb_ins_install_dist_silent.html