C H A P T E R 9 - DRM Server Integration

C H A P T E R 9

DRM Server Integration

One of the options provided with the Content Delivery Server for protecting content requires an application that implements the Open Mobile Alliance (OMA) Digital Rights Management (DRM) 1.0 guidelines for managing digital rights. To use this option, you must provide the application that the Content Delivery Server works with. For this release, Content Delivery Server provides support for SafeNet DRM Mobile as the OMA DRM 1.0 implementation.

This chapter describes how to integrate the Content Delivery Server with DRM Mobile. For information on configuring DRM support in the Content Delivery Server, see the Sun Java System Content Delivery Server Installation Guide. For information on applying DRM to content, see the Sun Java System Content Delivery Server Administration Guide.

9.1 Setting Up DRM Mobile

DRM Mobile can be obtained from SafeNet. See http://www.safenet-inc.com/products/sentinel/DRM_Mobile.asp for information.

Install DRM Mobile on the server on which the Catalog Manager is deployed. Use the instructions provided with DRM Mobile. DRM Mobile consists of a protection component and a license component. Install both components with the Catalog Manager.

Create an operator user in DRM Mobile for accessing the protection component and the license component. If you do not want to use the same user name for both components, create a content provider user to access the protection component and a content distributor user to access the license component.

Note the user names and passwords for the users that you created as well as the URL needed to access the DRM Mobile components. You need this information to configure the Content Delivery Server to use DRM Mobile as described in the next section.

9.2 Configuring the Content Delivery Server to Use DRM Mobile

After you install DRM Mobile and set up the required users, set the properties shown in the following table. These properties are in the $CDS_HOME/deployment/deployment-name/conf/drmmobile.properties file. Set these properties in the Catalog Manager deployment and in each Vending Manager deployment.

Note - This file contains unencrypted passwords. Set the file permissions to restrict access to this file.

TABLE 9-1 Properties for DRM Mobile
Property	Description
`protection.url`	URL used to access the protection component of DRM Mobile.
`protection.username`	User name used to access the protection component of DRM Mobile.
`protection.password`	Password for the user name used to access the protection component of DRM Mobile.
`protection.uploadDirectory`	Directory from which DRM Mobile accesses the unprotected content and uses for temporary files created during the protection process. These files are deleted when the protection process completes. Note: The directory specified must be the same as the directory specified for the `java.io.tmpdir` property in the DRM Mobile `protectionConfig.properties` file.
`protection.deployDirectory`	Directory to which DRM Mobile writes the protected content. Note: The directory specified must be the same as the directory specified for the `com.dmdsecure.mobile.protection.deployment.FileContentHost.outputPath` property in the DRM Mobile `protectionConfig.properties` file. See the DRM Mobile documentation for information on the proper format for this value.
`protection.domain`	Domain name used to generate unique IDs for the protected content, for example, using `sun.com` as the domain generates IDs similar to `cid:2001-SD@sun.com`.
`license.url`	URL used to access the license component of DRM Mobile.
`license.username`	User name used to access the license component of DRM Mobile.
`license.password`	Password for the user name used to access the license component of DRM Mobile.
`license.rightsIssuerUrl`	URL used to access the license for content when separate delivery is used, for example, `http://www.sun.com/cds?cid={cid}` The Content Delivery Server replaces the value inside the braces with the content ID for the content that the subscriber is accessing.

If you did not enable the OMA DRM 1.0 method when you deployed and configured the Content Delivery Server, use the following command to enable this method:

cdsi db import [-conf db-configuration-file] -cs enableomadrm10.sqli

db-configuration-file is the name of the database configuration file that contains the information for creating the Catalog Manager schema. If db-configuration-file is not provided, the value specified for the DEFAULT_DB variable in the init_env.sh script is used. For information on enabling DRM methods, see Section 4.7.1, "Set the DRM Methods Supported," in the Sun Java System Content Delivery Server Installation Guide.