Data Storage Considerations
The raw and aggregate events databases can take a considerable amount of space. The default configuration is fairly conservative, only retaining 1 hour worth of raw and only aggregating a limited set of time intervals and groups. To make space management and upgrades easier it is recommended to place the raw and aggregate events tables in their own schemas or databases.
DataSource Configurations
To better manage the storage and performance requirements of the raw event and aggregate event data sets these can be moved into their own databases. To configure separate JDBC connection information for these data sets edit uportal-war/src/main/resources/properties/rdbm.properties and change the RawEvents and AggrEvents database configuration. After doing this either ant initdb
or ant db-hibernate-raw-events
and ant db-hibernate-aggr-events
need to be executed to setup the required tables.
##### uPortal Raw Events DB RawEventsJdbcDriver=${environment.build.hibernate.connection.driver_class} RawEventsJdbcUrl=${environment.build.hibernate.connection.url} RawEventsJdbcUser=${environment.build.hibernate.connection.username} RawEventsJdbcPassword=${environment.build.hibernate.connection.password} ##### uPortal Aggregate Events DB AggrEventsJdbcDriver=${environment.build.hibernate.connection.driver_class} AggrEventsJdbcUrl=${environment.build.hibernate.connection.url} AggrEventsJdbcUser=${environment.build.hibernate.connection.username} AggrEventsJdbcPassword=${environment.build.hibernate.connection.password}
Persistent Event Filtering
The default configuration results in all PortalEvents being persisted to the RawEvents database. To exclude certain events filters can be configured in the listenerEventFilters list in uportal-war/src/main/resources/properties/contexts/eventHandlerContext.xml. There is provided support for filtering events by type and by the user the event was generated for.
Purging Persistent Events
The Event Aggregation process also handles purging of aggregated events. The default configuration is to purge raw event data 1 hour after it has been aggregated. This window size can be changed by setting the org.jasig.portal.events.aggr.PortalEventPurgerImpl.purgeDelay property in uportal-war/src/main/resources/properties/portal.properties