Clean up events

This guide will walk you through the process of cleaning up events stored in database which allows to minimize it's size.

Prerequisites

To successfully complete this topic guide you need to ensure following prerequisites:

  • Onegini IdP instance must to be running, for the sake of this guide we assume it's available under http://dev.onegini.me/idp-core address
  • access to the Onegini IdP admin console

Introduction

Event cleanup consist of two steps - migration and database cleanup.

Migration

Before cleanup can be applied it requires to regenerate data required by Onegini IdP components. Process should be started manually from the admin panel in Event cleanup tab. Operation itself is sensitive so it should be started while application is not in a high usage. Depending on how many data needs to be regenerated it can be long running operation (up to 24 hours). After operation has been completed appropriate information will be shown in the user interface and it won't be possible to start migration once again.

It is one-time use operation - after having migration completed it won't be possible to run it again.

Cleanup

Not yet available

Having data migrated it is possible to constantly remove unnecessary data from database. The operation can be configured from the same admin panel tab as migration. In opposite to migration it is a cron job that deletes data based on definition. For example to remove events once a day at 4am it should have value 0 0 4 * * ?.