SSE Proxy Set-up
If you will be using CUE to work with video or audio content instead of or alongside Content Studio, then you will need to add a setting to your Content Engine's SSE Proxy. The Content Engine uses SSE (Server-sent Events) to send information about content changes to CUE clients, so that CUE does not need to poll the Content Engine for changes. The Content Engine sends these SSE notifications via an SSE Proxy, a lightweight web proxy installed somewhere in the network. If you are already using CUE with the Content Engine, therefore, you will already have an SSE Proxy installed in your network. If you are currently in the process of moving to CUE, then you will need to set up an SSE Proxy. For general information about the SSE Proxy and how it is installed and Configured, see SSE Proxy.
In order to be able to work with video or audio content in CUE, you need
to add an extra back-end service definition to the SSE Proxy's
sse-proxy.yaml configuration file. The file will
already contain a back-end service definition for basic
events that should look something like this:
backends: - uri: "http://editorial.example.com:8081/webservice/escenic/changelog/sse" credentials: username: "someuser" password: "verysecret"
All you need to do is add a second service definition with the URI
port should be the same as for the existing
entry, and so should the user name and password. For example:
backends: - uri: "http://editorial.example.com:8081/webservice/escenic/changelog/sse" credentials: username: "someuser" password: "verysecret" - uri: "http://editorial.example.com:8081/webservice/escenic/video/mediaStatusSSE" credentials: username: "someuser" password: "verysecret"