Installing fix packs for WebSphere Application Server V7.0

Hi everyone,

Today we are going to discuss how to install fix pack on Websphere Application Server.

On a regular basis, WebSphere fix packs and individual interim fixes for public download. Fix packs contain multiple corrections and improvements in the areas of function, security, stability, and performance. It is recommended that you run your WebSphere with current fix pack levels.

Procedure

1.       Download the Update Installer for WebSphere Software

2.       Install the Update Installer.

3.       Extract the Update Installer package to a temporary directory.

4.       Navigate to the UpdateInstaller subdirectory and start the installation wizard with the following command:

a.       Windows: install.exe

b.      UNIX/Linux: ./install

Follow the instructions in the wizard. When the Installation summary panel is displayed, review the summary which provides links to information resources for the Update Installer. Click Next to begin the installation or click Back to make changes to previous panels. After the installation process completes, verify the success of the installer program.

5.       Download packages to the maintenance directory:

a.        Windows:was_root_dir\UpdateInstaller\maintenance

b.      UNIX/Linux: was_root_dir/UpdateInstaller/maintenance

6.       Stop all WebSphere Application Server and IBM HTTP Server processes.

7.       Backing up a repository using backupConfig 

a.       C:\WebSphere\AppServer\bin>backupConfig  -nostop

8.       Install the maintenance packages.

Navigate to the UpdateInstaller directory in the was-root-di> and start the application with the following command:

a.       Windows: update.bat

b.      UNIX/Linux: ./update.sh

On the Product Selection page, select the installation location from the dropdown list, type it into the edit box, or use Browse to browse to select the location.

On the Maintenance Operation Selection page, select Install maintenance package.

On the Maintenance Package Directory Selection page, specify the location of the downloaded fix packs (was_root_dir\UpdateInstaller\maintenance.).

On the Available Maintenance Package to Install page, accept the selection for recommended updates. Then, click Next.

After the installation finishes, verify that the results say that the installation completed successfully.

9.       Restore a configuration using restoreConfig

                        C:\WebSphere\AppServer\bin>restoreConfig WebSphereConfig_[date].zip
 
Related Topics:

• WebSphereApplication Server V8.5 Fix Pack Installation

“Effort only fully releases its reward after a person refuses to quit.”

Regards,

Akhilesh B. Humbe

How to manually generate a Heapdump in WebSphere Application Server

Hi Everyone,

Occasionally a heapdump needs to be generated without waiting for an OutOfMemoryError condition to occur.

For example: an OutOfMemoryError will probably cause a system outage. On a production system this is not a desired event. If we manually create a heapdump before the OutOfMemoryError generates one, then the application server can be recycled and we will get a heapdump without an unscheduled outage.

The manually generated heapdump will not be as useful as one which was generated by an OutOfMemoryError, but sometimes it can be of some use. The longer we can wait before generating the heapdump, the more likely the heapdump will contain the objects causing the OutOfMemory. If the heapdump is generated too soon, the largest memory user is not likely to be the same largest memory user when the heap is completely full.

1. From a Windows Command Prompt, enter the wsadmin.bat command to get a wsadmin command prompt.

 E.g.: [C: \IBM\WebSphere\AppServer\bin\wsadmin.bat]

Note: If security is enabled or the default SOAP ports have been changed, you will need to pass additional parameters to the batch file in order to get a wsadmin prompt. For example:
wsadmin.bat [-host host_name] [-port port_number] [-user userid[-password password]

2. Get a handle to the problem application server:

wsadmin> set jvm [$AdminControl completeObjectName type=JVM,process=server1,*]

Where server1 is the name of the application server that you want a heapdump from. If wsadmin is connected to a Deployment Manager and if the server names in the cell are not unique, then you can qualify the JVM with a node attribute in addition to the process name.

3. Generate a heapdump:

wsadmin> $AdminControl invoke $jvm generateHeapDump

“Effort only fully releases its reward after a person refuses to quit.”

Regards,

Akhilesh B. Humbe