|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (10)
View Page History
...
{pop-away:metadata | comments | children | labels} * Your capture devices are configured as indicated in the [Cookbook|Galicaster:Cookbook].
The installation process consists of six steps: [Install dependencies|#dependences], [check the configuration|#check], [download Software|#download], [configure Galicaster|#config], [check Matterhorn Core connection|#matterhorn] and [test it|#running].
The installation process consists of six steps: [installing dependencies|#dependences], [checking the configuration|#check], [downloading software|#download], [configuring Galicaster|#config], [checking the connection to a Matterhorn core|#matterhorn] and [testing it|#running].
{anchor:dependences}
...{anchor:matterhorn}
h6. 5.\- Opencast Matterhorn cConnection
One of the key features of Galicaster is the connection to the 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 the publishing platform. If you are using Matterhorn as your media publishing and distribution system, you need to configure Galicaster to work as a Capture Agent and connect it to your core machine. Here are some tips to do so:
* Your Galicaster unit needs 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.
* 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.
* Use a valid *host* URL. It may be a fully-qualified name or simply an IP address.
* If your Matterhorn Core is not running in the default port (80), then you need to explicitly include it in the URL (i.e. {{http://<host_name_or_ip>:8080}}).
* The use of the {{http://}} prefix is mandatory.
* You need to use a Matterhorn account which authenticates via Digest (usually, this account is set up in the {{config.properties}} file in your Matterhorn server). A regular account will not work.
* Remember to activate the connection in Galicaster (in the configuration file, section {{ingest}}, value {{active}}).
* A wrong workflow will raise an error in Matterhorn. Please make sure you use a workflow name that exists in the machine you connect Galicaster to.
* Check your Galicaster unit is registered as a Capture Agent in the Admin Tools section of your Matterhorn installation.
** The log (in {{/tmp/galicaster.log}}) will record any problem occurring on the connection to the Matterhorn server.
* If your Matterhorn Core is not running in the default port (80), then you need to explicitly include it in the URL (i.e. {{http://<host_name_or_ip>:8080}}).
* The use of the {{http://}} prefix is mandatory.
* You need to use a Matterhorn account which authenticates via Digest (usually, this account is set up in the {{config.properties}} file in your Matterhorn server). A regular account will not work.
* Remember to activate the connection in Galicaster (in the configuration file, section {{ingest}}, value {{active}}).
* A wrong workflow will raise an error in Matterhorn. Please make sure you use a workflow name that exists in the machine you connect Galicaster to.
* Check your Galicaster unit is registered as a Capture Agent in the Admin Tools section of your Matterhorn installation.
** The log (in {{/tmp/galicaster.log}}) will record any problem occurring on the connection to the Matterhorn server.
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.
If your Galicaster is registered as a Capture Agent you should be able to receive the recording schedule, if any, and ingest any recordings in Galicaster to the Matterhorn Core. If this is not so, please review all the steps above and try again. The logs in Matterhorn and Galicaster will give you the hints to know what is failing.
...