4 Working With Image and Video Conversions

Digital Asset Manager enables you to define and provide images, videos, and audio files in specified formats and sizes for download by the people in your organization who need them. This helps your organization maintain consistent standards for branding and digital content use.

For Digital Asset Manager to work, the following components must be installed and enabled on the correct server as noted:

Component Name	Component Description	Enabled on Server
DAMConverter	Enables Inbound Refinery to convert digital assets into multiple renditions.	Inbound Refinery Server
DamConverterSupport	Enables the content server to support digit asset management features. This component is highly dependent on the ZipRenditionManagement Component.	Content Server
DigitalAssetManager	Enables the user interface for digital asset management in tight integration with components used to create and manage renditions and zip file archives. This component is highly dependent on the ContentBasket Component.	Content Server
ContentBasket	Enables users to select renditions of content items and place them in a personal storage space called the Content Basket.	Content Server
ZipRenditionManagement	Enables Content Server access to digital asset renditions created and compressed into a ZIP file by Inbound Refinery.	Content Server

This section covers the following topics:

• Section 4.1, "Digital Asset Manager Overview"

• Section 4.2, "Configuring Digital Asset Manager"

• Section 4.3, "Configuring For Image Conversion"

• Section 4.4, "Configuring For Video Conversion"

4.1 Digital Asset Manager Overview

Digital Asset Manager creates multiple formats of digital assets automatically when an image or video is checked into Content Server, and lists the formats under one content ID. This ensures that the asset, such as a corporate logo or promotional video, maintains a standard size and quality in the multiple formats required by your organization, while providing the content management features of Content Server. For people in your organization who need to find and use digital assets, Digital Asset Manager gives them the confidence that they are using the approved asset and format for their needs. For example, one person can bundle and download images of the logo for use on a web-site, and another can download and bundle images of the same logo for use in office presentations or print collateral, all from a single digital asset checked into Content Server.

Digital assets are valuable electronic images and videos to be made available within your organization in multiple output formats. Each output format is called a rendition. The quantity and type of renditions are defined by the system administrator in rendition sets. A user selects a rendition set used to create renditions of a digital asset at the time the asset is checked into Content Server. Once checked in, a digital asset is routed to Inbound Refinery and converted using the specified conversion application.

4.1.1 Supported Conversion Applications

By default, Inbound Refinery supplies rendition sets for use with Oracle Outside In Image Export to convert images. For additional image conversion options, a stand-alone graphics conversion application can be installed. Oracle does not supply or support any specific third-party conversion engine, allowing you to choose the engine that is right for you. Sample configurations for additional image conversion engines can be accessed from the Universal Content Management Oracle Technology Network pages.

To convert videos, a stand-alone video conversion application must be installed. Digital Asset Manager is currently configured to work with Telestream's Flip Factory version 6.1. FlipFactory version 6.1 must be obtained separately from Digital Asset Manager. FlipFactory is developed by Telestream and is available from their web site (www.telestream.net).

Digital Asset Manager is designed and tested on fully functioning implementations of third-party conversion applications. Demonstration versions of conversion applications are not recommended or supported.

4.1.2 Supported Streaming Servers

For streaming digital video, Digital Asset Manager currently supports the following streaming servers:

• Windows Streaming Media—versions for supported Windows operating systems

• QuickTime Streaming Media—Darwin and QuickTime Streaming Server version 10.4

• RealMedia—Helix DNA Server version 11

4.1.3 Supported Input Formats

Supported input formats are determined by the graphic or video conversion application being used. Digital Asset Manager now has the ability to use several graphic conversion engines. Only Oracle Outside In Image Export is included with Inbound Refinery. Formats supported by Oracle Outside In Image Export can be found on Oracle's web site at http://www.oracle.com/technology/products/content-management/oit/imageexport.html.

Third-party conversion engines may offer additional support to graphics format. Third-party conversion engines must be obtained independently of Inbound Refinery and are not officially supported by Oracle.

The graphics formats supported by compatible conversion engines include the following:

• JPG/JPEG (Joint Photographic Expert Group)

• GIF (Graphics Interchange Format)

• BMP (Bitmap)

• PNG (Portable Network Graphics)

• TIFF (Tag Image File Format)

• PSD (PhotoShop)

• AI (Adobe Illustrator)

• PDF (Portable Document Format)

For a comprehensive listing of formats supported, view the documentation that came with your chosen graphic conversion engine.

Video formats supported by FlipFactory include the following:

• Flash Media Format

• MP3 Audio Format

• MPEG Layer 3 and 4 Elementary Stream Media Format

• PacketVideo MPEG4 Format

• QuickTime Media Format

• QuickTime Streaming Format

• Windows Media Format

• AVI Media Format

• DVD Stream Media Format

• MPEG1 System Stream Media Format

• MPEG2 Program Stream Media Format

• MPEG2 Transport Stream Format

• MPEG4 Media Format

• Pinnacle MediaStream Media Format

See the FlipFactory documentation from Telestream for a comprehensive listing of formats supported by FlipFactory.

4.1.4 Supported Output Formats

Output formats are determined by the conversion application. Formats supported by Oracle Outside In Image Export can be found on Oracle's web site at http://www.oracle.com/technology/products/content-management/oit/imageexport.html.

Viewing of renditions in your browser is limited to what can be displayed effectively in your browser. For images, only formats supported by your web browser can be displayed. For video, only formats that have browser plug-ins are available for viewing in your web browser, such as output formats supported by Windows Media Player, Real Player, QuickTime Player, and Flash. Any image or video assets rendered in a format not supported for viewing in a browser will still be managed by Content Server, but will be available only for download.

Video Manager currently supports the following output formats:

• MPEG Layers 1, 2, and 4 (.mpg, .mpeg, .mp2, .mp4)

• MPEG Layer 3 Audio (.mp3)

• Adobe Flash (.flv)

• QuickTime (.mov)

• Audio Video Interleave (.avi)

Due to the extensive number of formats supported by Telestream's FlipFactory, Windows Media Player, Real Player, QuickTime Player, and Adobe Flash, and the difficulty in configuring all the possible combinations, Video Manager officially supports a limited subset of these formats. You can configure Digital Asset Manager to accept additional formats and test them as your needs require.

4.2 Configuring Digital Asset Manager

You must take additional steps to configure Digital Asset Manager for image and video conversion, including modifying the following configuration files:

• Content Server config.cfg, located in the <IntradocDir>/config/ directory

• Inbound Refinery intradoc.cfg file, located in the refinery IntradocDir/bin/ directory

This section details the necessary configuration steps.

• "Configuring For Image Conversion"

• "Modifying the Content Server Configuration File"

• "Associating File Formats and Mapping File Extensions"

• "Associating a File Format"

• "Mapping File Extensions"

4.2.1 Configuring For Image Conversion

Digital Asset Manager requires a conversion application to create renditions of an image. Default rendition sets for use with Oracle Outside In Image Export are provided and no configuration is necessary.

Default Rendition Sets

Default rendition sets are defined in the damconverter_basedefinitions.hda file, which is located in the refinery IdcHomeDir/components/DAMConverter/resources/ directory and should never be altered. Upgrades to the component would overwrite any changes. For information on defining and using rendition sets other than the default sets included in the damconverter_basedefinitions.hda, see "Defining Image Rendition Sets".

The following default rendition sets are included in the damconverter_basedefinitions.hda file installed with Digital Asset Manager:

Rendition Set Name	Description
ThumbnailOnly	Creates one 72 dpi PNG rendition exactly 80 pixels high
BasicRenditions	Creates the following renditions: Web: A 72 dpi JPEG rendition no bigger than 800 x 600 pixels Thumbnail: A 72 dpi PNG rendition exactly 80 pixels high Preview: A 72 dpi GIF rendition exactly 250 pixels wide
MultipleFormats	Creates the following renditions: Web:A 72 dpi JPEG rendition no bigger than 800 x 600 pixels Thumbnail: A 72 dpi PNG rendition exactly 80 pixels high Preview: A 72 dpi GIF rendition exactly 250 pixels wide Jpeg2000:A 72 dpi Jpeg 2000 rendition no bigger than 800 x 600 pixels wide Tiff: A TIFF rendition with no parameters specified. When no parameters are specified, the dpi and pixel size of the original file is maintained. Bitmap: A BMP rendition with no parameters specified

Alternate Conversion Applications

If you would like to use an alternate conversion application, Digital Asset Manager allows you the flexibility to choose one that best meets your needs. To use a conversion application other than Oracle Outside In Image Export, you must obtain and install the application and define rendition sets suitable for the application you choose.

Note:

For best performance rendering images, install the image conversion application on the same server as the Inbound Refinery instance being used for Digital Asset Manager. For best performance rendering videos, refer to the recommendations of the video conversion application. For example, Flip Factory documentation recommends that it be installed on its own server-class machine.

Additional rendition sets should be defined in a new file called extraRendition_definitions.hda which must be created in the /data/configuration/dam/ directory. For information on creating additional rendition sets, see "Defining Image Rendition Sets".

4.2.2 Modifying the Content Server Configuration File

To avoid an error in case a video rendition set is not selected at time of check in, a default value must be set for the VideoRenditions metadata field.

To modify the configuration file, do these steps:

1. Open the following directory of your Content Server instance:

   <IntradocDir>/config/

2. Open the config.cfg file in a standard text editor.

3. Under the #Additional Variables section, add DefaultVideoConversionSet and set it equal to the factory you want as the default rendition set. The default must match a rendition set in the choice list of the VideoConversions metadata field, defined using the Configuration Manager applet.

4. Save changes to the config.cfg file and close the file.

5. Restart Content Server

Digital Asset Manager allows a user to bundle and download assets to a local or shared file system. You can specify the maximum allowable size of a download, either in megabytes or number of files in the Additional Variables section of the config.cfg file by setting the following variables:

• MaxRenditionBundleInMegabytes=Maximum size of bundle in megabytes.

• MaxRenditionFileEntries=Maximum number of files in the bundle, expressed numerically.

Note:

The DefaultVideoConversionSet identifies the rendition set to be used if a user does not specify a Video Rendition Set when checking in a video. It must be set in the config.cfg file, and not in the Default Value field of the Content Manager applet.

4.2.3 Associating File Formats and Mapping File Extensions

Content Server identifies content items as digital assets based on the extension of the file checked in. The following file formats must be associated with Digital Asset Manager and the file extensions mapped to the correct format.

4.2.3.1 Image Formats

• JPEG (.jpeg; .jpg)

• GIF (.gif)

• AI (.ai)

• PSD (.psd)

• BMP (.bmp)

• PNG (.png)

• TIFF (.tiff; .tif)

4.2.3.2 Video Formats

• MPEG Layers 1, 2, and 4 (.mpg, .mpeg, .mp2, .mp4)

• QuickTime (.mov)

• Audio Video Interleave (.avi)

• Flash Video (.flv)

Remember, the conversion engine passes rendition information to the third-party conversion application, so any additional format you associate must be supported by the third-party conversion application used by your organization.

Note:

If you are only converting one type of digital asset, images or videos, then you should only associate the formats for that type of asset.

4.2.4 Associating a File Format

To associate a format with the Digital Asset Manager conversion engine, do these steps:

1. Log in to Content Server. You must have administration rights.

2. Click Admin Applets on the Administration tray. The Administration page is displayed

3. Click Configuration Manager. The Configuration Manager applet opens.

4. Select Options—File Formats. The File Formats screen is displayed.

5. Associate the format with the Digital Asset Manager conversion engine by performing one of these steps:

   If the format is listed in the File Formats (upper) section of the File Formats screen:

   1. Select the format from the list. For example select, image/jpeg for images or video/mpeg for videos.

   2. Click Edit. The Edit File Format screen is displayed.

   3. Select Digital Media Graphics for image formats and Digital Media Video for video formats from the Conversion choice list. Digital Media Graphics and Digital Media Video are the names of the Digital Asset Manager conversion engines.

   4. Modify the description in the Description field if desired. This description is displayed in the Configuration Manager, and is not displayed in the Content Server interface.

   5. Click OK. The Edit File Format screen is closed.

   If the format is not listed in the File Formats (upper) section of the File Formats screen:

   1. Click Add. The Add New File Formats screen is displayed.

   2. Enter the type of format in the Format field. The type can be anything, and is displayed on the Content Information and Rendition Information pages of Content Server. Choose something descriptive, for example, application/PaintShop.

   3. Select Digital Media Graphics for images or Digital Media Video for videos from the Conversion choice list. Digital Media Graphics and Digital Media Video are the names of the Digital Asset Manager conversion engines.

   4. Optionally, enter a description in the Description field. This description is displayed in the Configuration Manager, and is not typically displayed in the Content Server interface. The description can be displayed in the user interface if the configuration variable IsOverrideFormat is set equal to true in the Content Server configuration file. Setting IsOverrideFormat=true in the Content Server configuration file enables a choice list on the check in page that allows a user to select a conversion format for a specific file, bypassing the assigned format.

   5. Click OK. The Add New File Formats screen is closed.

4.2.5 Mapping File Extensions

After a format is associated with the appropriate Digital Media conversion engine, you must ensure that all appropriate file extensions are mapped to the file format in Configuration Manager. All files with a file extension mapped to the format will be passed to the Digital Asset Manager conversion engine.

To map a file extension to a file format associated with the Digital Asset Manager conversion engine, perform these steps:

1. Log in to Content Server. You must have administration rights.

2. Click Admin Applets under the Administration tray. The Administration page is displayed.

3. Click Configuration Manager. The Configuration Manager applet opens.

4. Select Options—File Formats. The File Formats screen is displayed.

5. Map the extensions to the appropriate format by performing one of these steps:

   If the extension is listed in the File Extensions (lower) section of the File Formats screen:

   1. Select the extension from the list. For example select, psp.

   2. Click Edit. The Edit File Extension screen is displayed.

   3. Select the appropriate format from the Map to Format choice list. For example, application/PaintShop or video/mpeg.

   4. Click OK. The Edit File Extension screen is closed.

   If the format is not listed in the File Formats (upper) section of the File Formats screen:

   1. Click Add. The Add File Extensions screen is displayed.

   2. Enter the file extension in the Extension field. For example, psp. Do not enter the dot of the file extension.

   3. Select the appropriate format from the Map to Format choice list. For example, application/PaintShop or video/mpeg.

   4. Repeat steps a through c for each extension to be associated with the format. For example, pspimage could also be associated with application/PaintShop.

   5. Click OK. The Add File Extensions screen is closed.

   6. Click Close. The File Formats screen is closed.

   7. Close Configuration Manager.

   After associating a format to the appropriate Digital Asset Manager conversion engine (Digital Media Graphics or Digital Media Video), and mapping the appropriate file extensions to the format, all files with those extensions checked into Content Server are passed to Inbound Refinery for processing through the conversion application. Remember, the conversion engine passes rendition information to the third-party conversion application, so any additional format you associate must be supported by the third-party conversion application used by your organization.

4.3 Configuring For Image Conversion

This section covers the following topics:

• "Understanding Image Rendition Sets"

• "Defining Image Rendition Sets"

• "Creating and Configuring Image Rendition Sets"

• "Working with XMP and EXIF Data"

4.3.1 Understanding Image Rendition Sets

When a digital asset is checked in to Content Server, Digital Asset Manager creates multiple renditions of that asset. For images, the criteria for each rendition is defined in one of two files. The default renditions set is defined in the damconverter_basedefinitions.hda file and should not be modified. Custom rendition sets can be added to a component resource file called extraRendition_definitions.hda. This file can be created with a standard text editor and must be located in a new directory named dam in the refinery IntradocDir/data/configuration/ directory. The full file path should be:

IntradocDir/data/configuration/dam/extraRendition_definitions.hda

For videos, the criteria is defined in your video conversion application. By default, Digital Asset Manager was designed to work with FlipFactory, and so the criteria for rendering digital video assets is defined when a factory is created.

Image Asset Rendition Definition

The criteria defining the default rendition sets at installation are in the damconverter_basedefinitions.hda file located in the content server IdcHomeDir/components/DAMConverter/resources/ directory. This file should not be edited.

The definitions are grouped into rendition sets which correspond to rendition sets available to contributors on the content check in form when a image asset is checked in. It includes the following predefined rendition sets:

• ThumbnailOnly

• BasicRenditions

• MultipleFormats

The included rendition sets are examples that work with Outside In Image Export. If they do not meet your organization's unique needs, you should remove them from the option list on the check in page using the Configuration Manager to suppress their functionality. You should not edit the resource file to remove the sets. Any changes made will be lost when a component is updated.

Additional rendition sets can be added to a file called extraRendition_definitions.hda. This file can be created with a standard text editor and must be located in a new directory named dam in the refinery IntradocDir/data/configuration/ directory. Digital Asset Manager merges damconverter_basedefinitions.hda and extraRendition_definitions.hda when running, with the second file you created taking precedence over the resource file. For example, if you create a new rendition in your file with the same name as one in the resource file but with different parameters, the new parameters will be used.

4.3.2 Defining Image Rendition Sets

When a contributor checks a digital asset into Content Server, they select a rendition set on the check in form. For image files, that rendition set matches a rendition set defined in the extraRendition_definitions.hda file. Depending on the needs of your organization, the system administrator may need to modify, delete, or add renditions or rendition sets. For example, higher resolution may be required for print material than is specified in the default Print rendition set, or a new rendition set to handle CAD files from an engineering company.

For images, image rendition sets defined in the extraRendition_definitions.hda files contain the options for converting digital assets into the image renditions specified in the set, and for displaying and accessing the renditions from within Content Server. The default renditions sets are in the component resource file, which should not be changed. Any additional rendition sets should be added to the extraRendition_definitions.hda file you created during installation. In that file, the top properties section contains the file path to a third-party conversion application. The bottom section contains the rendition set options, organized into sets, called rendition result sets.

When a file is checked into Content Server, the format of the file determines whether or not it is a digital asset. If it is an image file, Content Server passes the file to Inbound Refinery, which calls rendition options from the extraRenditions.hda and pass them to the image conversion application. The resulting renditions are then passed back through Inbound Refinery to Content Server or other specified location, where they are managed under a single content ID and made available to your organization.

For image assets, the names of the rendition sets defined for the choice list in the PackagedConversions metadata field in the Configuration Manager applet must match exactly with the names of the rendition sets defined in the extraRendition_definitions.hda file.

When modifying or adding renditions, it is important to remember that a contributor will only see the name of the rendition set when they check in a digital asset. The rendition set name should be descriptive. Rendition names and descriptions are displayed on the content information and rendition information pages.

Spaces and other characters reserved for Idoc Script tags or are illegal for use in URLs, such as spaces, cannot be used in rendition names.

4.3.3 Creating and Configuring Image Rendition Sets

To add, modify, or delete image renditions and rendition sets, you must edit the extraRendition_definitions.hda file, located in the refinery IntradocDir/data/configuration/dam/ directory. To successfully modify the extraRendition_definitions.hda file, you should be aware of basic HDA file structure. For more detailed information, see Oracle Fusion Middleware Developer's Guide for Universal Content Management.

This section covers the following topics:

• "extraRendition_definitions.hda File Structure"

• "Adding a Rendition Set"

• "Enabling a Rendition Set"

4.3.3.1 extraRendition_definitions.hda File Structure

When defining additional rendition sets, the extraRendition_definitions.hda file should contain a header line and two section types.

Section Types

The extraRendition_definitions.hda file has two section types using the following format:

@section_type section_name
Section data
@end

The two section types are:

• Properties Section

• ResultSet Section

In the extraRendition_definitions.hda file, there is one properties section and multiple result set sections. All rendition sets are organized in result sets.

Comments are not allowed within a section of an HDA file. However, you can place comments in the HDA file before the first section, between sections, or after the last section.

Blank lines within a section of an HDA file are interpreted as a NULL value. Blank lines before the first section, between sections, or after the last section are ignored.

Properties Section

The properties section of the extraRendition_definitions.hda file defines the path to an external conversion application. In the default file, it also declares the values of Idoc Script variables defining conversion options used by the default rendition result sets.

Default Idoc Script variables in the properties section are used by the default rendition sets. They are not required for any additional rendition sets you define and are not discussed in this guide. Conversion options can be specified directly within the result sets. For more information on working with IdocScript, see the Idoc Script Reference Guide.

Result Set Sections

There are two types of result sets in the extraRendition_definitions.hda file, listed here in order of display in the file:

• Rendition Result Sets

• ExtensionFormatMap

Rendition result sets organize rendition sets and contain information about creating renditions. There can be many rendition result sets, in any order. They can be added, modified, or deleted, but each name must be unique.

The ExtensionFormatMap is an optional result set lists file extension/format pairs, so that Inbound Refinery can return the correct file format to Content Server for use internally. This is not a required set, as Inbound Refinery uses a different system to map extensions to mime types, but if this result set is defined, the mapping specified in it takes precedence.

4.3.3.2 Adding a Rendition Set

The simplest way to add a rendition set to the extraRendition_definitions.hda file is to copy an existing rendition result set and modify it. To successfully modify an existing set, you should be aware of basic set structure.

Modifications made to a component resource such as damconverter_basedefinitions.hda will be over-written if Digital Asset Manager is updated to a newer version. Additional rendition sets should be added to the extraRendition_definitions.hda file created in the IntradocDir/data/configuration/dam. Digital Asset Manager uses both files when running.

Rendition Result Set Structure

HDA files are ordered using simple name/value pairs, representing tabular data in an ASCII text format. The first line of a ResultSet section declares the set with the command @ResultSet, and then specifies the name of the set. The second line specifies the number of columns a table has, and the following lines name and populate the columns based on their order in the result set. Finally, the last line closes the result set with the command @end.

The first line of the rendition result set declares it as a result set by starting with @ResultSet, and the last line closes the set, with @end. The first line also gives the set a name. In this case, the name is ThumbnailOnly.

The name used should be descriptive, but spaces and other characters reserved for Idoc Script tags or illegal for use in URLs, such as spaces, cannot be used in rendition names.

The second line identifies how many columns are in the result set. In rendition result sets for Digital Asset Manager, there are 6 columns.

Each column has the following name and description:

Column Name	Column Description
extRenditionName	The name of the rendition displayed on the Rendition Information page. Make sure that you do not use Primary or Alternate for rendition names. These terms are reserved for internal use by Content Server.
extEngine	The path to the conversion engine used. By default, this is expressed as an Idoc Script variable declared in the properties section of the extraRendition_definitions.hda file.
extType	How the rendition is being used. Thumbnail: Used on the Thumbnail view of a search results page. Preview: Used on the Rendition Information page. Web: The web-viewable version of a content item. Displayed in the main content area when accessed by clicking the content ID or thumbnail from a search results page, or when clicking the web-viewable link on a content information page. Displayed in a new browser window when accessed by clicking the Preview image on a Rendition Information page. If no web rendition is defined the native file is used by Content Server as the web-viewable file. Extra: Any rendition not defined as Thumbnail, Preview, or Web. Rendition types may be combined. For example, by listing the type as web, preview, the rendition is used both as the web file and as the preview file.
extSourceFile	The file path to the asset checked into for conversion expressed as Idoc Script.
extParameters	The options passed to the conversion engine defining how the source file is rendered. By default, this is expressed as Idoc Script variables declared in the properties section of the extraRendition_definitions.hda file, but it can be expressed as a literal string. <$infile$>: The name of the source file used to generate the rendition, expressed as Idoc Script. <$outfile$>: The name of the rendered file. This is a required parameter, expressed as Idoc Script. <$parameter_variable$>: The options used for rendering by the conversion application. In the provided rendition sets, these are expressed as Idoc Script variables, which are declared in the properties section of the extraRendition_definitions.hda file. They can also be expressed as a literal string of options used by your conversion application. For example, the literal string used in the damconverter_basedefinitions for the Web rendition is: outputid=FI_GIF, graphicoutputdpi=72, graphicwidthlimit=250, graphicheightlimit=0 but it could also be expressed as the following variable: <$ImageExport_BasicRenditions_Web$>
extDescription	The description for the rendition displayed on the Rendition Information page.

For more information on working with .hda files, see the Working With Components guide.

To add a new rendition result set, perform these steps:

1. Open the extraRendition_definitions.hda in a standard text editor.

2. Copy and paste an existing rendition result set.

   1. Select a rendition result set to copy, starting at the @ResultSet line and ending at the @end line, and copy it.

   2. Position the cursor between any two existing rendition result sets in the extraRendition_definitions.hda file.

   3. Paste the rendition result set into the file.

   Blank lines between result set sections are ignored. To help visually organize the extraRendition_definitions.hda file, you may want to insert a blank line before and after the new rendition result set.

3. Change the name of the new rendition result set, listed next to @ResultSet. For example, @ResultSet NewName.

   The name used should be descriptive, but spaces and other characters reserved for Idoc Script tags or illegal for use in URLs, such as spaces, cannot be used in rendition names.

4. Change rendition information for each rendition you want to keep in the result set.

   1. Change the name of the rendition, listed in the extRenditionName column. Rendition names may have spaces.

   2. Change the type of the rendition, listed in the extType column. Each rendition can multiple types, for example, preview, web.

   3. Change the conversion options for rendering, listed in the extParameters column. Conversion options are dependent on which third-party conversion application being used.

   4. Change the description of the rendition, listed in the extDescription column. The description can be anything, and is displayed on the Rendition Information page.

      Do not change the <$InFilePath$> variable used in the extSouceFile column. This is required by .

5. Delete any extraneous renditions in the result set.

6. Save the extraRendition_definitions.hda file.

4.3.3.3 Enabling a Rendition Set

After a rendition set is added to the extraRendition_definitions.hda file, it must be made available as an option in the Image Rendition Set field on the Content Check In Form, using Configuration Manager.

To add the name of the rendition set as an option in Configuration Manager, perform these steps:

1. Log in to Content Server. You must have administration rights.

2. Click Admin Applets on the Administration tray. The Administration page is displayed

3. Click Configuration Manager. The Configuration Manager applet opens.

4. Verify the Information Fields tab is active, select the PackagedConversions information field and click Edit. The Edit Custom Info screen is displayed.

5. Click Configure. The Configure Option List screen is displayed.

6. Click Edit. The Option List screen is displayed.

7. Add the name of the new result set as it is listed in the extraRendition_definitions.hda file's packedConversion result set. Rendition sets can be listed in any order.

   The name used in the extraRendition_definitions.hda file and the PackagedConversions option list must match. Spaces and other characters reserved for Idoc Script tags or illegal for use in URLs cannot be used.

8. Click OK to close the Option List screen.

9. Click OK to close the Configure Option List screen.

10. Click OK to close the Edit Custom Info screen.

4.3.4 Working with XMP and EXIF Data

Most digital images have data associated with them by the hardware or software used to create them. For example, digital photographs have the date they were created and the camera used to create them associated with them, among other things. Digital files such as those created with Adobe Photoshop have a greater set of metadata associated with them. The metadata associated with digital photographs is called EXIF data, which stands for Exchangeable Image File Format. It is a subset of the type of data created by computer applications such as Adobe Photoshop. The application metadata is called XMP data, which stands for EXtensible Metadata Platform.

By default, Inbound Refinery is now configured to send EXIF and XMP data to Content Server, where it is indexed and available for searching as text.

4.3.4.1 Searching XMP and EXIF Data in Content Server

By default, XMP schema and EXIF data are extracted by Inbound Refinery and passed to Content Server. Content Server then displays the data on the Image Data tab of a digital asset. If OracleTextSearch is installed and enabled, the data is indexed and available for searching through a full-text search. To enable searching on a specific criteria in the XMP or EXIF metadata, a placeholder field must be enabled on the Content Server user interface and the search collection must be rebuilt. Once done, users can search for content using the specific criteria in the data.

To enable an XMPor EXIF data field on the user interface and make the specific criteria available for searching, do these steps:

1. On the Content Server, expand the Administration tray and click DAM Adminstration. The DAM Search Fields Administration page is displayed.

2. Expand the section under the XMP Schema Categories that has the data field to enable on the user interface. For example, to search for digital images based on the date and time the image was take, expand the EXIF category.

3. Find and enable the placeholder field to be used for searching. For example, in the EXIF catagory, scroll to the XMP Date Time Original and enable it.

4. Click Update.

5. Rebuild the search index. For information on rebuilding the search index, see the content server documentation.

   Note:

   Enabling a field in the user interface creates a placeholder field in content server and allows the information to be indexed and searched against. It does not modify database tables or allow information to be entered or modified in the field for storage in the database.

4.3.4.2 Applying XMP and EXIF Data as Text Overlay to a Rendition

Once a placeholder field has been created and the metadata indexed, XMP and EXIF metadata can be used as a text overlay in a custom rendition.

4.4 Configuring For Video Conversion

Digital Asset Manager requires a third-party conversion application to render video assets checked in to Content Server. Currently, Digital Asset Manager is designed to work with Telestream's FlipFactory version 6.0 and 6.1 (http://www.telestream.net/products/flipfactory.htm).

This section has the following topics:

• "Installing FlipFactory"

• "Installing Digital Asset Manager Video Plug-ins"

• "Ensuring the JDOM Library is Installed for FlipFactory 6.0"

• "Sharing Directories with FlipFactory"

• "Setting the Conversion Engine Shared Directory Path"

• "Setting the Default Media Location"

• "Defining Video Rendition Sets"

• "Creating and Configuring Factories in FlipFactory"

• "Managing Video Conversion"

• "Enabling Plug-in Debugging Logs"

4.4.1 Installing FlipFactory

If you do not already have an instance of FlipFactory installed, follow the instructions included with FlipFactory to install and set up the application to meet your requirements. FlipFactory must be installed on a Windows server.

Cautions:

FlipFactory installation will fail if installing on a computer with an instance of Microsoft SQL Server 2000 or lower. Ensure that SQL Server 2000 or lower is not installed on the computer on which you are installing FlipFactory.

FlipFactory requires QuickTime to be installed for QuickTime renditions to be made. Review the FlipFactory documentation for information regarding obtaining and integrating the proper QuickTime version for use with the specific version of FlipFactory your are using, either 6.0 or 6.1. Also, visit Telestream's site at http://www.telestream.net/ for the latest information relating to FlipFactory.

Due to the demand on computer resources required for rendering video assets, it is recommended that FlipFactory and Inbound Refinery be installed on separate server-class machines. For ease of access, it is also recommended that both servers have a duplicate user list of administrators.

4.4.2 Installing Digital Asset Manager Video Plug-ins

The monitor, transport, and notification plug-ins that Inbound Refinery uses to communicate with FlipFactory to convert videos are distributed in the idcFlipFactoryPlugin.zip file installed by the DAMConverter component. The idcFlipFactoryPlugin.zip file is located in the refinery IdcHomeDir/components/DAMConverter/VideoManagerFlipFactoryPlugin/ directory.

To install and configure the Digital Asset Manager plug-ins for FlipFactory, perform these steps:

1. Open Services on the Windows server on which FlipFactory is installed.

2. Select the Flip Engine service and then select Actions, Stop.

3. Select the idcFlipFactoryPlugin.zip located in the refinery IdcHomeDir/components/DAMConverter/VideoManagerFlipFactoryPlugin/ directory, and extract the file to the FlipFactory installation directory. For example: C:/Telestream/FlipFactory/. Two directories are extracted to the following locations:

   • /<FlipFactory_install_dir>/idcTools/

   • /<FlipFactory_install_dir>/Plugins/

     Caution:

     To ensure that all files are extracted to the correct place, keep the directory structure when extracting the idcFlipFactoryPlugin.zip file to the FlipFactory installation directory. The full directory structures are:

     • /<FlipFactory_install_dir>/idcTools/jars/

     • /<FlipFactory_install_dir>/Plugins/com/stellent/refinery/ff/impl

4.4.3 Ensuring the JDOM Library is Installed for FlipFactory 6.0

FlipFactory 6.0 requires the JDOM library jdom.jar to be installed in the /<FlipFactory_install_dir>/Jars/ directory. After installing the Digital Asset Manager Video plug-ins, navigate to the /<FlipFactory_install_dir>/Jars/ directory and ensure that the jdom.jar file is there. If is not there, download the latest API from http://www.jdom.org/ and copy only the jdom.jar file to the /<FlipFactory_install_dir>/Jars/ directory and restart FlipFactory.

This is not necessary for FlipFactory 6.1.

4.4.4 Sharing Directories with FlipFactory

To convert videos, each implementation of Digital Asset Manager must have a staging directory and a watched directory on a file system shared with FlipFactory. The staging and watched directory can be the same directory. For Digital Asset Manager to work properly, a subdirectory in each watched directory must have the same name as the rendition set in Digital Asset Manager, which in turn must have the same name as the factory created in FlipFactory.

Additionally, there must be an “in” directory and an “out” directory within each subdirectory of the watched folder.

Cautions:

If multiple factories point to the same “in” directory, the input file will be rendered by whichever factory receives notification first. As different factories may have different parameters, unexpected results may occur. For conversion to work properly and provide the expected results for each rendition, each factory created in FlipFactory should point to its own unique “in” directory.

The path to the shared directories must not contain spaces.

To create the required directories, perform these steps:

1. Establish a shared file system that can be accessed by both FlipFactory and Inbound Refinery. For best results, set up the shared directories on the system that has FlipFactory installed.

2. Create a staging directory. It can be named anything. For example, Video_Staging.

3. Create a watched directory. It can be named anything. For example, Video_Watch. A single shared directory can be used for both the watched and staging directory

4. Open the watched directory and create a directory for each rendition set defined in Digital Asset Manager. The name of the directory must equal the name of the rendition set as defined by editing the VideoRenditions custom metadata field in Configuration Manager.

   Caution:

   For conversion to work properly, the names of the watched subdirectories, the Digital Asset Manager rendition sets, and the FlipFactory factories must be the same. Paths to the shared directories should not contain spaces.

5. Open each directory in the watched directory and create two subdirectories, one named in, the other out. For example:

   /<Video_Watch_dir>/MediumBandwidth/in
   /<Video_Watch_dir>/MediumBandwidth/out
   

4.4.5 Setting the Conversion Engine Shared Directory Path

Once the staging and watched directories are created, both Inbound Refinery and FlipFactory must know where to find them. Inbound Refinery must be able to place a copy of the asset in the staging directory and retrieve the renditions from the watched directory when rendering is complete. Inbound Refinery must also post an XML file requesting the file be rendered in the watched directory, telling FlipFactory where to find the asset and where to return the renditions, in a syntax that FlipFactory can understand. For best results, set up the shared directories on the system that has FlipFactory installed.

Setting the Shared Directory Path In Inbound Refinery

To set the shared directory path in Inbound Refinery, perform these 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/ucm/ibr/bin/intradoc.cfg

2. Add the variable VideoStagingDir and set it equal to the path of the staging directory shared with FlipFactory. For example:

   VideoStagingDir=\\\\NetworkIdentity/Video_Staging/

   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. For example, the path \\NetworkIdentity/Video_Staging becomes \\\\NetworkIdentity/Video_Staging.

   Caution:

   The path to the shared directories must not contain spaces.

3. Add the variable RefineryFlipFactoryWatchRootDir and set it equal to the path to the watched directory shared with FlipFactory. For example:

   RefineryFlipFactoryWatchRootDir=\\\\NetworkIdentity/Video_Watch.

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

Directory Configuration

When both applications are running on a Windows platform, the VideoStagingDir and RefineryFlipFactoryWatchRootDir can have the same value, because the syntax for accessing the directories and posting the directory locations in the XML request can be identical.

If Inbound Refinery is running on a UNIX platform, however, the paths to the shared directory may require a different syntax for accessing the directory than for posting the directory location in the XML request in a way that FlipFactory, running on a Windows platform, can understand.

The following additional variables are added to the Inbound Refinery connection intradoc.cfg file to provide context for Inbound Refinery to accurately post a file path that FlipFactory can understand.

• VideoStagingDirFactoryContext

• RefineryFlipFactoryWatchRootDirFactoryContext

For example, if a staging directory is created on a FlipFactory instance at \\\\NetworkIdentity/Video_Staging/, and mounted on the UNIX Inbound Refinery machine as /mnt/Video_Staging, then the following would be true:

• VideoStagingDir=/mnt/Video_Staging

• VideoStagingDirFactoryContext=\\\\NetworkIdentity/Video_Staging/

To add the additional multi-platform support variables to the intradoc.cfg file, perform these 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/ucm/ibr/bin/intradoc.cfg

2. Add the variable VideoStagingDirFactoryContext and set it equal to the path of the staging directory from the FlipFactory context. For example:

   VideoStagingDirFactoryContext=\\\\NetworkIdentity/Video_Staging/

3. Add the variable RefineryFlipFactoryWatchRootDirFactoryContext and set it equal to the path to the watched directory from the FlipFactory context. For example:

   RefineryFlipFactoryWatchRootDirFactoryContext=\\\\NetworkIdentity/Video_Watch

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

Setting the Shared Directory Path in FlipFactory

The watched directory is defined in FlipFactory using the Oracle IBR monitor plug-in each time a factory is created. See the section "Installing Digital Asset Manager Video Plug-ins" for more information.

The staging directory does not need to be explicitly defined in FlipFactory.

Note:

For FlipFactory to access a shared directory on a UNIX platform, you may need to configure the Flip Engine service on the FlipFactory server to be run by particular user. For more information, see the documentation that came with FlipFactory.

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.

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

This section covers the following topics:

• "Configuring Default File Placement Locations"

• "Configuring Specific File Placement Locations"

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.

Note:

Both Content Server and Inbound Refinery must have physical access to the placement locations.

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/ucm/ibr/bin/intradoc.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=\\\\NetworkIdentity/contentserver/weblayout/
   

   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

   \\NetworkIdentity/contentserver/weblayout/media/groups/public/ documents/adacct/movie.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.

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/ucm/cs/bin/intradoc.cfg
   

   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.

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=\\\\NetworkIdentity/contentserver/weblayout/
   

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://NetworkIdentity/contentserver/
   

   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.

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.

4.4.6.2 Configuring Specific File Placement Locations

You can specify different locations for differing video renditions based on the media format. Three media categories are available to define physical and URL roots for different formats:

• WinMedia

• DarwinMedia

• HelixMedia

These category names serve as labels only, and any format can be grouped under any category label.

In order to specify different locations for different formats, you must edit the intradoc.cfg files for both Inbound Refinery and Content Server to:

• enable a category

• specify the formats handled by the category

• set the physical root specific to the category

For Content Server only:

• set the URL root specific to the category

Note:

Both Content Server and Inbound Refinery must have physical access to the placement locations.

To set a different location for a specific format, 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/ucm/ibr/bin/intradoc.cfg
   

2. Enable a category by setting the appropriate variable equal to true. For example, the following variable may be set:

   WinMediaSupportEnabled=true
   DarwinMediaSupportEnabled=true
   HelixMediaSupportEnabled=true
   

3. Set the format of the media handled by the category by setting the appropriate variable equal to the format extension. For example:

   WinMediaFormats=wm*|asf|asx
   

   Note that each format is separated by a pipe (|), and that an asterisk (*) can be used as a wildcard.

   The following variables may be set, and must match the enabled category or categories:

   • WinMediaFormats

   • DarwinMediaServerFormats

   • HelixMediaServerFormats

4. Set the physical root for the media handled by the category by setting the appropriate variable equal to the physical path. For example:

   HelixMediaPhysicalRoot=\\\\NetworkIdentity/RealMedia/
   

   The following variables may be set, and must match the enabled category or categories:

   • WinMediaPhysicalRoot

   • DarwinMediaPhysicalRoot

   • HelixMediaPhysicalRoot

   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

   \\NetworkIdentity/contentserver/weblayout/media/groups/public/ documents/adacct/movie.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.

5. 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/ucm/cs/bin/intradoc.cfg
   

6. Repeat steps 2 through 4 in the Content Server intradoc.cfg file.

7. Also in the Content Server intradoc.cfg file, add one of the following variables based on the formats being rendered, and set it to the URL root path, including the protocol, where the file can be accessed. For example:

   HelixMediaUrlRoot=rtsp://NetworkIdentity:554/
   

   The following variables may be set, and must match the enabled category or categories:

   • WinMediaUrlRoot

   • DarwinMediaUrlRoot

   • HelixMediaUrlRoot

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

9. Restart your managed servers.

4.4.7 Using Streaming Servers

Depending on how you set your media conversions, categories, and URL root variables, renditions can be served out of a web server or streaming media server. 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

• set your conversion application to deliver the correct streaming format

• configure a category to deliver the rendition to the correct place

• configure the web URL root with the proper protocol and syntax for the streaming server

Currently Digital Asset Manager supports Darwin Streaming Server (QuickTime), Helix Streaming Server (RealMedia), and Windows Media Server. For information about protocols used with streaming media, see the documentation that came with your media server.

4.4.8 Defining Video Rendition Sets

For video, factories defined in FlipFactory contain the options for converting digital assets into video renditions specified in the factory. A corresponding directory on a file system shared by FlipFactory and Inbound Refinery has an "in" subdirectory that is watched by FlipFactory for a request posted there by Inbound Refinery in the form of an XML file. Once a factory creates the requested renditions, the files are placed in an "out" subdirectory of the watched factory directory, along with an XML file. Inbound Refinery monitors the "out" directory for the XML file, and uses it to locate the finished renditions and return them to Content Server or place them at another configured location. See "Configuring For Video Conversion" for more information on video renditions.

When a file is checked into Content Server, the format of the file determines whether or not it is a digital asset. If it is a video file, Content Server passes the file to Inbound Refinery, which notifies the video conversion application that there is a file to convert. The resulting renditions are then passed back through Inbound Refinery to Content Server or other specified location, where they are managed under a single content ID and made available to your organization.

For video assets, the names of the rendition sets defined for the choice list of the VideoRenditions metadata field in the Configuration Manager applet must match exactly with the names of factories set up in FlipFactory and the factory directories monitored in the watched directory.

When modifying or adding factories, it is important to remember that a contributor will only see the name of the rendition set when they check in a digital asset. The rendition set name should be descriptive. Factory names and descriptions are displayed on the content information and rendition information pages.

Spaces and other characters reserved for Idoc Script tags or are illegal for use in URLs, such as spaces, cannot be used in rendition names.

4.4.9 Creating and Configuring Factories in FlipFactory

Factories created in FlipFactory must have the same names as rendition sets defined in Content Server, and must be configured to access the appropriate watched directory.

Creating Factories

To create a factory in FlipFactory, perform these steps:

1. After installing the Digital Asset Manager plug-ins, open Services and verify the Flip Engine service is started. For more information on installing the Digital Asset Manager plug-ins, see "Installing Digital Asset Manager Video Plug-ins".

2. Start and log in to FlipFactory.

3. Click Manage Factories. The Manage Factories page is displayed.

4. Right-click on the Factories folder, and select New Factory from the contextual menu. An untitled folder is created in the Factories folder.

5. Select the new untitled folder. The Factory Editor panel is displayed on the right of the page.

6. Enter a name in the Name field that corresponds to the name of a rendition set in Digital Asset Manager. The names must be identical. For example, if your rendition set is named MixedBandwidth, the new factory must be named MixedBandwidth. A factory description is optional.

Configuring Plug-ins

Once a factory is created that corresponds to a rendition set in Digital Asset Manager, the appropriate plug-ins must be configured to communicate between FlipFactory and Inbound Refinery.

Setting the Watch Directory Path

The directory watched by Inbound Refinery must also be watched by the factory. To set the path to the watched directory for a factory, perform these steps:

1. Open the folder of the new factory. Four subfolders are displayed:

   • Monitors

   • Process/Analyze

   • Products

   • Notifications

2. Select the Monitors folder. A panel is displayed to the right, showing multiple tabs.

3. Select the Refinery Monitor tab and click Add. The Refinery Monitor item is displayed in the Monitors folder.

4. Select Refinery Monitor in the Monitors folder. The Refinery Monitor panel is displayed on the right side of the page.

5. Verify that the Enable check box is checked.

6. Click Browse under the Watch Folder section. The Watch Folder dialog box is displayed.

7. Using the dialog box, locate the watched folder created for this implementation and continue to browse within it to the “in” subfolder of the directory whose name is identical to the factory name. For example, if this factory is named MixedBandwidth, you would browse to <Video_Watch>/MixedBandwidth/in. If you have not created the subfolders of the watched directory, see "Sharing Directories with FlipFactory".

8. Click Select. The Watch Folder dialog box closes.

Enabling Keyframe Extraction

You must tell FlipFactory to create key frames of the video asset for use in the story board section of the Rendition Information page. To enable keyframe extraction, perform these steps:

1. With the new factory folder still open, select Process/Analyze and select Video Analysis.

2. Check Enabled. Video Analysis is displayed in the Process/Analyze folder.

3. Select Video Analysis in the Process/Analyze folder. A tabbed panel is displayed on the right side of the page.

4. Verify that the KeyFrame Extraction tab is selected and the Enabled checkbox is checked.

5. Configure the key frame parameters to meet your needs. For more information on the parameter options, see the FlipFactory documentation.

Note:

Failure to enable keyframe extraction may result in broken image links for the rendition on a search result page in Content Server, and disables the story board functionality for that rendition on the Rendition Information page.

Enabling Notification

You must tell the factory to notify Inbound Refinery when a request has been completed. To enable notification, perform these steps:

1. With the new factory folder still open, select Notifications. A tabbed panel is displayed to the right of the page.

2. Select the Refinery Notify tab and click Add. The Refinery Notify item is enabled and added to the Notification folder. There are no settings in the Refinery Notify item than can be configured by a user.

Adding Products and Setting Rendition Destinations

Each product in a factory corresponds to a rendition in a rendition set, and the destination of each product corresponds to the rendition name that is displayed on a Rendition Information page. To add a product and set the destination, perform these steps:

1. With the new factory folder still open, right-click on Products and select New Product from the contextual menu. A product folder is created and the Product panel is displayed on the right side of the page.

   Notes:

   The Product panel is used to specify the conversion format. By default, Duplicate Original is enabled. Note that you may not have all format options available to you, depending on your license agreement with FlipFactory. Note that available options may not be supported by Digital Asset Manager.

   To properly render to the correct output format, the correct codec to play the input format must be installed on the same server on which FlipFactory is installed. Popular web formats, such as .avi and others, may use different codecs even within the same format. If you experience problems rendering, verify that the original input file will play on the FlipFactory machine. If it does not, you may need to obtain the proper codec. For more information, refer to the FlipFactory documentation.

2. Open the Product folder. The Destination folder is displayed.

3. Select the Destination folder. A tabbed panel is displayed on the right side of the page.

4. Select the Refinery Transport tab and click Add. The Refinery Transport item is created in the Destinations folder.

5. Select the Refinery Transport item in the Destinations folder. The Refinery Transport panel is displayed on the right side of the page.

6. Enter the name of the rendition in the Rendition Name field. It can be anything. This is the name that is displayed on the Rendition Information page in Content Server.

Caution:

You must enter a rendition name. If you do not, rendering of the asset will fail. If rendering fails, the content item must be removed from Content Server using Repository Manager, and Inbound Refinery must be restarted.

4.4.10 Managing Video Conversion

Content Server identifies content items as digital assets based on the extension of the file checked in. At installation, Digital Asset Manager checks to see if the following common file formats exist in the Content Server Configuration Manager applet.

This section covers the following topics:

• "Editing the Video File Type Configuration Table"

• "Setting the Default Video Format Preferences"

4.4.10.1 Editing the Video File Type Configuration Table

If you add a file format and map the extension to the Digital Media Video conversion engine, and would like that format to play in an embedded player (such as on the Rendition Information page), the extension must exist in the Video File Type configuration table of the dam_cfg_tables.htm file. The dam_cfg_tables.htm file is located in this directory:

IdcHomeDir/components/DAMConverter/resources/

The format must exist in the Video File Type configuration table only for the file to play in an embedded player. If the format is not in the table, the rendition can still be opened and played in a stand alone player that supports the rendered format.

To verify that the added format exists in the Video File Type configuration table, open the dam_cfg_tables.htm file in a standard browser and review the file extensions listed. If the file extension does not exist, you must write a custom component listing the extension and additional necessary information and merge the tables. Information on custom components can be found in the Oracle Fusion Middleware Developer's Guide for Universal Content Management.

The following table lists the columns of the Video File Type configuration table and their function:

Column Name	Definition
fileExtension	The extension of the file formats to be supported played in the embedded players.
formatName	The name of the format associated with the extension. This value corresponds to the values in the Video Format Prefs table, which is configurable, and is displayed in the choice lists of the embedded players.
player	The player that supports the added format extension. The values are case-sensitive. Currently only three values are allowable: real quicktime wmplayer
metafileExtension	The metafile extension associated with the format extension, used to determine what embedded player will play a streaming version of the format. There must be a value in this field if the format is streamed.

4.4.10.2 Setting the Default Video Format Preferences

Embedded players are displayed on the Rendition Information page or when a web-viewable link is clicked. The format chosen to play in the embedded player is based on a table of user preferences regarding available rendition format options, set on the Video Preferences page. Prior to user input, default preferences are based on values set in the Video Format Preferences table of the dam_cfg_tables.htm file. The dam_cfg_tables.htm file is located in the resources directory:

IdcHomeDir/components/DigitalAssetManager/

To add new settings or modify default preferences, create a custom component containing the new or modified settings and merge the custom data table into the corresponding default data table. Information on creating custom components can be found in the Oracle Fusion Middleware Developer's Guide for Universal Content Management.

Note:

Do not edit a standard Content Server component resource directly. Always create a custom component to merge changes into Content Server or Inbound Refinery.

Modifications made to a component resource will be over-written if Digital Asset Manager is updated to a newer version.

The following table lists the columns of the Video Format Preferences table and their function:

Column Name	Definition
format	Configurable name displayed in the choice list of an embedded player.
pickOrder_win	Determines the order a format is selected on a Windows operating system.
pickOrder_mac	Determines the order a format is selected on a Macintosh operating system.
pickOrder_other	Determines the order a format is selected on an operating system other than Windows or Macintosh.

4.4.11 Enabling Plug-in Debugging Logs

The standard log outputs from FlipFactory are found in the stdout.log file located in the FlipFactory installation directory. Additional logging detail can be found by enabling the plug-in logging. To enable FlipFactory plug-in debugging, perform these steps:

1. Stop the Flip Engine service.

2. Open the log4j.properties file located in the <FlipFactory_install_dir> in a standard text editor.

3. Delete the # symbol in front of the following entries in the log4j.properties file:

   • log4j.logger.com.stellent.refinery.ff=DEBUG

   • log4j.rootLogger=ERROR, IBRPlugin

4. Save the log4j.properties file and restart the Flip Engine service.

Information regarding plug-in output is now logged to /<FlipFactory_install_dir>/stdout.log.