Hi Francesco,
Thanks for you reply and suggestions, as always.
I'll do some smoke trials of a fully deployed system and see what I get ;-)
I'd also like to try the simple upgrade you suggest, but as we have done
some pretty funky re-packaging of the syncope
bits to an rpm, containing half-configured connectors and special
default product data (i.e. for adding product RBAC roles +
resourceEntitlements) which are then fully configured by scripts, at
deploy or upgrade time, I'm concerned it may get rather
complex to "industrialise" a further syncope upgarde process into our
current update procedures - I guess I will do some tests.
On 10/12/2013 11:19, Nik wrote:
Hi fellow syncopers,
Looking at the syncope wiki pages I have had a little question on my
mind for a while.
I was wondering how I can upgrade/uodate an embedded syncope IDM from
1.1.2
directly to 1.1.5 or if this is even possible?
The safest path is to perform step upgrades (1.1.2 to 1.1.3, 1.1.3 to
1.1.4, 1.1.4 to 1.1.5).
You might try to perform a single upgrade step, but you can naturally
encounter some unexpected issues.
Would I just simply:
a) recompile my 2 war files (syncope.war & syncope-console.war) at
version 1.1.5using the correct pom.xml.
b) stop my 1.1.2 syncope service
c) change some appropriate files on my embedded syncope 1.1.2:
i.e.
Files affected for 1.1.5
-bash-4.1# find . -name indexes.xml
./syncope/WEB-INF/classes/indexes.xml
-bash-4.1# find . -name rest.properties <----- file not found in 1.1.2
-bash-4.1# find . -name restContext.xml
./syncope/WEB-INF/classes/restContext.xml
-bash-4.1# find . -name syncopeContext.xml
./syncope/WEB-INF/classes/syncopeContext.xml
-bash-4.1# find . -name orm.xml
./syncope/WEB-INF/classes/META-INF/orm.xml
-bash-4.1# find . -name orm.xml.sqlserver
./syncope/WEB-INF/classes/META-INF/orm.xml.sqlserver
syncope/WEB-INF/classes/report
-bash-4.1# ls
report2fo.xsl report2html.xsl staticReportlet2fo.xsl
staticReportlet2html.xsl userReportlet2fo.xsl userReportlet2html.xsl
-bash-4.1#
d) apply all database changes from upgrades [1] to a live syncope
1.1.2 db i.e. upgrade changes: "1.1.2to 1.1.3" & "1.1.3to 1.1.4" &
"1.1.4to 1.1.5"
e) unravel my war files (from step a) above) in the appropriate path,
making sure I don't obliterate certain config files like:
WEB-INF/classes/persistence.properties
WEB-INF/classes/security.properties
etc
f) do a backup as per [2]
g) zip up the deployed syncope IDM into 2 new wars (syncope.war &
syncope-console.war)for safety.
I don't understand why you don't simply
a1) backup syncope.war and syncope-console.war and database (so that
you will always be able to recover from any failure)
b1) upgrade POM files to 1.1.5 in your source tree
c1) add or replace files as per upgrade instructions, again in your
_source tree_
d1) undeploy old syncope.war and syncope-console.war
e1) apply database changes
f1) build your source tree and deploy the updated syncope.war and
syncope-console.war
OR
Is there a better/simpler way?
Of course: pay someone else for this job ;-)
I agree, but unfortunately, I don't have hands on the company purse
strings ;-)
Best Regards,
Nik
Regards.
[1]
https://cwiki.apache.org/confluence/display/SYNCOPE/Upgrade+from+1.1.4+to+1.1.5#Upgradefrom1.1.4to1.1.5-Other
[2]
https://cwiki.apache.org/confluence/display/SYNCOPE/Calling+RESTful+services+from+CLI
