Oracle DIVAnet provides a unified view of archived digital assets across multiple, distributed Oracle DIVArchive systems and the cloud. It facilitates the moving of content back and forth among DIVArchive sites, and from customer Source/Destination servers and disks. DIVAnet assists with disaster recovery, content distribution, access control, performance, and content availability.
By connecting to multiple DIVArchive sites, DIVAnet creates a virtual archive system that spans geographical locations. You can leverage disaster recovery sites to provide additional asset availability when outages occur, and improve archive and restore performance for some assets when systems run normally. You can use DIVA installations from other parts of your organization as strategic backup sites, content sharing partners, and participants in global business media workflows. DIVAnet eases the burden of keeping track of content that could exist in local DIVA sites, remote DIVA sites, and the cloud.
Applications can use DIVArchive API to connect directly to DIVAnet. This allows applications to store and access digital assets in different geographical locations. DIVAnet synchronizes asset information from each DIVA site, so that it always has an up-to-date asset inventory. DIVAnet uses this information to enforce naming uniqueness, and to select the best site for various requests (for example Restore and Copy requests). DIVAnet also provides access rules to limit the operations that users are allowed to perform.
DIVAnet allows applications written using the DIVA API to control multiple DIVArchive sites as if they were one large archive system. The DIVArchive API allows client applications to connect to an archive system and store content, copy content, delete content, or restore content (see the Oracle DIVArchive C++ API Programmer's Guide in the Oracle DIVArchive Additional Features Documentation library for more on the DIVArchive API). The API also supports retrieving of information about archived objects. DIVAnet implements support for a large subset of the DIVA API - that which is commonly used by popular applications such as Media Asset Management (MAM) applications.
For more information, see Chapter 7.
DIVAnetUI allows the user to monitor DIVAnet requests, and view, copy, restore, and delete DIVAnet Assets (DIVA archived objects) across multiple DIVArchive sites. All DIVAnet level requests can be monitored, whether issued through the API or through the UI itself. You can also view asset information for all configured DIVArchive sites, whether the asset was archived through DIVAnet or not. DIVAnetUI provides flexible ways of querying both request information and asset information.
DIVAnet 2.3.0 does not support the DIVArchive Control GUI (even in Direct Mode). Instead, use the DIVAnetUI to monitor DIVAnet, and the DIVArchive Control GUI to monitor DIVArchive.
For more information, see Chapter 5.
You can use the DIVAnetAdmin command-line tool to:
Monitor the status of database synchronization
Set site-specific parameters and limits
View API connections
Reload the workflow profiles and access rules
Change the log level of DIVAnet services
For more information, see Chapter 6.
Using DIVAnet, you can create rules to control which users and which Workflow Profiles can perform certain operations. For instance, you can create rules that limit which Source/Destinations can receive restored content, or limit which objects can be copied to sites. For more information, see "Access Rules".
You can use the AutoCopy feature to control which assets automatically replicate from one site to another. This feature supports flexible ways of scheduling copy tasks and can handle large numbers of requests. For more information, see "AutoCopy".
Some inter-site transfer tasks are not performed specifically by DIVAnet, but instead are carried out by other DIVArchive components as noted below:
The Drop Folder Monitor (DFM) service monitors content that is being written to disk in a folder. It then archives that content into a DIVArchive system after the content has been completely transferred. DFM can be used as part of an intersite copy workflow, and can also be used with DIVAnet. See the Oracle DIVArchive Drop Folder Monitor (DFM) User's Guide in the Oracle DIVArchive Additional Features Documentation library for more information on DFM.
You can configure Storage Plan Manager (SPM) to automatically perform an operation when content arrives at a DIVArchive site. One of these operations is to restore the new content to a drop folder, which can then archive that content into another DIVA system. This functionality is similar to what you can achieve using AutoCopy. See the Oracle DIVArchive Storage Plan Manager (SPM) User's Guide in the Oracle DIVArchive Additional Features Documentation library for more information on SPM.
DIVArchive itself provides the ability to transfer content from Source/Destinations to DIVA systems and back again, and copy and delete archived content.
DIVAnet, DIVArchive, SPM, and DFM work in unison to satisfy distributed media workflows.