1. Manuals
  2. Brands
  3. Miranda Manuals
  4. Server
  5. Xmedia Server
  6. Configuration manual

Miranda Xmedia Server Configuration Manual

Digital asset management system
Hide thumbs
Table of Contents

Advertisement

Quick Links

Xmedia Server
Digital Asset Management System
Configuration Guide
M841-9900-480
25 March 2013
www.miranda.com

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Xmedia Server and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Summary of Contents for Miranda Xmedia Server

  • Page 1 Xmedia Server Digital Asset Management System Configuration Guide M841-9900-480 25 March 2013 www.miranda.com...
  • Page 2 Configuration Guide, you agree to the following terms and conditions: Miranda Technologies Partnership hereby grants permission and license to owners of Xmedia Server and Vertigo Suite to use their product manuals for their own internal business use. Manuals for Miranda Technologies Partnership products may not be...
  • Page 3 Document Revision History After the original release date, this user manual may be updated with edits and then re- released. The following table tracks the versions of this document. Publication date Description November 23, 2012 Original release of this user manual for Vertigo Suite v.4.8 March 25, 2013 •...

  • Page 4: Safety Compliance

    Safety Compliance This equipment complies with the requirements of the following standards for Safety of Information Technology Equipment: • CSA C22.2 no. 60950-1-07 (2 Edition) • UL 60950-1 (2 Edition) • IEC/EN 60950-1 (2 Edition) Warning: An appropriately listed/certified main supply power cord must be used for the connection of the equipment to the main voltage at either 120V or 240V CAUTION:...
  • Page 5 WARNING Xmedia Server devices contain Class 1 lasers, which are deemed safe under normal operating conditions. Standalone Equipment - Laser source(s) employed: CLASS 1 LASER PRODUCT APPAREIL A LASER DE CLASSE 1 WARNING Xmedia Server devices contain a Lithium battery in the service access area, which...

  • Page 6: Table Of Contents

    Logging Data Server events ......................3-9 Controlling the Data Server service .................... 3-11 File Ingest Server and Transcode Server ..................3-13 Xmedia Server Control Panel - XmediaServer Properties Window ..........3-14 Xmedia Server Control Panel’s settings pages................3-16 The XMS’s General Configuration Settings............... 4-1 Viewing the Xmedia Server’s product information ................
  • Page 7 Table of Contents MOS Server Configuration and Monitoring............... 7-1 Configuring the Xmedia Server’s MOS settings .................7-2 Instructions for configuring the Xmedia Server as a MOS server ..........7-3 Editing the Newsroom Control System’s properties ..............7-6 Deleting the Newsroom Control System ..................7-7 Logging MOS Server activities ......................7-8...
  • Page 8 Table of Contents Transition properties and permissions ..................10-14 Adding a new transition to the workflow..................10-18 Editing a transition’s properties and permissions..............10-20 Deleting a transition from the workflow ..................10-21 Workflow option: Priorities ......................10-22 Adding a new priority to the workflow ..................10-23 Deleting an existing priority from the workflow................
  • Page 9 Setting and Monitoring the XMS Publishing Activities ..........18-1 Setting the Central XMS IP Override....................18-2 The Insta-publish device setting on the Xmedia Server Control Panel ..........18-3 Insta-publishing from the EXMS to a Localhost device ...............18-4 Monitoring and managing publish requests in the queue ..............18-5 User Rights Management....................
  • Page 10 Table of Contents Adding and removing users from a role assignment..............19-47 Restricting access to asset categories ..................19-49 Setting access permissions for an asset category..............19-50 Granting additional users access to a restricted category ............19-53 Removing users from a category’s security ................19-53 Removing all access restrictions from a category..............

  • Page 11: Introduction

    NTRODUCTION The Xmedia Server (XMS) is the central graphical asset management server for Miranda’s Vertigo Suite channel branding and playout system. The Xmedia Server allows all branding assets to be ingested once, centrally archived, and automatically moved to the desired graphics device using rule-based publishing.

  • Page 12: About The Xmedia Server

    Vertigo Suite channel branding and playout system. Assets only need to be ingested once for them to be centrally archived on the Xmedia Server. These assets are then made available to all of the Vertigo Suite applications on the network, which allow you to create a wide range of graphics, including advanced, data-driven broadcast applications that link on- air graphics elements to live data feeds.

  • Page 13: Xmedia Server's Standard And Option Features

    Introduction Xmedia Server’s standard and option features The Xmedia Server is a 2RU rackmount server with 2TB of RAID-1 storage and is factory configured to run Windows Server 2003 as its operating system. Additional software applications and services that are factory installed include: •...

  • Page 14: Xplorer - Media Asset Management Application

    (VX-Xplorer), which is a graphical PLORER content management system for viewing and managing the asset and file contents of the Xmedia Server and the devices to which the XMS has published assets. See the X PLORER for more information.

  • Page 15: Xms Configuration Guide

    Physically, the Xmedia Server is a 2RU rackmount server that incorporates redundant fans, power, and ethernet ports, with 2 TB of RAID-1 storage. The Xmedia Server features easy frontal access to the storage drives, and a control panel featuring LEDs and buttons for system monitoring and operation.

  • Page 16: Xms Hardware Overview

    Drives Figure 2-1. The Xmedia Server’s front panel components Figure demonstrates that the control panel located on the front of the Xmedia Server chassis has six LEDs and two buttons. The table on page 2-3 describes the function of each LED and button, as well any corrective action you may need to take.
  • Page 17 XMS Hardware Overview Indicates a power supply module has failed. This should be accompanied OWER by an audible alarm. A backup power supply module will take the load and keep the system running, but the failed module will need to be replaced. This LED should be off when the system is operating normally.

  • Page 18: Back Panel Components And Connectors

    PCI expansion slots (video, audio, and graphics cards), and various I/O port connectors (USB, COM1, VGA, Ethernet...etc). When using the Xmedia Server in a replication setup, you will insert the license dongle in one of the USB ports (see page 6-8).

  • Page 19: Mounting The Xmedia Server Chassis In A Rack

    Note that the rails are designed to fit in racks with a depth of 26” to 33.5”. Due to the heavy weigh of the unit, the rack in which the Xmedia Server unit will be installed should be anchored to the building’s structure.
  • Page 20 XMS Hardware Overview To install chassis rails and mount the Xmedia Server’s chassis into an equipment rack: Remove the Xmedia Server’s faceplate by pulling the faceplate’s handles away from the chassis. Install the inner rail extensions to the server’s chassis.
  • Page 21 CAUTION Due to the heavy weight of the Xmedia Server, ensure that the rack is securely anchored onto a unmovable surface or structure before installing the chassis into the rack. Figure 2-7. Mounting the Enterprise Server’s chassis into a rack CAUTION Slide/rail mounted equipment is not to be used as a shelf or a workspace.

  • Page 22: Xms Network Integration And Service Applications

    NTEGRATION AND ERVICE PPLICATIONS It is recommended that the Xmedia Server be installed on a dedicated LAN, using the existing security infrastructure. A qualified system administrator should verify that the setup follows the organization’s security standards. Specific recommendations regarding proper virus strategies, that won’t compromise performance are provided in this chapter.

  • Page 23: Xmedia Server Virus Protection Guidelines

    Network Setup and Configuration Ideally, the Xmedia Server and other non-critical components should be running anti-virus software, while the Vertigo XGs reside on a separate network. In such a case, the Vertigo XGs would not be running anti-virus software, leaving them potentially vulnerable.

  • Page 24: Standard Anti-Virus Protection

    Any machine that will be attached to the same network as the Xmedia Server must undergo a complete system scan. • Any floppy, zip or other external media to be copied to or run on the Xmedia Server must undergo a complete scan. •...

  • Page 25: Xmedia Server Network Ports

    XMS Network Integration and Service Applications Xmedia Server network ports Users can connect to the Xmedia Server from any client PC on their network. All of connections used by the Vertigo Suite applications are over TCP and UDP, using the...

  • Page 26: Vertigoxmedia Data Server Service

    XMS Network Integration and Service Applications VertigoXmedia Data Server service The Data Server is a service that runs in the background on the Xmedia Server and is responsible for managing data coming from various feeds by providing live updates of data values when requested, and distributing the data to the appropriate recipients (figure 3-2).
  • Page 27 XMS Network Integration and Service Applications The Data Server Control Panel features three (3) tabbed pages that contain parameters for configuring the connection, metadata, and logging options, as well as stopping and starting the Data Server service. The upper portion of the Data Server Control Panel’s G page identifies the Data ENERAL Server’s software version, the directory path where the Data Server’s executable file is...

  • Page 28: Setting The Data Server's Connection Parameters

    G ETADATA ENERAL page, which determine the Data Server’s settings for connecting and communicating with the Xmedia Server(s). These settings are used to identify the primary Xmedia Server that the Data HOST PORT Server will connect to. •...
  • Page 29 15-5). When enabled, this setting causes the Data Server service to cease if the Xmedia Server connection is lost. In a replication setup, this condition forces a failover to the secondary Xmedia Server. When enabled, the Data Server does not parse the schemas until they are SE LAZY LOADING requested.

  • Page 30: Logging Data Server Events

    Figure 3-5. Data Server Panel’s Logging page The Data Server’s Logging Levels and Debug Categories settings allow you to specify the type and categories of events that you want to be recorded in the Xmedia Server log files. Log Level This sets the default log level used by all logging categories except those that have been checked in the Debug Categories list.
  • Page 31 Debug categories at once. ELECT Log Destinations All log files related to Vertigo Suite products are centrally archived in the Xmedia Server • : Currently not available for external use. The events are written to a OG TO CONSOLE console for Miranda personnel to use for testing and debugging tasks.

  • Page 32: Controlling The Data Server Service

    By default, the Data Server service is set to automatically start when its host machine (i.e. Xmedia Server) is started. You can then use the controls on the Data Server Panel’s page to stop and start the service (figure 3-7). The service’s current state (started ERVICE or stopped) is always reported on this page as well.
  • Page 33 XMS Network Integration and Service Applications The figures below demonstrate that once the C setting is enabled, ONTROL THE ERVER the following changes are applied to the Data Server panel’s G and S pages: ENERAL ERVICE General Page • The upper portion of the General page’s software identification banner reads: ONTROLLED BY THE MEDIA ERVER...

  • Page 34: File Ingest Server And Transcode Server

    The Vertigo File Ingest Server is a service responsible for automatically ingesting media into the Xmedia Server from a user-created ingest folder. The File Ingest Server is also responsible for issuing media conversion requests to the Transcode Server, which is the service responsible for transcoding media from one format to another.

  • Page 35: Xmedia Server Control Panel - Xmediaserver Properties Window

    ERVER ROPERTIES commonly referred to as the X MEDIA ERVER ONTROL ANEL Once the Xmedia Server has been installed, you can open the Xmedia Server Control Panel window by selecting: S > S > C > V TART ETTINGS ONTROL...
  • Page 36 XMS Network Integration and Service Applications In most cases, the XMS Service is set to automatically launch when the Xmedia Server is started and it runs in the background, regardless of whether or not any applications from the Vertigo Suite have been opened. If the XMS service fails to start, the Xmedia Server Control Panel’s S...

  • Page 37: Xmedia Server Control Panel's Settings Pages

    Xmedia Server Control Panel’s settings pages The following table describes the Xmedia Server Control Panel’s fifteen (15) tabbed pages that contain the parameters and settings that are used to configure the Xmedia Server to interact with the Vertigo Suite applications and offer extended functionality.
  • Page 38 YSTEM ARAMETERS YSTEM ARAMETERS are ingesting into the Xmedia Server, at what time expired published and archived assets will be purged, and the system’s field rate. “Setting the XMS System Parameters” on page 11-1 for more information about setting the parameters on the S page.
  • Page 39 XMS Network Integration and Service Applications The Xmedia Server Control Panel’s A page configures the Xmedia UTOMATION UTOMATION Server to communicate with a specific automation system for the purposes of publishing to devices based on the automation system’s schedule. “The XMS Automation Parameters for Scheduled-based Publishing” on...

  • Page 40: The Xms's General Configuration Settings

    ENERAL ONFIGURATION ETTINGS The G page on the Xmedia Server Control Panel (figure 4-1) allows you to view and ENERAL set some of the Xmedia Server’s basic configuration and connection settings. The G ENERAL page is divided into three (3) thematic areas and each is described in the following sections: •...

  • Page 41: Viewing The Xmedia Server's Product Information

    Working directory: Identifies the full directory path of the VertigoXmedia Apps folder that contains the Vertigo Suite’s .ini files, license files, some log files, and some MOS- related XML files. Figure 4-2. Xmedia Server product information on the Xmedia Server Control Panel’s General page XMS Configuration Guide...

  • Page 42: Configuring The Xms's Network Connection And Directories

    (figure 4-2) features two sections that ENERAL allow you to specify and view the Xmedia Server’s communication port and the full directory paths where the XMS stores or retrieves information from. The following table provides more details about each field in these sections:...

  • Page 43: Configuring The Authorization Manager

    Configuring the Authorization Manager The Vertigo Suite offers system administrators and workflow managers the possibility of restricting access to some of the functionality on a per-user basis using the Xmedia Server and the operations, tasks, and roles defined in Microsoft’s Authorization Manager (see “User Rights Management”...

  • Page 44: Verifying The Xms's Database Settings

    The following sections describe how to use the Xmedia Server Control Panel’s D ATABASE page to verify the Xmedia Server’s database settings, as well as how to take a backup of the SQL Server database: • “Verifying the SQL Server database settings” on page 5-2 •...

  • Page 45: Verifying The Sql Server Database Settings

    The following instructions describe how to verify the MS SQL S ERVER on the Xmedia Server Control Panel’s Database page (figure 5-1) SETTINGS Figure 5-1. The MS SQL Server settings...
  • Page 46 When this setting is enabled, the value specified establishes the number of connections in the connection pool. Having a connection pool helps the Xmedia Server service its clients in a timely fashion. When this setting is disabled, it will not use a connection pool to the database and it will have only a single connection.

  • Page 47: Making A Backup Of The Sql Server Database

    (XmediaSuite.bak) is created/updated and saved within the root folder of the server’s Virtual Database (as indicated by the directory path in the V DB R field). IRTUAL OOT DIRECTORY Figure 5-3. Create or update a backup of the Xmedia Server’s MS SQL Database XMS Configuration Guide...

  • Page 48: Replication Of The Xms Server's Database

    EPLICATION OF THE ERVER ATABASE Replication enables full redundancy of an Xmedia Server that is available for near instant failover with no interruption in services including on-air playout. The Xmedia Server implements a simple technique of replicating all events that change the database and/or virtual database (VDB).

  • Page 49: Conditions That Trigger A Failover

    A failover occurs when one or more of the following conditions are met: • The primary Xmedia Server service is stopped. • The primary server loses network connectivity. •...

  • Page 50: Mos Enabled Replication

    The Newsroom Control System (NCS), which requires the Xmedia Server MOS presence, is configured to be aware of the Xmedia Server using a single IP address, which is often referred to as the Virtual IP address.

  • Page 51: Replication Settings On The Xmedia Server Control Panel

    Replication is setup and enable using the Xmedia Server Control Panel’s R page EPLICATION on both the primary and secondary servers (figure 6-2). To open the Xmedia Server Control Panel, select Start>Settings>Control Panel>VertigoXmedia XmediaServer and then select the R tab.
  • Page 52 Replication of the XMS Server’s Database IP: The name or IP address of the peer host. It is specifically the UDDY ETTINGS OST NAME OR name as it is known to this server. It is typically the same as “PeerPublicHost”. However, it can be different if you chose to use a private network between the two nodes.

  • Page 53: Setting Up And Enabling Xmedia Server Replication

    Setting up and enabling Xmedia Server replication The procedure below identifies the high-level steps involved in setting up and enabling the replication service of the Xmedia Server’s database. Subsequent sections (identified by the links within the procedure) provide step-by-step instructions for performing each step.

  • Page 54: Server Replication Requirements

    Replication of the XMS Server’s Database Server replication requirements Before setting up or using Xmedia Server’s replication, you should ensure that the servers respect the specific guidelines and requirements that are necessary to support replication. The following table briefly lists the mandatory requirements for Xmedia Server replication.
  • Page 55 Repeat steps 1 to 4 on the secondary server. Confirm that the Machine IDs are an exact match. If they are not, contact a Miranda technical services representative. Figure 6-3. The dongle’s Machine ID is displayed on the Xmedia Server Control Panel’s Licensing page XMS Configuration Guide...
  • Page 56 Stop the XMS service on the server that is about to receive the license file, and then paste/replace the license file. Figure 6-4. The server’s licenses are displayed on the Xmedia Server Control Panel’s Licensing page XMS Configuration Guide...
  • Page 57 Verify the XmediaServer software versions on both servers Ensure that both the primary and secondary servers are running the same version of the VertigoXmedia XmediaServer software. Open the Xmedia Server Control Panel of each server and compare the software versions displayed on the G page (figure 6-6).
  • Page 58 MOS is enabled. If this is not the case, then you do not need to proceed with this procedure. To verify and/or install the Xmonitor service: Verify if the Xmonitor service is already installed on the server. Open the Xmedia Server Control Panel. Select the S tab. ERVICE...
  • Page 59 Replication of the XMS Server’s Database Install the Xmonitor service. Open the server’s command prompt window (S > R and type cmd, TART MENU then press E NTER At the prompt, type: “%vxapps%”\..\lib\xmonitor –i Press E NTER Figure 6-8. Launch the Vertigo Xmonitor installation from the command prompt Start the Vertigo Xmonitor service.

  • Page 60: Specifying The Replication Settings On The Primary Server

    Then, select the R tab. EPLICATION Figure 6-10. The Xmedia Server Control Panel’s Replication page on the primary server A quick-reference of each of the Replication page’s fields and settings is available on page 6-4. Meanwhile, the following topics provide instructions for specifying the necessary settings for server replication.
  • Page 61 , which is an identifier added to each file name in the queue folder. UEUE Enabled check box Queue settings To set the Queue settings: Open the Xmedia Server Control Panel and select the R tab. EPLICATION Select the E check box. NABLED Type the full path for the folder’s location (i.e.
  • Page 62 ERVER ATABASE CONNECTION Database connection while the two servers are still fully independent of each other. To set the DataServer Database connection settings: Open the Xmedia Server Control Panel and select the R tab. EPLICATION Ensure that the E check box is selected.
  • Page 63 Open the command prompt and type: ipconfig Figure 6-12. The server’s IP Configuration values Take note of the server’s IP and S ADDRESS UBNET Open the Xmedia Server Control Panel and select the R tab. EPLICATION Ensure that the E check box is selected. NABLED...
  • Page 64 On the buddy server, open the command prompt and type: ipconfig Take note of the server’s IP ADDRESS Go back to the server that you are configuring. Open the Xmedia Server Control Panel and select the R tab. EPLICATION Ensure that the E check box is selected.
  • Page 65 Next, you must identify the buddy server by also providing it a name. Then click A PPLY The same procedure must be performed on the secondary server’s Xmedia Server Control Panel’s Replication page, but the settings should be inverted (see figure 6-14).

  • Page 66: Specifying The Replication Settings On The Secondary Server

    Replication of the XMS Server’s Database Specifying the Replication settings on the secondary server Once you have specify all of the replication settings on the primary servers Xmedia Server Control Panel’s Replication page, you must also specify the complimentary replication settings on the secondary server’s Xmedia Server Control Panel’s Replication page.

  • Page 67: Make A Backup Of The Primary Server's Database

    ONTROL THE ERVER ensure that the DataServer remains paired with the Xmedia Server at all times in a replication environment. An essential objective in the replication environment is to keep the server (which in reality has two components: the XMS and the Data Server) together.

  • Page 68: Specifying The Server Settings On Client Applications

    Xmedia Servers. Therefore, you must open each of the client applications and specify the appropriate Server settings for the primary and the secondary Xmedia Servers (also referred to as the backup Xmedia Server). To specify the server settings on a client application:...
  • Page 69 SERVER PORT secondary server’s Xmedia Server Control Panel. This is typically, 14050. IP A The IP address of the primary Xmedia Server that is running the ERVER DDRESS Data Server. Thus, this value should be identical to the value set...

  • Page 70: Verifying Proper Functioning Of The Servers And Replication

    Stop the primary Xmedia Server’s XMS service control. Failback Start the primary Xmedia Server’s XMS service control. Failover Terminate the primary Xmedia Server’s service control using a kill utility like PsKill (or similar). Failback The service control manager should auto-start the primary XMS.

  • Page 71: Mos Server Configuration And Monitoring

    ONFIGURATION AND ONITORING The Xmedia Server Control Panel’s MOS Server settings enable the Xmedia Server as a Media Object Server, which allows it to integrate into newsroom environments. As a MOS server, the Xmedia Server uses the MOS protocol to send metadata and pointer information about its MOS objects (i.e.

  • Page 72: Configuring The Xmedia Server's Mos Settings

    Configuring the Xmedia Server’s MOS settings Selecting the MOS tab on the Xmedia Server Control Panel displays the MOS component settings for the Xmedia Server. The MOS page has three (3) views, which are controlled using the MOS O drop-down list at the top of the MOS page. Figure...

  • Page 73: Instructions For Configuring The Xmedia Server As A Mos Server

    Specify and/or verify the following options: Type VERTIGO (all capital letters) in the MOS ID field. All MOS messages to and from the Xmedia Server will be identified by this MOS ID. If the Xmedia Server has been configured for a replication environment (see...
  • Page 74 NCS client. When disabled, the Xplay playlists will not be deleted when the NCS’s rundowns are deleted. Identify the Newsroom Control System (NCS) that the Xmedia Server will communicate with by selecting the N button in the Newsroom Control System (NCS) section.
  • Page 75 Xmedia Server Control Panel. Or, click OK to close the Xmedia Server Control Panel. Figure 7-5. Stop and restart the XMS Service to apply the MOS server settings to the Xmedia Server XMS Configuration Guide...

  • Page 76: Editing The Newsroom Control System's Properties

    “The service is running.” Click A and then return to the MOS configuration page by selecting the MOS PPLY tab at the top of the Xmedia Server Control Panel. Or, click OK to close the Xmedia Server Control Panel. XMS Configuration Guide...

  • Page 77: Deleting The Newsroom Control System

    MOS Server Configuration and Monitoring Deleting the Newsroom Control System To delete the Newsroom Control System’s properties: Open the Xmedia Server Control Panel and select C from the MOS ONFIGURATION drop-down list. OPTION Verify that the E check box is selected.

  • Page 78: Logging Mos Server Activities

    Figure 7-8. MOS Logging Options and log file access buttons Specifying MOS logging options The Xmedia Server Control Panel’s MOS Configuration page provides you with a set of MOS , which determine the criteria for what type of information populates the...

  • Page 79: Viewing The Mos Log File

    MOS Server Configuration and Monitoring Viewing the MOS log file During operation, the Xmedia Server’s MOS activities are recorded in a log file. The logging criteria is determined by the settings specified in the MOS L (see page 7-8). OGGING...

  • Page 80: Monitoring Inbound/Outbound Mos Messages

    ONITOR PTION (figure 7-11), which allows you to view the real-time inbound and outbound MOS messages that are being communicated between the Xmedia Server (MOS Server) and the Newsroom Control System (NCS). The I column displays messages that originate from the NCS. The...

  • Page 81: Mapping Mos Channels

    (i.e published to all locations inferred by the MOS channel name). A MOS channel map is created on the Xmedia Server Control Panel by adding a MOS for each of the MOS channel names listed in the NCS’s rundown. The...

  • Page 82: Adding A Mos Channel Association

    MOS Server Configuration and Monitoring Adding a MOS Channel Association A MOS channel map is created on the Xmedia Server Control Panel by adding a MOS for each of the MOS channel names listed in the NCS’s rundown. CHANNEL SSOCIATION To map a MOS channel name to a publish location: Open the Newsroom Control System (NCS) client application (i.e.
  • Page 83 MOS Server Configuration and Monitoring Click A The A MOS C dialog box closes and the MOS channel DD A HANNEL SSOCIATION name’s channel map is immediately displayed in the MOS C list. HANNEL APPINGS Optional: Click R to refresh the MOS channel mappings list to verify if any other EFRESH additions, deletions, or modifications of channels, devices and publoc2 assets have taken place.

  • Page 84: Editing A Mos Channel Association

    SSET TYPE Click S and the E MOS C dialog box closes. HANNEL SSOCIATION The edits made to the MOS channel association are immediately displayed in the MOS Channel Mappings list on the Xmedia Server Control Panel. 7-14 XMS Configuration Guide...

  • Page 85: Deleting A Mos Channel Association

    Figure 7-18. Select Yes to delete the select MOS channel association Click Y to confirm your intention to delete the selected MOS channel association. The MOS channel association is immediately removed from the MOS Channel Mappings list on the Xmedia Server Control Panel. XMS Configuration Guide 7-15...

  • Page 86: License Management

    Licensing page provides you with an interface where you can: • View the list of the existing application and device licenses stored on the Xmedia Server. • View the details of a particular license, such as which computer or IP address is using the license, the license type, the allocation count...etc.

  • Page 87: An Overview Of Vertigo Suite Licenses

    All Vertigo Suite applications and devices require a valid license to operate. These licenses are added to and stored on the central Xmedia Server (or in some cases on the Intuition XG’s EXMS). Factory configured XGs and Miranda commissioned Xmedia Servers will already have licenses installed according to the sales agreement.

  • Page 88: Vertigo Suite Application And Device Licenses

    License Management Vertigo Suite application and device licenses All Vertigo Suite applications and devices are required to have a valid license. Without a license the application or device will not be able to launch, or it will not operate to full functionality.

  • Page 89: Types Of Vertigo Suite Licenses

    Fixed licenses restrict the use of an application to one specific computer or device. Fixed licenses are recommended for a single-user or a devoted machine environment. The Xmedia Server allows you to deallocate (free up the license so that it can be used by another machine) up to four (4) times. The D...

  • Page 90: The Vxls.bin License File

    Figure 8-1. The license file (vxls.bin) and its backups are stored in the Apps folder on the XMS The following instructions explain how to revert to a valid license file using a backup. The same procedure can be followed to install a license file sent by Miranda’s Technical Support team.

  • Page 91: Xmedia Server Control Panel Licensing Page Versus License Manager

    Server. Vertigo Suite applications, like Xstudio, are installed on client computers and the Xmedia Server is likely only accessible to the IT technicians. As such, the Vertigo Suite applications (i.e. Xplorer, Xstudio, Xbuilder, and Xplay) are equipped with a L ICENSE (figure 8-2) that allows you to view and manage licensing from the application.

  • Page 92: Licensing In A Server Replication Environment

    Since a critical part of the licensing mechanism is that machine ID matches exactly with the license, each Xmedia Server must have a dongle with matching Machine IDs. If the dongles do not have the same Machine IDs, then a licensing error will occur and client applications will not be able to connect to the secondary server when a failover occurs.

  • Page 93: Orientation To Xmedia Server Control Panel's Licensing Page

    Figure 8-3. Switching between the Licensing page’s Licenses and Softkeys views The following sections provide a quick reference of the field and settings on each of the views on the Xmedia Server Control Panel’s Licensing page, including a brief description of what the view allows you to accomplish.

  • Page 94: Licences View - License Summary Tab

    License Summary table which lists all of the licenses that are currently installed on the Xmedia Server. Each row in the table represents a license category and provides the license’s name, type, and the number of licenses installed , and L ).

  • Page 95: Licenses View - License Detail Tab

    License Management Licenses view - License Detail tab Figure and the following descriptions provide an overview of the L table ICENSE ETAIL that is displayed when the License Detail tab is selected, or when a row in the License Summary table is double-clicked. The License Detail table is a one-row listing of properties related to the particular license that was last selected in the License Summary table.
  • Page 96 License Management • Computer: The name of the machine that is currently using the floating license. • IP Address: The IP address of the machine that is currently using the floating license. • Machine ID: The Machine ID of the computer that is currently using the floating license. •...

  • Page 97: Soft Keys View

    Soft Keys page. Figure 8-6. The Soft Keys page helps you to acquire and add new licenses to the Xmedia Server Machine ID: This is a unique machine ID of the computer running the Xmedia Server.
  • Page 98 License Management License Keys: A license key is a long alpha-numeric code that Miranda’s Technical Support sends you in response to a license request. The license key is used to add and engage licenses on the Xmedia Server. Paste Softkey: Since the license keys are long alpha-numeric codes, it is recommended that you copy (CTRL+C) the license key(s) from the email onto your clipboard.

  • Page 99: Viewing The Existing Device And Application Licenses

    All of the licenses currently installed on the Xmedia Server Figure 8-7. The License Summary table provides a list of the licenses installed on the Xmedia Server If the Xmedia Server Control Panel’s Licensing page does not display the License Summary table: •...

  • Page 100: Viewing The Details Of A Particular License

    License Detail left-to-right. These properties cannot be edited, except for deallocating a license (see page 8-22). Therefore, we recommend that you contact your Miranda Sales representative if the License Details does not contain the expected license settings. XMS Configuration Guide 8-15...

  • Page 101: Resolving License Errors And Adding Licenses To The Xmedia Server

    Resolving license errors and adding licenses to the Xmedia Server Your system’s license requirements may have already been installed on the Xmedia Server when the system was factory configured or commissioned. Nevertheless, there are circumstance in which you may be required to resolve a license error that is preventing an application from opening, or features from being functional.

  • Page 102: Verifying The Application's Or Device's Server Settings

    The source of a license error may be as simple as incorrect server settings on the application or the device. The server settings specify the Xmedia Server’s IP address and port, which allow the Xmedia Server to communicate licensing information to the applications and devices.
  • Page 103 (figure 8-12). ETTINGS Figure 8-12. The application’s Setting dialog box Verify that all of the settings are correct, especially the Xmedia Server’s IP address and port. If necessary, make the appropriate changes to the settings. Click OK to close the S dialog box.
  • Page 104 HANGES Close the XG/CG window and then launch it again. If the settings are correct but the licensing messages still appears, then verify the License Summary table and License Details on the Xmedia Server Control Panel’s Licensing page (see page 8-20).

  • Page 105: Verifying The License Summary And License Details

    As such, we recommend that you verify the License Summary table to ensure that the appropriate license is indeed installed on the Xmedia Server. If so, then we also recommend that you verify the License Details to ensure that all of the license’s properties are valid.

  • Page 106: Acquiring And Adding Licenses To The Xmedia Server

    NUMBER Support department (support@miranda.com) and describe your need for valid licenses. Upon receipt of the email, a Miranda representative will verify the licensing agreement that you purchased and an email will be returned to you with the appropriate license code (soft key).

  • Page 107: Deallocating A Fixed License

    Licenses rarely need to be transferred or shared in these circumstances, but in case they do, the Xmedia Server allows you to manually deallocate a fixed license up to four (4) times. If you wish to deallocate a fixed license more than four times, you must contact Miranda’s Technical Support department.
  • Page 108 (figure 9-1) allows you to set parameters OGGING to create a logging criteria that records the status of Xmedia Server events while the XMS Service is operating. The Xmedia Server events are recorded to a log text file (XmediaServer*.log), which allows you to determine whether the Xmedia Server is being used correctly and it helps you to diagnose error conditions.

  • Page 109: Logging Xmedia Server Events

    Logging Xmedia Server Events The Xmedia Server’s Logging Levels and Debug Categories settings (figure 9-2) allow you to specify the type and categories of events that you want to be recorded in the Xmedia Server log files. EVEL This sets the default log level used by all logging categories except those that have been checked in the Debug Categories list.
  • Page 110 Logging Xmedia Server Events Log Destinations The following settings allow you to manage and access the Xmedia Server log files on your system. • : Currently not available for external use. The events are written to a OG TO CONSOLE console for Miranda personnel to use for testing and debugging tasks.

  • Page 111: Work Order Workflow Configuration

    ORKFLOW OPTIONS that appear on the Xmedia Server Control Panel’s Workflow page. Another feature of the Xmedia Server Control Panel’s Workflow page is the E-N OTIFICATION workflow option, which allows the work order module to automatically send email alerts to users when a job’s assignee is specified, or when a work order’s has transitioned to a new...

  • Page 112: Xmedia Server Control Panel's Workflow Options

    Work Order Workflow Configuration Xmedia Server Control Panel’s Workflow options Selecting the W tab on the Xmedia Server Control Panel displays the W page. ORKFLOW ORKFLOW The W page is a multi-view interface that allows you to configure the W...

  • Page 113: Workflow Models

    (i.e. add new users, or edit roles or permissions) to meet your organization’s work order needs. The following diagram and descriptions identify the states and transitions in the Xmedia Server’s default work order workflow. START: Work orders and jobs are requests made...
  • Page 114 In such a case, the default workflow’s options can be edited to any degree to accommodate your organization’s needs. Figure 10-2 demonstrates that the Xmedia Server’s W can be simplified ORKFLOW PTIONS to reflect work order workflow models that are as simple as a three-state (2 transitions) workflow.

  • Page 115: Workflow Option: States

    Figure 10-3. The States option displays a list of the current workflow’s states Figure 10-3 and the following list identifies the workflow states that are present in the Xmedia Server’s default workflow. Further details are also available on page 10-3. • START - The work order/job is created.

  • Page 116: Adding A New State To The Workflow

    Work Order Workflow Configuration Adding a new state to the workflow To add a new state to the workflow: Open the Xmedia Server Control Panel and select S from the W TATES ORKFLOW OPTION drop-down list. Click A in the lower-right corner of the Workflow page.

  • Page 117: Editing A State's Properties

    Work Order Workflow Configuration Editing a state’s properties To view and edit the properties of a state that already exists in the workflow: Open the Xmedia Server Control Panel and select S from the W TATES ORKFLOW OPTION drop-down list.

  • Page 118: Removing A State From The Workflow

    In other words, a state can only be deleted from the workflow if it is not actively assigned to a transition. To remove and delete a state from the current workflow: Open the Xmedia Server Control Panel and select S from the W TATES ORKFLOW OPTION drop-down list.

  • Page 119: Workflow Option: Permissions

    Figure 10-7 and the following lists identifies the workflow permissions that are present in the Xmedia Server’s default workflow. • - Grants permission to approve/reject a completed job RTISTIC PPROVAL •...

  • Page 120: Adding A New Permission To The Workflow

    Work Order Workflow Configuration Adding a new permission to the workflow To add a new permission to the workflow: Open the Xmedia Server Control Panel and select P from the W ERMISSIONS ORKFLOW drop-down list. OPTION Click A in the lower-right corner of the Workflow page.

  • Page 121: Editing A Permission's Properties

    Work Order Workflow Configuration Editing a permission’s properties To view and edit the properties of a permission that already exists in the workflow: Open the Xmedia Server Control Panel and select P from the W ERMISSIONS ORKFLOW drop-down list. OPTION Select the permission that is to be edited from the A list.

  • Page 122: Removing A Permission From The Workflow

    To remove and delete a permission from the current workflow: Open the Xmedia Server Control Panel and select P from the W ERMISSIONS ORKFLOW drop-down list.

  • Page 123: Workflow Option: Transitions

    Work Order Workflow Configuration Workflow option: Transitions Transitions are the specific actions, like assign or approve, that are executed by users to advance the work order from one state to the next. Transitions are made available only to users who are assigned a specific role and permissions. They are created and configured in the T workflow option section of the X RANSITIONS...

  • Page 124: Transition Properties And Permissions

    Work Order Workflow Configuration Transition properties and permissions A transition’s properties are initially defined when the transition is created using the N dialog box (see “Adding a new transition to the workflow” on page 10-18). Once RANSITION the transition has been created you can view or edit the transition’s properties and permission assignment in the T dialog box (see “Editing a transition’s...
  • Page 125 Work Order Workflow Configuration Transition tab settings The following table describes each of the settings that are found on the T tab of RANSITION the T dialog box. These descriptions also explain the affect that the RANSITION ROPERTIES settings have on the appearance and behavior of the transition buttons that appear on the Work Order and jobs windows in the Vertigo Suite applications.
  • Page 126 Work Order Workflow Configuration Target role Identifies the role that will be assigned to the job after the transition is executed. If the assignee is specified during the transition, the assignee must have this role to be able to proceed. See “Permissions tab”...
  • Page 127 Work Order Workflow Configuration Permissions tab The P tab on the T dialog box displays the permissions ERMISSION RANSITION ROPERTIES that have been assigned to the transition (figure 10-13). The permissions ensure that only certain users are able to use the transition to move the work order or job from one state to another.

  • Page 128: Adding A New Transition To The Workflow

    Work Order Workflow Configuration Adding a new transition to the workflow To add a new transition to the workflow: Open the Xmedia Server Control Panel and select T from the W RANSITIONS ORKFLOW drop-down list. OPTION Click A in the lower-right corner of the Workflow page.
  • Page 129 Work Order Workflow Configuration Select the P tab and add permissions to the transition. These permissions ERMISSIONS ensure that only users that have been granted specific permissions are able to use the transition to move the work order or job from one state to the other. Click A The A dialog box appears (figure 10-16).

  • Page 130: Editing A Transition's Properties And Permissions

    Work Order Workflow Configuration Editing a transition’s properties and permissions To edit an existing transition’s properties and/or permissions: Open the Xmedia Server Control Panel and select T from the W RANSITIONS ORKFLOW drop-down list. OPTION Select the transition that is to be edited from the A list.

  • Page 131: Deleting A Transition From The Workflow

    R button in the lower-right EMOVE corner of the Workflow page. To remove and delete a permission from the current workflow: Open the Xmedia Server Control Panel and select T from the W RANSITIONS ORKFLOW OPTION drop-down list.

  • Page 132: Workflow Option: Priorities

    Figure 10-19 identifies the priorities that are present in the Xmedia Server’s default workflow. Although these default priorities suggest degrees of urgency, it is completely up to your organization to define the meaning and assignment of these priorities to work orders.

  • Page 133: Adding A New Priority To The Workflow

    Work Order Workflow Configuration Adding a new priority to the workflow To add a new priority category to the existing workflow: Open the Xmedia Server Control Panel and select P from the W RIORITIES ORKFLOW drop-down list. OPTION Click A in the lower-right corner of the Workflow page.

  • Page 134: Deleting An Existing Priority From The Workflow

    Priorities view is disabled (greyed out). However, if neither of the two conditions is true, then you can use the procedure below to delete the priority from the workflow. To remove and delete a priority from the current workflow: Open the Xmedia Server Control Panel and select P from the W RIORITIES ORKFLOW OPTION drop-down list.

  • Page 135: Workflow Option: Roles

    Work Order Workflow Configuration Workflow option: Roles There are some actions within the work order workflow, like approving a job, that you will want to restrict to a certain group of people. Rather than assigning individual permissions to each user, you can create groupings of permissions, called roles. Roles allow users to perform the tasks applicable to their job function.

  • Page 136: Adding A New Role To The Workflow

    Therefore, we also recommend that you review the roles that already exist in the workflow before adding a new role. To add a new role to the workflow: Open the Xmedia Server Control Panel and select R from the W OLES ORKFLOW OPTION drop-down list.
  • Page 137 Work Order Workflow Configuration Select the P tab and add permissions to the role. Users with this role are ERMISSIONS granted these permissions, which allow them to perform their job functions within the workflow. Click A The A dialog box appears (figure 10-24). DD PERMISSIONS TO ROLE Figure 10-24.

  • Page 138: Editing An Existing Role's Properties And Permissions

    Work Order Workflow Configuration Editing an existing role’s properties and permissions To edit an existing role’s properties and/or permissions: Open the Xmedia Server Control Panel and select R from the W OLES ORKFLOW OPTION drop-down list. Select the role that is to be edited from the A list.

  • Page 139: Deleting A Role From The Workflow

    However, if neither of the two conditions is true, then you can use the procedure below to delete the priority from the workflow. To remove and delete a role from the current workflow: Open the Xmedia Server Control Panel and select R from the Workflow option drop- OLES down list.

  • Page 140: Workflow Option: Users

    Work Order Workflow Configuration Workflow option: Users Only people with a registered user profile can participate in the work order workflow. User profiles consist of a user name and password. Each user is assigned a role (or many roles), which determines what functions the user is allowed to perform in the workflow process. For example, figure 10-27 demonstrates the need for user profiles to be created to allow...

  • Page 141: Add A New User To The Workflow

    Work Order Workflow Configuration Add a new user to the workflow To add a new user to the workflow: Open the Xmedia Server Control Panel and select U from the W SERS ORKFLOW OPTION drop-down list. Click A in the lower-right corner of the Workflow page.
  • Page 142 Work Order Workflow Configuration Select the R tab. The Roles tab displays the roles that have been assigned to the user. OLES Click A The A dialog box appears (figure 10-30). DD ROLES TO USER Figure 10-30. Select the roles that you want to add to the user’s profile Select the role(s) that are to be added to the user profile.

  • Page 143: Edit A User's Workflow Properties And/Or Roles

    Work Order Workflow Configuration Edit a user’s workflow properties and/or roles To edit an existing user’s properties and/or roles: Open the Xmedia Server Control Panel and select U from the W SERS ORKFLOW OPTION drop-down list. Select the user profile that is to be edited from the A list.

  • Page 144: Deleting A User From The Workflow

    Workflow page’s Users view is disabled (greyed out) EMOVE when you are unable to delete a user because of the above two conditions. To delete a user profile from the current workflow: Open the Xmedia Server Control Panel and select U from the W drop- SERS ORKFLOW OPTION down list.

  • Page 145: Setting Up E-Notifications

    (figure 10-33) allows you to OTIFICATIONS configure the Xmedia Server to automatically send an email to alert specific workflow users when a job’s assignee is specified, or when a work order’s state has changed. Figure 10-33. The Workflow page’s E-Notifications workflow option...

  • Page 146: Creating The Email Template Files For E-Notifications

    Prior to being able to use the e-notification system, you must first create the email template text files for the state change and job assignment notifications. Using Notepad, you must create two (2) separate template text files and save them in a directory that is accessible to the Xmedia Server: • StateEmailTpl.txt •...

  • Page 147: Setting The Notification Parameters

    • Either type the exact directory path location of the Job Assignment template’s text file. • Click the Browse button and browse for the Job Assignment template’s text file. Click A in the lower-right corner of the Xmedia Server Control Panel. PPLY XMS Configuration Guide 10-37...

  • Page 148: Creating An E-List For Each State Change Notification

    Work Order Workflow Configuration Creating an E-List for each state change notification The U section of the E-N workflow option page OTIFICATION TATE OTIFICATION (figure 10-35) allows you to create an email recipient list (E-L ) for each of the states in the workflow.
  • Page 149 Work Order Workflow Configuration Click the M button . The L dialog box IST OF E MAILS OF EXISTING USERS appears (figure 10-37) and displays the email addresses of all of the users with workflow user profiles. Figure 10-37. Create the E-List by selecting user email addresses Select the email addresses that are to be added to state’s e-notification.

  • Page 150: Editing A State Change Notification's E-List

    Work Order Workflow Configuration Editing a state change notification’s E-List The following sections provide instructions for adding or removing workflow users from a state’s E-Notification email list (E-List): • “Adding additional users to the E-List” on page 10-40 • “Removing an individual user from the E-List” on page 10-41 •...
  • Page 151 Work Order Workflow Configuration Removing an individual user from the E-List To remove an individual user from a state’s E-list: Open the state’s S dialog box by either: TATE MAIL APPING • Double-clicking on a state in the U section of the OTIFICATION TATE E-Notification page.
  • Page 152 YSTEM ARAMETERS (ingested) into the Xmedia Server, at what time expired published and archived assets will be purged from the target device and XMS storage respectively. You can also set the system’s field rate on this page.

  • Page 153: Setting The Xms System Parameters

    Intuition XG. By lowering the ingest throttle throughput you may be able to avoid playout performance issues on the Intuition XG. The ingest throttle throughput is the rate at which binary data is ingested into the Xmedia Server. It is reported in units of megabits per second (mbits/sec).

  • Page 154: Setting The Expiration Parameters

    Setting the XMS System Parameters Setting the Expiration Parameters When an asset is ingested into the Xmedia Server, you have the option of setting the E XPIRY and P fields in the Vertigo Suite application’s I window. These UBLISH IFESPAN...

  • Page 155: Setting The System Field Rate

    Setting the XMS System Parameters Setting the System field rate The S setting on the S page (figure 11-4) allows you YSTEM FIELD RATE YSTEM ARAMETERS to specify the frame rate at which scenes are intended to be played out. It also specifies what zone the playout is intended for.
  • Page 156 Server to communicate with master control and automation systems using the Oxsox protocol. You can also set the logging options to record the OxSox activities to a log file. Figure 12-1. The Xmedia Server Control Panel’s OxSox page XMS Configuration Guide...

  • Page 157: Oxsox Connection Settings

    NABLE ALL CATEGORIES Enabling all categories allows the Xmedia Server to reflect all of the assets in its database regardless of category as a flat list, thereby emulating the Intuition and ImageStore. When disabled, the XMS only reflects the assets stored in the asset type root categories.
  • Page 158 You must use the Xmedia Server Control Panel’s A page to configure the UTOMATION Xmedia Server to communicate with an automation system for the purposes of schedule- based publishing. Figure 13-1. The Automation page XMS Configuration Guide...

  • Page 159: Xftp Settings

    ETTINGS Although the XFTP page still exists on the Xmedia Serve Control Panel, the functionality of importing files using a FTP server running locally on the Xmedia Server has been deprecated. Figure 14-1. The Xmedia Server Control Panel’s XFTP page...

  • Page 160: Controlling The Xms Service

    Xmedia Server is powered up. Once properly configured, you usually do not have to interact with the service or the Xmedia Server Control Panel unless you want to run diagnostic tests on the system or you want to change the configuration settings that affect the relationship between the XMS, Vertigo Suite applications, and/or Vertigo devices.

  • Page 161: Verifying The Xms Service's Status

    Controlling the XMS Service Verifying the XMS service’s status You can quickly verify if the XMS service is running or stopped by checking the S ERVICE status displayed on the Xmedia Server Control Panel’s S page. TATE ERVICE ONTROL Figure...

  • Page 162: Stopping And Starting The Xms Service

    AUNCH SERVICE AT SYSTEM STARTUP allow the XMS service to be started automatically, there are situations where you will need to stop or start the service manually using the buttons on the Xmedia Server Control Panel’s Service Control page. To manually stop the XMS service:...

  • Page 163: Automatically Starting The Xms Service

    XMS service TART Automatically starting the XMS Service The Xmedia Server Control Panel provides you with two (2) settings to that enable the system to automatically start or restart the XMS service without user interaction. When the L...

  • Page 164: Controlling The Dataserver

    ONTROL THE ERVER with the Xmedia Server at all times in a replication environment. The objective in the replication environment is to keep the server’s two components, the XMS and the Data Server, together. As a result of enabling this setting, the Xmedia Server becomes the master server to a Data Server and therefore is replicated as well.

  • Page 165: Launching The Services Management Console

    ROPERTIES control over the service. Since the most common functionality (i.e. stopping and restarting the XMS service) is already provided on the Xmedia Server Control Panel’s Service Control page, we discourage the use of this interface. Figure 15-7. The XmediaServer Properties window is only for advanced users...
  • Page 166 Xmedia Server Control Panel displays a real- UNTIME TATISTICS time tally of the Xmedia Server’s session events and the asset content of its database. This information is useful when you have two Xmedia Servers in a replication setup (page 6-1).

  • Page 167: Displaying Xms Runtime Statistics

    The number of back channel messages sent to all clients for the lifetime of MESSAGES SENT this Xmedia Server session. The number of assets that have been added to the Xmedia Server database SSET NSERTS since the beginning of the current XMS service session.
  • Page 168 The number of template assets that are stored on the Xmedia Server. EMPLATE COUNT The number of video clip assets that are stored on the Xmedia Server. IDEO COUNT The number of work orders that are stored on the Xmedia Server.
  • Page 169 17-1 demonstrates that the recipient server XMS 1 has listed the propagation server (XMS 0) as a propagation location on its Xmedia Server Control Panel. In such a configuration, when assets are propagated from the XMS 1 server to the XMS 0 server, the XMS 0 server may also propagate the assets to the other associated servers (XMS 2 &...

  • Page 170: Propagating Assets To Other Xmedia Servers

    Automatic propagation requires you designate propagable categories on the propagation server’s Xmedia Server Control Panel. Once this is set up, certain events within the propagable category, like adding or editing an asset, will trigger the propagation server to automatically propagate the category’s assets to the designated recipient servers.
  • Page 171 Propagating Assets to Other Xmedia Servers The following sections provide information and instructions for configuring and using the propagation to move assets and categories using from one Xmedia Server to others: • “Configuring Xmedia Servers for asset propagation” on page 17-4 •...

  • Page 172: Configuring Xmedia Servers For Asset Propagation

    Propagating Assets to Other Xmedia Servers Configuring Xmedia Servers for asset propagation For an Xmedia Server to propagate assets to one or more recipient servers, the recipient servers’ location must be defined in the Propagation Locations settings on the propagation server’s Xmedia Server Control Panel (figure 17-2).
  • Page 173 IP addresses. Also make sure that they can talk to each other via the standard XMS port (by default 14050) and the background port (14051). Open the Xmedia Server Control Panel on the propagation server and select the Propagation tab.

  • Page 174: Using Automatic Propagation

    Instructions for how to create propagable categories and recipient associations for automatic propagation are provided in “Setting up propagable categories and recipient associations” on page 17-7. Figure 17-4. Create propagable categories on the propagation server’s Xmedia Server Control Panel 17-6 XMS Configuration Guide...

  • Page 175: Setting Up Propagable Categories And Recipient Associations

    For an asset to be propagated by automatic propagation, it has to be placed in a propagable category on the propagation server. A category on a propagation server becomes propagable when it is associated with a recipient server on the Xmedia Server Control Panel’s P page.
  • Page 176 Propagating Assets to Other Xmedia Servers In the C column, expand and select the specific category that you wish to ATEGORIES propagate. In the P column, select the check box for the recipient server(s) ROPAGATION OCATIONS that you wish to propagate this category to (figure 17-6). You can choose to propagate to one, multiple, or no spokes.

  • Page 177: Using Manual Propagation

    Propagating Assets to Other Xmedia Servers Using manual propagation Manual propagation allows you to perform an immediate, on-demand propagation of any category of assets stored on the propagation server to a specific recipient server. Unlike automatic propagation, manual propagation does not require you to first set up propagable categories on the propagation server.

  • Page 178: Resolving Propagation Exceptions

    The propagation server is merely notified that an exception occurred on one of its recipient servers. When an exception is raised, the R button is highlighted on EFRESH the recipient server’s Xmedia Server Control Panel’s Propagation Exceptions page. Click the R button to update the Exception List with the most current exceptions. EFRESH The following sections describe each of the three (3) types of propagation exceptions, as well as providing instructions for how to resolve and clear these exceptions.

  • Page 179: Information Propagation Exceptions

    Propagating Assets to Other Xmedia Servers Information Propagation Exceptions Information Propagation Exceptions identify that a problem has occurred during the propagation process, but the problem was resolved without any immediate user intervention required to proceed. An Information Propagation Exception is raised when: •...

  • Page 180: Categorisation Propagation Exceptions

    Propagating Assets to Other Xmedia Servers Categorisation Propagation Exceptions Categorisation Propagation Exceptions are raised when a propagated asset fails to be categorized due to a name clash. Figure 17-11 demonstrates that in such a case, the propagated asset is temporarily renamed within the recipient server’s category until the name conflict is resolved.

  • Page 181: Removing Propagated Assets From A Recipient Server

    To remove an asset or an asset category from both the propagation and recipient servers: Open either Xplorer or Xstudio: Start>Programs>VertigoXmedia>Xplorer Start>Programs>VertigoXmedia>Xstudio Ensure that the application is connected to the Xmedia Server that is designated as the propagation server (T >S >XMS OOLS...

  • Page 182: Propagation And Distributed Work Orders

    Propagating Assets to Other Xmedia Servers Propagation and distributed work orders Work orders are mechanisms within the Vertigo Suite for requesting the creation and addition of assets to the system (figure 17-13). Within a work order job, a placeholder can be created for an image or clip.

  • Page 183: Distributed Work Order Concepts And Behaviors

    Propagating Assets to Other Xmedia Servers Distributed work order concepts and behaviors There are a few concepts and behaviors that you need to be aware of regarding the creation and use of distributed work orders in a hub and spoke propagation system: •...

  • Page 184: Setting Up A Hub And Spoke Server For Distributed Work Orders

    Before using distributed work orders, the Xmedia Servers must be properly configured in a hub and spoke configuration by designating one Xmedia server as the hub server and at least one Xmedia Server as a spoke server. The following sections provide instructions for accomplishing this setup: •...
  • Page 185 Set the V setting to 1 and then click OK. ALUE DATA The resulting registry key should appear similar to the picture below. On the Xmedia Server that is to be designated as the hub server, open the X MEDIA ERVER ONTROL...
  • Page 186 Propagating Assets to Other Xmedia Servers In the N section, fill in the following text fields: ROPERTIES Enter an arbitrary name to identify the spoke. This does not need to be the hostname of the spoke server. The IP address of the spoke server. DDRESS The standard XMS port of the spoke server.
  • Page 187 VERRIDE command, complete the procedure for adding a new spoke node. Select the node from the Propagation Locations section of the Xmedia Server Control Panel’s Propagation page. Click the P button to open the Edit node window. Click the O button.

  • Page 188: Using Distributed Work Orders

    Propagating Assets to Other Xmedia Servers Using distributed work orders The following instructions describe how to generally create a distributed work order within a system configured for propagation. Setup the hub and spoke servers for propagation as described on page 17-16.
  • Page 189 Propagating Assets to Other Xmedia Servers Complete the work order and job fields, including the name of the work order, the name of the job, and the Assignee’s name. Save the work order. The work order, job, and placeholders now exist on both the spoke and the hub server. They are easily identifiable by their spoke-indexed identification number (i.e.
  • Page 190 • “Setting the Central XMS IP Override” on page 18-2 • “The Insta-publish device setting on the Xmedia Server Control Panel” on page 18-3 • “Monitoring and managing publish requests in the queue” on page 18-5 Figure 18-1. The Xmedia Server Control Panel’s Publishing page...

  • Page 191: Setting And Monitoring The Xms Publishing Activities

    Setting and Monitoring the XMS Publishing Activities Setting the Central XMS IP Override The Xmedia Server is often equipped with two network cards and with two IP addresses: a private IP address and a public IP address. The private IP address is only accessible from behind the firewall and it is the server main IP address for the Vertigo Suite.

  • Page 192: The Insta-Publish Device Setting On The Xmedia Server Control Panel

    Xmedia Server Control Panel, it NSTA PUBLISH DEVICE is not relevant to the Xmedia Server. Therefore, there is no impact on the Xmedia Server whether or not the I setting is enabled or disabled. To be on the safe...

  • Page 193: Insta-Publishing From The Exms To A Localhost Device

    Setting and Monitoring the XMS Publishing Activities Insta-publishing from the EXMS to a Localhost device While this guide’s main focus is on configuring the Xmedia Server, the following information applies only to configuring the Embedded Xmedia Server (EXMS) installed on Vertigo XG devices.

  • Page 194: Monitoring And Managing Publish Requests In The Queue

    (figure 18-5) allow you to manage UBLISH EQUEST and monitor (in real-time) the items that are waiting to be published by the Xmedia Server. Figure 18-5. A real-time view of the Publish Requests that are in the Publish Queue Xplorer’s P and Xstudio’s P...
  • Page 195 Setting and Monitoring the XMS Publishing Activities Each row in the Publish Request list identifies an asset that is waiting or has been published by the Xmedia Server. The following information is provided in each row: Asset Identifies the name of the asset.

  • Page 196: User Rights Management

    The Vertigo Suite offers system administrators and workflow managers the possibility of restricting access to some of the functionality on a per-user basis using User Rights Management (URM). Access rights are controlled using the Xmedia Server and the operations, tasks, and roles defined in Microsoft’s Authorization Manager.

  • Page 197: Target Audience And Prerequisites For Setting Up Urm

    Microsoft’s user documentation to determine if the issues are Windows related. If the issues are determined to be specific to the Vertigo Suite’s use of the Authorization Manager, please contact a Miranda Technical Support representative (support@miranda.com).

  • Page 198: Overview Of The Authorization Manager

    User Rights Management Overview of the Authorization Manager User rights management for Vertigo Suite applications is provided by Microsoft’s Authorization Manager (often referred to as AzMan). The Authorization Manager allows for a role-based management system, which grants or restricts user access by mapping the user’s login profiles to roles that are inspired by job functions.
  • Page 199 Policy Store. In essence, an application is a scope or a grouping, and the VertigoXmedia application is the grouping that the Xmedia Server uses via the Authorization Manager to implement an access control list. See “Vertigo Suite Operations”...
  • Page 200 Windows users and groups that are allowed to see the category in the asset browser. They are created by the Xmedia Server and edited within the asset browser in Vertigo Suite applications. The scopes that are created in the Authorization Manager snap-in must not be modified or deleted manually.

  • Page 201: Vertigo Suite Operations

    User Rights Management Vertigo Suite Operations The Vertigo Suite provides a set of pre-defined operations, which are used to implement a security model for the Vertigo Suite applications. Not granting a specific operation to a role is the equivalent of revoking the right to the operation. Instructions for installing these operations within the Policy Store are provided in “Granting the domain user administrative rights to the Organizational Unit”...
  • Page 202 WriteWorkOrderJobOp Grants permission to modify work order jobs WriteWorkOrderOp Grants permission to modify work orders XmsMgmtOp Grants permission to manage the Xmedia Server using the Xmedia Server Control Panel XPSMgmtOp Grants permission to manage the Xpublish Agent XMS Configuration Guide...

  • Page 203: Configuring The Policy Store In Active Directory

    User Rights Management Configuring the Policy Store in Active Directory Before using the Authorization Manager, system administrators must create and configure a Policy Store repository. The Policy Store contains the AzMan-related configuration and Vertigo Suite access restrictions. It is manipulated via a Microsoft Management Console snap-in.
  • Page 204 Store in Active Directory. Please refer to Microsoft’s documentation on user management and Active Directory Service more information. • Create a new domain user, which will be used to grant the Xmedia Server access to the required domain resources. • A new organizational unit named V...

  • Page 205: Open The Authorization Manager

    User Rights Management Open the Authorization Manager Factory configured Xmedia Servers presently run Windows Server 2003, SP1 or later. Within Windows Server 2003, Microsoft provides the Authorization Manager snap-in. Therefore, the Authorization Manager is already installed and you can perform the instructions below to launch the AzMan snap-in.

  • Page 206: Creating A New Organizational Unit And Assigning A Policy Store

    User Rights Management Creating a new organizational unit and assigning a Policy Store Before creating a policy store repository in Active Directory, it is recommended that you create a new Organizational Unit (OU) in the domain Program Data container within the domain-naming context (CN=Program Data residing directly in domain DC container).
  • Page 207 User Rights Management Enable the A setting (radio button). CTIVE IRECTORY Type in the S field the policy store’s LDAP name. For example: TORE C N=LDAPAzMAnStor e ,OU=Vertigo,DC=<yourDomain> This specifies the Policy Store Name as Program Data. Optional - Type a description of the new authorization store in the D text ESCRIPTION box.

  • Page 208: Granting The Domain User Administrative Rights To The Organizational Unit

    User Rights Management Granting the domain user administrative rights to the Organizational Unit Delegate administrative control of the organizational unit to the newly created domain user. If you need further information, please refer to the Microsoft Active Directory documentation: http://technet.microsoft.com/en-us/library/cc778807.aspx To grant the domain user administrative rights to the Vertigo organizational unit: Open the A by selecting:...

  • Page 209: Stopping The Xms Service

    Select the S tab on the X (figure ERVICE ONTROL MEDIA ERVER ONTROL ANEL 12). Figure 19-12. Accessing the XMS Service controls on the Xmedia Server Control Panel Click the S button to stop the XMS Service. 19-14 XMS Configuration Guide...

  • Page 210: Adding The Domain User To The Xmedia Server's Security Credentials

    Adding the domain user to the Xmedia Server’s security credentials A direct consequence of the use of user rights management is that the Xmedia Server and the VxDataServer services must run under a security context other than LocalSystemAccount. In fact, they both need to be running inside the security context of a domain user.
  • Page 211 ERVICES DMINISTRATIVE OOLS ERVICES Navigate down the list of services to the X service. Right-click on the MEDIA ERVER Xmedia Server Service and select P . The X dialog ROPERTIES MEDIA ERVER ROPERTIES box appears (figure 19-16). Figure 19-16. The XmediaServer Properties dialog box...
  • Page 212 User Rights Management Select the L tab and change the Log On as assignment from the local system account to the newly created domain account. Press the B button. The S dialog box appears (figure 19-17). ROWSE ELECT Figure 19-17. The Select User dialog box Type the domain user’s name in the text box and press OK.

  • Page 213: Granting The Domain User Administrative Rights To The Policy Store

    User Rights Management Granting the domain user administrative rights to the Policy Store Delegate administrative control of the Policy Store to the newly created domain user. To edit the Policy Store’s security credentials: Open the Authorization Manager by selecting: >P >A >A TART MENU...
  • Page 214 User Rights Management Click the A button and the S dialog box ELECT SERS OMPUTERS ROUPS appears (figure 19-20). Figure 19-20. Specify the domain user’s name to grant them administrative privileges Type the Domain user’s login name in the text box and click OK. The S ELECT SERS dialog box closes and the user’s name now appears in the...

  • Page 215: Setting The Authorization Manager Configuration Settings

    Starting the XMS Service to populate the VertigoXmedia application After having made changes to the Xmedia Server Control Panel settings, the XMS Service must be restarted for the changes to take effect. In restarting the XMS service, the Xmedia 19-20...
  • Page 216 ANAGER ONFIGURATION VertigoXmedia application (in the store repository) with the Vertigo Suite operations. To start the XMS Service and populate the VertigoXmedia application: With the Xmedia Server Control Panel open, select the S tab on the ERVICE ONTROL Xmedia Server Control Panel.

  • Page 217: Configuring The Policy Store In An Xml File

    User Rights Management Configuring the Policy Store in an XML file Before using the Authorization Manager, system administrators must create and configure a Policy Store repository. The Policy Store contains the AzMan-related configuration and Vertigo Suite access restrictions. It is manipulated via a Microsoft Management Console snap-in.
  • Page 218 “Setting the Authorization Manager Configuration settings” on page 19-33. Start the XMS Service in the Xmedia Server Control Panel and populate the Policy Store with the Vertigo Suite operations. “Starting the XMS Service to populate the VertigoXmedia application” on page 19-34.

  • Page 219: Opening The Authorization Manager

    User Rights Management Opening the Authorization Manager Factory configured Xmedia Servers presently run Windows Server 2003, SP1 or later. Within Windows Server 2003, Microsoft provides the Authorization Manager snap-in. Therefore, the Authorization Manager is already installed and can follow the instructions below for launching the AzMan snap-in.

  • Page 220: Configuring The Authorization Manager To Use An Xml File Stored On A Network Share

    Windows NT file system (NTFS) volume. The XML policy store should be stored on the Xmedia Server as a shared file. If you select to store the Policy Store in an XML file, you’ll need to designate its location in network- accessible folder structure by its path and specify particular permissions for that file.

  • Page 221: Creating The Vertigoxmedia Policy Store In The Authorization Manager

    Vertigo Suite-related Authorization Manager elements. Once the application is created, the Xmedia Server will create the pre-defined set of operations offered by the suite in the application upon first start (after the Xmedia Server Control Panel has been properly configured).
  • Page 222 User Rights Management Select D and click OK. EVELOPER MODE Return to the Authorization Manager window. Right-click the Policy Store node (i.e. X ) and select N command. TORE PPLICATION The N dialog box appears (figure 19-29). PPLICATION Figure 19-29. The New Application dialog box Enter VertigoXmedia as the A and Vertigo Vertigo Suite PPLICATION...

  • Page 223: Obtaining A Windows User With Full Control Of The Shared Directory

    For the Xmedia Server to manipulate the Policy Store, a Windows user must be created and be granted full control of the shared directory. In a later step, the user credentials of the Xmedia Server will be set to this network user who has permission to access and change the XML Policy Store (see page 19-30).

  • Page 224: Stopping The Xms Service

    Select the S tab on the X (figure ERVICE ONTROL MEDIA ERVER ONTROL ANEL 31). Figure 19-31. Accessing the XMS Service controls on the Xmedia Server Control Panel Click the S button to stop the XMS Service. XMS Configuration Guide 19-29...

  • Page 225: Adding The New User To The Xmedia Server's Security Credentials

    Adding the new user to the Xmedia Server’s security credentials Earlier a new user was created. With the XMS Service now stopped, you must grant administrative rights (read/write) to the user on the Xmedia Server machine. To grant the user administrative privileges to the Xmedia Server: Start and log into the Xmedia Server as an Administrator user.

  • Page 226: Changing The Security Credentials Of The Policy Store

    Changing the security credentials of the Policy Store Now that the new user has been granted administrative privileges, they must be added to the Policy Store’s security credentials so that the Xmedia Server can add, delete, or modify the Policy Store (i.e. operations).
  • Page 227 User Rights Management Click the A button and the S dialog box ELECT SERS OMPUTERS ROUPS appears (figure 19-36). Figure 19-36. Specify the user’s name to grant them administrative privileges Type the user’s login name in the text box and click OK. The S ELECT SERS dialog box closes and the user’s name now appears in the...

  • Page 228: Setting The Authorization Manager Configuration Settings

    ETTINGS ONTROL ANEL ERTIGO MEDIA MEDIA ERVER Figure 19-37. Authorization Manager Configuration settings on the Xmedia Server Control Panel Select the E check box in the Authorization Manager Configuration section of NABLED the G page (figure 19-21). ENERAL Set the P URL field.

  • Page 229: Starting The Xms Service To Populate The Vertigoxmedia Application

    Starting the XMS Service to populate the VertigoXmedia application After having made changes to the Xmedia Server Control Panel settings, the XMS Service must be restarted for the changes to take effect. In restarting the XMS service, the Xmedia Server will read the A...

  • Page 230: Setting Up Your User Rights Management System

    User Rights Management Setting up your user rights management system Once the Policy Store repository has been created, the system administrator must populate it with role definitions, and role assignments that are appropriate for your organization’s workflow and security policies. The procedure below identifies the high-level steps involved in setting up your user rights management system in the Authorization Manager.

  • Page 231: Establish Your User Rights Management Security Criteria

    User Rights Management Establish your user rights management security criteria An advantage of building the Vertigo Suite user rights management (URM) model around Microsoft’s Authorization Manager technologies is the flexibility that it affords to system administrators to design and implement a security design that is appropriate to the organization’s specific workflow and security needs.

  • Page 232: Creating A New Task Definition

    User Rights Management Creating a new task definition A task definition is a grouping of operations and/or lower-level task definitions that are similar enough in nature or together they achieve a common goal. Task definitions provide the benefit of not having to repeatedly assign each operation individually to a role definition. Instead you can easily assign the single task definition.

  • Page 233: Creating And Populating A New Role Definition

    User Rights Management Creating and populating a new role definition Role definitions are normally based on a job function in your organization’s workflow. The tasks and operations that are associated with the role provide the mechanism for granting permissions to access content or perform actions. If there are several authorization rules associated with a role definition (for example, it has several lower level roles and tasks), the authorization rules run synchronously.
  • Page 234 User Rights Management Select the D tab on the D dialog box (figure 19-42). EFINITION EFINITION ROPERTIES Figure 19-42. The Role Definition’s properties dialog box Click the A button and the A dialog box appears (figure 19-43). EFINITION Figure 19-43. The Add Definition dialog box allows you to assign roles, tasks, and/or operations Select the tabs on the A dialog box to display the roles, tasks, and EFINITION...

  • Page 235: Creating A New Role Assignment

    User Rights Management Creating a new role assignment A role assignment is a virtual container that is based on a single role definition. Once populated, the role assignment identifies the Windows users and/or groups that are authorized to perform the tasks and operations associated with the role definition. To create a new role assignment: Open Authorization Manager.

  • Page 236: Associating Windows Users And Groups With A Role Assignment

    User Rights Management Associating Windows users and groups with a role assignment The most common procedure that system administrators carry out is the assignment of Windows users and groups to a role definition. Since the role definitions determine the permissions for accessing content or perform actions, a role assignment is responsible for designating which users are granted specific permissions.
  • Page 237 User Rights Management If only one match is found, then the name is immediately added to the text box. However, if multiple names match the search criteria, then the M ULTIPLE AMES OUND dialog box appears (figure 19-46). Select the name of the user(s) that you want to add from the M dialog box and press OK.

  • Page 238: Maintaining The Authorization Manager's Elements

    User Rights Management Maintaining the Authorization Manager’s elements Once your user rights management system for the Vertigo Suite products is properly configured, you may need to occasionally perform maintenance tasks like, editing the characteristics of role definitions, add tasks or operations to a role, or add additional users to a role assignment.
  • Page 239 User Rights Management Adding additional tasks or operations to a role definition The following instructions guide you through the process of adding additional tasks or operations to an existing role definition. To add additional tasks and/or operations to a role definition: Open Authorization Manager.

  • Page 240: Editing Task Definitions

    User Rights Management Deleting a role definition The following instructions guide you through the process of removing an existing role definition from the Authorization Manager. To delete a role definition from the AzMan’s application: Open Authorization Manager. Navigate through the AzMan’s policy store until you reach the Role Definitions folder (i.e.
  • Page 241 User Rights Management Add tasks or operations to a task definition The following instructions guide you through the process of adding additional tasks or operations to an existing task definition. To add additional tasks and/or operations to a task definition: Open Authorization Manager.

  • Page 242: Adding And Removing Users From A Role Assignment

    User Rights Management Deleting a task definition The following instructions guide you through the process of removing an existing task definition from the Authorization Manager. To delete a task definition from the AzMan’s application: Open Authorization Manager. Navigate through the AzMan’s policy store until you reach the Task Definitions folder (i.e.
  • Page 243 User Rights Management To remove a user from a role assignment: Open Authorization Manager. Navigate through the AzMan’s policy store until you reach the R folder SSIGNMENTS (i.e. X >V >D >R TORE ERTIGO EDIA EFINTIONS SSIGNMENTS Expand the Role Assignments folder to display the existing Role Assignments. Select a specific Role Assignment and the users and groups associated with the role assignment are listed in the right-side panel.

  • Page 244: Restricting Access To Asset Categories

    User Rights Management Restricting access to asset categories Normally, the Asset Browser in the various Vertigo Suite applications displays all of the available assets and asset categories. As such, all users have access to these asset categories. Configuring and enabling the user rights management system allows system administrators to restrict access of certain asset categories from specific users.

  • Page 245: Setting Access Permissions For An Asset Category

    ERMISSIONS Authorization Manager is not installed; or that the Xmedia Server does not have its Authorization Manager Configuration settings enabled or set properly; or the user does not have access to the Policy Store.
  • Page 246 User Rights Management The text box provides a space for you to type the names of the user or group that you want to find. Press the C button. HECK AMES If only one match is found, then the name is immediately added to the text box. However, if multiple names match the search criteria, then the M ULTIPLE AMES...
  • Page 247 (figure 19-53). Figure 19-53. The Category Security dialog box lists the users and/or groups who have permission Meanwhile, the Xmedia Server has created a scope and placed it as a folder in the Authorization Manager’s Policy Store (figure 19-54).

  • Page 248: Granting Additional Users Access To A Restricted Category

    User Rights Management Granting additional users access to a restricted category The following procedure describes how to grant additional users permission to access and interact with an asset category that is already restricted to specific users. To add additional users to an asset category’s access control permissions: In the Asset Browser, right-click on the asset category and select the P ERMISSIONS command from the context menu.

  • Page 249: Removing All Access Restrictions From A Category

    User Rights Management Removing all access restrictions from a category The following procedure describes how to all remove users from a category’s security and thereby removing all access restrictions from the category. As a result, the category will once again be accessible to all users. To remove all access restrictions from an asset category rendering it accessible to all users: In the Asset Browser, right-click on the asset category and select the P...

  • Page 250: Ingesting Media Files Using The File Ingest Server

    The Vertigo File Ingest Server is an application that can be used to automatically ingest media into the Xmedia Server by simply placing the media files into a user-created ingest folder (watch folder). The File Ingest Server is also responsible for issuing media conversion requests to the Transcode Server, which is the service responsible for transcoding media from one format to another.
  • Page 251 Monitor. The following sections describe how to set up and use the File Ingest Server to ingest media into the Xmedia Server from a watch folder: • “Installing the File Ingest Server and creating an ingest watch folder” on page 20-3 •...

  • Page 252: Installing The File Ingest Server And Creating An Ingest Watch Folder

    Xmedia Server. However, if your organization’s demand for ingest and transcoding is particularly high, we recommend installing and running the File Ingest Server and Transcode Server on a dedicated ingest server as to not burden the resources of the Xmedia Server. Installing the File Ingest Server and Transcode Server: Recent factory-configured Xmedia Servers will already have the File Ingest Server and Transcode Server installed as part of the Vertigo Suite software.

  • Page 253: Running The File Ingest Server And Transcode Server

    Ingesting media files using the File Ingest Server Running the File Ingest Server and Transcode Server Both the File Ingest Server and the Transcode Server are applications that should start-up automatically and run in the background. When they are started, the File Ingest Server and Transcode Server icons both appear in the Windows notification area (figure 20-3).

  • Page 254: Configuring An Ingest Server Instance

    Ingesting media files using the File Ingest Server Configuring an ingest server instance The File Ingest Server can be configured to watch one or more watch folders by defining instances of the ingest server in the File Ingest Server Control Panel (figure 20-5). Each instance defines the set of rules that are mapped to a watch folder and determines how the files will ingested, including if any file format conversion is necessary.
  • Page 255 The Ingester Settings window appears and displays the instance’s property settings on six (6) tabbed pages. Together these settings define the instance’s behavior including identifying its target watch folder, Xmedia Server, as well as mapping the conversion and metadata definitions for the various file types.

  • Page 256: Ingester Settings Properties

    Ingesting media files using the File Ingest Server Ingester Settings properties The following sections provide descriptions of each properties and setting on the Ingester Settings window’s pages: • “General page - Ingester Settings” on page 20-7 • “XMS page - Ingester Settings” on page 20-9 •...
  • Page 257 Controls whether an asset can be replaced on the XMS (True - default). LLOW SSET EPLACE If set to False, the ingest fails. When set to True, subcategories will be created in the Xmedia Server LLOW ATEGORY based on the directory subtree in the watch folder. For example, the REATE subdirectory Images>Sports might not already exist on the target XMS.
  • Page 258 The host name or IP Address of the primary Xmedia Server. RIMARY OSTNAME XMS P The port of the primary Xmedia Server. The default value is 14050. RIMARY The host name or IP address of the backup Xmedia Server. ACKUP...
  • Page 259 Ingesting media files using the File Ingest Server VAF page - Ingester Settings The table below describes each of the properties and settings on the VAF page of the Ingester Settings window. These settings apply when the and/or MOV CONVERTS TO MAGE properties on the General page are set to VAF.
  • Page 260 Ingesting media files using the File Ingest Server OXI page - Ingester Settings The table below describes each of the properties and settings on the OXI page of the Ingester Settings window. These settings apply when the and/or MOV CONVERTS TO MAGE properties on the General page are set to OXI.
  • Page 261 Ingesting media files using the File Ingest Server When set to True, upon ingest each field will be clipped to a dynamically LIPPED changing bounding box, eliminating transparent areas. When set to False, no clipping will be performed. Level of transparency to consider as transparent (between 0 and 1023). LIPPED EVEL Anything at or below the specified value will be considered transparent for...

  • Page 262: Editing An Instance's Properties

    Reloading the instances in the File Ingest Server Control Panel Changes to the status of the watch folders, Xmedia Server, or instance properties may have occurred while the File Ingest Server Control Panel has been open. Click the Reload button to ensure that all of the instances and their properties are accurate and up to date.

  • Page 263: Ingesting Files And Monitoring The Ingest's Progress

    Once an instance of the File Ingest Server has been configured and associated with a watch folder, you may begin to ingest files into the Xmedia Server. To perform and monitor the ingesting of files into the Xmedia Server: Optional - Ensure that the File Ingest Server and the Transcode Server are running by...
  • Page 264 LIPS MAGES ingested into the Xmedia Server, not the source file type (see note below). You will place the files in the subfolder that represents the final ingested asset type. For example, if you are ingesting a .MOV file and the instance is configured to convert f MOV...
  • Page 265 Ingesting media files using the File Ingest Server Once completely ingested, the file is automatically removed from or renamed in the ingest folder (depending upon the when Complete parameter’s setting). If a file failed to be ingested, it will remain in the watch folder, have .failed appended to its name and a log file specific to the failed file(s) will also be provided.

  • Page 266: File Ingest Server's Logging

    The IngestServer.log file allows you to determine whether the File Ingest Server is being used correctly and it helps you to diagnose error conditions. In fact, Miranda’s Technical Support team will often ask its customers to send them the File Ingest Server’s log file to help them troubleshoot any unexpected behavior that they may be experiencing.

Table of Contents