This document guides you through the steps involved in patching activity i.e. to install maintenance packages to update WebSphere Application Server environment & HTTP Server (IHS).
The intended audiences are those who are responsible for the patching activity of WebSphere Application Server & HTTP Server(IHS) environments.
IBM Update Installer product is used to install interim fixes, fix packs, and refresh packs. The Update Installer is also known as the Update Installer program, the UpdateInstaller program, and the Update Installation wizard.
Before you Begin:
Below is the url for downloading the fix-packs for WebSphere & IHS.
http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Ensure that correct Update Installer software is used for applying fixpacks (check pre-requisite).
If older version of the UpdateInstaller is there uninstall that software and install new version.
Use the correct authorizations to successfully install product updates
Overview of Installation Procedure:
Download the most current version of the Update Installer, fix pack, or refresh pack ZIP or TAR file from the Support site into the installation root directory.
Unpack the downloaded file to create the updateinstaller directory and several subdirectories, including the updi_root/maintenance directory.
Stop all the running instances before applying the patch which includes WebSphere & HTTP server.
Taking Back-Up:
For Websphere: Go to the specific location where the back-up will be stored & issue following command
tar –cvf bck_up_folder_name.tar <was_home>/AppServer
For Http Server: Go to the specific location where the back-up will be stored & issue following command
tar –cvf bck_up_folder_name.tar <IHS_home>
Tip: bck_folder_name: The name of folder should reflect the date of back-up
Eg: AppServer_backup_040109 indicates date 4th JAN 2009.
Note: Taking backup of HTTP server will automatically include backup of PLUGINS as this directory is present in <IHS_home> folder.
Copy the Fix-Packs (.PAK) file to the maintenance folder of UpdateInstaller.
i.e updi_root/maintenance directory.
Start Patching:
WebSphere:
log-in as the user who owns the WebSphere process (usually wasadmin).
Run the command from below path using X-Manager(for AIX/Linux) as it supports graphics.
updi_root/bin/update.sh : for AIX and Linux
updi_root/bin/update.bat : for Windows
Follow the instruction to apply patch.
HTTPServer:
Log-in as the user who owns HTTPServer process i.e. as ROOT user.
Run the command from below path using X-Manager(for AIX/Linux) as it supports graphics.
updi_root/bin/update.sh : for AIX and Linux
updi_root/bin/update.bat : for Windows
Follow the instruction to apply patch.
Start the Server instances including both Websphere & HTTP Server as the user who owns the respective processes.
Check the updated version of product that have been patched.
<Was_home>/AppServer/bin/versionInfo.sh (versionInfo.bat for WIN)
<IHS_home>/bin/versionInfo.sh (versionInfo.bat for WIN)
Once the latest version has been confirmed, one can state that patch has been successfully applied.
In Case of failure:
If the activity of patching turns out to be a failure, for proper running of the services one need to revert back the activity. Thus here comes the back-up folder into picture.
Stop all the services (server instances).
For Websphere: rename the AppServer folder to any other name.
Eg : AppServer to AppServer_Old.
Unpack the back-up folder at the location <was_home> by running:
tar –xvf path_of_bck_up_folder_name.tar
Rename the extracted folder to “AppServer”.
For HttpServer: rename the entire HTTPServer to any other name.
Eg : HTTPServer to HTTPServer_Old.
Unpack the back-up folder at the location <IHS_home> by running:
tar –xvf path_of_bck_up_folder_name.tar
Rename the extracted folder to “HTTPServer”.
Restart the respective services.
No comments:
Post a Comment