Fix (APAR): PM25001 Status: Fix Release: 6.1.1.2,6.1.1 Operating System: AIX,HP-UX,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: PM25001 Byte size of APAR: 21279 Date: 2010-11-19 Abstract: Comma separators are not displayed with work classes created using scripting. Description/symptom of problem: PM25001 resolves the following problem: ERROR DESCRIPTION: The routing policy of application cannot be set using a wsadmin script, as shown in the following example. testServer# ./wsadmin.sh -lang jython -f ../../../bin/workclassoperations.py addRules --wcname Default_HTTP_WC --appname A --type ARP --rule "0?virtualhost IN (\'test1\',\'test1\',\'test2\')?permit?A" WASX7209I: Connected to process "dmgr" on node xdblade01b09 using SOAP connector; The type of process is: DeploymentManager WASX7303I: The following options are passed to the scripting environment and are available as arguments that are stored in the argv variable: "[addRules, --wcname, Default_HTTP_WC, --appname, A, --type, ARP, --rule, 0?virtualhost IN (\'adf\',\'dcdf\',\'freed\')?permit?A]" ********************Add Rules****************** INFO: rule virtualhost IN ('adf','dcdf','freed') created in work class Default_HTTP_WC(cells/xd611/applications/A.ear/workclasses/Defau lt_HTTP_WC|workclass.xml#Default_HTTP_WC). INFO: saving changes... INFO: finished. *************************************************** In the administrative console, however, the result is as follows: virtualhost IN ('adf' 'dcdf' 'freed') LOCAL FIX: Modified XDPYModules.py to: wcRuleAttributes = '[[matchAction "%$:%$][matchExpression "%$"][priority "%$"]]' % (actionType, action Value, expr, priority) PROBLEM SUMMARY USERS AFFECTED: All users of WebSphere Virtual Enterprise who use the workclassoperations.py script to create work classes PROBLEM DESCRIPTION: Comma separators are not displayed with work classes created using scripting. RECOMMENDATION: None The routing policy of an application cannot be set using wsadmin scripting, as shown in the following example: testServer# ./wsadmin.sh -lang jython -f ../../../bin/workclassoperations.py addRules --wcname Default_HTTP_WC --appname A --type ARP --rule "0?virtualhost IN (\'test1\',\'test1\',\'test2\')?permit?A" WASX7209I: Connected to process "dmgr" on node xdblade01b09 using SOAP connector; The type of process is: DeploymentManager WASX7303I: The following options are passed to the scripting environment and are available as arguments that are stored in the argv variable: "[addRules, --wcname, Default_HTTP_WC, --appname, A, --type, ARP, --rule, 0?virtualhost IN (\'adf\',\'dcdf\',\'freed\')?permit?A]" *******************Add Rules***************** INFO: rule virtualhost IN ('adf','dcdf','freed') created in work class Default_HTTP_WC(cells/xd611/applications/A.ear/workclasses/Defau lt_HTTP_WC|workclass.xml#Default_HTTP_WC). INFO: saving changes... INFO: finished. ************************************************* In the administrative console, however, the result is displayed as follows: virtualhost IN ('adf' 'dcdf' 'freed') PROBLEM CONCLUSION: 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 /updateinstaller/version.txt. 1) Copy 6.1.1.0-WS-WXDOP-IFPM25001.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-WXDOP-IFPM25001.pak file which was copied in the maintenance 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-WXDOP-IFPM25001.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: