Sync Module Parent Server Setup
You set up a server as a parent server by adding child servers to it via sync configuration.
On the Parent server, click Add Child Server on the Configuration page:
Choose a nickname for the child server, this does not have to match what you have stored as the "name for current server" on the child server.
Copy/paste the UUID from the child server (see child server setup)
This can be put in later, but should be set before sync is ever "turned on".
Alternatively, if you use the same username/password as you define next on the child server, this gets filled in automatically the first time you sync from child to parent
Make a new and unique-to-this-child-server username/password that will be created on this parent server for the child server. This is used on the child server to fetch data from the parent.
"Send info to administrator" is not a working feature yet
"Download data backup file" will make an ajax call to zip up the current server's database for sending to the child server. You can do this now, or save the current child and then click the "download" button.
You will upload this zip file to the child when defining the parent server over there.
Alternatively, you can initiate the zip and transfer over the web from the child server when defining the parent server there.
Under "more options": You can optionally choose which java classes to not send to this child server. (or you can globally set this up at the config current server page.) By default, all compatible objects are sent to the child except for global properties.
(Back to Sync Module home page)
The database that you use for the child server should be copied as CLOSE to the time you create the child in the sync admin pages as possible.
Any changes made to the central server between the time you copy the database and when you add the server here will not propagate. You will need to "backport" changes using the backporting section of the Maintenance sync admin page.