Before you Begin

Be aware of the following information before starting the upgrade process:

• See Oracle Waveset 8.1.1 Upgrade for comprehensive upgrade instructions.

• If you upgrade your JDK or JRE, you must use a JDK or JRE supplied by the same vendor as your previous JDK. For example, do not install a Sun JDK if previously you were using a JDK from IBM. If you mix JDKs from different vendors, data encrypted under a previous JDK cannot be read by a JDK from another vendor. (ID-17800)

• Upgrade Identity Manager in the following order:

  1. Upgrade all Identity Manager server instances and Gateway instances

  2. Upgrade all PasswordSync instances

  The 8.1.1 version of Oracle Waveset server provides limited, temporary support for older versions of PasswordSync. This support is provided so that older versions of Identity Manager can continue to run while you upgrade your PasswordSync instances. All instances of PasswordSync should be updated to the same version as the Oracle Waveset server as soon as possible.

• When uninstalling PasswordSync, use the add/modify programs feature from the Windows Control Panel to ensure correct removal. You must reboot after uninstalling.

  When installing PasswordSync, use the appropriate binary file for the operating system on which you are installing. The binary for 32-bit Windows is called IdmPwSync_x86.msi and the binary for 64-bit Windows is called IdmPwSync_x64.msi. After each PasswordSync installation you must reboot.

• Be sure to use only one Oracle Waveset server to import update.xml.

• During an upgrade, only one Oracle Waveset/Sun Identity Manager server should be running. If you start any other Oracle Waveset servers during the upgrade, you must stop and restart those servers before making them available. Note that changes to RepositoryConfiguration do not affect an Oracle Waveset server until you restart that server.

• If the upgrade process fails to log in with the default configurator account and password, the log file logs the error, but does not log anything after the error. (ID-18929)

  The update.xml file is imported during the upgrade process. The import attempts to log in as configurator with the default password. If the login fails, an error is displayed, and the upgrade program prompts you for the correct login information. If you provide the correct information, the upgrade continues. When looking through the log file for the upgrade process, you can see the error message when the default log in fails, but you do not see any further information about the upgrade in the log file. This issue does not affect the upgrade, only the log file.

• If your current Identity Manager installation has a large amount of custom work, consider contacting Professional Services for assistance with planning and executing your upgrade.

• When running Oracle Waveset on multiple physical servers, the servers' system clocks must be synchronized. Each Oracle Waveset server regularly issues a timestamped “heartbeat” to the Oracle Waveset repository. If any server observes that another server's heartbeat is too old (by default five minutes), then it will mark that server as “recovered” and mark all tasks currently executing on that server as terminated. Proper Oracle Waveset operation requires that all server clocks be synchronized to within five minutes of each other, and preferably within one minute. (ID-22418)