Fix (APAR):  PM33283

Status:  Fix

Release:  6.1.1.3,6.1.1.2,6.1.1

Operating System:  AIX,HP-UX,Linux,Solaris,Windows

Supersedes Fixes:  PK99664;PM04611;PM05220;PM06349;PM07037;PM08969;PM11582;PM11623;PM12939;PM18326;PM22866;PM25095;PM30114;PM31735;PM31801;PM33050

CMVC Defect:  PM33283

Byte size of APAR:  498973

Date: 2011-04-07

Abstract:  When a new ODR is created on a node that did not previously contain an ODR, the signature files are not updated correctly.

Description/symptom of problem:  
PM33283 resolves the following problem:

ERROR DESCRIPTION:                                              
If an ODR is added to a node, the signature file is never       
altered to reflect that it is now a controller.                 

LOCAL FIX:                                                      
n/a                                                             

PROBLEM SUMMARY

USERS AFFECTED:
 All users of WebSphere Virtual Enterprise
who are using IBM Tivoli License Manager

PROBLEM DESCRIPTION:
When a new ODR is created on a node
that did not previously contain an
ODR, the signature files are not
updated correctly.

RECOMMENDATION:
None

When an on demand router (ODR) is added or removed, the
corresponding node agent must be cycled in order for the
signature files to correctly reflect the current state of the
node since signature files are not dynamically updated in
WebSphere Virtual Enterprise. Therefore after an ODR is added
or removed, IBM Tivoli License Manager reports might not be
correct until the node agent where the change occurred is
cycled.

PROBLEM CONCLUSION:                                             
The process that handles updating the WebSphere Virtual         
Enterprise signature files has been updated to dynamically      
alter the signature files in reaction to changes in the         
environment.                                                    
                                                                
This fix will be included in the next available fix pack for    
WebSphere Virtual Enterprise.                                   


Directions to apply fix:  
Install Fix to:
__ Application Server Nodes
__ Deployment Manager Nodes
_X_ Both

NOTE:
The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. Also, you should be logged in with the same authority level when unpacking a fix, fix pack or refresh pack.

DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL A FIX.
The Fix Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

The Update Installer for V5.0 does not have a maintenance directory. It uses fixpacks and fixes as the location of the unpacked files.

Customers must be at V6.1.0.17 or newer of the Update Installer.?This can be checked by reviewing the level of the Update Installer in file <was_root>/updateinstaller/version.txt.

1) Copy 6.1.1.0-WS-WXD-IFPM33283.pak file directly to the maintenance directory

2) Shutdown WebSphere
Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that maintenance is being applied to.

3) Launch Update Installer

4) Enter the installation location of the WebSphere product you want to update.

5) Select the "Install maintenance package" operation.

6) Enter the file name of the maintenance package to install (6.1.1.0-WS-WXD-IFPM33283.pak file which was copied in the maintenance directory). The V5.0 and V5.1 fix packs and fixes are unpacked as .jar files and should be unpacked into fixpacks or fixes directory.

7) Install the maintenance package.

8) Restart WebSphere

Directions to remove fix:  
NOTE:  The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.

NOTE:  FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED.
DO NOT REMOVE A FIX UNLESS
ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.
YOU MAY REAPPLY ANY REMOVED FIX.

Example:  If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, fix2 removed, and fix3 re-applied.

1) Shutdown WebSphere
Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that uninstall is being run against.

2) Start Update Installer

3) Enter the installation location of the WebSphere product you want to remove the fix.

4) Select  "Uninstall maintenance package" operation.

5) Enter the file name of the maintenance package to uninstall (6.1.1.0-WS-WXD-IFPM33283.pak).

6) UnInstall maintenance package.

7) Restart WebSphere

Directions to re-apply fix:  
1) Shutdown WebSphere

2) Follow the Fix instructions to apply the fix.

3) Restart WebSphere

Additional Information: