Hi Colm, Massimiliano's answer is the best one and the way to follow. I add this only for completion and to give visibility to a new technology. In your case another approach could be the docker one. You could have on the same machine two instances of docker running the same syncope with the same configuration (same port, datasource, etc.) and "bypass" other supplementary configuration. I mean simple standalone configuration. These instances may be attacched to another docker instance acting as database. Obviously you have to bind docker instances on different ports on localhost as you did. To have more info on how to run syncope in docker please refer to [1]. Syncope with docker is experimental and maybe it's not so easy to set-up, and maybe some docker (and docker-compose) notions are needed. Cluster has not yet been attempted :) but I think it could be an option for you. [1] http://blog.tirasa.net/apache-syncope-with-docker.html
Best regards, Andrea Il 06/gen/2016 01:58 PM Colm O hEigeartaigh <[email protected]> ha scritto: > > > > > > > > > Hi all, > > > > > > I want to set up a trivial Syncope cluster on my machine (to test a > > > CXF-based client using CXF's failover feature). I had thought of just > > > setting up two Tomcat instances on different ports using a shared H2 > > > database file sitting on the hard drive. > > > > > > Is it still necessary to set a value for "openjpa.RemoteCommitProvider" > > > as per: > > > > > > https://cwiki.apache.org/confluence/display/SYNCOPE/Setup+a+Syncope+cluster > > > > > > ? If so how does it work when I have two instances on the same machine, > > > and presumably sharing the same port? Or is this whole approach invalid? > > > > > > Thanks, > > > > > > Colm. > > > > > > -- > > > Colm O hEigeartaigh > > > > > > Talend Community Coder > > > http://coders.talend.com
