These notes assume a multi-server configuration where it matters. There is a 2 way interaction between the calendar server and the sync engine.
...
In localBedework.xml the name should match the name in the Connector Id above. The bwWSDLURI element refers to either the soap wsdl loaded from the remote server or it can be loaded locally. In either case that file must provide the location of the calendar server in the soap:address element right near the end of wssvc.wsdl. That file is deployed as part of the bwxml module. The files is in wildfly-10.1.0.Final/standalone/deployments/bw-xml-3.11.0.ear/bwwsdls-3.11.0.war/synch/wssvc.wsdl. The server location can be set as part of the build process or edited in later (but that will need to be done on each rebuild/redeploy). The build uses the value in the build time property org.bedework.bwsynch.service which is set in .default/cal.properties.
...
- At startup sends a startServiceRequest to bedework
- Bedework sends back a response holding a token
- The connector periodically pings bedework to keep the connection alive. Each time it gets a new (random) token.
- The connector will check each of the subscriptions for changes.
- When changes occur interactions with bedework (updating collections) use the supplied token
When a subscription is created an opaque token
...
is handed over to the connector. This is returned when changes take place. This token actually contains some properties. At the moment these are
- public-admin - true/false
adminCreateEprops - true/false - indicates whether the admin update can create event properties - e.g. location/category/contact. If false they get preserved as x-properties. Only set true for a very trusted source.