In computing, a plug-in is a software component that adds a specific feature to an existing software application. When an application supports plug-ins, it enables customization. In the context of Ooyala Flex, various parts of the platform allow for the development and configuration of Plugins. This guide provides an overview of the existing Plugins. This guide does not cover customer-specific plugins. It covers all plugins that are bundled with every deployment of Ooyala Flex.
Internal Plugins: Internal Plugins run inside Ooyala Flex and are configured and managed within the Ooyala Flex Console. Examples are the Transcode Action and the Storage Resource.
Adapter Plugins: Adapter Plugins are internal Ooyala Flex components that translate Ooyala Flex commands to other product interfaces. Adapters help Jobs to translate internal Ooyala Flex messages to messages recognised by external Resources such as Transcoders and QC Systems.
Apps: Apps are external web and mobile apps that are deployed in other applications or run in web browsers and connect remotely to Ooyala Flex via Ooyala Flex's API. Examples of Apps are the Adobe CQ Player Plugin and the Adobe Premiere and Prelude Partner Panel Plugins which communicate with Ooyala Flex via REST.
Internal Plugins reside within Ooyala Flex. Ooyala Flex's architecture is designed to ensure that powerful Plugins can be created with minimal coding effort. Ooyala Flex's configuration model allows for configuration of Plugins as well as scriptable fields. This ensures that your Plugin will be versatile and easy to reuse.
Internal Plugins comprise two functionalities :
Plugin Code: Custom Java code written against Ooyala Flex's API.
Plugin Configuration XML: A Ooyala Flex Metadata XML file with details about configuration parameters used to configure the Plugin once installed.
The screen shots below show what a Plugin Configuration file looks like inside a plugin and also once loaded in the UI.
Ooyala Flex's Plugin configuration is managed by Metadata Definitions. As such, each parameter has a Field Type. For a full list of Field Types, please see the Field Types section.
The following internal plugin types are supported:
Actions - Plugins for Ooyala Flex Action Types
Event Handlers - Plugins for Ooyala Flex Event Types
Players - Plugins for Ooyala Flex Players
Resources - Plugins for Ooyala Flex Resource Types
Quotas - Plugins for Ooyala Flex Quotas
Timed Actions - Plugins for Ooyala Flex Timed Actions
Wizards - Plugins for Wizards
Adaptor pugins are special low-level internal plugins that translate Ooyala Flex commands into messages that communicate with external Resources. Examples of Adapater Plugins in Ooyala Flex are the Transcode Adapter and the QC Adapter.
Adapters are extremely useful when resources from different vendors must work in tandem. For example, you might want to use an Amberfin transcode resource and also a Telestream transcode resource. Without a Transcode Adaptor, one would require two separate Transcode Action types, two separate Transcode Profile types and two separate Transcode Resource Plugins. With an Adapter in place, one can use the default Transcode Plugin and the built in Ooyala Flex Transcode profile to Transcode using two competing products from different vendors at the same time. So in essence, the Transcode Adapter does the work of translating messages at a low level to communicate ely to each external Resource.
With adapters, to support new vendor solutions, you just need to update a single adapter rather than to implement a range of new plugins.
The following internal adapter plugins are supported:
Apps are created using other software APIs and typically connect to Ooyala Flex through Ooyala Flex's REST API.
Some example of Apps created are as follows:
Editing - Plugins for external editing software
Logging - Plugins for external logging software
CMS - Plugins for external content management systems
For each Plugin, we provide the following information in addition to the name and description. Please note not all fields are shown for all Plugins as some are not relevant in some cases.
|Icon||[ ]||Plugin icon|
|Sub-type||Publish||Sub-type of this Plugin|
|Deployment||Internal||Whether the plugin is deployed inside Ooyala Flex or within another product|
|Supports Configuration||Whether this Plugin supports configuration|
|Supports Scripting||Whether configuration supports scripting|
|Scripting Context||User, asset||What Ooyala Flex objects can be referenced from within the scripting context|
|Compatibility||5.x||What versions of Ooyala Flex this plugin works for|
|Lifecycle||Stable||Maturity of this plugin (Experimental, Unstable or Stable)|
If the plugin supports configuration, then the configuration properties are provided:
|Username||string||0..1||The Username for the Account|
In this section we list the Vendor solutions that Ooyala Flex plugs in to through its Plugin framework.
Please note that we integrate with a wider range of solutions than those listed below. Many solution vendors support integration via standard protocols, for example, FTP, SMB/CIFS, REST, SOAP etc. In addition, Ooyala Flex's API can be used by developers to create their own script-based or Java-based plugins.
Telestream FlipFactory Loudness Plugin
Content Management Tools
Adobe Experience Manager (CQ)
The Plugins section includes the following plugin categories: