IBM Rational Automation Framework for WebSphere. Guided Activity: Applying fix packs to nodes in a WebSphere Application Server cell

Transcription

1 IBM Rational Automation Framework for WebSphere Guided Activity: Applying fix packs to nodes in a WebSphere Application Server cell Contacts: ataylor@atech.com IBM Corporation Level: Beginner January 2010 Copyright 2010 IBM Corporation

2 Page 2 of 17 Contents 1.0 Audience Overview Information resources Actions Prerequisite tasks Objectives Download and extract the IBM Update Installer Download fix packs for WebSphere Verify that actions to install fix packs are available (Optional) Create a custom action for a missing fix pack action Create a Rational Build Forge project for the fix pack actions Run the Rational Build Forge project to apply the fix packs...14 Trademarks...17 Resources...17 About the authors...17

3 Page 3 of Audience The audience for this guided activity is WebSphere administrators. 2.0 Overview Apply a fix pack to the nodes in a WebSphere Application Server cell by using fix pack actions provided by Rational Automation Framework for WebSphere. Create a Rational Build Forge project to execute the actions that apply the maintenance fix packs. This guided activity shows you how to apply the Fix Pack 7 ( ) and the Java SDK 1.6 SR6 Fix Pack to WebSphere Application Server V7.0. It also shows you how to create a custom fix pack action if the fix pack you want to install is not available. Note: The procedures and steps in this guided activity can be adapted to apply other fix packs for WebSphere Application Sever. 3.0 Information resources For information about WebSphere Application Server, refer to the IBM information center for your WebSphere product version: 3.1 WebSphere Application Server WebSphere Application Server WebSphere Application Server For information about Rational Automation Framework for WebSphere (RAFW), refer to the RAFW IBM information center: 3.4 Rational Automation Framework for WebSphere

4 Page 4 of Guided activities Other guided activities can be found at IBM Software Support for Rational products: In the Search field, enter guided activities. For guidance about applying maintenance to WebSphere Application Server, see the IBM Support site: 3.6 Fixes by version for WebSphere Application Server Update strategy for WebSphere Application Server V Java SDK upgrade policy for WebSphere Application Server Actions The examples in this guided activity use the following actions: Action was_70_install_updateinstaller Description Installs the IBM Update Installer 7.0 for WebSphere Software. was_70_install_fp7 Installs WebSphere Application Server Fix Pack 7 ( ). was_70_install_jdk_sr6 Installs the Java SDK 1.6 SR6 Fix Pack for WebSphere Application Server. 5.0 Prerequisite tasks 5.1 Install WebSphere Application Server V Add actions to start and stop all processes in a WebSphere Application Server cell. Use the Java program provided in the following guided activity to add the actions to Rational Build Forge as libraries. Guided Activity: Restarting all processes in a WebSphere cell

5 Page 5 of Objectives 6.1 Download installation media for the latest version of the IBM Update Installer for WebSphere. Copy or extract installation media to the correct directory in the media tree. 6.2 Download the fix packs for WebSphere: WebSphere Application Server Fix Pack 7 ( ) and the Java SDK 1.6 SR6 Fix Pack. Copy or extract fix packs to the correct directories in the media tree. 6.3 In Rational Build Forge, create a project for the fix packs and then run the project to apply the fix packs. 7.0 Download and extract the IBM Update Installer WebSphere Application Server Fix Pack 7 ( ) requires the latest version of the IBM Update Installer. 7.1 Download the latest version of the IBM Update Installer 7.0 for WebSphere Software. Installation media is provided for each operating system platform supported by WebSphere Application Server. 7.2 In the media tree, copy the installation media to the correct directory path. Installation media for the Update Installer is installed to the update_installer_image directory. The media tree directory path for the Update Installer uses the following structure: <rafw_media_home>/<os>/<arch>/was/70/update_installer_image Note: If there is an earlier version of the Update Installer in the update_installer_image directory, delete or archive the earlier version. The following example uses the wget command to download the Update Installer media for WebSphere Application Server V7.0 on Linux (32-bit Intel) to the correct media tree directory: [rafw ~]$ cd /opt/ibm/rafw/media/linux/x32/was/70/update_installer_image [rafw update_installer_image]$ wget ftp://ftp.software.ibm.com/software/websphere/appserv/support/tools/updateins taller/7.0.x/linuxia32/ ws-updi-linuxia32.tar.gz

6 Page 6 of 17 The following example extracts the downloaded media. After extracting media from the archive, you can delete or back up the archive file. [rafw update_installer_image]$ tar xvzf WS-UPDI-LinuxIA32.tar.gz 8.0 Download fix packs for WebSphere Download the WebSphere Application Server Fix Pack 7 ( ) and the Java SDK 1.6 SR6 Fix Pack for WebSphere Application Server. Notes: PAK files are not archives and are used as-is; do not attempt to extract or modify PAK files. If the fix pack directories do not exist, the actions to install the PAK files might also be missing and, therefore, must be created or obtained from IBM Software Support. To create missing directories, you must use the correct media tree directory names. 8.1 Download the PAK file for the WebSphere Application Server Fix Pack 7 to: <rafw_media_home>/<os>/<arch>/was/70/patches/was70_fp7 The following example uses the wget command to download Fix Pack 7 to the correct media tree directory for WebSphere Application Server V7.0 on Linux (32-bit Intel): [rafw ~]$ cd /opt/ibm/rafw/media/linux/x32/was/70/patches/was70_fp7 [rafw was70_fp7]$ wget ftp://ftp.software.ibm.com/software/websphere/appserv/support/fixpacks/was70/ cumulative/cf7007/linuxx32/7.0.0-ws-was-linuxx32-fp pak 8.2 Download the PAK file for the Java SDK 1.6 SR6 Fix Pack for WebSphere Application Server to: <rafw_media_home>/<os>/<arch>/was/70/patches/was70_jdk_sr6

7 Page 7 of 17 The following example uses the wget command to download the Fix Pack for Java SDK 1.6 SR6 to the correct media tree directory for WebSphere Application Server V7.0 on Linux (32-bit Intel): [rafw ~]$ cd /opt/ibm/rafw/media/linux/x32/was/70/patches/was70_jdk_sr6 [rafw was70_jdk_sr6]$ wget ftp://ftp.software.ibm.com/software/websphere/appserv/support/fixpacks/was70/ cumulative/cf7007/linuxx32/7.0.0-ws-wassdk-linuxx32-fp pak 9.0 Verify that actions to install fix packs are available The actions to install the fix packs must be installed on the framework server. Use the commands in the following examples to verify that actions for fix packs are available. 9.1 To verify that the was_70_install_fp7 action to install WebSphere Application Server Fix Pack 7 ( ) is installed, run the following command on the framework server: [rafw rafw]$./bin/rafw.sh -e <ENV> -c <CELL> -n <NODE> -l grep fp7 If was_70_install_fp7 is installed, the command returns results similar to the following: was_70_install_fp7 - Install WAS 7.0 Fix Pack To verify that the was_70_install_jdk_sr6 action to install the Java SDK 1.6 SR6 Fix Pack for WebSphere Application Server is installed, run the following command on the framework server: [rafw rafw]$./bin/rafw.sh -e <ENV> -c <CELL> -n <NODE> -l grep sr6 If was_70_install_jdk_sr6 is installed, the command returns results similar to the following: was_70_install_jdk_sr6 - Install WAS 7.0 JDK Update SR6

8 Page 8 of If the command results indicate that the fix pack actions are installed, go to 11.0 Create a Rational Build Forge project for the fix pack actions, and follow the instructions. If you discover that the fix pack actions that you need are not installed, you can: Upgrade to the latest version of Rational Automation Framework for WebSphere to obtain them. Contact IBM Software Support if you need assistance upgrading to the latest product version. Create the missing fix pack actions as a custom action by using an existing fix pack action as a template. For instructions, see Create a custom action for a missing fix pack action (Optional) Create a custom action for a missing fix pack action Note: The following example uses Fix Pack 1 ( ) as a template to create a custom action to install Fix Pack 7 ( ). You can adapt this example to create a custom action to install a fix pack Select a fix pack action similar to the one that you want to create to use as a template. You copy the Ant code from the template to create the code for the custom action. Run the template action with the p option to print the Ant code as command output. The following example prints the Ant code for the Fix Pack 1 action: was_70_install_fp1. [rafw rafw]$./bin/rafw.sh -e <ENV> -c <CELL> -n <NODE> -p was_70_install_fp1 Note that the output for the example prints the Ant code that invokes the action. <target depends="only_execute" description="install WAS 7.0 Fix Pack 1" name="was_70_install_fp1"> <antcall target="was_install_patch_was_to_level"> <param name="patch_name" value="was70_fp1"/> </antcall> </target>

9 Page 9 of Create the custom action in the custom install XML file. The custom install XML file is located in the user/actions directory path; for example: <rafw_home>/user/actions/install/was/70/custom_install_was70.xml To create the custom action, copy the Ant code to the custom install XML file and modify it. In the following example, the Ant code from was_70_install_fp1 is added to the custom_install_was70.xml file. The was_70_install_fp1 code is in bold text: <project default="default" basedir="."> <description> Contains custom install tasks for WAS 70 Base </description> <target depends="only_execute" description="install WAS 7.0 Fix Pack 1" name="was_70_install_fp1"> <antcall target="was_install_patch_was_to_level"> <param name="patch_name" value="was70_fp1"/> </antcall> </target> </project> 10.3 Modify the custom install XML file to create the custom action. Edit the variables in bold text in the following example to create the custom action to install Fix Pack 7: Important: Prefix the fix pack name with custom_ to indicate that it is a custom action. <project default="default" basedir="."> <description> Contains custom install tasks for WAS 70 Base </description> <target depends="only_execute" description="install WAS 7.0 Fix Pack 7" name="custom_was_70_install_fp7"> <antcall target="was_install_patch_was_to_level"> <param name="patch_name" value="was70_fp7"/> </antcall> </target> </project>

10 Page 10 of Repeat steps 10.1 through 10.3 to add a custom action to install the Java SDK 1.6 SR6 Fix Pack. Important: Make necessary modifications to the steps so that they apply to the Java SDK fix pack. For example, the PATCH_NAME parameter value for the Java SDK 1.6 SR6 fix pack is was70_jdk_sr Create a Rational Build Forge project for the fix pack actions Note: To complete this task, install the actions to start and stop all processes in a WebSphere Application Server cell. See the Guided Activity: Restarting all processes in a WebSphere cell Create a project that defines the steps to apply fix packs to a WebSphere cell. In the Rational Build Forge UI, select Project and fill in the project details, for example: Name: Selector: Access: WAS_70_ApplyFixPack7 RAFW Build Engineer

11 Page 11 of Add the steps to the project to apply the fix packs. Add the steps in the order listed in the example Stop All Processes. The first step in the project must be the Stop All Processes library. Add the library as an Inline step. All the processes in the cell must be stopped to apply fix packs to the nodes. Note: If this is a standalone cell, use the RAFW_stop_servers instead of the RAFW_stop_cell library. Name: Stop All Processes Result: RAFW Inline: RAFW_stop_cell Timeout: 0

12 Page 12 of Update the Update Installer. Install the latest version of the IBM Update Installer for WebSphere Software. Note: Fix Pack 7 must be installed using the latest version of the Update Installer. Note: The logic in the step Condition field assumes that the deployment manager (DMGR) is on the same host as one of the nodes in the cell. If this is not true for your environment, add another step to update the Update Installer on the DMGR host. Name: Update Update Installer Step Type: While Condition: true(${bf_iteration}<=${number_of_nodes}) Command: ${RAFW_HOME}/bin/rafw${SCRIPT_EXT} -e ${ENVIRONMENT} -c ${CELL_NAME} -n ${BEGIN_VARIABLE}NODE${BF_ITERATION}_NODE_NAME${END_VARIABLE} -t was_common_install_updateinstaller Result: RAFW Timeout: 0

13 Page 13 of Apply Fix Pack 7 ( ). Note: The logic in the step Condition field assumes that the deployment manager (DMGR) is on the same host as one of the nodes in the cell. If this is not true for your environment, add another step to install Fix Pack 7 on the DMGR host. Note: If a custom action was created to install the fix pack, use the name of the custom action. For example, custom_was_70_install_fp7. Name: Apply FP7 Step Type: While Condition: true(${bf_iteration}<=${number_of_nodes}) Command: ${RAFW_HOME}/bin/rafw${SCRIPT_EXT} -e ${ENVIRONMENT} -c ${CELL_NAME} -n ${BEGIN_VARIABLE}NODE${BF_ITERATION}_NODE_NAME${END_VARIABLE} -t was_70_install_fp7 Result: RAFW Timeout: Apply Java SDK 1.6 SR6 Fix Pack. Note: The logic in the step Condition field assumes that the deployment manager (DMGR) is on the same host as one of the nodes in the cell. If this is not true for your environment, add another step to install the Java SDK 1.6 SR6 Fix Pack on the DMGR host. Note: If a custom action was created to install the fix pack, use the name of the custom action. For example, custom_was_70_install_jdk_sr6.

14 Page 14 of 17 Name: Apply JDK SR6 Step Type: While Condition: true(${bf_iteration}<=${number_of_nodes}) Command: ${RAFW_HOME}/bin/rafw${SCRIPT_EXT} -e ${ENVIRONMENT} -c ${CELL_NAME} -n ${BEGIN_VARIABLE}NODE${BF_ITERATION}_NODE_NAME${END_VARIABLE} -t was_70_install_jdk_sr6 Result: RAFW Timeout: Start All Processes. The last step in the project must be the Start All Processes library. Add the library as an Inline step. All the processes in the cell must be started to apply fix packs to the server nodes. Note: If this is a standalone cell, use the RAFW_start_servers library instead of the RAFW_start_cell library. Name: Start All Processes Result: RAFW Inline: RAFW_start_cell Timeout: Run the Rational Build Forge project to apply the fix packs To apply fix packs to all of the nodes in a cell, run the project against the Rational Build Forge environment created for the WebSphere cell definition In the Projects list, select the project that you created: WAS_70_ApplyFixPack7.

15 Page 15 of Select the environment for the WebSphere cell definition you want to patch. An environment object is automatically created when you run the RAFW Environment wizard and create the cell definition in the environment tree. In this example all nodes represented by the int_was70 cell definition will be patched. Save the project Run the project. Click the project name in the Projects list. Select the project name to open the project. Verify that the environment is correct. Click Start Project.

16 Page 16 of 17 Note: If the servers are not running, the Stop All Processes step might fail. If the step fails, restart the project and exclude the Stop All Processes step from the project. Note: The last step in the project starts all the processes in the cell To verify that the fix packs are applied successfully, check the step output for the Apply JDK SR6 step. If successful, the step output should list the version of WebSphere Application Server and the version of Java SDK installed. Note: To view the step output, select Jobs and then select the job name to display the list of steps in the project. Select a step name to display step output.

17 Page 17 of 17 Trademarks IBM, the IBM logo, WebSphere, WebSphere Application Server, Rational Build Forge and Rational Automation Framework for WebSphere are trademarks of IBM Corporation in the United States, other countries, or both. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Also, if this article uses any of the product names from other companies that require trademarks, add the appropriate information here. See Special Attributions for details. Other company, product, or service names may be trademarks or service marks of others. Resources Learn Visit the Rational software area on developerworks for Slashdot it! technical resources and best practices for Rational Software Delivery Platform products. Subscribe to the developerworks Rational zone newsletter. Keep up with developerworks Rational content. Every other week, you'll receive updates on the latest technical resources and best practices for the Rational Software Delivery Platform. Subscribe to the Rational Edge newsletter for articles on the concepts behind effective software development. Subscribe to the IBM developerworks newsletter, a weekly update on the best of developerworks tutorials, articles, downloads, community activities, webcasts and events. Browse the technology bookstore for books on these and other technical topics. Get products and technologies Download trial versions of IBM Rational software. Download IBM product evaluation versions and get your hands on application development tools and middleware products from DB2, Lotus, Rational, Tivoli, and WebSphere. Discuss Check out developerworks blogs and get involved in the developerworks community. About the authors Share this article Digg this story Post to del.icio.us Alden Taylor (ataylor@atech.com) is the architect and lead developer for the Rational Automation Framework for WebSphere. He is a consultant with Ascendant Technology, specializing in WebSphere and Portal architecture, infrastructure, and development. Jill Ackerman (jeackerm@us.ibm.com) is a technical writer working with the Rational Automation Framework for WebSphere and Rational Build Forge teams at IBM Austin.