Fix (APAR): PM09018 Status: Fix Release: 7.0.0.9,7.0.0.7 Operating System: AIX,HP-UX,IBM i,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: PM09018 Byte size of APAR: 28922 Date: 2010-04-26 Abstract: Tivoli Federated Identity Manager 6.2 will not install on WebSphere Application Server 7.0.0.7-7.0.0.9. Description/symptom of problem: PM09018 resolves the following problem: ERROR DESCRIPTION: Tivoli Federated Identity Manager (TFIM) 6.2 will not install on WebSphere Application Server 7.0.0.7-7.0.0.9. LOCAL FIX: none PROBLEM SUMMARY USERS AFFECTED: IBM WebSphere Application Server users who install IBM Tivoli Federated Identity Manager 6.2 on WebSphere 7.0.0.7-7.0.0.9 PROBLEM DESCRIPTION: Tivoli Federated Identity Manager 6.2 will not install on WebSphere Application Server 7.0.0.7-7.0.0.9. RECOMMENDATION: Install a fix pack or interim fix that contains this APAR. The Tivoli Federated Identity Manager 6.2 product fails to install on WebSphere Application Server 7.0.0.7-7.0.0.9. A call stack similar to the following may be observed: (Feb 9, 2010 3:02:46 PM), Install, com.tivoli.am.fim.installer.ismp50.product.actions.Configuration RepositoryUtils, dbg, File ID: itfim/plugins/com.tivoli.am.fim.osgi.connector_6.2.0.0/META-INF/ MANIFEST.MF File Data: 76541 (Feb 9, 2010 3:02:46 PM), Install, com.tivoli.am.fim.installer.ismp50.product.actions.Configuration RepositoryUtils, dbg, exception: java.lang.NullPointerException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor Impl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod AccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at com.tivoli.am.fim.installer.utils.RuntimeConfigurationManagement ServiceWrapper.putConfiguration(RuntimeConfigurationManagementSe rviceWrapper.java:266) at com.tivoli.am.fim.installer.ismp50.product.actions.Configuration RepositoryUtils.putConfiguration(ConfigurationRepositoryUtils.ja va:176) at com.tivoli.am.fim.installer.ismp50.product.actions.Configuration RepositoryUtils.putConfiguration(ConfigurationRepositoryUtils.ja va:161) at com.tivoli.am.fim.installer.ismp50.product.actions.Configuration RepositoryUtils.putConfiguration(ConfigurationRepositoryUtils.ja va:161) at com.tivoli.am.fim.installer.ismp50.product.actions.Configuration RepositoryUtils.install(ConfigurationRepositoryUtils.java:99) PROBLEM CONCLUSION: The Tivoli Federated Identity Manager 6.2 install uses a Java Runtime Environment(JRE)5 that is included in its product packaging. The WS-Security interface class files included in the com.ibm.wsfp.main.jar file in 7.0.0.0-7.0.0.5, were compiled to the 1.5 target, which enabled them to be loaded by the JRE5 class loader. In 7.0.0.7, they were no longer compiled to the 1.5 target, therefore they could not be loaded by the JRE5 class loader. Since Tivoli Federated Identity Manager 6.2 install loads the referenced jar, its JRE5 class loaded failed to load the jar. The application server is updated to include interface class files from the WS-Security component compiled to the 1.5 target. They can now be loaded by the JRE5 class loader that is included with the Tivoli Federated Identity Manager 6.2 install. Any customer application running within the Application Server will not experience this problem since the Application Server uses the JRE6 class loader. Also, since JRE6 is required for remote Java clients, they should not experience this problem. Please refer to the "List of supported software for WebSphere Application Server V7.0" for more information on the Java runtimes required for WebSphere Application Server V7.0: http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg27012373 The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.11. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 Directions to apply fix: Fix applies to Editions: Release 7.0 _X_ Application Server (Express or BASE) _X_ Network Deployment (ND) 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.ibm.com/support/docview.wss?rs=180&uid=swg21205991 1) If your iFix is delivered as a single file with a .pak extension, Copy the .pak file directly to the maintenance directory. If your iFix is delivered as a single file with a .zip extension, unzip the file into the maintenance directory. 2) Shutdown WebSphere Application Server. Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that maintenance is being applied to. 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 Application Server. Directions to remove fix: NOTE: * The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * 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 Application Server. 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 (PKxxxxx.pak). 6) UnInstall maintenance package. 7) Restart WebSphere Directions to re-apply fix: 1) Shutdown WebSphere Application Server. 2) Follow the Fix instructions to apply the fix. 3) Restart WebSphere Application Server. Additional Information: