Grass Valley NewsBrowse Desktop Browsing System Installation v.2.7 - Manual (Page 30)

30 NewsBrowse Installation and Configuration Guide December 16, 2004
Chapter 3 Configuring the NewsBrowse System
MDI naming convention
You should use a consistent naming convention for the Managed Device Interfaces
(MDIs) in the system. The NewsBrowse system manages a device through an MDI.
Each type of device has its own MDI. The MDI software component usually is not
hosted on the same machine that it manages. The following table illustrates a
suggested convention.
NOTE: If you are exporting NewsBrowse EDLs to NewsEdit, the NewsEdit
workstation must be able to resolve the Profile MDI name (present in the EDL) to
the IP address of the Profile XP system to which the MDI connects. You can do this
by either (a) mapping the MDI name to the Profile IP address in the NewsEdit
workstation’s host table, or (b) by naming the Profile MDI name the same as the
Profile host name.
Services naming convention
Similar to MDIs, you need to have a naming convention for the Ingest Control service
and the Proxy Transfer service. These services run on encoders, so the naming
convention should help you differentiate between the service itself and the host (table)
name of the encoder on which it runs. The following table illustrates a suggested
convention.
MDI type MDI name(s) Comments
Proxy PROXY1 There is but one Proxy MDI in the system. It manages the
storage locations on all the NAS machines.
Profile SAN1 Manages the one designated Profile on an Open SAN.
PROFILE1, PROFILE2,
PROFILE3,… Manages a stand-alone Profile system.
NTFS NTFS1 There is but one NTFS MDI in the system. It manages NTFS
storage on one or more machines—typically the server and the
NAS machines.
Avalon, FlashNet,
DIVA ARCHIVE1 Manages the archive device.
Service type Service name(s) Comments
Ingest Control INGEST-CH1, INGEST-CH2,
INGEST-CH3 The Ingest Control service runs on single-channel
encoders. Enumerate in parallel with the host (table)
names of the encoders.
Proxy Transfer ADV1, ADV2, ADV3 For Proxy Transfer service running on Advanced
encoders, use this naming convention. Enumerate in
parallel with the host (table) names of the encoders.