Note | ||
---|---|---|
| ||
The content below is for Apache Syncope <= 1.2 - for later versions the Reference Guide is available. |
Table of Contents | ||
---|---|---|
|
Introduction
Almost every configurable aspect of a running Apache Syncope instance is contained into the internal storage: attribute schemas, connectors, resources, mapping, roles, synchronization tasks and other parameters.
...
An option is clearly acting at low level by empowering DBMS' dump & restore capabilities, but what if poor developer is running MySQL (or even in-memory H2) while sysadmin features Oracle?
Export
Click on the Configuration icon at top, then to the rightmost icon on the tab row: you will be prompted for downloading a file named content.xml
.
You can also get this file via CLI.
Import
Basically, all you need to do is replace local content.xml
with the one exported as explained above; but where is this content.xml
located at?
core/src/test/resources/content.xml
for embedded modecore/src/main/resources/content.xml
for real environmentswebapps/syncope/WEB-INF/classes/content.xml
from the Apache Tomcat directory, for standalone distribution
Gotchas
Wipe existing content
When not running in-memory H2, internal storage's content must be wiped before starting Apache Syncope, otherwise content.xml
will be just ignored.
Check core-persistence.log
for message
Code Block |
---|
Empty database found, loading default content
|
If the internal storage is not empty, instead, you will get
Code Block |
---|
Data found in the database, leaving untouched
|
MySQL and lower case table names
...
On some platforms (namely, Mac OS X) MySQL is configured by default to be case insensitive: in such cases, you might want to edit {{/etc/my.cnf
}} file and add the following line into {{\[mysqld
\]
}}:
Code Block |
---|
lower_case_table_names=1
|
OpenJPA sequences
In exported content.xml
you might find some elements like as
Code Block |
---|
<OPENJPA_SEQUENCES_TABLE ID="SEQ_ConnInstance" SEQUENCE_VALUE="1100"/>
|
...