Skip to end of banner
Go to start of banner

Backup and restore

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

This page applies to upgrades from JJUPIN 3.0 or lower. Starting with version 4.0.0, all persistence uses Active Objects and does not require having the plugins installed when importing a backup to a new syst


At Restore: install first the plugins


Mundane operations as backup and restore may pose some problems to the unsuspecting JIRA administrator. Since all the Kepler plugins create some tables in the JIRA schema  - we created this mechanism long before Active Objects was introduced into Atlassian's framework - you need to take some precautions at restore.

Specifically, at restore you need to create the tables used by our plugins. You do not need to copy schema from the previous JIRA or fill it with data, you just need to simply install the plugins into JIRA before restoring (enabling the plugins would create the needed tables).

JJUPIN has two dependencies:

  1. katl-commons (core support)
  2. warden (used for licensing)

For reference, these are the tables created by each add-on

PluginTables
JJUPIN

krunnablesils

krssecurity

klistenersils

jjlf_config

jjlf_project

jjlf_category

katl-commons

kplugins

kpluginscfg

kissuestate

kstatevalues

warden-


  • No labels