The Grouper registry can be exported to XML and imported back in another database. There are a few variations on this.
- Export / import Grouper MySQL database
- Grouper database migration utility
- Grouper export to a GSH script
XML Import / Export for Grouper
As of v2.1, not all features are exported/imported with this tool. Examples are external subjects, entities, point-in-time auditing, etc. This can be used to make a backup for upgrades, but shouldn't be used to migrate from one version to another during upgrades.
As of Grouper v1.4.0 the invocation of these tools has moved from Ant to gsh (GrouperShell):
Grouper includes XML import / export tools. Exported XML may be used for:
- provisioning to other systems
- switching database backends - including to upgraded schemas (required by new Grouper API versions) in the same database
- moving or syncing a folder of grouper to another environment
Imported XML may be used for:
- loading - adding to or updating existing Stems, Groups and Group Types. Whole or partial Grouper registries can be exported, and subsequently imported at a specified Stem (or the Root Stem if not specified) in the new instance.*
- initializing a new, empty registry to a known state - useful for demos, testing and system recovery
In general, exported data can be imported into the same Grouper instance it was exported from**, or a different instance. Stems and Groups and Group Types will be created, if not already present, or updated if they already exist (depending on import options provided).
Any tool which can create XML, in the correct format, can be used as a loader.
*To successfully load Subject data, the new Grouper instance must be configured with the same Subject Sources. The export tool does not export Subject registries. Subjects which cannot be resolved will be logged, but otherwise ignored.
**The initial version of the import tool did not maintain system attributes i.e. uuid, date created etc. Now all metadata about the object is kept in sync, though if an object already exists, it will use the existing uuid, not the imported uuid.
Note: you should set include/exclude and require groups off in grouper.properties when importing:
Since so many new columns and tables have been added to Grouper especially in 1.5, and since exporting/importing these with the current design would be difficult, we decided to rewrite the Grouper export/import. It will have these differences from the current version
- Doesn't store the XML document in memory (SAX) for good memory performance
- Doesn't manually marshal XML (will use xstream)
- Will keep logic in beans (more object oriented)
- Handles all data columns in the database (e.g. uuids). Note, in import will need to lookup the business key to see if there is a different UUID, and maintain the existing UUID if it exists, will not change any UUIDs on import
- Handles all the new tables (e.g. new attribute framework, though I didn't think we need to import the "set" tables, e.g. groupSet. We can calculate that stuff after import. This is a tradeoff between size of file, speed of import (probably faster to export the "set" tables), and data integrity (probably better to recalc all after import)
- Sorted output so XML can be diffed, though uuids might make differs thing there are diffs, when really there might not be
- The export settings will be at the top of the export file (i.e. are exporting the entire registry?)
- Basic features will be implemented in the first pass, then we can do the advanced features. e.g. we will export all the data as GrouperSystem
- The XML export is not intended to be used for reporting or provisioning, web services and SQL can be used for that
- It's not really possible to have a readonly import mode without a huge transaction that will bog down the db
- Should have good logging (depending on level), and should print to stdout status periodically. i.e. try to say how many records have been processed and how many left to go (will need a preparse for this). For example every 30 seconds.
- The table: grouper_ddl will not be exported/imported, since that should be tied to the ddl in the schema
- The subject and subjectattribute tables will not be exported/imported, since they aren't really a part of grouper, just the quick start
- Effective membership create and last update date can be calculated from the repository, but will not be in the first pass (these are some of the group_set records). Same for other _set tables like actions, permissions, roles (well, the immediate part of the tables will be exported)
- Privileges (e.g. admin or read on a group) will be exported from the memberships table if they are there. If you are not using the default privilege interface in grouper.properties, then you need to export/import yourself
- It's assumed that composite memberships don't need to be exported since the composite table is exported, and if the composite is added, the API will add the membership data
- Should audits be handled as they are now, as a separate file? These are in the audit file so they are handled consistently, and foreign keys get translated
- Should change log be exported/imported? Currently assuming no
- Should audit logs be inserted when importing? Assuming will check for uuid of record, if not found, insert
- Assuming that the legacy imports will still work, at least for a little while longer (at least they will work in v1.6). just use -xmlimportold, or -xmlexportold
- Need to update docs
The XML Import Export, described above, is for importing/exporting the registry as an admin.
There are also import/export procedures available for a group owner to import/export/change the membership of their group.
To learn about that, see the Lite UI Training Video - Part 2