Standalone RMI
In the past, RMI had to have the Aurora Ingest Server in order to function even at a
base import level. This tether is removed in 7.0, which makes RMI much more flexible
and opens it up to practical operation in the field.
With the standalone RMI, the Aurora Core is still a requirement as is the iSCSI
connectivity of the system.
Standalone RMI will require a local database, which get installed as part of the Aurora
Core. This is so that RMI can recognize previously imported clips and disks.
The following screenshot shows the configuration for both the client (current) and
standalone methods of running RMI. You'll see that selecting standalone enables
configuration for both the MediaFrame server and the Aurora Playout components.
18 October 2010
Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions
45
New topics