Configuring Default File Placement Locations

4-20 Administrators Guide for Conversion

4.4.6 Setting the Default Media Location

So that both Inbound Refinery and Content Server knows what to do with video renditions once they are returned from FlipFactory, you must configure where you want video renditions placed. Video renditons can be placed in a variety of locations, depending on your business need. For example, they can be returned to the Content Server web layout directory, placed on a file system for access outside of Content Server, or sent to a streaming server. This section covers the following topics: ■ Configuring Default File Placement Locations on page 20 ■ Configuring Specific File Placement Locations on page 22

4.4.6.1 Configuring Default File Placement Locations

For Digital Asset Manager to work, Inbound Refinery must know what to do with a submitted asset and its renditions, and Content Server must know how to access them. A default location for assets must be set in the configuration files of both Inbound Refinery and Content Server. Additionally, a default URL root must be set in the configuration file for Content Server. To set the default file placement locations, do the following steps: 1. Open the intradoc.cfg file for each Inbound Refinery connection accessing the shared directories in a standard text editor. The intradoc.cfg file is located in the connection directory of an Inbound Refinery installation. For example: DomainDir ucmibrbinintradoc.cfg 2. Add the variable DefaultMediaPhysicalRoot equal to the default location you want video renditions placed. Because Inbound Refinery may be converting for several Content Servers, the agent name of the Content Server must be appended to the variable. For example: DefaultMediaPhysicalRoot-AgentName=\\\\NetworkIdentitycontentserverweblayout Note: If you are planning to stream rendered videos, you must install and properly configure a supported media server based on the instructions that came with your media server, and set your conversion application to deliver the correct streaming format. Currently Digital Asset Manager supports Darwin Streaming Server QuickTime, Helix Streaming Server HelixMedia, and Windows Media Server Note: Both Content Server and Inbound Refinery must have physical access to the placement locations. Working With Image and Video Conversions 4-21 3. Open the intradoc.cfg file for each Content Server connection accessing the shared directories in a standard text editor. The intradoc.cfg file is located in the connection directory of a Content Server installation. For example: DomainDir ucmcsbinintradoc.cfg 4. You must also add the variable DefaultMediaPhysicalRoot to each Content Server and set it equal to the default location video renditions are placed by the refinery server. For example: DefaultMediaPhysicalRoot=\\\\NetworkIdentitycontentserverweblayout 5. Set DefaultMediaUrlRoot equal to the default location of the URL root path, including the protocol, to where the file can be accessed. For example: DefaultMediaUrlRoot=http:NetworkIdentitycontentserver

6. Save changes and close the intradoc.cfg file.

7. Restart your managed servers.

If all rendered video assets are to go to the default locations, then setting the default variables in the configuration files are all you need to do. If you want to send some media formats to other locations, for example all .ra files to a streaming server or all .mpgs to an external storage system, then you must also configure where to place those specific formats. Note: This is a root directory only. The media file will actually exist in a subdirectory that mirrors the typical Content Server weblayout directory. For example, a file named movie.ra might be located in \\NetworkIdentitycontentserverweblayoutmediagroupspublic documentsadacctmovie.ra The path can be a local, mapped, or a Universal Naming Convention UNC path. The backslash is an escape character in Java, so any path using a backslash must be escaped using two backslashes. Note: Depending on how your network is set up, this path may or may not be identical to the path set in the Inbound Refinery intradoc.cfg file, but the two paths must resolve to the same location. Note: The DefaultMediaPhysicalRoot variables for each Content Server agent using Inbound Refinery must resolve to the same location as the respective DefaultMediaPhysicalRoot-AgentName variables for the refinery. Additionally, each DefaultMediaUrlRoot variable in Content Server must resolve to the same location as the Content Server DefaultMediaPhysicalRoot for that server. 4-22 Administrators Guide for Conversion

4.4.6.2 Configuring Specific File Placement Locations