Fix (APAR):  PM50579

Status:  Fix

Release:  6.1.1.4,6.1.1.3,6.1.1.2

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

Supersedes Fixes:  

CMVC Defect:  PM50579

Byte size of APAR:  12629

Date: 2012-04-13

Abstract:  On demand routers are created with not optimal settings.

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

ERROR DESCRIPTION:?                                             
The default value of an outbound request read timeout is        
different                                                       
for                                                             
WVE V6.1.1.4. Properties have been                              
accidentally removed from the odr templates requiring a         
reversion to other defaults, such as the 120 for                
outboundRequestTimeout.                                         

LOCAL FIX:?                                                     
A template could be created with the desired defaults, and that 
template used to create ODRs.                                   
                                                                
maxConnectionsPerServer="0" enableLogging="true"                
outboundRequestTimeout="300" outboundConnectTimeout="10000"     
enableWebServicesSupport="false"                                

PROBLEM SUMMARY:?

USERS AFFECTED:
 All users of WebSphere Virtual Enterprise
using the on demand router.

PROBLEM DESCRIPTION:
On demand routers are created with
not optimal settings.

RECOMMENDATION:
None

Default values in on demand router template are not optimal,
resulting in on demand routers created with that template
having less than ideal settings

PROBLEM CONCLUSION:?                                            
The on demand router template was updated with preferred        
settings.                                                       
                                                                
This fix will be included in the next available fix pack for    
WebSphere Virtual Enterprise.                                   


Directions to apply fix:  
Install Fix to:
NOTE: Developers -  Place and X next to the proper installation method and remove this note
__ 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.4-WS-WXDOP-IFPM50579.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.4-WS-WXDOP-IFPM50579.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.4-WS-WXDOP-IFPM50579.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: