|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (3)
View Page History
...
{pop-away:metadata | comments | children | labels} In the Section [Galicaster Configuration] you will find a description of all section of {{conf.ini}} file.
h6. 5.\- Running
h6. 5.\- Opencast Matterhorn connection
One of the key features of Galicaster is the connection to de publishing platform. Then it's important to your configuration that your Galicaster unit is working as Matterhorn Capture Agent. Some tips to do so:
One of the key features of Galicaster is the connection to de publishing platform. Then it's important to your configuration that your Galicaster unit is working as Matterhorn Capture Agent. Some tips to do so:
* Your Galicaster unit need access to your Matterhorn Core network.
* Use a valid *host* URL. The IP address is suitable too.
* Include the port on the URL, if it's not a default one (for instance host:1234)
* Your Matterhorn account should allow Digest, a regular account won't work.
* Remember to activate the connection (config file, section _ingest_, value_ active_).
* A wrong workflow will raise an error, so check it too.
* Once running, check if your Galicaster unit is registered as a Capture Agent, on the admin tools of the Matterhorn worker.
** The log (in /tmp/galicaster.log) would record if any trouble connecting to the Matterhorn server, too.
If your Galicaster is registered as a Capture Agent you should be able to receive the scheduled recording, if any, and ingest whatever you want. If not, review all the steps above and retry.
h6. 6.\- Running
* Use a valid *host* URL. The IP address is suitable too.
* Include the port on the URL, if it's not a default one (for instance host:1234)
* Your Matterhorn account should allow Digest, a regular account won't work.
* Remember to activate the connection (config file, section _ingest_, value_ active_).
* A wrong workflow will raise an error, so check it too.
* Once running, check if your Galicaster unit is registered as a Capture Agent, on the admin tools of the Matterhorn worker.
** The log (in /tmp/galicaster.log) would record if any trouble connecting to the Matterhorn server, too.
If your Galicaster is registered as a Capture Agent you should be able to receive the scheduled recording, if any, and ingest whatever you want. If not, review all the steps above and retry.
h6. 6.\- Running
Galicaster Class is launched with the command:
...