1.3 User Preference Persistence

Oracle VM Manager is designed to store user preferences so that they are persistent for a user across successive sessions. The data for these preferences is stored within the Oracle VM Manager database and are related to the internal user ID associated with a particular set of login credentials. This design ensures that these preferences are persistent across sessions, regardless of the browser or client system used to acess the Oracle VM Manager Web Interface. Preferences that are stored in this way include accessibility preferences as described in Section 1.4, “Oracle VM Manager Accessibility Features”; and parameters that control the views presented on the Health tab, as described in Chapter 2, Health Tab. A summary of the preferences that are stored is presented in the following list:

  • Health – Status Overview – Number of Columns

  • Health – Status Overview – Refresh Interval

  • Health – Status Overview – Order By

  • Health – Status Overview – Server Processor %

  • Health – Status Overview – Server Memory %

  • Health – Status Overview – VM Processor %

  • Health – Error Conditions – Refresh Interval

  • Health – Error Conditions – Include Acknowledged

  • Health – Statistics – Refresh Interval

  • Accessibility – Screen Reader

  • Accessibility – High Contrast

  • Accessibility – Large Fonts

These preferences are maintained transparently and are updated when a user modifies any of these options directly within the Oracle VM Manager Web Interface. There is no option to manually edit these preferences directly within the Oracle VM Manager Web Interface.

The Oracle VM Manager Web Interface loads these preference values at login and as components are created in the user interface. This means that if a user is logged in across multiple browsers, changes may not be reflected until a user logs out and back in. Furthermore, in the case that multiple clients make changes to the same preference, the last change made is the one that is persisted.

Preference settings are lost if Oracle VM Manager is reinstalled, even if the database is restored. This is because each preference is associated with an identifier for the associated user account and these identifiers are stored and managed by the underlying WebLogic server software. Preferences are unaffected by a database backup and restore operation.