Selecting a persistence manager
This topic describes the two types of persistence managers you can use for storing data for alerts and annotations.
When used with alerts, the persistence manager is responsible for storing alert definitions, alerts user preferences, notifications, acknowledgments, and more. When used with annotations, the persistence manager is responsible for storing annotations, user data, attachments, and archive logs. Storage in XML files is the default, but for production environments, storing data in a relational database such as DB2 is recommended. This topic explains the benefits and limitations for each type of persistence manager.
The XML-file persistence manager
Each new project is set up by default to use an XML-file persistence manager. This persistence manager stores data in the file system as a series of discrete XML files. This manager does not guarantee that changes to alerting data are performed in the context of a transaction. Furthermore, any changes saved by one manager are not propagated to other persistence managers unless they are using a shared file system. This manager is, however, a good choice for development environments where transactionality and immediate change propagation are not required. Because this is the default persistence manager, it runs automatically without further configuration. You may, however, choose to edit some of the default project settings related to XML-file storage.
Since the XML-file persistence manager stores data in files there are no maximum limits for any character-based data such as user names, roles, or alerts IDs.
The database persistence manager
The database persistence manager stores data in a central relational database. It guarantees that changes to data are performed in the context of a database transaction and that committed changes are immediately propagated to all portlets that are connected to a database persistence manager configured to access the same central database. This manager is the preferred choice for a production environment.
The character columns in the database tables used by the database persistence manager have been sized to comfortably accommodate the most common application requirements for alerts and annotations. For example, the default maximum size of an alert definition ID is 128 characters while user names and roles have a maximum size of 32 characters. We can review the maximum sizes allocated to various columns by opening in an editor the database creation script for your selected database.
Choosing to use a database persistence manager requires some additional configuration, including setting up a database and changing the default project properties to point to the database and data source you prepare. Parent topic: Setting up dashboard features
Related tasks
Overriding alerts configuration properties
Overriding annotations configuration properties
Setting up a database for a dashboard application
Configuring a database persistence manager
Sharing a persistence manager between projects
Library | Support | Terms of use |
Last updated: Thursday, March 15, 2007 11:57am EST
This information center is powered by Eclipse technology. (http://www.eclipse.org)