This chapter describes an overview of the Oracle DIVA Enterprise Connect and includes the following information:
Oracle DIVA Enterprise Connect is a standards-based Web Service API implemented on the Oracle WebLogic Suite. DIVA Enterprise Connect interacts with Oracle DIVArchive and Oracle DIVAnet systems, acting as a web service binding for the DIVArchive API. DIVA Enterprise Connect provides a client computer with a language and operating system independent method of submitting requests to archive, restore, copy, or delete content. It allows clients to gather information about archived objects and media, and manage archive devices (for example, tape libraries and disk arrays).
The DIVA Enterprise Connect platform consists of Oracle WebLogic, installation and administration scripts, data files, and configuration. The installation scripts assist in installing and configuring the DIVA Enterprise Connect platform.
Oracle DIVArchive is a Content Management Solution specifically engineered for archiving, tracking, and restoring large amounts of rich media and broadcast digital assets. It integrates with a multitude of industry standard software, archive media, transfer protocols, hardware platforms, and the Cloud. Oracle DIVArchive enables organizations to manage the lifecycle of their digital assets through automated policies that move data to the appropriate tier of storage based on access patterns, age, and storage utilization.
Oracle DIVAnet provides a unified view of archived digital assets across multiple, distributed DIVArchive systems, and the Cloud. It facilitates moving content back and forth among DIVArchive sites, and to and from customer Source/Destination servers and disks. DIVAnet performs tasks for 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.
Oracle DIVA Enterprise Connect provides web services that allow client applications to submit requests to a remote Oracle DIVArchive or Oracle DIVAnet system. Web services are software modules that you can invoke remotely using a standard messaging format; in this case, XML. The client applications can use standard internet protocols (for example, HTTP and URLs).
The Web Services API enables a remote client to archive, restore, copy, and delete digital assets. The API also provides services to list archive objects, list archive device status (tape libraries and disks), and obtain the status of requests issued to DIVArchive. SOAP and REST bindings for the API are provided with DIVA Enterprise Connect.
When a caller sends a request to DIVA Enterprise Connect, it forwards the request to either DIVArchive or DIVAnet. The response returns as an XML document back to the caller, in either REST or SOAP format.
The Web Services use basic authentication by default. Oracle recommends using basic authentication with an SSL/TLS transport (the default is port 9444 in Web Services), and also recommends assigning credentials using the API Key Generator. For more information, see "Authentication".
See the Oracle DIVA Enterprise Connect Web Services API Programmer's Guide in the Oracle DIVA Enterprise Connect documentation library for detailed API information.
This release of the DIVA Enterprise Connect is compatible with DIVArchive 7.4 and later (Oracle recommends DIVArchive 7.5 and later), and DIVAnet 2.1 and later. DIVAnet 2.2 and later is required for the HTTP-based transport to the DIVAnet ManagerAdapter.
The current DIVA Enterprise Connect software release is 1.0.1. DIVA Enterprise Connect 1.0+ supports the 2.2 version of the DIVA Web Services API. Earlier API versions are not supported on release 1.0. This is true for both SOAP and REST. Enterprise Connect 1.0.1 introduces a Windows version, in addition to the Linux version.
The Web Services 2.2 API contains the same basic information elements as the 2.1 version, but applications written against version 2.1 may not be compatible with version 2.2. There are some minor changes from 2.1 (for example, different return code behavior, and slightly different naming for namespaces in XML responses). Other modifications include changes in service authentication, HTTP return codes, HTTP header fields that are now strictly required (for example, Content-Type), a new 2.2 WSDL document, and new security restrictions. The SOAP 1.2 bindings are no longer supported.
Some deviations from 2.1 will require more effort to remedy. For example, 2.2 no longer supports passing parameters in the URL, and the URL format has changed slightly from the 2.1 release.