WAS v8.0 > Install the application serving environment > Distributed operating systems > Centralized installation manager (CIM) > Use the centralized installation manager (CIM) to manage v6.1.x and 7.x > Install packages using the centralized installation manager (CIM) for previous versions

Install v6.1.x and 7.x interim fixes using the centralized installation manager (CIM)

Install selected interim fixes to specific installation targets using the centralized installation manager (CIM) to update your product environment.

New feature: Supported configurations: This topic applies to WAS v6.1.x and 7.x only. For information about using centralized installation manager (CIM) for v8.0, see Submit Installation Manager jobs.

We must download the following items to the CIM repository before you can complete this task:

• The binary files for one or more interim fixes

You do not need to install the Update Installer after you have downloaded it. The CIM automatically installs the Update Installer before installing any refresh packs, fix packs or interim fixes if the target does not have the Update Installer already installed.

The descriptors for an interim fix package type are installed when you install WAS Network Deployment v8.0. These specific descriptors are included to apply the following types of updates:

• Maintenance for WAS Network Deployment Version 6.x
• Maintenance for WAS Network Deployment Version 7.x

For details on how to locate the descriptor and associated files, read the "Downloading package descriptors and the associated binary files" topic.

By default, all of the workstations containing nodes that are defined in the cell are displayed as installation targets. We can only install interim fixes on targets that are part of the cell. During the installation process, the wizard prompts you to select an authentication method, either user name and password or SSH public/private key. If you choose to use the SSH public/private key authentication method, first create a pair of keys and install the public key on all the installation targets to successfully complete this task.

Before installing an interim fix to any targets, install the same interim fix to the dmgr first, if the interim fix is applicable to the dmgr node.

For WAS v7.x nodes, CIM can detect what interim fixes have been installed. If you select an interim fix that has been previously installed to a node, that node is not available for selection.

For WAS Version 6.x nodes, you can still select nodes that have the interim fix installed, but you are notified that the interim fix has been previously applied on the Installation history page.

The CIM relies heavily on remote node information maintained locally on the dmgr node. This remote node information (namely the node-metadata.properties file) for each node is refreshed every time the node agent on the remote node starts and provides the centralized installation manager with up-to-date information regarding the WebSphere products and versions that are installed on the target nodes.

One example of how the node-metadata.properties information is being used by the CIM is in the filtering of nodes that might be selected for the installation of an interim fix.

Assume you have downloaded an interim fix for the Feature Pack for Web Services to the CIM repository to be installed on remote node. CIM looks at the information contained within the interim fix and determines that the fix is only applicable for nodes that have the Feature Pack for Web Services v6.1.0.9 or higher installed. CIM then checks the node-metadata.properties of all the nodes within the cell to determine which of the remote nodes meet the requirement for this interim fix. This process allows the cell administrator to see which nodes are potential candidates for this update and then initiate the installation of the interim fix on one or all the candidate nodes. Because of the availability of the node-metadata.properties on the dmgr node, you could use CIM to perform this filtering without accessing the target nodes. The node agent process that runs on each node ensures that the node-metadata.properties files of the nodes on the dmgr are kept up-to-date.

For this reason, if you apply maintenance to the node or install new WebSphere products (such as the Feature Pack for Web Services) outside of CIM on the remote node, restart the node agent process after the installation to get the dmgr copy of the node-metadata.properties of the node up to date.

In addition, for the case of installing a new WebSphere product on the remote 6.1 nodes you must take one of the following two steps:

• If the product you are installing supports profile augmentation, augment an existing profile for an already federated node.

• If the product you are installing does not support augmenting an existing profile or you prefer not to augment an existing profile, then create a new profile using a profile template for the new product (for example, a Feature Pack for Web Services profile) thereby creating a new node. Federate this new node to the current dmgr cell.

After the profile is augmented or a new one is created and federated to the cell, the node agent must be started to make the updated or new node-metadata.properties file that contains the new product information available to the dmgr node. Unless this is done, CIM, running on the dmgr node, has no knowledge of the new product that has been installed on the remote host and cannot perform the filtering correctly.

Complete the following steps to install recommended interim fixes for WebSphere Application Server Network Deployment v6.x or 7.x.

Procedure

1. Access the wizard from the admin console.

   1. Click System administration > Centralized Installation Manager > Available installations.

   2. Select Interim fix as the package type. Next, select one of the following maintenance installation packages.
      • Maintenance for WAS Network Deployment 7.x
      • Maintenance for WAS Network Deployment 6.x

      If you previously downloaded any interim fixes by using the Installation Packages function, the interim fixes are displayed in a list below the Select one or more maintenance packs prompt. Select one or more interim fixes from this list.

   3. Click Show installation targets to populate the table with a list of applicable target workstations on which to install the selected interim fixes. After you select one or more installation targets, click Install to start the Installation wizard.

2. Read and accept the license agreement.

   Click View License Agreement to read the agreement and accept the terms. Click Next to continue.

3. Select an authentication method to access the installation target, and click Next. We can select to either use the SSH public/private key method or the user name and password method to authenticate.
4. Provide your authentication information, and click Next.

   Depending on the authentication method that you choose in the previous step, provide the appropriate user name and password for one or more installation targets, or provide the location of the SSH private key file and password on the dmgr.  

   If you choose to authenticate by using the user name and password method, you can provide a common user name and password to access all of the installation targets, or you can configure unique user names and passwords for each target.

5. Verify the installation and the working locations of each installation target, and click Next.

   The installation location is the remote location of each installation target in which the interim fixes are to be installed. The working location specifies the directory on the remote target where the files are sent before the package is installed in the specified location.

   Make sure we have enough disk space in both the installation location and the working location. The space required in the installation and working location varies by installation packages. The CIM transfers the selected interim fix files and the Update Installer binary file if necessary from the repository to the working location.

6. Read the installation summary, and click Finish to submit the installation request to the CIM for processing.

Results

Your installation request is sent to the CIM for processing. The Update Installer is automatically installed to the selected targets if the Update Installer is not found on the targets.

To check the status of your request, click Installations in progress in the admin console.

Troubleshoot

• The following message is displayed if you attempt to install an interim fix without having a copy of the IBM Update Installer for WebSphere Software in your CIM repository:

  The installation binary files required for the install_package_name or its dependent package
  Update Installer for WAS for workstation_platform do not exist.
  

• If you are trying to use CIM to install an interim fix for the Feature Pack for Web Services on a WAS Version 6.1 or 7.x host in your v8.0 Network Deployment cell, the Show Installation Targets function on the CIM Available installations panel might not list the host as an available installation target. WAS v6.1 or 7.x Feature Pack installations without a profile created for the environment are not visible to CIM as installed products on the target host.

  To make the dmgr and CIM aware that the v6.1 or 7.x feature pack is installed, create a Feature Pack for Web Services profile and federate the defined node to the dmgr.

What to do next

Click Installation history in the admin console to review the log files for each of the installation requests that you submit.

From the Installation History panel the administrator can click View Details to display a panel with additional details on the results. Links to logs on the remote targets are included. However, those logs can be moved, replaced, or deleted by other users or administrator, if they are not viewed immediately after an installation operation.
Install refresh packs or fix packs for previous versions using the centralized installation manager (CIM)
Install packages using the centralized installation manager (CIM) for previous versions

+

Search Tips   |   Advanced Search