I am preparing myself for an engagement in a customer's site tomorrow to patch their OpenAM deployment from 10.0.0 to 10.0.2.
The upgrade process is fairly easy. But of course, remember to backup, backup, and backup! You never know what will happen.
Clicking on "Save Report" will download a OpenAM Upgrade Report on the activities that the upgrade is going to take.
OpenAM Upgrade Report
Existing Version: OpenAM 10.0.0 (2012-April-13 10:24)
New Version: OpenAM 10.0.2 (2013-December-12 18:38)
Services Upgrade Report
Added attribute openam-auth-ldap-operation-timeout
Added attribute openam-auth-ldap-heartbeat-interval
Added attribute openam-auth-ldap-heartbeat-timeunit
Removed attribute iplanet-am-auth-ldap-server-check
New Sub Schemas
Server Default Upgrade Report
* attr name: com.sun.identity.authentication.multiple.tabs.used : value: false
* attr name: com.iplanet.am.version
old value: OpenAM 10.0.0 (2012-April-13 10:24)
new value: OpenAM 10.0.2 (2013-December-12 18:38)
* attr name: com.sun.identity.authentication.mutiple.tabs.used
Based on the Upgrade Report above, the embedded OpenDJ which is used as the default configuration store will update a value in the LDAP attribute called "com.iplanet.am.version".
I found there is a .version text file in the file system.
Before the upgrade, the content within the .version was: OpenAM 10.0.0 (2012-April-13 10:24)
After the upgrade, nothing was changed. But everything runs fine.