[midPoint] Migrating to another database

[Pavol Mederly]

I'm sorry I have to clarify myself: I meant exporting via midPoint, i.e. 
"Export all objects" in Configuration -> Repository objects.
You can then inspect generated XML and do any fixes you need manually 
(if needed).

Before importing, I'd delete automatically generated connector objects 
from MariaDB, so the only ones left would be imported ones.

Best regards,
Pavol

On 04.08.2016 9:11, Pavol Mederly wrote:
>
> Hello Aivo,
>
>
> one of possible ways is to export all objects from H2 and re-import 
> them to MariaDB.
>
> Beware of encrypted data compatibility - it's probably good idea to 
> copy midPoint keystore before first start of midPoint in MariaDB.
>
>
> Best regards,
>
> Pavol Mederly
> Software developer
> evolveum.com
> On 04.08.2016 9:08, Aivo Kuhlberg wrote:
>>
>> I have so far used midPonit with embedded H2 database but now plan to 
>> move to MariaDB. I can set up my test environment again from scratch 
>> but it would be much easier to migrate existing data to another 
>> database. Is there a (not too complicated) way to migrate current 
>> midPoint data to another database?
>>
>>
>> Thanks,
>> Aivo Kuhlberg
>>
>>
>> ------------------------------------------------------------------------
>> Käesolev e-kiri võib sisaldada asutusesiseseks kasutamiseks 
>> tunnistatud teavet.
>> This e-mail may contain information which is classified for official 
>> use.
>>
>>
>> _______________________________________________
>> midPoint mailing list
>> midPoint at lists.evolveum.com
>> http://lists.evolveum.com/mailman/listinfo/midpoint
>
>
>
> _______________________________________________
> midPoint mailing list
> midPoint at lists.evolveum.com
> http://lists.evolveum.com/mailman/listinfo/midpoint

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20160804/cd135277/attachment.htm>