Fix (APAR): PK71796 Status: Fix Release: 7.0 Operating System: AIX,HP-UX,i5/OS,IBM i,Linux,Linux pSeries,Linux Red Hat - pSeries,Linux zSeries,Solaris,Windows Supersedes Fixes: CMVC Defect: 548988 Byte size of APAR: 20922 Date: 2008-09-18 Abstract: contextId has the deployment parameter which expects an associated application name. This causes a NoSuchElementException. Description/symptom of problem: PK71796 resolves the following problem: ERROR DESCRIPTION:? 1. Navigate to "Service integration > buses" 2. Create a bus through the new bus wizard 3. Navigate to the new buses detail panel, click on the "Bus members" link and create a new bus member 4. Save to master configuration 5. Navigate to "Service integration > WS-Notification > Services" 6. Create a new WS-Notification service item using the wizard. Be sure to create a service point at step 4 of this wizard. 7. Navigate to "Services > Service clients" 8. Select a service (OutboundNotificationService was used in this scenario) 9. The result is an error on the page instead of displaying the correct service client detail panel. Details of the Java exception occurring on the page: An error occurred while processing request /ibm/console/secure/layouts/configboxLayout.jsp Message: java.util.NoSuchElementException java.util.NoSuchElementException at java.util.StringTokenizer.nextToken(Unknown Source) at com.ibm.ws.console.core.ConfigFileHelper.parseContextId (ConfigFileHelper.java:1204) LOCAL FIX:? PROBLEM SUMMARY:? USERS AFFECTED: Customers using WS-Notification get an exception when accessing "Services > Service clients" link PROBLEM DESCRIPTION: contextId has the deployment parameter which expects an associated application name. This causes a NoSuchElementException. RECOMMENDATION: Apply iFix PK71796 Accessing the "Services > Service clients" link for the WS-Notification service client results in an exception on the console. Details of java exception: An error occurred while processing request: /ibm/console/secure/layouts/configboxLayout.jsp Message: java.util.NoSuchElementException java.util.NoSuchElementException at java.util.StringTokenizer.nextToken(Unknown Source) at com.ibm.ws.console.core.ConfigFileHelper.parseContextId(ConfigFi leHelper.java:1204) An if statement was introduced to check for the application name value in the contextId string, if it is an empty string the tokenizer is prevented from being advanced to the missing element. PROBLEM CONCLUSION:? The fix for this APAR is currently targeted for inclusion in fixpack 7.0.0.1. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 Install Fix to all WebSphere installations unless special instructions are included below. Special Instructions: None NOTE: The user must: * Logged in with the same authority level when unpacking a fix, fix pack or refresh pack. * Be at V7.0.0.0 or newer of the Update Installer. Certain iFixes may require a newer version of the Update Installer and the Update Installer will inform you during the installation process if a newer version is required. This can be checked by reviewing the level of the Update Installer in file /updateinstaller/version.txt. The Update Installer can be downloaded from the following link: http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg24020212 1) The fix is delivered as a single file with a .pak extension (such as 7.0.0.0-WS-WAS-IFPK71796.pak). Copy the .pak file directly to the maintenance directory, /maintenance. 2) Shutdown WebSphere 3) For IBM i users, use the update command to install and uninstall the interim fix. The IBM Information Center can provide additional details, if needed, on the use of this command. http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-iseries&topic=rins_update. For non-IBM i users, launch the Update Installer and click the Next button on the Welcome page. 4) Enter the directory path of the installation location of the WebSphere product you want to update, and click the Next button. 5) Select the "Install maintenance package" operation and click the Next button. 6) Enter the directory path of your maintenance directory where you have the maintenance packages (.pak files) and click the Next button. 7) The Available Maintenance Package to Install page should list all maintenance packages (.pak files) that it finds in the directory path provided in the previous step. The Update Installer will select the correct maintenance packages based on your system configuration and will not allow an invalid combination to be installed. Please keep the Update Installer recommendations and click the Next button and continue with the installation of the maintenance package. To determine why some maintenance packages have been identified as not applicable, see description in log found in /logs/tmp*/updatelogs.txt 8) For all platforms except Windows. In pre-install summary panel, use the "verify permission" feature to verify the user has permissions to apply updates to files associated with the selected maintenance. Correct any file permissions before clicking next to start the install. 9) Restart WebSphere Directions to remove fix: 1) Shutdown WebSphere 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) Select name of the maintenance package to uninstall (PK71796.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: