Fix (APAR): PM56332 Status: Fix Release: 7.0.0.2,7.0.0.1,7.0 Operating System: AIX,HP-UX,IBM i,Linux,Solaris,Windows Supersedes Fixes: PM52394;PM54709 CMVC Defect: xxxxxx Byte size of APAR: 536260 Date: 2012-06-07 Abstract: The On Demand Router does not properly handle non-default clone id separators. Description/symptom of problem: PM56332 resolves the following problem: ERROR DESCRIPTION: On the JSESSIONID a delimiter is used to parse the session ID from the Application Server ID. This delimiter is set and returned from the Application Server to the ODR for session routing. By default this is set to colon (:) in the application server. However, the Application Server session management or webcontainer (deprecated in 7.0) properties CloneSeparatorChange and CloneSeparator can be used to change the delimiter to another character. Most commonly if changed this will be set to plus sign (+) however, this does not have to be the case. Since the delimiter is returned from the application server and the ODR can route to multiple application servers there is no guarantee that each application server will use the same delimiter. However, currently the ODR can only read a single delimiter. This means that the ODR could fail to route to application servers which are not using the same delimiter that the ODR is using. This can be seen in the ODR trace as the example below: [1/5/12 12:17:19:928 EST] 0000001c XDDWLMClientS 3 delimiter ':' not found in session ID '1111j4KdU1111DCtec_MuEiujK_+16mkl87y6' This shows a response from an application server which is using a separator of '+' however, the ODR is looking for a delimiter of ':' LOCAL FIX: Set all the CloneSeparators in the application servers to the same value and use this value in the ODR. PROBLEM SUMMARY USERS AFFECTED: All users of WebSphere Virtual Enterprise that have configured a web container to use non- default clone id separators. PROBLEM DESCRIPTION: The On Demand Router does not properly handle non-default clone id separators. RECOMMENDATION: None The On Demand Router does not properly handle clone id separators when web container custom property CloneSeparatorChange has been set to true. PROBLEM CONCLUSION: Support for the CloneSeparatorChange web customer property has been added to the On Demand Configuration component. Please note that PM55852 is also needed before the On Demand Router will properly handle the CloneSeparatorChange web customer property. 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 7.0.0.0-WS-WVE-IFPM56332.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 (7.0.0.0-WS-WVE-IFPM56332.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 (7.0.0.0-WS-WVE-IFPM56332.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: ODC