Page 1 Avid Technology, Inc. MOS Gateway Installation & Operations Manual Version 2.0...
Page 2 Copyright and Disclaimer © 2003, Avid Technology, Inc. All rights reserved. All Avid products are covered by U.S. and foreign patents, issued and pending. Information in this publication supersedes that in all previo1usly published material. Specifications and price change privileges reserved.
Page 3: Table Of Contents
Chapter 1 Overview of MOS Gateway ........14 MOS Control Workflow .
Page 4 Chapter 6 MOS Gateway Components ....... . . 100 Where to Look For Errors ........100...
Page 5 Appendix B Sample Configuration File on MOS Gateway Servers ... . . 118 Sample Configuration File on iNEWS Servers ....124 Sample /etc/hosts File on iNEWS Servers .
Page 7: Preface
Congratulations on your purchase of iNEWS MOS Gateway, the system that removes barriers between newsroom computing and broadcasting. MOS Gateway uses the MOS protocol as a standard for communications between newsroom computer systems and Media Object Servers (MOS), such as video servers, audio servers, still stores, and character generators.
Page 8: Symbols And Conventions
Troubleshooting Use this manual to prepare for and set up your system on the network, after you have purchased the MOS Gateway components according to iNews requirements and specifications. Before installing any equipment, the site must already have a configured network.
Page 9: Cross References
Symbols and Conventions • Bulleted lists, when the order of primary items is unimportant. Indented dashed lists, when the order of secondary items is unimportant. A single-step procedure or as a list of optional procedures. Look here in the In the margin you will find tips that help you perform tasks more easily and margin for tips and efficiently.
Page 10: If You Need Help
“Click” means to click the left mouse button, usually in response to a dialog box. “Right-click” means to click the right mouse button. If You Need Help If you are having trouble using MOS Gateway, you should: 1. Repeat the procedure, carefully following the instructions provided for the task in this guide.
Page 11: If You Have Documentation Comments
If You Have Documentation Comments If You Have Documentation Comments The Avid Broadcast Technical Publications department continually seeks to improve its documentation. We value your comments about this manual or other Avid-supplied documentation. Send your documentation comments by e-mail to: techpubs_wi@avid.com Include the title of the document, its part number, revision, and the specific section that you are commenting on in all correspondence.
Page 13: Introduction To Mos Gateway
Chapter 1 Introduction to MOS Gateway This chapter contains the following major sections: • Overview of MOS Gateway MOS Control Workflow...
Page 14: Overview Of Mos Gateway
Chapter 1 Overview of MOS Gateway The iNEWS MOS Gateway is an application that does the following: • receives information from the iNEWS newsroom computer system as machine control events are entered in production cues in scripts • converts the information into commands in version 2.8 of the MOS Protocol and directs it to specified MOS-compliant devices •...
Page 15 After the news staff has entered the machine control events in the scripts, the producer can download rundowns to the MOS device using the monitor server in iNEWS and MOS Gateway. The downloaded rundown can be controlled using the MOS device’s interface.
Page 16: Loading A Show To The Mos Gateway
After the monitor server is turned on, it continues to monitor the rundown, examining every story saved for new, deleted, or updated events in the playlist. MOS Gateway is not yet involved. Playlists can be printed and distributed to equipment operators. The devices can be controlled using traditional methods.
Page 17: Monitor Mode - Load
MOS device. The MOS device begins its assigned task, such as inserting CG text, checking for availability of video clips, and so forth. Each MOS device sends MOS Gateway the status of the playlist, called a running order in the MOS Protocol. Each MOS device also sends the status of individual running order items, each one corresponding to a machine control event.
Page 18 Chapter 1 MOS Gateway then forwards these status messages to the monitor server. Error messages are returned to the iNEWS Workstation used to load the rundown. The monitor server also inserts status for video clips, such as whether the clip is available, into stories in the rundown and event lists located in the iNEWS database.
Page 19: Preparing For Installation
Chapter 2 Preparing for Installation This chapter describes the preliminary steps you must take before installing the MOS Gateway software, including: • Familiarizing yourself with this manual, release notes, and other iNEWS documentation. • Verifying required hardware and software components This chapter contains the following major sections: •...
Page 20: Before You Begin The Installation Procedure
• Ensure the installation CD is available. Hardware Requirements To install and run MOS Gateway, your system must have the minimum base equipment described in T a b l e 1. For a list of qualified PCs, contact Avid Broadcast Customer Support.
Page 21: Software Requirements
(version 1.5.1 or higher) • Internet Explorer 5.0 with Java Virtual Machine (version 5.0.3802 or higher) All iNEWS Workstations on a network using MOS Gateway 2.0 must be running version 1.5.1 or higher of the iNEWS client software.
Page 22: Supported Mos Devices
Chapter 2 Supported MOS Devices The following is a list of supported MOS devices; however, this list is subject to change. For the latest information, visit the Avid Web site or contact Avid Broadcast Customer Support. • Avid AirSPACE (CountDown) •...
Page 23: Installing Mos Gateway Program Files
Chapter 3 Installing MOS Gateway Program Files This chapter describes the process of installing the MOS Gateway and contains the following major sections: • Overview of the Setup Adding IP Addresses on MOS Gateway Server Installing MOS Gateway Software Upgrading MOS Gateway Software...
Page 24: Overview Of The Setup
The monitor server communicates with the MOS Gateway software only if the MOS Gateway Server’s IP address is added to all of the iNEWS Servers’ /etc/hosts files. Procedures for configuring iNEWS Servers, including adding MOS Gateway IP addresses, are located in “Adding IP...
Page 25: Installing Mos Gateway Software
To install MOS Gateway: 1. Insert the iNEWS MOS Gateway CD into your CD-ROM drive. 2. Open Windows Explorer. To do this, click the Start button and select Windows Explorer from the menu, or press the Windows and E keys simultaneously.
Page 26 Chapter 3 4. Click the setup.exe file. The MOS Gateway Setup dialog box opens. 5. Click the Next button. The Choose Destination Location dialog box opens.
Page 27 Browse to set another drive and directory as the destination. 7. Select the type of setup: • A Complete setup installs the MOS Gateway Server software, the License Service and Remote Administration tool. • A Remote Administration setup installs only the Remote Admin-...
Page 28 Chapter 3 8. Click Next. The Start Copying Files dialog box appears, allowing you to review the your selections for the setup before initiating the copy process. 9. If a change must be made, click Back to do so; otherwise, click Next to continue.
Page 29 The Setup Status dialog box appears with a progress bar, indicating the percentage of installation completeness. ® 10. The MOS Gateway requires the Microsoft Java Virtual Machine, so it is automatically installed next. If Virtual Machine already exists on the computer, the installation program will detect it and skip steps and 11.
Page 30 12. If a Complete setup type was chosen in step, then Setup installs the Microsoft Installer and XML Parser. 13. MOS Gateway installs a license server that listens on an IP port for license requests. In the dialog box that appears, specify an IP port that...
Page 31 Overview of the Setup The default is 53211. 14. Click Next. The MOS Gateway License Server Key dialog box appears.
Page 32 If not, contact Avid Broadcast Customer Support with your customer ID and MOS Gateway Server hostname to receive one. 16. Type the name of the MOS Gateway Server, if necessary. Since this information is typically supplied automatically by the setup program,...
Page 33: Upgrading Mos Gateway Software
Finish. Upgrading MOS Gateway Software Before upgrading to a newer version of MOS Gateway software, any previous version of the software must be uninstalled first. Running the setup program on a system that already has a previous version installed will not overwrite all the necessary files.
Page 34 Use the Add/Remove programs feature in the Windows Control Panel. After all previous versions of the software is uninstalled, upgrade by installing the latest version of MOS Gateway, according to the procedure “Installing MOS Gateway Software” on page25 After the new version of software is installed, complete the upgrade by using the printed copy of your old configuration file to edit the new default mosconfig.xml file with your site’s <mosDevice>...
Page 35: Chapter 4 Setting Up The Inews Server
Chapter 4 Setting up the iNEWS Server After MOS Gateway is installed, you must set up the iNEWS Server to use MOS Gateway. This chapter provides the procedures for setting up the servers. This chapter contains the following major sections: •...
Page 36: Configuring Inews Servers
Workstation. If you have ControlAir (formerly known as iNEWS Broadcast Control System or BCS), much of this work may already be done. These tasks must be completed to download playlists and updates to MOS Gateway. This chapter assumes: •...
Page 37: Configuration Details
Configuring iNEWS Servers Create an Entry in the SYSTEM.MAP Story (page 55) Adding IP Addresses for the MOS Gateway (page 62) Updating the iNEWS System Dictionaries (Optional) (page 64) Configure iNEWS for MOS Replication (Optional) (page 68) Configuration Details The following steps do not include setting up external devices, such as character generators and still stores, which play broadcast events.
Page 38 Chapter 4 The mailbox enables iNEWS to notify the monitor server of changes made to a rundown queue while a show is monitored. The monitor server then updates composite and event lists, as well as any playlists, if necessary. To create and configure a monitor server: 1.
Page 39 Configuring iNEWS Servers 3. Add the monitor server to the /site/config file on each iNEWS Server—such as server A and server B in a dual server system— by doing the following: Always back up the /site/config file before making any changes. See “Changing the Configuration File”...
Page 40 Chapter 4 Do not confuse the d. Add a configuration line for the monitor server in the host configuration line, definition belonging to the iNEWS Server that will run the server which starts with program. This line begins with the word server and contains the server, and the mailbox number assigned to the monitor server.
Page 41 Configuring iNEWS Servers Comments appearing The following are sample configuration lines for various server after the semicolons (;) programs: are optional. server action actphon ;action svr server distribution 257 devname1 ;dist server server parallel devname2 server keyword key1 ;keyword server server seek seek ;seek server...
Page 42: Reconfigure The System
Chapter 4 These tasks are covered in the next two sections. Reconfigure the System You do not need to stop To reconfigure the system: anything to reconfigure 1. At the console, select the master computer (typically server A). the system. 2.
Page 43: Using The List Command To View Assigned Mailboxes
Configuring iNEWS Servers To assign a mailbox to the rundown queue: 1. Log in as a system administrator—that is, with a superuser account—to an iNEWS Workstation. 2. Navigate to the rundown queue, such as the queue named Rundown located in the SHOWS.6PM directory. 3.
Page 44 MOS Gateway. You may want to create only composite and/or event lists for certain production devices, such as MOS Gateway. If you do not create list queues for some devices, the monitor server will not create lists.
Page 45 Configuring iNEWS Servers For these lists to exist, queues for them must be created—if they do not already exist—and they must be “mapped” to the monitor server so it knows where to put composite information and event lists. This step in the procedure explains how to create queues.
Page 46 Chapter 4 A new queue appears under the folder you selected and at the end of any list of existing queues. The title, New-Queue, is highlighted, so you can rename it. 4. Type the name of the new queue, such as COMPOSITE or CG1. The pathname of each device’s event list queue is a combination of the event list directory and the device manager’s name.
Page 47 Configuring iNEWS Servers 6. To have monitor server display information in these lists properly, each queue must have a 1-line display and be assigned the proper queue form. Assigning these forms is covered in “Assigning Forms to Queues” on page53. To set the display of any queue, such as a composite or event list queue:, log in as a system administrator at an iNEWS Workstation, and do the following:...
Page 48 “Create an Entry in the SYSTEM.MAP Story” on page55 Step 3: Set Up Queue and Story Forms Add MOS Gateway fields to existing rundown queue and story forms in iNEWS. These fields are explained in Table For a field to exist in a queue form, it must also exist in a story form. Refer...
Page 49 Configuring iNEWS Servers Table 1 iNEWS Form Fields for MOS Gateway Field Type Description MOS-ACTIVE This field is required on the story form so a queue can display whether a MOS item, such as a Media Browse video event, is attached to a script; this is typically done by dragging and dropping the MOS item into the story form from an ActiveX plugin.
Page 50: Calculating Duration In Time Fields
Chapter 4 Calculating Duration in Time Fields Some form fields in iNEWS are dependent on others. This is primarily evident in the relationship between the RUNS-TIME field and the MOS- DURATION field. Figure1 provides a visual outline of how input in certain form fields directly affects what appears in others.
Page 51 • The first column has the MOS device’s mosID—reported by the vendor's ActiveX control. It must match the <mos> value in the mosconfig.xml file, which is installed on the MOS Gateway Server. • The second column has an iNEWS device name associated with the mosID to display in machine control events in the story body.
Page 52 Chapter 4 The SYSTEM.MOS-MAP story may also be used to set up whether times related to MOS items are displayed in the Queue panel (rundown) or Story Form panel. It may be configured for all MOS devices or on an individual basis.
Page 53 TABLE-END Step 5: Assigning Forms to Queues After you create queues to hold the composite and event lists, you must assign forms containing MOS Gateway fields to each queue. For instance: • Assign a form designed to display composite list information to SHOWS.6PM.COMPOSITE...
Page 54 Chapter 4 3. Select Properties. The Directory/Queue Properties dialog box will appear. Access to the Directory/Queue Properties dialog box and its appearance vary, depending on certain circumstances. See Chapter 5 of the iNEWS Newsroom Computer System Operations Manual for more information. 4.
Page 55 Configuring iNEWS Servers You must assign a queue form and a story form. The queue form determines the look of the queue. The story form determines how an event request is displayed when you double-click it. For instance, to assign the standard composite list queue form to the SHOWS.6PM.COMPOSITE queue, select mcs-composite from the Queue drop-down list in the Queue Properties dialog box.
Page 56 To add an entry for the show in the map story: 1. Open the SYSTEM.MAP story, which contains a separate entry for each show that will be produced using MOS Gateway or ControlAir. ControlAir is another Avid product that works with the iNEWS newsroom computer system to control production devices, such as character generators, still stores, and video playback machines.
Page 57 Configuring iNEWS Servers • The composite list queue • Groups of users who can monitor the show • The time you want the monitor to turn itself off—when you want the system to stop monitoring the show The composite list queue The directory where you want to hold the The time you want the...
Page 58 Chapter 4 Table 2 Entry Header Parameters Parameter Definition Rundown Queue The full pathname of the show’s rundown queue. Event List Directory (Optional) The directory in which event lists are stored. The monitor server combines information you put here with the device name. For instance, if you specify SHOWS.6PM here and you have a still store machine called “ss1,”...
Page 59 <amcp> value in the mosconfig.xml file; in the example, the value is sony. The second part of the name must match the hostname of the computer with MOS Gateway’s IP address, as identified in the /etc/hosts file on the iNEWS Server. In the example, the hostname is mosgwy.
Page 60 Chapter 4 The type of The name of Whether the monitor The ControlAir Worksta- The address range production the production updates the tion form for that show, or you want to use device device device’s playlist the MCT form for that (CGs and still stores ;...
Page 61 Configuring iNEWS Servers Table 3 Device List Line Parameters (Continued) Parameter Definition Address/Stack Specify a range of addresses in this field. The monitor server uses this range to store the forms it builds. To specify a range of addresses, enter the starting address, followed by a space and the ending address.
Page 62 Step 7: Adding IP Addresses for the MOS Gateway To enable monitor server to communicate with MOS Gateway, the IP address of the MOS Gateway Server must be added to all iNEWS Servers’ /etc/hosts files. Ideally, all MOS Gateway Servers and iNEWS Servers would have each other’s addresses and computer names.
Page 63 Enter IP addresses, computer names, and comments, such as: 125.1.10.50 MOSGWY mosgwy #MOS Gateway machine c. Type a period (.) to stop appending information to the file. d. (Optional) Type p to print the appended file and verify your changes.
Page 64: Editing The /Site/Dict/Mcs Dictionary File
Chapter 4 (saves changes by writing the file to the disk) Do not use an (ed responds by displaying file size) uppercase W. (quits the edit session) Step 8: Updating the iNEWS System Dictionaries (Optional) Machine Control System (MCS) dictionary files in iNEWS can be modified to customize the appearance of status indicators from various devices.
Page 65 Configuring iNEWS Servers When navigating in the file, remember the UNIX line editor is case- sensitive. So, typing either /Play or /play will not locate a line with “PLAY.” 4. Substitute the new word, such as “OnAir,” for the second occurrence of the existing word, PLAY, by typing: s?/PLAY?/OnAir The console will respond with a display similar to the following:...
Page 66 Chapter 4 To update your iNEWS dictionaries: The prompt endings 1. Select all servers. change from a colon 2. At the console, type su to become a superuser and type the superuser (:)—indicating a system operator password. The prompts will appear as follows: login—to a pound sign NRCS-A: su (#)—indicating a...
Page 67 Configuring iNEWS Servers 5. Select all servers. 6. Type logout all to log out all users. If a user is editing a story, this saves the file and logs out the user. 7. Type list s again to check for connect session users. The logout all console command does not log out users who are currently in a connect session.
Page 68 MOS items. All other iNEWS users should have read-only permission to those queues. Other configuration required for MOS replication, which must be done on the MOS Gateway Server, is explained in Chapter5. See “Using the MosAdmin Application” on page 91 for more information.
Page 69 Configuring iNEWS Servers 3. Click New User. The Add New User dialog box appears. 4. In the User ID field, enter the login name of the user account, such as MosReplication. The User Name is optional and may be the same as the User ID. There is no need to assign Home, Destination, or Mail queues to a MOS replication user account.
Page 70 Chapter 4 c. When the results appear, double-click on the name to open and modify the preferences. d. Uncheck the Force Change check box. e. Click OK. To create a write group for MOS replication: For more information 1. Choose a name for the group, such as mosreplication. on creating groups in 2.
Page 71 Configuring iNEWS Servers e. Type the new group name, such as mosreplication, in the Title (Slug) field of the Queue panel or in the corresponding field in the Story Form panel. Press Enter. g. Click inside the Story Text panel and type the group name and membership list in the following format: group mosreplication mosreplication...
Page 72 Chapter 4 A new queue appears under the selected folder and at the end of any existing queues in that folder. The title, New-Queue, is highlighted so you can rename it. 4. Type the name of the device-specific queue, such as VIDEO. 5.
Page 73 Configuring iNEWS Servers To configure database traits for all queues in a directory, right-click on the parent folder instead of an individual queue and then select Properties from the pop-up menu. Make any necessary configuration changes and ensure the check box labeled Apply changes to all subdirectories and queues is selected before clicking OK.
Page 74 Chapter 4 5. On the Groups tab, ensure the MOS replication group is selected as the Write Group. If the appropriate group does not appear as an option in the list, it must be created in SYSTEM.GROUPS; the procedure for creating the group is on page It is not necessary to assign any Read or Notify groups;...
Page 75 Configuring iNEWS Servers 6. On the User Interface tab, ensure that Refresh and Batch Allowed are selected. 7. Click OK to save changes and apply settings. Selecting and/or unselecting check boxes in the Directory/Queue Properties dialog box does not apply changes immediately. Only step does that.
Page 76 Chapter 4...
Page 77: Configuring Mos Gateway
Chapter 5 Configuring MOS Gateway MOS Gateway must be configured to communicate with various MOS devices. This requires changes to be made in both the iNEWS Server and MOS Gateway. This chapter contains the following major sections: • MOS Gateway Configuration File...
Page 78: Mos Gateway Configuration File
MOS Gateway Configuration File MOS Gateway must be configured with information about each MOS device that will connect to it. This is done by editing the MOS Gateway configuration file, which is installed on the MOS Gateway Server. During installation, the configuration file, which is named mosconfig.xml, is placed, by default, in the following location:...
Page 79: Stopping And Starting Mos Gateway
MOSAdminService must be stopped before MOSRouterService, and so forth, with the last service being MOSConfigService. To stop and restart services: Graphics for the 1. At the MOS Gateway Server, click the Start button on the Windows following procedure Task bar. show views similar to 2.
Page 80: Configuration File Components Explained
7. Click Close. Configuration File Components Explained In this section, lines of the MOS Gateway configuration file are shown in groups; each group of lines is a section of the file that can or should be modified to configure the MOS Gateway to work with MOS devices at your site.
Page 81: The Group
MOS Gateway will save its log files. The COUNT_GOES_HERE should be changed to the maximum number of log files that the MOS Gateway will create before recycling them. The SIZE_GOES_HERE should be changed to the maximum size each log file can be, such as 1000000 (which equals about 1MB).
Page 82: The Group
<lower>MOS_IN_LOWER_PORT_GOES_HERE</lower> </logging> The MOS_OUT_UPPER_PORT_GOES_HERE should be changed to the port on which the MOS Gateway will send running order MOS commands. The recommended value is 10541. The MOS_OUT_LOWER_PORT_GOES_HERE should be changed to the port on which the MOS Gateway will send media object metadata MOS commands.
Page 83: The Group
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.
Page 84: The Group
This is useful in cases where the MOS device provides a small space for the running order name, such as the text on a button. If the entire group is missing or a particular name for a rundown is missing, MOS Gateway will...
Page 85: The Group
Server name followed by a forward slash (/) and the iNEWS rundown’s full queue name. For instance, if the server’s name is NRCS and the rundown queue is SHOW.11PM.RUNDOWN, then MOS Gateway will send the running order name as: NRCS/SHOW.11PM.RUNDOWN.
Page 86: The Group
The YESNO should be changed to YES if the MOS device supports the roItemInsert, roItemDelete, and roItemReplace MOS commands; when set to YES, MOS Gateway will use those commands to move items in stories. The default is YES. The <prependPageNumber> Group <prependPageNumber>...
Page 87 MOS Gateway Configuration File The iNEWS Server expects one of ten event status codes to be returned as the status of a MOS item. Since the MOS Protocol specifies a string as the status of a MOS item in the roItemStat MOS command, MOS Gateway must map these strings to the iNEWS event status codes.
Page 88: The Group
ActiveX controls. For examples of the most commonly used ProgIDs, see Table5 on page89 If the settings are manually edited, then MOS Gateway services must be stopped and restarted. See “Stopping and Starting MOS Gateway” on page79 for more information.
Page 89 MOS Gateway Configuration File The REP_TIME should be set to the time of day when MOS replication should occur. This line is only necessary if the trigger is set to scheduled replication. The TRUE_FALSE value should be set to TRUE if all stories are to be cleared from the queue in the iNEWS database before replication is performed.
Page 90 Chapter 5 Table 5 ProgIDs GVG News Q Pro Browser GVG.XMOSCtrl.1 Omnibus Browser OmnibusODCLauncher.Launcher Editor OmniBusItemEdit.Edit Thunder Editor ThunderX.ThunderXCtrl.1 VizRT Browser VCPAxFiller.VCPTemplateFiller Editor VCPAxFiller.VCPTemplateFiller...
Page 91: Using The Mosadmin Application
The MosAdmin window appears, with two tabbed options: • Status – See Figure5. The Status tab is a read-only tab showing incoming MOS objects, being replicated from the MOS device to the iNEWS Server. This information is also logged into text files by the MOS Gateway Logger.
Page 92 Chapter 5 Figure 5 MosAdmin Status Tab • Replication – Figure 6” on page93 The Replication tab shows a list of devices—obtained from the mosconfig.xml file—and the current replication configuration settings for each device. Before the Replication tab may be viewed, a dialog box appears, prompting the user for a password.
Page 93 MOS Gateway Configuration File A Path text field specifies the queue in the iNEWS database to which media object metadata will be replicated. The queue’s pathname appears in the Directory column of the MosAdmin application and in between the <path> and </path> tags in the configuration file.
Page 94: The Group
MOS devices. So, it is possible that channel names will vary accordingly. For this reason, there is a group of lines in the MOS Gateway configuration file that maps the iNEWS channel name to the channel name accepted by the MOS device.
Page 95: Adding Mos Devices To The System.mos-Map Story
The table contains at least two columns of names separated by white space. The first column is the MOS ID of a MOS device; this must match the name that appears for that device in the MOS Gateway configuration file between the <mos> and </mos> tags.
Page 96: Moving The Configuration File
Chapter 5 Moving the Configuration File MOS Gateway is configured by filling in values in the MOS Gateway configuration file. A default copy of this file is installed in the same directory as MOS Gateway executable files. A sample copy of the MOS Gateway configuration file appears in Appendix See “MOS Gateway Configuration File”...
Page 97 5. Right-click on the ConfigFile value in the right side of the Registry Editor window (under the Name column). 6. Select Modify from the pop-up menu. 7. Replace the existing file path with the one for the new MOS Gateway configuration file.
Page 98 Chapter 5...
Page 99: Troubleshooting
Chapter 6 Troubleshooting This chapter contains information to help you recover from various types of system failures. This chapter contains the following major sections: • MOS Gateway Components • Where to Look For Errors Error Categories...
Page 100: Mos Gateway Components
See “Using the MosAdmin Application” on page 91. Where to Look For Errors Each MOS Gateway service writes errors in one of two places: • Log files located in the Log File directory, as specified in the MOS Gateway configuration file •...
Page 101 The Event Viewer shows a table of events, sorted from most to least recent. The Source column displays the application name that created the event. MOS Gateway services appear in this column. Double-clicking on an event opens the Event Properties/Details dialog box,...
Page 102: Error Categories
Event Properties Dialog Box for Windows 2000 The Description section provides status information, including error messages. Error Categories MOS Gateway errors can be divided into the following categories: • Startup errors, which are reported when MOS Gateway cannot start •...
Page 103 Some resolutions require stopping and restarting any or all MOS Gateway services. For more information on how to do this, see “Stopping and...
Page 104 Chapter 6...
Page 105: Error Messages
Category: Which type of error. Action: What to do about the problem. Some error messages are warnings only; the MOS Gateway will continue to run with a default behavior. Warnings are indicated below with an additional opening Action statement "This is a warning only," and a description of the default behavior.
Page 106: Errors
Source: MOS Gateway Router Category: Runtime configuration Action: This is a warning only. MOS Gateway received a channel specification for a MOS device that does not match any of the entries in the <roChannels> group of lines in that device’s <mosDevice> group.
Page 107 Errors Action: Open the MOS Gateway configuration file. Edit the <in_lower> value in the <tcpPorts> group to insert a port number. Stop and restart the Router. Error: Bad In MOS Upper port value. Location: Event Log Source: MOS Gateway Router Category: Startup Action: Open the MOS Gateway configuration file.
Page 108 Source: MOS Gateway Router Category: Startup Action: MOS Gateway cannot find the host name of a MOS device that connected to it. Ensure the MOS Gateway machine and the MOS device can find each other over the network. Check the domain name server and any local hosts files, or ask your network administrator for details.
Page 109 Source: MOS Gateway Router Category: Miscellaneous Action: MOS Gateway received a MOS item containing errors from the iNEWS Server. Delete the MOS item from its story and add a new MOS item. If this still does not work, contact the vendor of the ActiveX control for assistance.
Page 110 Location: Event Log Source: MOS Gateway Logger Category: Startup Action: Ensure the MOS ConfigService is started. Error: MOS Gateway Logger cannot start: Config file incomplete, the <logging> group must include <directory>, <maxFileCount> , and <maxFileBytes> elements." Location: Event Log Source: MOS Gateway Logger Category: Startup Action: Open the MOS Gateway configuration file.
Page 111 If the path is correct, open the Windows Explorer and see if the MOS Gateway configuration file is in that directory. If not, create one. Error: MOS Gateway Logger cannot start: failed to write test file - error is (The system cannot find the path specified.) Location: Event Log...
Page 112 Source: MOS Gateway Router Category: Startup Action: Open the MOS Gateway configuration file. Edit the <in_lower> value in the <tcpPorts> group to insert a port number. If there is no <in_lower> line, put one in the file. Stop and restart the Router.
Page 113 Errors Action: Open the MOS Gateway configuration file. Edit the <out_lower> value in the <tcpPorts> group to insert a port number. If there is no <out_lower> line, put one in the file. Stop and restart the Router. Error: MOS Out Upper port(RO) did not exist in config file.
Page 114 Source: MOS Gateway Router Category: Runtime configuration Action: MOS Gateway cannot connect to the MOS device devicename. Ensure that MOS Gateway and the MOS device can find each other on the network, and that all appropriate applications are running on the MOS device.
Page 115 Errors Action: This is a warning only. MOS Gateway cannot find status-string in the <statusTranslations> group of the <mosDevice> group for devicename. It will set the status of the event to UNKNOWN in such a case. To avoid this, add status-string to the <statusTranslations> group...
Page 116 Appendix A...
Page 117: System Reference Files
System Reference Files This appendix contains various samples of system files, such as the /etc/hosts file for the iNEWS Server. • Sample Configuration File on MOS Gateway Servers • Sample Configuration File on iNEWS Servers • Sample /etc/hosts File on iNEWS Servers •...
Page 118: Sample Configuration File On Mos Gateway Servers
<socket>off</socket> </logging>    <tcpPorts> <out_upper>10541</out_upper> <out_lower>10540</out_lower>...
Page 119 Sample Configuration File on MOS Gateway Servers  <AllowReplication>YES</AllowReplication> <ReplicationUsername>mosrep</ReplicationUsername> <ReplicationPassword>mosrep</ReplicationPassword>     <AllowMosItemReplace>YES</AllowMosItemReplace> </ncs>  ...
Page 120 Appendix B    <statusTranslations> <statusUnknown/> <statusUnavailable>Bad Clip</statusUnavailable> <statusUnavailable>Unalloc.</statusUnavailable> <statusAvailable>UPDATED</statusAvailable> <statusCueing>Cueing</statusCueing>...
Page 121 Sample Configuration File on MOS Gateway Servers   <statusTranslations> <statusUnknown>UNKNOWN</statusUnknown> <statusUnavailable>BAD CLIP</statusUnavailable> <statusUnavailable>NOT READY</statusUnavailable> <statusUnavailable>UNKNOWN - ERROR INSERTING ITEM</statusUnavailable> <statusAvailable>LOADED</statusAvailable> <statusAvailable/> <statusCueing>Cueing</statusCueing> <statusCued>Ready</statusCued>...
Page 122 <handlesSpecMosReqAll>NO</handlesSpecMosReqAll>    ...
Page 123 <handlesSpecMosReqAll>YES</handlesSpecMosReqAll>    ...
Page 124: Sample Configuration File On Inews Servers
Appendix B <statusStopped>PLAYED</statusStopped> <statusRewinding/> </statusTranslations> <mosObjReplication> <trigger>scheduled</trigger> <replicationTime>10:36:00 AM</replicationTime> <clearQueue>true</clearQueue> <path>mos.nqp</path> <mosItemBrowserProgID>GVG.XMOSCtrl.1</mosItemBrowserProgID> </mosObjReplication> </mosDevice> </listDevices> </mosGatewayConfiguration> Sample Configuration File on iNEWS Servers After you choose a mailbox and a device number for your monitor server, you must add certain information to your system configuration file—/site/config on the iNEWS Servers.
Page 125 Sample Configuration File on iNEWS Servers host ab net- Add the monitor server to the servers servers line for the computer host ab on which you want the server to net- run. servers host a net- servers Also, add the monitor server to each server’s alternate host host b definition.
Page 126: Sample /Etc/Hosts File On Inews Servers
172.101.6.11 inews-web INEWS-WEB 172.101.6.12 MOSGWY mosgwy # MOS Gateway machine 172.101.6.13 MG1 # MOS Gateway Server 1 172.101.6.14 MG2 # MOS Gateway Server 2 Sample System Stories in iNEWS There are two stories in the iNEWS System directory that contain MOS- related information.
Page 127: Mosreplication Form
MOSREPLICATION Form • The SYSTEM.MOS-MAP story, an example of which is provided below: ReplaceTime=YES TABLE-START DeviceTable ;MOSID AMCPDeviceName sony sonyem MOSGATE qamosgw chan1 chan2 chan3 PILOT pilot AIRSPACE airem VERTIGO vertigo NewsQPro NQPro <noDur> NETIAMOS netia TABLE-END Procedures for editing the SYSTEM.MOS-MAP story are in Chapter4. See “Edit the SYSTEM.MOS-MAP Story”...
Page 128 • Use the dbrestore command at the iNEWS console to transfer using the dbrestore three stories provided in the Replication folder on the MOS Gateway command, see the Install CD to the MOSREPLICATION queue. The stories are in a file iNEWS Newsroom called mosreplication.dbdump.
Page 129 MOSREPLICATION Form Figure 3 Story for MOS Replication to the Story Form Figure 4 Story for MOS Replication to the Story Form and Body...
Page 130 Appendix B...
Page 131: Glossary
Glossary Low-cost point-to-point 10Mb/sec Ethernet using four unshielded twisted 10Base-T pairs (UTP) of wire (only two pairs are actually used) with RJ-45 connec- tors. Low-cost point-to-point 100Mb/sec Ethernet using four UTP (only two 100Base-T pairs are actually used) with RJ-45 connectors. The time assigned to a clip when it was encoded.
Page 132 American Standard Code for Information Interchange. The standard that ASCII governs the recording of characters by a sequence of binary digits, as in a computerized timecode or video editing system. A function in iNEWS newsroom computer system that writes a backup auto-backup copy of an open story to a user’s local disk at specified time intervals.
Page 133 duction devices, such as character generators, still-stores, and videotape devices. See production cue. The amount of airtime required from the beginning of the show up to a cume (cumulative) certain point in the show in order for the show to remain on-schedule. It is time displayed with each entry in a rundown queue.
Page 134 The length of a show or story. It is calculated by using the elapsed time in a duration broadcast when a story begins. A feature that allows a user to open a queue or story while preventing oth- easy lock ers from doing the same.
Page 135 The indicator in a Story Text panel that links a script to production infor- grommet mation. Also called: anchor or marker. A story in a newscast that has a fixed start time, usually at the end of a seg- hard out ment or show.
Page 136 See rundown. lineup The process of opening a clip into the editor in preparation for viewing or load editing. This is a network of computers located in a common environment, such as Local Area Network in a building or building complex. (LAN) To protect a queue or story from access by unauthorized users.
Page 137 A fault tolerance method that keeps identical copies of data on disk parti- mirroring tions located on different physical hard disks and servers. Acronym for Media Object Metadata. Acronym for Media Object Server. See also MOS device. A vendor product that stores media objects and supports the MOS proto- MOS device col.
Page 138 End point of an edit, or a mark on a clip indicating a transition point. Also Out point known as a Mark OUT. The total length of time for a show (shown in hours, minutes, and seconds) out time or the actual time by which the show must end (shown in 12-hour-clock time).
Page 139 The person presenting a newscast on-air to a television audience. Also presenter called an anchor. To rehearse an sequence without actually performing (exporting) it. preview priority queue 1. An area where iNEWS places copies of wire stories (usually in WIRES.ADVISORY.PRIORITY). 2.
Page 140 A trait that controls the characteristics of a queue in the iNEWS database. queue property Queue properties include the refresh trait, read-only purge interval, sort- ing, and so forth. Authority granted to users that allows them to read and duplicate the con- read access tents of a directory, queue, or story.
Page 141 of the iNEWS Workspace. The rundown queue typically uses a form with BACK-TIME or CUME-TIME fields to display the timing of the newscast. ® Santa Cruz Operation UNIX operating system. A buffer in which text or notes are stored until the appropriate recovery scratch pad procedures is performed.
Page 142 A printer attached to the workstation. slave printer A queue in which stories are sorted according to criteria specified by the sorted queue system administrator. A queue from which stories are copied or moved. source queue Uniquely identified file containing text; stories are grouped in queues and story are displayed in the Story panel of the iNEWS Workspace.
Page 143 A special alphanumeric code that identifies a user account in the iNEWS user ID system. A user ID can be up to 20-characters long. User ID given the authority to add, modify, delete, and search for informa- user manager tion about user accounts. User manager status can be assigned by a system administrator only.
Page 144 The ability to add new stories, edit existing stories in a particular queue, write access add a queue, or add a directory.
Page 145: Index
Index Index Symbols iNEWS 38 moving 96 /etc/hosts 24 configuration groups editing 63 handlesEmptyStories 85 /site/config 38 handlesRoItemLevelCommands 86 /site/dict 64 handlesRoStoryMoveMultiple 85 /site/dict/mcs, editing 64 logging 81 mosObjReplication 88 names 84 ncs 83 prependPageNumber 86 ActiveX control 15 prependSeparator 86 amcp tags 95 prependStringForEmptyPageNumber 86 assign forms 53...
Page 146 38 dialog boxes configuration summary 36 Choose Destination Location 26 – configuring 35 MOS Gateway License Server Key 31 prerequisites for configuring 36 MOS Gateway Setup 26 IP addresses Queue Properties 43 adding to MOS Gateway Server 24...
Page 147 47 listing assigned mailboxes 44 monitor on 16 MOS control workflow 14 MOS devices, adding 95 parameters MOS Gateway character generator 60 configuring 77 device list line 60 License Server Key dialog box 31 entry header 58 Setup dialog box 26...
Page 148 93 Procedures defined 14 add IP addresses to iNEWS Servers 63 forms for 127 add IP addresses to MOS Gateway Server 24 ncs section 80 assign form to queue 53 stories for form 128 assign mailbox to queue 43...
Page 149 Index sample entry header 57 XML, MOS configuration file 78 SYSTEM.MOS-MAP 51 adding MOS devices 95 device table 51 sample story 53 tags handlesEmptyStories 85 handlesRoItemLevelCommands 86 handlesRoStoryMoveMultiple 85 logging 81 mosObjReplication 88 names 84 ncs 83 prependPageNumber 86 prependSeparator 86 prependStringForEmptyPageNumber 86 roChannels 94 roSlugMaps 84...
Page 150 Index...
Page 151: Reader's Comments
Please send your comments to: Avid|iNEWS Technical Publications Dept 6400 Enterprise Lane Suite #200 Madison, WI 53719 Publication: MOS Gateway Installation & Operations Manual Overall Rating: Superior Good Average Below Average Poor...
Page 152 -152 Reader’s Comments...

This manual is also suitable for:

Inews

Avid Technology MOS Gateway Installation & Operation Manual

Preface

Chapter 1 Introduction to MOS Gateway

Chapter 2 Preparing for Installation

Chapter 3 Installing MOS Gateway Program Files

Chapter 4 Setting up the Inews Server

Chapter 5 Configuring MOS Gateway

Chapter 6 Troubleshooting

Appendix A Error Messages

Appendix B System Reference Files

Glossary

Index

Reader's Comments

Quick Links

Need help?

Questions and answers

Related Manuals for Avid Technology MOS Gateway

Summary of Contents for Avid Technology MOS Gateway

This manual is also suitable for:

Table of Contents