You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@syncope.apache.org by "Holloway, Dan G." <DA...@leidos.com> on 2019/11/14 16:59:46 UTC
Syncope configuration/server replication inquiry
Good Afternoon,
I have a question about how to best replicate an entire Syncope configuration (to include schemas) on one server to another Linux server with minimal involvement. With that, I did read in the Syncope 2.1.5 reference guide in section 4.6.8 (Deal with internal storage export - import) about making use of a curl command to export the MasterContent.xml file and replacing (importing) the file in a particular directory on the destination server. Other than actually creating an instance of Syncope on the destination server, would the placement of the MasterContent.xml file (as mentioned above) indeed be all one has to do in order to stand-up another Syncope instance with the same configuration on another server? If not, would you please identify what would have to be done in order to replicate an entire Syncope configuration on another server? If additional actions are necessary, would you please also include any relevant APIs or other commands?
Your guidance in this matter would be greatly appreciated. Have a great day.
Very Respectfully,
Dan Holloway
RE: EXTERNAL: Re: Syncope configuration/server replication inquiry
Posted by "Holloway, Dan G." <DA...@leidos.com>.
Hello Francesco,
Thank you for the help!
Regards,
Dan H.
From: Francesco Chicchiriccò <il...@apache.org>
Sent: Friday, November 15, 2019 2:20 AM
To: user@syncope.apache.org
Subject: EXTERNAL: Re: Syncope configuration/server replication inquiry
On 14/11/19 17:59, Holloway, Dan G. wrote:
Good Afternoon,
I have a question about how to best replicate an entire Syncope configuration (to include schemas) on one server to another Linux server with minimal involvement. With that, I did read in the Syncope 2.1.5 reference guide in section 4.6.8 (Deal with internal storage export - import) about making use of a curl command to export the MasterContent.xml file and replacing (importing) the file in a particular directory on the destination server. Other than actually creating an instance of Syncope on the destination server, would the placement of the MasterContent.xml file (as mentioned above) indeed be all one has to do in order to stand-up another Syncope instance with the same configuration on another server? If not, would you please identify what would have to be done in order to replicate an entire Syncope configuration on another server? If additional actions are necessary, would you please also include any relevant APIs or other commands?
Hi,
exporting the MasterContent.xml file from one instance and placing it into another instance's conf directory (say /opt/syncope/conf/domains by default) is exactly what is needed to replicate configurations from one environment to another; beware that such two Syncope instances must be exactly equal (including connector bundle versions), best if built from same sources.
Also, please don't forget that, in any case, MasterContent.xml is bootstrapped into the internal storage only if the latter is empty, e.g. was not already inited by Syncope.
In case you don't want to erase the target Syncope instance's storage, there is no alternative than exporting the needed configurations via REST from source and importing via REST into the destination (you can use Swagger UI for that if it comes handy).
HTH
Regards.
--
Francesco Chicchiriccò
Tirasa - Open Source Excellence
http://www.tirasa.net/
Member at The Apache Software Foundation
Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail
http://home.apache.org/~ilgrosso/
Re: Syncope configuration/server replication inquiry
Posted by Francesco Chicchiriccò <il...@apache.org>.
On 14/11/19 17:59, Holloway, Dan G. wrote:
>
> Good Afternoon,
>
>
>
> I have a question about how to best replicate an entire Syncope configuration (to include schemas) on one server to another Linux server with minimal involvement. With that, I did read in the Syncope 2.1.5 reference guide in section 4.6.8 (Deal with internal storage export - import) about making use of a curl command to export the MasterContent.xml file and replacing (importing) the file in a particular directory on the destination server. Other than actually creating an instance of Syncope on the destination server, would the placement of the MasterContent.xml file (as mentioned above) indeed be all one has to do in order to stand-up another Syncope instance with the same configuration on another server? If not, would you please identify what would have to be done in order to replicate an entire Syncope configuration on another server? If additional actions are necessary, would you please also include any relevant APIs or other commands?
>
>
Hi,
exporting the MasterContent.xml file from one instance and placing it into another instance's conf directory (say /opt/syncope/conf/domains by default) is exactly what is needed to replicate configurations from one environment to another; beware that such two Syncope instances must be exactly equal (including connector bundle versions), best if built from same sources.
Also, please don't forget that, in any case, MasterContent.xml is bootstrapped into the internal storage only if the latter is empty, e.g. was not already inited by Syncope.
In case you don't want to erase the target Syncope instance's storage, there is no alternative than exporting the needed configurations via REST from source and importing via REST into the destination (you can use Swagger UI for that if it comes handy).
HTH
Regards.
--
Francesco Chicchiriccò
Tirasa - Open Source Excellence
http://www.tirasa.net/
Member at The Apache Software Foundation
Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail
http://home.apache.org/~ilgrosso/