IBC 2014 : EBUCore and FIMS presentations

FIMS REST API simulator

Entertainment

Feature Films, TV Fictions,

Animation, Movies

FRANCE - BELGIUM - CANADA - LUXEMBOURG

Mikros Image : who we are, what we do

Communication

Advertising, Corporate,

Digital Content, Print

and

Museums, Art, Video Clips,

Video Games

VFX Studio / Animation Studio/ DI Service

Digital Laboratory & Deliveries / R&D

Mikros Image : Research & Development

In-house tools to improve productivity

Collaborative projects, with open source contribution

Third party developments for partners like ARPP, ABMA/BVAM and FTV

OpenVG Crowd Colorpipe Tools

FileMetaCheckerTuttleOFXDynArchi

www.dynarchi.org http://opensource.mikrosimage.eu

PADdef

Mikros Image : REST API simulator Context : SOA FIMS architecture

● set up automatic process for mastering and archiving tasks (MIK digital lab)

( )

ESB

Orchestrator(BPM) DynArchi

CatalogueSpaces(MAM)

ERP

RenderFarm/ Disk Space Monitoring

Dispatch Job Repository Transfer Transform Quality Analysis

cp ftp

mv

rsync

scp

Tuttle OFX

FFmpegEpisode

FileMetaCheckerPuli OnlineNear

OnlineOffline

SAN Sas I/O+

Stockage

SALT IBMStorageManager

FIMS modules File

Reloader

Media Bus Metadata Bus

Flow

Mikros Image : REST API simulator

Why we do it

Mikros Image initial objectives

1. Check standard compliance :

○ to verify our SOA implementation with FIMS specifications

2. Check backward compatibility with new versions :

○ because FIMS is still evolving

That could be part of your objectives too!Like :

3. Comfort & quality when using FIMS API

4. Training and knowhow for your software team

Mikros Image : REST API simulator

What we do, and how

● Based upon light-weight generic REST server

○ powered by CherryPy 3.2.0

○ with no database

● Needs some tweakings regarding FIMS 1.1 REST implementation

○ still with some SOAP legacy (nobody is 100% Restfull)

● “1 JSON file” specifications

○ for resource definition, format, filtering options, etc…

● “1 JSON file” test dataset

○ with on-the-fly init and validation content“1 JSON file” : one single file, which can be updated for each version

Mikros Image : REST API simulator

Mikros Image : REST API simulator

What we have in mind

● Extend Unit Test automation to setup some generic REST controller

○ applied on request / response formats

○ passing error description

● Provide users with a documented test console

○ why not use Swagger ?

● Feed simulator with “standard” specification format

○ why not use WADL?

○ to improve REST standardisation & interoperability

○ depending on forthcoming new FIMS specs

● and much more...

Contacts

Nicolas PROVOSTnipr@mikrosimage.eu

Jean-Pierre EVAINevain@ebu.ch