Abstract This cumulative interim fix updates IBM WebSphere Application Server Hypervisor Edition Version 7.0.0.17 with Intelligent Management Pack enabled to the current Version 7.0 level of IBM WebSphere Virtual Enterprise. About the interim fix APARs addressed: PM41431 Prerequisite: root user must be used to apply this interim fix. 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 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. Apply this interim fix to update WebSphere Application Server Hypervisor Edition Version 7.0.0.17 with Intelligent Management Pack enabled to the current level of WebSphere Virtual Enterprise Version 7.0. The following updates are included in this interim fix: * When the application placement controller is in elasticity mode, a REMOVE action is issued regardless if the servers are still running on the node. The product has been updated to ensure that the REMOVE action is not issued until all of the servers are stopped on the node. * When the application placement controller is in elasticity mode and an ADD action is issued in an IBM Workload Deployer environment, a new virtual machine and node are created. The node is then federated into the cell, and an instance of the dynamic cluster, which required the ADD action, is created. The product has been updated to ensure that the newly created dynamic cluster instance is started after the ADD action is completed. * Cells in a multi-cell performance environment can be dynamically linked together. * The operation of runtime tasks issued by the application placement controller is similar to the operation of runtime tasks in WebSphere Virtual Enterprise Version 6.1.1.x. * WebSphere Virtual Enterprise retrieves statistics about virtual machines from IBM Workload Deployer. * Support for a custom health policy condition based on PMI metrics associated with a specific data source has been added. * Additional support for historical charting has been added. * NullPointerException errors are corrected when the visualization data service is not enabled. * Problems no longer exist with a horizontal slider bar in the administrative console when Mozilla Firefox is used. * The historic mode time stamp is passed to the visualization data service correctly. * The name of the manageODC.py script has been changed to ve_manageODC.py script. * The cellAgentLocation property has been added to the on demand configuration so that the application placement controller can properly determine the location of running cell agents in a multi-cell performance environment. * On demand configuration events of dynamic clusters that belong to another cell in a multi-cell environment are ignored. * The script package to set elasticity mode has been updated to add default elasticity actions. * Operand arguments can be expressed as name/value pairs with strings or literals. --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Steps for applying the interim fix to deployed virtual systems To apply the interim fix to your deployed virtual systems, use one of the following two procedures: * 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. * Log in to the system and apply the interim fix manually. 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 ./installServiceforIMP.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. --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Steps for applying the interim fix to new deployments To apply the interim fix to new deployments, use the following procedure: 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 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 clone and extend. 3. From the Virtual Systems panel, select the deployed virtual system through clone and extend , 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. 7. Navigate to Catalog > Virtual Images > . 8. Click the capture icon and then OK to capture the virtual system. The capture process creates a new virtual image 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.