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.

[Updated in March 2013] 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. Before using the installation manager, refer to the Installation Manager Information Center for a description of the various Installation Manager options you can specify when you install the Installation Manager. [Updated in March 2013]

mar2013

[Updated in March 2013] When using the Installation Manager, you should understand the following directory terminology:
Agent Data Location
The Agent Data Location directory contains the metadata that tracks the history and state of all product installations that the Installation Manager is managing. This directory is created when Installation Manager is itself installed.

The Agent Data Location directory, which is sometimes referred to as the appDataLocation, is critical to the healthy functioning of the Installation Manager. After the directory is created, it cannot be moved. If the Agent Data Location directory becomes corrupt, all product installations that are tracked by the metadata in the Agent Data Location directory become unserviceable and need to be reinstalled if service is needed.

See the Installation Manager information center for the default location of the Agent Data Location directory. To override the default location specify the –dataLocation (or –dL) command line option when installing the Installation Manager, and then use the –dataLocation (or –dL) command line option to specify a different location.

Shared Resources Directory
The Shared Resources Directory is used for two purposes:
  • It might be used to contain resources that can be shared by installed products at run time. WebSphere Application Server products do not have run time dependencies on the contents of this folder.
  • It might be used at installation time to stage the payload before it is installed into its target folder. In this scenario, filesum checks are performed on the transferred data to ensure that it is intact. By default, this content remains cached in the Shared Resources Directory after installation so that it can be used for future updates or rollback.

The location of the Shared Resources Directory is set when the first product is installed. Each product repository specifies a default location. Therefore, if this location is not overridden, then the first installed product determines the location.

The -sharedResourcesDirectory command line option can be used the first time the Installation Manager installs a product to specify the location of this directory. The location of the Shared Resources Directory cannot be changed after it is initially set.

Because product payloads are cached in this directory, space requirements can grow very large over the lifetime of the product, as service updates are applied. The WebSphere Application Server product image is large, so if this content is permitted to accumulate, then this directory will grow to be many gigabytes in size over the course of multiple fix pack applications. You should never manually delete the content in this folder. Instead, during any installation or maintenance operation, you can specify the following preference to remove some of the content in this folder:
–preferences com.ibm.cic.common.core.preferences.preserveDownloadedArtifacts=false

When this preference is set to false, all data that is no longer needed is removed after the operation completes. You must still ensure you have enough space to stage the payload during the installation and maintenance operations, but data no longer accumulates over time. If you have previously not used this preference, all old payloads are removed the first time you use this preference. You can also specify this preference by selecting the Delete Saved Files option on the Preferences panel in the Installation Manager GUI. You can also use this panel to indicate that download artifacts are not to be preserved.

[Updated in March 2013]
mar2013
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.
Tip: You can import an existing WebSphere Application Server Version 7.0.0.x installation that contains Version 1.0 of the Feature Pack for SCA if no fixes have been applied to the 1.0 level using the Update Installer; then, you can use Installation Manager to update it to Version 1.0.1 or later. Read Installing the feature pack on distributed operating systems using the GUI and Updating the feature pack on distributed operating systems for more information.
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
  • Do not install a generally available (GA) version of the feature pack on an existing WebSphere Application Server Version 7.0 installation where the Beta version of the feature pack was installed.
  • Do not use a version of Installation Manager that was obtained with a Beta version of a feature pack to install, maintain, or uninstall a generally available (GA) version of the feature pack.
  • [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.
  • If you attempt to install a level of the Feature Pack for Service Component Architecture (SCA) that is less than Version 1.0.1.5 on an installation that already contains the Feature Pack for OSGi Applications and Java Persistence API 2.0, Installation Manager blocks the installation. The Feature Pack for OSGi Applications and Java Persistence API 2.0 requires that any installation of the Feature Pack for SCA be at a minimum service level (MSL) of Version 1.0.1.5.
  • The Feature Pack for OSGi Applications and Java Persistence API 2.0 Version 1.0.0.0 requires that an installation that also contains the Feature Pack for SCA must have Version of 1.0.1.5 or higher of the Feature Pack for SCA. In the following scenarios, however, Installation Manager does not prevent you from having the Feature Pack for OSGi Applications and Java Persistence API 2.0 Version 1.0.0.0 and a version of the Feature Pack for SCA that is lower than 1.0.1.3 on your system.
    • If you select the Feature Pack for OSGi Applications and Java Persistence API 2.0 Version 1.0.0.0 and a version of the Feature Pack for SCA that is lower than 1.0.1.3 for concurrent installation, you will not be blocked.
      Solution: To resolve this problem, perform one of the following actions:
      • Install the Feature Pack for SCA Version 1.0.1.5 and the Feature Pack for OSGi Applications and Java Persistence API 2.0 Version 1.0.0.0 in separate installation sessions.
      • Install the Feature Pack for OSGi Applications and Java Persistence API 2.0 Version 1.0.0.0 and the Feature Pack for SCA Version 1.0.1.5 concurrently.
    • If you install the Feature Pack for OSGi Applications and Java Persistence API 2.0 Version 1.0.0.0 and you then try to install a version of the Feature Pack for SCA that is lower than 1.0.1.3, you will not be blocked.
      Solution: To resolve this problem, perform one of the following actions:
      • Install the Feature Pack for SCA Version 1.0.1.5 and the Feature Pack for OSGi Applications and Java Persistence API 2.0 Version 1.0.0.0 in separate installation sessions.
      • Install the Feature Pack for OSGi Applications and Java Persistence API 2.0 Version 1.0.0.0 and the Feature Pack for SCA Version 1.0.1.5 concurrently.
    • If you have the Feature Pack for OSGi Applications and Java Persistence API 2.0 Version 1.0.0.0 as well as any version of the Feature Pack for SCA installed and you then roll back the Feature Pack for SCA to a version that is lower than 1.0.1.3, you will not be blocked.
      Solution: Do not roll back the Feature Pack for SCA to a version that is less than 1.0.1.5 when the Feature Pack for OSGi Applications and Java Persistence API 2.0 Version 1.0.0.0 is present on the system.
  • [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 Version 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 Version 1.3.x installation image to the system. Also, you must identify the Java shared libraries in the Installation Manager Version 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
  • Installation Manager console mode, which is included in Installation Manager Version 1.4.3 and later, does not work with WebSphere Application Server Version 7.0 offerings.
  • You can use 64-bit Installation Manager Version 1.6 for the following installations only:
    • WebSphere Application Server Version 7.0.0.25 and later
    • WebSphere Application Server CEA Feature Pack 1.0.0.13 and later
    Using 64-bit Installation Manager Version 1.6 for anything else can result in issues with installation and deployment
  • [Windows] You can use 64-bit Installation Manager Version 1.6.2 or later to install this offering on Windows systems.

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.

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.



In this information ...


Related 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: Jun 11, 2013 11:43:36 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v701sca&product=was-nd-mp&topic=tins_installfp_dist
File name: tins_installfp_dist.html