Viz Multichannel
Version 4.0 | Published January 23, 2019 ©
Integration module for Harris ADC
The integration for Harris uses the direct integration architecture type as explained in the section Direct Integration Architecture Overview. The integration is based on the Harris ADC-12 API.
Before using the integration module, in most cases, the Page Content Filling Service must be installed.
Note: Harris is now renamed Imagine Communications (http://www.imaginecommunications.com), this documentation currently uses the old Harris brand name.
Installing the Harris Integration Module
-
To install the Harris Integration locate the VizMultichannel_HarrisIntegration_VERSION.msi installer where VERSION is the version/release/build number. Double click the msi-file to start the installation.
-
Press Next to start the installation
-
If required change the installation directory. This is normally not required nor recommended. Press Next
-
Press the Install button and wait for the installation to finish.
Configuration and Startup
-
To start and configure the integration module for Harris, click the Windows Start menu and open the program by browsing to All Programs > Vizrt > Viz Multichannel > Viz Multichannel - Harris Integration
The Harris integration module will display the Configuration and start window:
|
Detail |
Description |
|
Profile Name |
You can have multiple settings profiles. If you run multiple instances of the Harris Integrations service is it suggested to do configuration changes from one and only one instance to avoid overwriting configuration changes |
|
ADC List Service |
Address of the ADC List. Change the ip as required. Ask your Harris system administrators for the correct address |
|
ADC List Server Name |
The ADC List Server name that should be used in the integration |
|
List Number |
Sequence of list that should be used in the integration. Example: If the actual Harris system has three list-names called "Playlist 1", "Playlist 2", "Playlist 3" and we want to use "Playlist 2" for the integration, specify 2 as the list-number. |
|
Integrations Hub Address |
Specify the URL of the REST service. Note: You can browse to this URL with a browser to see that the Integrations Hub is installed and working. Expected result answer is: Integrations Hub |
|
MCP Channel Name |
The channel name you have defined in Multichannel that should be used with this direct integration module |
|
MCP Playlist Name |
The name of the playlist you want to sync data with. The format of playlist name is [dd_MM_yyyy] and you can also input "continuous" or "running_playlist". Use the playlist name *running_playlis*t to sync data with the current running playlist |
|
Force Creating Video On Group |
Enable the application to use Media Name to search for videos in Viz One and add to an event. For this feature to work, integration with Viz One needs to be enabled in Multichannel |
|
Use Universal Sercom Driver Name |
If checked, Harris Integration will activate the Universal Sercom Driver Name and in doing this also Macro Name in the process |
|
Universal Sercom Driver Name |
This ID must match the ID column in Harris Automation. Ask your Harris administrator for this information |
|
Macro Name |
Prefix of page-name information from Harris Automation |
|
Log Mode |
Enable or Disable log messages. Verbosity can be specified as Off (no logs), Basic or Full. The Log and Error Log files will normally be located in %ProgramData%\Vizrt\Multichannel\HarrisIntegration. You can also open the log directories in Windows Explorer by pressing Show log folder or Show error folder |
|
Code Page |
The Description and CompileId fields returned from the Harris system are converted according to this defined code page. |
-
When all the appropriate setting are configured press Save
-
Press START.
Pushing Optional Metadata from Harris to Multichannel
ADC systems using the LST12 format can optionally use the generic Harris “Data” field (max 4096 characters) to push meta-data information to Multichannel. If the Harris Data-field contains entries of type “value=somedata<CRLF>” (or several formatted as “value1=somedata<CRLF>value2=somemoredata<CRLF>” etc) Multichannel will parse these entries and if a valid combination fieldname=value is found push this payload to the Integrations Hub.