Fix (APAR): JR31674 Status: Fix Release: 6.1.2.2,6.0.2.5 Operating System: AIX,HP-UX,i5/OS,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: JR31674 Byte size of APAR: 61721 Date: 2009-04-29 Abstract: An exception is thrown in the administrative console when trying to access details under Token generators in editing Request generator (sender). Description/symptom of problem: JR31674 resolves the following problem: ERROR DESCRIPTION: A ClassCastException exception is thrown in the administrative console when trying to access details under Token generators in editing Request generator (sender) binding because of improper auto-generation of the ibm-webservicesclient-bnd.xmi file. To navigate: Adminconsole -> Enterprise Applications > ModuleAppName > EJB Modules > ModuleEJB.jar > Web services: Client security bindings > Request generator (sender) binding > details under Token generators LOCAL FIX: manually add xmi:id tags for missing elements can work around this issue. PROBLEM SUMMARY USERS AFFECTED: WebSphere Process Server v6.1.2.x users WebSphere Process Server v6.0.2.x users PROBLEM DESCRIPTION: An exception is thrown in the administrative console when trying to access details under Token generators in editing Request generator (sender). RECOMMENDATION: None A ClassCastException exception is thrown in the administrative console when trying to access details under Token generators in editing Request generator (sender) binding because of improper auto-generation of the ibm-webservicesclient-bnd.xmi file. To navigate: Adminconsole -> Enterprise Applications > ModuleAppName > EJB Modules > ModuleEJB.jar > Web services: Client security bindings > Request generator (sender) binding > details under Token generators PROBLEM CONCLUSION: Applying this interim fix will resolve the issue. Directions to apply fix: Download and follow Update Installer installation instructions. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 1) Copy the pak file to the directory maintenance in the UpdateInstaller directory 2) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 3) Run the UpdateInstaller and follow the prompts. 4) Restart WebSphere Process Server. Directions to remove fix: NOTE: FIXES MUST BE REMOVED IN THE REVERSE ORDER IN WHICH 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, then fix2 may be removed 1) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix. 3) Restart WebSphere Process Server. Directions to re-apply fix: 1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 2) Run the UpdateInstaller and follow the instructions. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 3) Restart WebSphere Process Server. Additional Information: