Page Comparison

...

A REST service then receives these JSON requests and updates the wiki accordingly (todo hk: who sets this service up? Does it come with DPOD?). A series of configuration parameters controls where JSON requests are sent, as well as various default values for JSON fields..This REST Service should be implemented by the user . 

There is a reference implementation the demonstrate the REST service and a portal demo - called Service Wiki.

The service wiki is baed based on a Drupal CMS . - This is an open-source (apache license v2).

DPOD provides Reference implementation only, with no maintenance or support.TODO SG: --what do you wnat to add here--I don’t understand how service status or transaction data is update and when, so I didn’t write about it, but we probably should (e.g. “last transaction” field)

A series of configuration parameters controls where JSON requests are sent, as well as various default values for JSON fields.

For newly created services, the process is as follows:

1. A new service is created on a monitored device
2. The DPOD agent polls for the monitored device at fixed, configurable intervals todo hk: i didn't find this.
3. At the next polling interval, DPOD will receive the new service configuration data and create a new JSON request based on it
4. This JSON request is sent to the wiki updating service, which creates a new wiki page for the service.

For services which were changed, the process is as follows:

1. A service configuration is changed on a monitored device
2. At the next polling interval, DPOD receives the changed service configuration and compares it with the last configuration. When it notices the change it creates a new JSON request with the entire configuration data.
3. The JSON request is sent to the wiki updating service. The service then updates the configuration fields which were changed, and skips fields which remained the same.