Fix (APAR): JR33041 Status: Fix Release: 6.2 Operating System: AIX,HP-UX,i5/OS,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: xxxxxx Byte size of APAR: 1700852 Date: 2009-06-26 Abstract: An incorrrect properties file is loaded during portal configuration. Description/symptom of problem: JR33041 resolves the following problem: ERROR DESCRIPTION: A conflict on the classpath exists when running ConfigEngine during the Portal configuration when Process Server is installed. An incorrect properties file is loaded causing the following error: [wplc-modify-ldap-attribute-config] [04/07/09 23:53:13.187 EDT] CWRGS1049E Class 'boolean' defined in does not exist. Check classpath? [wplc-modify-ldap-attribute-config] [04/07/09 23:53:13.203 EDT] CWRGS1003E Validation of default XMT file failed. Error is: 'null The exception stack trace would be CWRGS1049E Class 'boolean' defined in does not exist. Check classpath? CWRGS1003E Validation of default XMT file failed. Error is: 'null CWRGS1049E Class 'boolean' defined in does not exist. Check classpath?' CWRGS1001E Failed to initialize MCCFile. com.ibm.sec.iauthz.util.MCCException: CWRGS1003E Validation of default XMT file failed. Error is: 'null CWRGS1049E Class 'boolean' defined in does not exist. Check classpath?' at com.ibm.sec.iauthz.mcc.engine.MCCFile.(MCCFile.java:139) at com.ibm.sec.iauthz.mcc.engine.MCCFile.(MCCFile.java:80) at java.lang.J9VMInternals.initializeImpl(Native Method) at java.lang.J9VMInternals.initialize(J9VMInternals.java:194) at com.ibm.sec.iauthz.mcc.engine.MCCStoreHandler.(MCCStoreHan dler.java:479) at com.ibm.sec.iauthz.storage.PolicySet.(PolicySet.java:51) at com.ibm.sec.iauthz.storage.PolicyStore.(PolicyStore.java:6 3) at com.ibm.sec.iauthz.storage.PolicyStorageFactory.getPolicyStore(P olicyStorageFactory.java:40) at com.ibm.sec.iauthz.storage.PolicyStorageFactory.getPolicyStore(P olicyStorageFactory.java:58) at com.ibm.sec.iauthz.mcc.CfgDataProcessingImpl.(CfgDataProce ssingImpl.java:167) at com.ibm.sec.iauthz.mcc.DataProcessingFactory.getCfgInstance(Data ProcessingFactory.java:209) at com.ibm.sec.authz.provider.CommonAuthzPolicyConfiguration. (CommonAuthzPolicyConfiguration.java:125) at com.ibm.sec.authz.provider.CommonAuthzPolicyConfigurationFactory .getPolicyConfiguration(CommonAuthzPolicyConfigurationFactory.ja va:99) at com.ibm.ws.wim.security.authz.jacc.JACCPolicyDefinition.createRo letoPermissionPolicy(JACCPolicyDefinition.java:206) at com.ibm.ws.wim.security.authz.jacc.JACCPolicyDefinition.loadPoli cy(JACCPolicyDefinition.java:175) at com.ibm.ws.wim.security.authz.ProfileSecurityManager.initialize( ProfileSecurityManager.java:186) at com.ibm.ws.wim.security.authz.ProfileSecurityManager.initialize( ProfileSecurityManager.java:138) at com.ibm.ws.wim.ProfileManager.initialize(ProfileManager.java:308 1) at com.ibm.ws.wim.ProfileManager.(ProfileManager.java:195) at com.ibm.ws.wim.ProfileManager.singleton(ProfileManager.java:201) at com.ibm.websphere.wim.ServiceProvider.initialize(ServiceProvider .java:112) at com.ibm.websphere.wim.ServiceProvider.(ServiceProvider.jav a:121) at com.ibm.websphere.wim.ServiceProvider.singleton(ServiceProvider. java:100) at com.ibm.websphere.wim.client.LocalServiceProvider.locateService( LocalServiceProvider.java:295) at com.ibm.websphere.wim.client.LocalServiceProvider.(LocalSe rviceProvider.java:146) at com.ibm.wplc.deploy.tasks.impl.ModifyWIMConfigImpl.getConfig(Mod ifyWIMConfigImpl.java:153) at com.ibm.wplc.deploy.tasks.impl.ModifyWIMConfigImpl.execute(Modif yWIMConfigImpl.java:90) at com.ibm.wplc.deploy.tasks.AbstractBaseAdminTask.executeTask(Abst ractBaseAdminTask.java:495) at com.ibm.wplc.deploy.tasks.AbstractBaseWsAdminWrapperTask.execute Task(AbstractBaseWsAdminWrapperTask.java:301) at com.ibm.wplc.deploy.tasks.AbstractBaseAdminTask.execute(Abstract BaseAdminTask.java:156) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java: 275) at org.apache.tools.ant.Task.perform(Task.java:364) at org.apache.tools.ant.Target.execute(Target.java:341) at org.apache.tools.ant.Target.performTasks(Target.java:369) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1 216) at org.apache.tools.ant.Project.executeTarget(Project.java:1185) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(Defau ltExecutor.java:40) at org.apache.tools.ant.Project.executeTargets(Project.java:1068) at org.apache.tools.ant.Main.runBuild(Main.java:668) at org.apache.tools.ant.Main.startAnt(Main.java:187) at org.apache.tools.ant.Main.start(Main.java:150) at com.ibm.wps.config.ConfigEngine.process(ConfigEngine.java:861) at com.ibm.wps.config.ConfigEngine.main(ConfigEngine.java:236) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor Impl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod AccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:263) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor Impl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod AccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at com.ibm.wps.config.launch.WpsConfigLauncher.process(WpsConfigLau ncher.java:243) at com.ibm.wps.config.launch.WpsConfigLauncher.main(WpsConfigLaunch er.java:459) LOCAL FIX: none PROBLEM SUMMARY USERS AFFECTED: WebSphere Process Server v6.2.0.x users running ConfigEngine during the Portal configuration when WebSphere Process Server is installed. PROBLEM DESCRIPTION: An incorrrect properties file is loaded during portal configuration. RECOMMENDATION: None A conflict on the classpath exists when running ConfigEngine during the Portal configuration when Process Server is installed. PROBLEM CONCLUSION: Applying this interim fix will resolve the issue reported in this APAR. 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: