[AIX HP-UX Linux Solaris Windows]

Installing and uninstalling the feature pack on distributed operating systems

IBM® Installation Manager is a common installer for many IBM software products that you use to install this WebSphere® Application Server feature pack.

Before you begin

This feature pack is one of the first WebSphere Application Server products to be installed by Installation Manager rather than by the programs based on InstallShield MultiPlatform (ISMP) that are used to install, update, and uninstall previous versions of WebSphere Application Server.

Installation Manager is a single installation program that can use remote or local software repositories to install, modify, or update new WebSphere Application Server products. It determines and shows available packages—including products, fix packs, interim fixes, and so on—checks prerequisites and interdependencies, and installs the selected packages. You also use Installation Manager to easily uninstall the packages that it installed.

Table 1. Installing a feature pack on a system that has WebSphere Application Server Version 7.0.0.x installed.

The following scenario is currently supported by the new Installation Manager solution.

Earlier ISMP-Based Installation Solution New Installation Manager Solution
  1. Locate and download earlier WebSphere Application Server feature-pack installation packages.
  2. Install each WebSphere Application Server feature pack separately.

    During installation, you often can select a known existing installation or browse to a different existing installation.

    Note: The required WebSphere Application Server fix pack is bundled within the feature pack even if the fix pack has already been applied to the existing WebSphere Application Server installation.
  1. Install Installation Manager.
  2. Start Installation Manager, and configure connections to remote or local product and service repositories.
  3. Browse to and import the WebSphere Application Server installation into Installation Manager.
  4. Select and install the new feature packs.
Restrictions:
  • Because of a change in the installation technology for the Version 7.0 feature packs, the following tools are not supported for installing this feature pack:
    • Centralized installation manager (CIM)
    • Installation Factory
  • [Linux] [Fix Pack 9 or later] On the Asianux Server 3 operating system, use IBM Installation Manager for WebSphere Version 1.3.4 or later to install feature packs for WebSphere Application Server Version 7.0.
  • [Fix Pack 11 or later] You must use IBM Installation Manager Version 1.4.0 or later to install, modify, or uninstall a feature pack on WebSphere Application Server Version 7.0 Fix Pack 11 or later. For more information, see the support documentation for IBM Installation Manager.
  • [HP-UX] [Solaris] The Installation Manager GUI is not supported on HP-UX PA-RISC and Solaris 10 x64 systems. Perform the following actions to install, import, or uninstall the feature pack on these systems:
    • Use the Installation Manager GUI on a supported system to record a response file that will allow you to install, import, or uninstall the WebSphere Application Server Version 7.0 feature pack silently.
    • Edit the recorded response file if necessary.
    • Use the response file to install, import, or uninstall the WebSphere Application Server Version 7.0 feature pack silently on your system.
  • [Linux] On SUSE Linux® Enterprise Server 9.4 with Graphical User Interface Toolkit (GTK) Version 2.2.4, Installation Manager displays an extra window for the available-space information in the Location panel of the Installation wizard; if you close the extra window, the JVM terminates. There is also an extra Dependencies window in the Feature panel of the Modify Packages wizard; if you close the extra window, the JVM terminates.
    To resolve this problem, perform one of the following actions:
    • Upgrade to GTK Version 2.4.13 or above.
    • Do not close the Available Space window or Dependencies window when it appears, and continue with the Installation or Modify Packages wizard.
  • [Linux] For any Linux system that is enabled for Security Enhanced Linux (SELinux), such as Red Hat Enterprise Linux Version 5 or SUSE Linux Enterprise Server Version 11, you must identify the Java shared libraries in the Installation Manager 1.3.x installation image to the system. Also, you must identify the Java shared libraries in the Installation Manager 1.3.x installation after it has been installed. For example:
    chcon -R -t texrel_shlib_t  ${IM_Image}/jre_5.0.3.sr8a_20080811b/jre/bin
    chcon -R -t texrel_shlib_t  ${IM_Install_root}/eclipse/jre_5.0.3.sr8a_20080811b/jre/bin

About this task

Perform one of these procedures to install or uninstall the feature pack using Installation Manager.

Procedure

Results

Notes on logging and tracing:
  • An easy way to view the logs for Installation Manager is to open Installation Manager and go to File > View Log. An individual log file can be opened by selecting it in the table and then clicking the Open log file icon.
  • Logs for Installation Manager are located in the logs directory of Installation Manager's application data location. For example:
    • [Windows] Administrative installation:
      C:\Documents and Settings\All Users\Application Data\IBM\Installation Manager\logs
    • [Windows] Non-administrative installation:
      C:\Documents and Settings\user_name\Application Data\IBM\Installation Manager\logs
    • [AIX] [HP-UX] [Linux] [Solaris] Administrative installation:
      /var/ibm/InstallationManager/logs
    • [AIX] [HP-UX] [Linux] [Solaris] Non-administrative installation:
      user_home/var/ibm/InstallationManager/logs
  • The main log files for Installation Manager are time-stamped XML files in the logs directory, and they can be viewed using any standard Web browser.
  • The Installation Manager log.properties file in the logs directory specifies the level of logging or tracing that Installation Manager uses. To turn on tracing for the WebSphere Application Server plug-ins, for example, create a log.properties file with the following content:
    com.ibm.ws=DEBUG
    PakInstallOperation=DEBUG
    com.ibm.cic.agent.core.Engine=DEBUG
    global=DEBUG
    Restart Installation Manager as necessary, and Installation Manager outputs traces for the WebSphere Application Server plug-ins.
Notes on troubleshooting:
  • [HP-UX] By default, some HP-UX systems are configured to not use DNS to resolve host names. This could result in Installation Manager not being able to connect to an external repository.

    You can ping the repository, but nslookup does not return anything.

    Work with your system administrator to configure your machine to use DNS, or use the IP address of the repository.

    .
  • If you use Installation Manager to modify features for an imported WebSphere Application Server Version 7.0. installation, you might see errors in the logs that are similar to the following:
    164	INFO	00:24.86	Elapsed time 00:00.09 for: Preparing com.ibm.websphere.ND.v70 7.0.3.20090609_0545.
    165	ERROR	00:26.02	Installation Manager cannot remove feature import.configLauncher.feature from 
      an installation package that was imported to Installation Manager. 
    166	ERROR	00:26.02	Installation Manager cannot remove feature import.productProviders.feature from 
      an installation package that was imported to Installation Manager. 
    167	INFO	00:26.05	com.ibm.ws.detect.edition.DetectNDEditionSelector - evaluate() 
    

    You will get these errors as soon as you open the Modify Packages panel. You do not have to select anything for the errors to show up in the log.

    These errors can be safely ignored.

  • In some cases, you might need to bypass existing checking mechanisms in Installation Manager.
    • On some network file systems, disk space might not be reported correctly at times; and you might need to bypass disk-space checking and proceed with your installation.
      To disable disk-space checking, specify the following system property in the config.ini file in IM_install_root/eclipse/configuration and restart Installation Manager:
      cic.override.disk.space=sizeunit  
      where size is a positive integer and unit is blank for bytes, k for kilo, m for megabytes, or g for gigabytes. For example:
      cic.override.disk.space=120 (120 bytes)
      cic.override.disk.space=130k (130 kilobytes)
      cic.override.disk.space=140m (140 megabytes)
      cic.override.disk.space=150g (150 gigabytes)
      cic.override.disk.space=true
      Installation Manager will report a disk-space size of Long.MAX_VALUE. Instead of displaying a very large amount of available disk space, N/A is displayed.
    • To bypass operating-system prerequisite checking, add disableOSPrereqChecking=true to the config.ini file in IM_install_root/eclipse/configuration and restart Installation Manager.
    • If you cannot access the importation repositories or the repositories that were used to install the products, you can bypass resynchronization checking. You can bypass resynchronization checking by adding cic.disable.resync.check=true to the config.ini file in IM_install_root/eclipse/configuration and restarting Installation Manager.
      Important: You should bypass resynchronization checking only if you are very sure that the installed WebSphere Application Server products are in sync—that is, they are the same versions that are reported in Installation Manager.
    If you need to use any of these bypass methods, contact IBM Support for assistance in developing a solution that does not involve bypassing the Installation Manager checking mechanisms.
  • Installation Manager might display a warning message during the feature-pack uninstallation process.
    When you uninstall an IBM WebSphere Application Server Version 7.0 feature pack using IBM Installation Manager, the following message is displayed when data repositories are undefined, lost, nonexistent, or not valid:
    Installation Manager is unable to connect to a repository that contains data to 
    perform synchronization checking. You must configure repository connections and ensure 
    that you can access the network or repository media to keep imported packages synchronized.

    Uninstalling an IBM WebSphere Application Server Version 7.0 feature pack using Installation Manager requires that the data repositories remain valid and available. This requirement ensures that the imported WebSphere Application Server base package remains synchronized with Installation Manager during the uninstallation process for the feature pack.

    A warning message is displayed by Installation Manager to alert you when repositories are not available or connected. A similar warning message might display after you add or modify data repository connection preferences in Installation Manager.

    If Installation Manager detects missing data repositories or fails to connect to repositories during the uninstallation process for a feature pack, complete the following actions:
    1. Click Cancel to end the uninstallation task.
    2. Select File > Preferences > Repositories, and add the appropriate data repositories that you can connect to successfully.
    3. Exit Installation Manager.
    4. Restart Installation Manager.
    5. Uninstall the feature pack.
  • For more information on using Installation Manager, read the IBM Installation Manager Information Center.
    Read the release notes to learn more about the latest version of Installation Manager. To access the release notes, complete the following task:
    • [Windows] Click Start > Programs > IBM Installation Manager > Release Notes.
    • [AIX] [HP-UX] [Linux] [Solaris] Go to the documentation subdirectory in the directory where Installation Manager is installed, and open the readme.html file.

What to do next

When you have finished the installation, you can create a WebSphere Application Server runtime environment that includes the feature pack's functions. To use the feature-pack functionality, you must create a new profile with the feature-pack functionality or augment an existing profile with the feature pack.

For more information, read Augmentation rules and limitations for feature packs on non-z/OS operating systems, Augmenting profiles using the graphical user interface, and Augmenting a profile using the command prompt.

Notes on maintenance:
  • The Installation Manager should be used only for the following tasks:
    • Import an existing WebSphere Application Server Version 7.0 installation
    • Install the feature pack.
    • Modify, update, or roll back the feature-pack installation.
    • Uninstall the feature pack.
    • Uninstall WebSphere Application Server.

    Use the existing Update Installer for WebSphere Application Server Version 7.0 base-product maintenance tasks.

  • The WebSphere Application Server and IBM SDK levels must be the same in order for a WebSphere Application Server Version 7.0 installation to be imported into Installation Manager.
  • After you use the Update Installer to apply maintenance to the base WebSphere Application Server product or the IBM SDK, you must re-import the WebSphere Application Server Version 7.0 installation into Installation Manager.



Subtopics
Installing the feature pack on distributed operating systems using the GUI
Installing the feature pack on distributed operating systems silently
Uninstalling the feature pack from distributed operating systems using the GUI
Uninstalling the feature pack from distributed operating systems silently
Updating the feature pack on distributed operating systems
Rolling back the feature pack on distributed operating systems
Related information
IBM Installation Manager
Task topic    

Terms of Use | Feedback

Last updated: Oct 21, 2010 12:58:21 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v700cea&product=was-nd-mp&topic=tins_installfp_dist
File name: tins_installfp_dist.html