MOS Gateway Configuration File
83
The <ncs> Group
<ncs>
<ncsID>NCS_ID_GOES_HERE</ncsID>
<host>HOST_GOES_HERE</host>
<AllowReplication>ALLOW_YESNO</AllowReplication>
<ReplicationUsername>USER_GOES_HERE</ReplicationUsername>
<ReplicationPassword>PUT_PASSWORD_HERE</ReplicationPassword>
</ncs>
The
NCS_ID_GOES_HERE
should be changed to the NCS ID of the
iNEWS Server to which devices will be replicating MOS
objects—typically, this ID is identical to the iNEWS Server’s host name.
The
HOST_GOES_HERE
should be changed to the network host name of
the iNEWS Server to which devices will be replicating MOS objects.
Verify that the server with this host name can be pinged from the MOS
Gateway Server.
The
ALLOW_YESNO
should be changed to
YES
if devices are to replicate
data to queues on the newsroom computer system. If this line does not
appear in the configuration file, the default is
YES
. If set to
NO
replication
is prevented and MOS objects are dropped at the MOS Gateway.
The
USER_GOES_HERE
should be changed to the User ID that the
replication service will use to replicate MOS objects to the iNEWS Server.
This user must exist on the newsroom computer system and have write
permissions to the queues to which the devices will replicate their data.
The
PUT_PASSWORD_HERE
should be changed to password set for the
user identified on the
<REPLICATIONUSERNAME>
line. It must also
match the one set for that user on the newsroom computer system.
n
For more information on configuring the iNEWS newsroom computer
system to support MOS replication, see
“Configure iNEWS for MOS
Replication (Optional)” on page68
.
Summary of Contents for iNEWS
Page 1: ...Avid Technology Inc MOS Gateway Installation Operations Manual Version 2 0 ...
Page 6: ...6 ...
Page 12: ...12 ...
Page 76: ...Chapter 4 76 ...
Page 98: ...Chapter 5 98 ...
Page 104: ...Chapter 6 104 ...
Page 116: ...Appendix A 116 ...
Page 130: ...Appendix B 130 ...
Page 150: ...Index 150 ...
Page 152: ... 152 Reader s Comments ...