Applying a fix to the base image or lifecycle script for a virtual application instance

You can apply fixes to the base image or lifecycle script.

Before you begin

After a virtual application is deployed, you can apply an emergency fix in the catalog to either the base operating system virtual image or a lifecycle script in the virtual application instance.

The fixes that you want to apply must be correctly packaged and must exist in the catalog before you can apply them.

For information about packaging a fix or adding the fix to the catalog, see the Related tasks section.

You must be assigned one of the following roles to perform these steps:
  • Workload resources administration role with permission to Manage workload resources (Full permission)
  • Workload resources administration role with permission to View all workload resources (Read-only)
  • Create new patterns
  • Create new catalog content
  • Create new environment profiles
  • IBM® License Metric Tool (ILMT) user

About this task

You can apply two types of fixes to a virtual application instance from the Instance Console:
  • An update to the base operating system virtual image by applying an emergency fix to the virtual image.
  • An update to a role used by a virtual application instance.
Note: You cannot update the base operating system virtual image to a newer version, such as 2.0.0.2 to 2.0.0.3, by applying an emergency fix. For information about updating the base operating system virtual image to a newer version, see the Related tasks section.

Procedure

  1. Click Patterns > Virtual Application Instances.
  2. Select the virtual application instance that you want to update.
  3. Click Manage in the toolbar.
    The Instance Console opens.
  4. Click the Operations tab.
  5. On the Operations page, select MAINTENANCE in the list.
    The Install maintenance fixes settings are displayed. The Maintenance fixes field lists any maintenance fixes that are already installed.
  6. Click Select and choose the fixes that you want to apply.
    The fixes that are displayed here meet the following requirements:
    • The fixes were uploaded to the catalog through Catalog > Emergency Fixes.
    • They have service.xml in their fix archive.
    • They are applicable to the plug-ins in the pattern type that this virtual application was deployed from.
    Important:
    • If there are dependencies between fixes that you want to install, deploy each fix separately instead of submitting them at the same time to avoid conflicts.
    • Only fixes that can be installed through the maintenance operation are displayed here. These fixes contain service.xml.
    • Fixes for middleware are displayed here; however, you must not attempt to deploy from here.
    • If you want to install a middleware fix, such as a WebSphere Application Server fix, use the update feature available with the middleware role. For information about applying a fix for IBM WebSphere® Application Server, see the Related tasks section.
    • If you are applying more than one fix, wait for the upload to the instance to complete (which you can verify by the update history section), and then refresh the page before you select the next fix.
  7. Click Submit.
    The status of the installation is displayed in the Operation Execution Results section. You can also check more detailed information in logs for the MAINTENANCE role.