This chapter describes an overview of the Oracle DIVA Enterprise Connect, the DIVA Web Services API, and includes the following information:
The DIVA Web Services API is a standards-based Web Service API that connects to Oracle DIVArchive or Oracle DIVAnet systems, acting as a web service binding for the DIVArchive API. The DIVA Web Services API provides a language and operating system independent method of submitting requests to archive, restore, copy, or 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. The API includes both SOAP and REST bindings.
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). See Authentication for more information.
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 its 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 is a software package that provides an implementation of the DIVA Web Services API. This implementation enables 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 DIVA Enterprise Connect platform consists of Oracle WebLogic, installation and administration scripts, data files, and configuration.
When a request is sent to DIVA Enterprise Connect, the request is forwarded to either DIVArchive or DIVAnet. The response is returned as an XML document back to the caller, in either REST or SOAP format.
DIVA Enterprise Connect 1.0 implements the DIVA Web Services 2.2 API, and is compatible with DIVArchive 7.4 and later (Oracle recommends DIVArchive 7.5 and later), and DIVAnet 2.1 and later. Earlier versions of the DIVA Web Services API are not supported on the DIVA Enterprise Connect platform. 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. DIVA Enterprise Connect 1.0 supports the 2.2 version of the DIVArchive Web Services API; earlier API versions are not supported on release 1.0. This is true for both SOAP and REST.
The DIVArchive 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. Some minor changes from version 2.1 can be expected; 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. SOAP 1.2 bindings are no longer supported.
Some deviations from version 2.1 will require more effort to remedy. For example, passing parameters in the URL is no longer supported, and the URL format has changed slightly from the 2.1 release. See Chapter 2 for more details on these changes.
The following commands available in the DIVArchive Web Services 2.1 API are deprecated:
insertTapeShort()
addGroupShort()
deleteInstanceByMediaName()
See Chapter 7 for more information on the deprecated commands.