Fix (APAR): JR29765 Status: Fix Release: 6.0.2.2 Operating System: AIX,HP-UX,i5/OS,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: xxxxxx Byte size of APAR: 20644 Date: 2008-07-24 Abstract: The NullPointerException is thrown in the administrative console when trying to edit the HTTP SSL Configuration from within Client security bindings settings, due to improper auto Description/symptom of problem: JR29765 resolves the following problem: ERROR DESCRIPTION: Customer has configured Security Token & Token Generator in WID Deployment Editor for a WebService import. ibm-webservicesclient-bnd.xmi in the generated EJB project looks like: This causes problems when trying to edit "Request generator (sender) binding" in WPS admin console after deployment of the project. (Enterprise Applications > APPLICATION_NAME > EJB Modules > APPLICATION_NAME_EJB.jar > Web services: Client security bindings) Exception is thrown: [11.02.08 17:36:55:735 CET] 0000005e ServletWrappe E SRVE0068E: Could not invoke the service() method on servlet action. Exception thrown: java.lang.NullPointerException at com.ibm.ws.console.wssecurity.WSSecurityUtil.makeChildNoSave(WSS ecurityUtil.java:2346) at com.ibm.ws.console.wssecurity.BasicAuthController.setupDetailFor m(BasicAuthController.java:94) at com.ibm.ws.console.core.action.BaseDetailController.perform(Base DetailController.java:268) at org.apache.struts.tiles.TilesRequestProcessor.processTilesDefini tion(TilesRequestProcessor.java:242) at org.apache.struts.tiles.TilesRequestProcessor.processForwardConf ig(TilesRequestProcessor.java:308) at org.apache.struts.action.RequestProcessor.process(RequestProcess or.java:279) at org.apache.struts.action.ActionServlet.process(ActionServlet.jav a:1486) LOCAL FIX: Insert the xmi:id attribute to the portQnameBindings as shown below PROBLEM SUMMARY USERS AFFECTED: WebSphere Process Server v6.0.2 Users. PROBLEM DESCRIPTION: The NullPointerException is thrown in the administrative console when trying to edit the HTTP SSL Configuration from within Client security bindings settings, due to improper auto generation of xmi file. RECOMMENDATION: None When Security Token and Token Generator has been configured in Websphere Integration Developer Deployment Editor for a WebService import and an attempt is made to edit HTTP SSL Configuration from Client Security Bindings settings in WebSphere Process Server administrative console after deployment of the project, the following exception can be seen: 5/30/08 11:26:14:797 PDT] 00000060 ServletWrappe E SRVE0068E: Could not invoke the service() method on servlet action. Exception thrown : java.lang.NullPointerException at com.ibm.ws.console.wssecurity.WSSecurityUtil.make ChildNoSave(WSSecurityUtil.java:2346) at com.ibm.ws.console.wssecurity.BasicAuthController.set upDetailForm(BasicAuthController.java:94) at com.ibm.ws.console.core.action.BaseDetailController. perform(BaseDetailController.java:268) at org.apache.struts.tiles.TilesRequestProcessor.process TilesDefinition(TilesRequestProcessor.java:242) at org.apache.struts.tiles.TilesRequestProcessor.process ForwardConfig(TilesRequestProcessor.java:308) at org.apache.struts.action.RequestProcessor.process (RequestProcessor.java:279) at org.apache.struts.action.ActionServlet.process (ActionServlet.java:1486) at org.apache.struts.action.ActionServlet.doGet (ActionServlet.java:510) at javax.servlet.http.HttpServlet.service (HttpServlet.java:743) at javax.servlet.http.HttpServlet.service (HttpServlet.java:856) This exception is thrown due to xmi:id attribute missing in automatically generated ibm-webservicesclient-bnd.xmi file for a webservice. PROBLEM CONCLUSION: Code has been added to include xmi:id attribute in the xmi file. Applying this interim fix resolves the problem. 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: