Thanks Francesco.
I guess I'm obliged to use this persistence method to keep my new data.
I have noticed a drop in performance when I do this change (expected but
this is very noticeable).
Is there anyway of getting back to the great perf of the in memory h2 or
is this the price to pay for
persistence?
Also, one puzzle for me (perhaps it is available through hard coding
data at compile time - a guess).
When the syncope standalone1.1.0 is used out of the box there is
persistence for the data it
comes with, obviously, my second thought is it should be possible to
somehow get new data out of volatile
memory to some sort of cache file (so you don't lose data when you stop
the tomcat because it is written to a cache).
On restart of the tomcat the syncope can read this cache back into
volatile memory and hence you keep the great
perf - I'm sure you have thought of this?
rgds,
Nik
On 18/04/2013 10:40, Nik wrote:
Hi Guys,
Call me a twit, if I missed something, obvious ;-)
Hi Nik,
first of all, you are right, what you have found below is true:
in-memory H2 lasts until Tomcat is running.
There has recently been a discussion around this [1], that should have
resulted in updating [2], not yet done.
I am sorry for not making this clear from the documentation: I will
try to update [2] with
1. warning about the volatile persistence
2. instructions about how to turn the H2 configuration into something
persistent
Basically, it is enough to replace
jpa.url=jdbc:h2:mem:syncopedb;DB_CLOSE_DELAY=-1
with
jpa.url=jdbc:h2:syncopedb
in $CATALINA_HOME/webapps/syncope/WEB-INF/classes/persistence.properties
I'll keep you posted.
Regards.
P.S. Please don't hijack other e-mail threads (e.g. reply to existing
e-mails, change subject and body) otherwise our mailing list archives
will go crazy :-)
[1] http://markmail.org/message/o326pp3bioxigl5f
[2]
https://cwiki.apache.org/confluence/display/SYNCOPE/Run+Syncope+standalone+distribution
I installed a standalone 1.1.0 syncope distro - was very impressed.
Started to link it up to my
own ldap service (after downloading an ldap connector and installing
it as described in the doc).
Made quick progress in learning some of the details of how to set-up
ldap resources/connectors, got a bit stuck
with how to get roles propagated through to the ldap server (doc is
not on this, at least for opendj requirements).
Followed the advice from this users group to follow my nose instead
of asking questions too soon.
Noticed that there was a apache ldap resource example already. Used
this as a comparison model (resource) to get IDM role propagation to
my ldap server (resource/connector working - didn't succeed yet, but
worked out that a syncope define IDM role gets propagated at the time
of the "save" of a (new) user to your remote resource ldap, after you
assign that role to the user (still have to
work to do to work out what ldap attributes to set up in the
connector and how to enable that the get propagated to the ldap to
create a group of the same "name" as the role in the backend
ou=groups,o=isp for example, cn=propagatednewrole,ou=groups,o=isp).
***So to cut this long story short*** I decided the restart my tomcat
and whoosh all my resource and connector work was lost! I'm
guessing 1) I have not done something right to save it or 2) this is
a side effect of a demo distro that stores data in H2 ram memory
without syncing it to some sort of persistent storage? Can you please
help me with this as I'm re-doing all my work of the last 3 days
now from scratch :-( and would not like to have it disappear if I
clear my volatile memory.
