Saplo Semantic Feedback Changelog Daemon Installation

This will install the feedback loop to Saplo. It is based on the changelog daemon framework that needs to be installed first.

Installing the Saplo Semantic feedback changelog daemon agent involves the following steps:

Unpack the changelog daemon distribution in an appropriate location
Start the daemon at least once with the following command
```
$ java -jar changelog.jar
```
This will create a few directories that you will need, and create some files you need to edit
You will now need to edit the .daemon-conf/Daemon.properties file

There are properties you will need to change in this file:
url
This is the URI to the changelog for your installation. For example:
```
url=http://editorial-host-ip-address/webservice/escenic/changelog/publication/publicationId
```
Where editorial-host-ip-address is the host name of IP address of your editorial-host, and publicationId is the publication id of the publication you will provide feedback to Saplo from.
username

The username of the user that will be used to log into the webservice to get access to the changelog

password

The password for the above user
You will now have a configured changelog daemon ready to get an agent to run in it.
You will now need to copy the content of /opt/escenic/engine/plugin/semantic-saplo/misc/changlog/lib into into the empty daemon-install-dir/lib directory.
Issue the following command that will create directories
```
$ mkdir -p classes classes/com/escenic/daemon/
```
In order to use Saplo you must set up an account. The log-in credentials for this account must then be added to a configuration file so that the Saplo Semantic changelog daemon can use the account. To set up the required log-in configuration:
1. Visit http://www.saplo.com and set up an account.
2. Create a configuration file by copying /opt/escenic/engine/plugins/semantic-saplo/misc/example/SaploFeedbackAgent.properties to your newly created directory:
```
$ cp /opt/escenic/engine/plugins/semantic-saplo/misc/example/SaploFeedbackAgent.properties \
      classes/com/escenic/daemon/
```
3. Open your configuration file for editing.
4. Uncomment the property assignments in the file and enter the API key, secret key and collection id supplied by Saplo:
```
apiKey=saplo-api-key
secretKey=saplo-secret-key
collectionId=collectionId
```
5. Create a configuration file by copying /opt/escenic/engine/plugins/semantic-saplo/misc/example/CacheManager.properties to your newly created directory:
```
$ cp /opt/escenic/engine/plugins/semantic-saplo/misc/example/CacheManager.properties \
      classes/com/escenic/daemon/
```
6. Open your configuration file for editing.
7. The schemes of the Content Engine tag structures that you want to be mapped to the Saplo categories:
```
category.person=tag:person@example.com,2011
category.organization=tag:organization@example.com,2011
category.location=tag:location@example.com,2011
category.unknown=tag:unknown@example.com,2011
category.url=tag:url@example.com,2011
```
  The Content Engine tag structures you map on to Saplo categories must exist (that is, they must be defined in the Content Engine). Tag structures are defined using the escenic-admin web application. For details, see Create a Tag Structure.
8. Now stuff should just work. Start the daemon with
```
$ java -jar changelog.jar
```
  and watch it run. It might be a good idea to add it to the start-up script of your server.

This is a note about please read more about all this in the changelog daemon documentation..