Data Storage Considerations
...
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.
Step 1: 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 modifying the rdbm.properties file to store the events to a different database, perform either of the following:
...
...
...
Code Block | ||||
---|---|---|---|---|
| ||||
##### 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} |
Step 2: After modifying the rdbm.properties file to store the events to a different database, perform either of the following:
ant initdb
(BEWARE: performing this command will re-initialize your entire database, use with caution. )ant db-hibernate-raw-events
and/orant db-hibernate-aggr-events
Persistent Event Filtering
...
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
...