DRM Server Integration

C H A P T E R 4

One of the options provided with 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 with which Content Delivery Server works. Content Delivery Server provides support for SafeNet DRM Fusion Toolkit as the OMA DRM 1.0 implementation.

This chapter describes how to integrate Content Delivery Server with DRM Fusion Toolkit. For information on configuring DRM support in Content Delivery Server, see Chapter 13. For information on applying DRM to content, see the Sun Java System Content Delivery Server Reference Manual.

This chapter includes the following topics:

Setting Up DRM Fusion Toolkit

Configuring Content Delivery Server to Use DRM Fusion Toolkit

4.1 Setting Up DRM Fusion Toolkit

Obtain DRM Fusion Toolkit from SafeNet. See http://www.safenet-inc.com/digital_rights_management/DRM_Fusion_Toolkit.asp for information.

Install DRM Fusion Toolkit using the instructions provided with it. You can install this application on any server.

Note the directory path in which you installed DRM Fusion Toolkit, the Master Key Password that you specified during installation, and the name and location of the configuration Java Archive (JAR) file that is created. You need this information to configure Content Delivery Server to use DRM Fusion Toolkit as described in the next section.

4.2 Configuring Content Delivery Server to Use DRM Fusion Toolkit

After you install DRM Fusion Toolkit, you must set configuration properties for Content Delivery Server, copy the DRM Fusion Toolkit JAR files to your Content Delivery Server deployments, and ensure that OMA DRM 1.0 is enabled.

4.2.1 Setting the Configuration Properties

Set the properties shown in the following table. These properties are in the $CDS_HOME/deployment/deployment-name/conf/drmfusion.properties file. Set these properties in the Catalog Manager deployment and in each Vending Manager deployment.

Note - This file contains an unencrypted password. Set the file permissions to restrict access.

TABLE 4-1 Properties for DRM Fusion Toolkit
Property	Description
`protection.password`	Master Key Password for DRM Fusion Toolkit.
`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`.

4.2.2 Copying DRM Fusion Toolkit JAR Files

The JAR files provided with DRM Fusion Toolkit must be copied to all Content Delivery Server deployments. These JAR files are found in the safenet-home/modules and safenet-home/modules/third-party directories, where safenet-home is the fully qualified name of the directory in which you installed DRM Fusion Toolkit. You must also copy the configuration JAR file safenet-toolkit-configuration.jar that was created when DRM Fusion Toolkit was installed. This file is in the same folder as the install.sh command for DRM Fusion Toolkit, typically safenet-home/bin.

Setting up Content Delivery Server with the DRM Fusion Toolkit JAR files depends on the application server you are using and whether you have already deployed. For each Content Delivery Server deployment, follow these steps:

1. For all application servers, place all of the DRM Fusion Toolkit JAR files in the $CDS_HOME/dist/cds/lib/external directory.

The DRM Fusion Toolkit is now included in all future deployments.

2. If you have existing deployments that need to use the DRM Fusion Toolkit, place the JAR files in the $CDS_HOME/deployment/deployment-name/lib/external directory for each deployment.

If you are using WebLogic Server, the classpath is handled for you.

If you are using Sun Java System Application Server, update the classpath for each deployment:

a. Back up the $CDS_HOME/deployment/deployment-name/sun/domains/cdsdomain/config/domain.xml file before editing it so you can recover from any errors that might be introduced during editing.

b. Edit domain.xml and modify the java-config element to add the absolute path for the JAR files to the classpath-suffix attribute.

c. Save your changes.

3. Restart any existing deployment to make it aware of the new JAR files.

4.2.3 Enabling OMA DRM 1.0

If you did not enable the OMA DRM 1.0 method when you deployed and configured 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 Chapter 13.