Release notes for WebSphere Application Server Hypervisor Edition Intelligent Management Pack Version 7.0

Content

Requirement: Before using WebSphere Application Server Hypervisor Edition Intelligent Management Pack Version 7.0, you must download and apply the base cumulative fix for Intelligent Management Pack. Download the fix from Fix Central at http://www.ibm.com/support/fixcentral.

The base cumulative interim fix for Intelligent Management Pack updates WebSphere Application Server Hypervisor Edition Version 7.0.0.17 with Intelligent Management Pack enabled to the current level of IBM WebSphere Virtual Enterprise Version 7.0.

Important: If you plan to deploy a virtual system that consists of WebSphere Application Server Hypervisor Edition Version 7.0.0.17 with Intelligent Management Pack enabled on Linux on System z s390 using a shared DASD, you must create a new virtual image and apply this interim fix to the virtual image. You can then deploy the virtual system using the newly captured virtual image. See the steps for applying the interim fix to new deployments for more information.

Steps for applying the interim fix to deployed virtual systems
Use one of the following two procedures to apply the interim fix to your deployed virtual systems:

Use the IBM Workload Deployer user interface to add the interim fix as an emergency fix.

1. Log in to the user interface with an administrator account.
2. Select Catalog > Emergency fix.
3. From the left panel of the Emergency Fixes window, click the add icon to add an emergency fix to the catalog.
4. Enter the emergency fix name. Optionally, you can also enter a description of the emergency fix.
5. Click OK.
6. Click Browse..., select the file to upload, and click OK.
7. Click Upload to import the file to the catalog.
8. Select the virtual image for which this emergency fix is applicable. The Applicable to field determines to which virtual image this emergency fix applies. If the WebSphere Application Server version and operating system of your virtual image is not listed, click Add more... to add it from the list.
9. From the Virtual Systems panel, select the deployed virtual system, and click the apply service icon.
10. Expand Select service level or fixes, and select the emergency fix.
11. (Optional) If you changed the password of root after the virtual system was deployed, you must specify "root" and the updated password in the Product administrator user name and password field.
12. Click OK, and the emergency fix will be applied automatically. You are not required to restart the system.

1. Provision the WebSphere Application Server Hypervisor Edition image.
2. (Optional) Copy the virtual image using the VMware Infrastructure client or analogous tool. Note: Any maintenance that you apply to the virtual image cannot be removed. After you apply the interim fix, this copy of the virtual image is the only mechanism that can be used to roll back the interim fix installation.
3. Download and save the interim fix, which is delivered as a ZIP file.
4. Run the su - root command to switch to the root user.
5. Extract the ZIP file.
6. Run the chmod +x ./installServicefor IMP.sh script.
7. Run the ./installServiceforIMP.sh script to install the service update. A message stating that the update completed is displayed.
8. (Optional) Delete the directory in which you extracted the ZIP file.
9. Restart your system.

1. Clone and extend the virtual image in which WebSphere Application Server Hypervisor Edition Intelligent Management Pack is enabled. Click the clone and extend icon to create an extension of the virtual image. Enter the values for each field, and click OK. A virtual system instance is created using the default pattern. You can modify this virtual system instance and then capture the modifications made to the virtual system instance into a new virtual image. After you click OK, the virtual image status is displayed as follows: Creating a virtual system instance for virtual image extension. A virtual system instance, with the name <new_virtual_image_name>, is deployed into the cloud.
2. Add the interim fix as an emergency fix to the catalog. a. Select Catalog > Emergency fix. b. From the left panel of the Emergency fixes window, click the add icon to add an emergency fix to the catalog. c. Enter the emergency fix name. Optionally, you can also enter a description of the emergency fix. d. Click OK. e. Click Browse..., select the file to upload, and click OK. f. Click Upload to import the file to the catalog. g. In the Applicable to field, select the extended virtual image that you created with the clone and extend operation.
3. From the Virtual Systems panel, select the deployed virtual system through clone and extend <new_virtual_image_name>, and click the apply service icon.
4. Expand Select service level or fixes, and select the emergency fix.
5. (Optional) If you changed the password of root after the virtual system was deployed, you must specify "root" and the updated password in the Product administrator user name and password field.
6. Click OK, and the emergency fix will be applied automatically. You are not required to restart the system. Ensure that the emergency fix is applied before you proceed to the next step.
7. Navigate to Catalog > Virtual Images > <new_virtual_image_name>.
8. Click the capture icon, and click OK to capture the virtual system. The capture process creates a new virtual images based on the deployed virtual system instance that you modified. This process does take an extended amount of time to complete as a large amount of processing is required. Multiple image captures can be scheduled and added to the task queue, yet no more than two image captures are performed concurrently because of resource limitations on the appliance and the large amount of data and processing involved with this process.
9. Click the lock icon to permanently make this virtual image read-only.
10. Use this virtual image for new deployments.