Fix (APAR): PM37444 Status: Fix Release: 6.1.1.3 Operating System: AIX,HP-UX,Linux,Solaris,Windows,z/OS Supersedes Fixes: CMVC Defect: xxxxxx Byte size of APAR: 114078 Date: 2011-07-21 Abstract: Dynamic weights are not calculated correctly by dynamic workload management (DWLM) in certain situations. Description/symptom of problem: PM37444 resolves the following problem: ERROR DESCRIPTION: Provide ability to disable usage of EJB statistics in the calculation of dynamic weight for a dynamic cluster member. This is required in certain situations, such as, when EJB traffic is not being sent through the ODR and there is no need to load balance the EJB traffic, or EJB traffic is driven through the web artificats like servlets and web service time is inclusive of EJB response time. LOCAL FIX: N/A PROBLEM SUMMARY USERS AFFECTED: All users of WebSphere Virtual Enterprise who are using dynamic clusters that have Enterprise JavaBeans (EJB) and web applications PROBLEM DESCRIPTION: Dynamic weights are not calculated correctly by dynamic workload management (DWLM) in certain situations. RECOMMENDATION: None The ability to disable the usage of EJB statistics when calculating dynamic weight for a dynamic cluster member should be supported. This support is required in certain situations, such as when EJB traffic is not sent through the ODR and there is no need for the load balancing of the EJB traffic. Another example of when this support is needed is when EJB traffic is driven through web artificats. PROBLEM CONCLUSION: The issue is fixed by setting the ignoreEJBStats custom property to true at the cell or dynamic cluster level. Setting the custom property at the cell level affects all the dynamic clusters in the cell, which must be recycled for the custom property changes to take effect. When the custom property is set to true, DWLM ignore EJB statistics during the weight calculation. The default value for the custom property is false. 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 /updateinstaller/version.txt. 1) Copy 6.1.1.3-WS-WXD-IFPM37444.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.3-WS-WXD-IFPM37444.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.3-WS-WXD-IFPM37444.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: