Namespaces

Variants
Actions

Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries over the next few weeks. Thanks for all your past and future contributions.

Archived:How to use Vista personal webserver to test OMA DRM 1.0

From Wiki
Jump to: navigation, search

Archived.pngArchived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.

We do not recommend Flash Lite development on current Nokia devices, and all Flash Lite articles on this wiki have been archived. Flash Lite has been removed from all Nokia Asha and recent Series 40 devices and has limited support on Symbian. Specific information for Nokia Belle is available in Flash Lite on Nokia Browser for Symbian. Specific information for OLD Series 40 and Symbian devices is available in the Flash Lite Developers Library.

Article Metadata
Article
Created: jimgilmour1 (30 Apr 2009)
Last edited: hamishwillee (13 May 2013)

Contents

Introduction

If you have a PC using Microsoft Windows(r)Vista(tm) Premium edition or above you have the ability to run a local personal webserver to test OMA DRM 1.0.

  • Why is OMA DRM 1.0 important?.

Digital Rights Management has always been important, in particular now that the Ovi store will be using DRM to deliver content around the world. Stopping your content being forwarded via bluetooth or SMS has become more important. The increasing importance of FlashLite and Web RunTime (WRT) in generating revenue will mean the need to understand how to protect your content.


  • Why create a local personal webserver?

To keep your content safe during development. The last thing you want is for your unprotected content to be seen by others.

Local personal webservers dont have web security issues that on-line servers always have like uploaded virus.

Let's install the local personal web server

Using Microsoft Windows(r)Vista(tm) Premium edition or above login as Adminstrator or have the Admin username/password available. Dont do this on Primary Domain Controllers or Domain clustered PC's without permission of you site/network adminstrator. Use a local PC connected to a local router, behind a firewall router.


Microsoft terminology is to call Microsoft Windows(r)Vista(tm) "personal webserver" by Microsoft product name IIS7, (Internet Information Server Version 7). From now on IIS7 will be used.

To install IIS with default settings

1.  Click the Start button, click Control Panel, ? click Programs, and then
    click Turn Windows features on or off. 
    If you are prompted for an administrator password or confirmation,
    type the password or provide confirmation.

2.  In the list of Windows features, select Internet Information Services, and then click OK.

.....

Message say "Takes a while... ", cup of coffee time...

....

Configuring personal web server with MIME types

  • Open IIS manager


To open IIS Manager from the Search box Click Start. In the Start Search box, type inetmgr and press ENTER.


The GUI method for those who like the long way round is Start -> Control Panel -> Administrative Tools -> Internet Information Services


Well we will be using type inetmgr because we will restart several times.

Checking MIME classes

Next setup the MIME first look and set if already installed

Open IIS manager as above

In middle pane, Features View, double-click MIME Types. On the MIME Types page, select the MIME type you want to change. In the right pane, Actions pane, click Edit. In the Edit MIME Type dialog box, change the value in the MIME type text box, and then click OK.

see Microsoft Technet Support IIS 7.0: Edit a MIME Type web page for more information if needed

Take a while to look at the currently installed MIME

Scroll down to .zip well known one everyone understands and double click. Look at the format this is layed out in. The extension at the top is .zip and the MIME type: application/x-zip-compressed. Leave this alone, Click cancel.

Adding a new MIME type for OMA DRM 1.0

See page 31 DRM Developer's Guide for Nokia Devices v3.0 for futher information on OMA DRM 1.0 MIME used below

On the right pane at the top is the "Add..."

  • OMA forward-lock and OMA combined delivery message

In the "File name extension" box put ".dm" In the MIME box put "application/vnd.oma.drm.message"


  • OMA DRM 1.0 Content Format

In the "File name extension" box put ".dcf" In the MIME box put "application/vnd.oma.drm.message"

  • OMA Download method

In the "File name extension" box put ".dd" In the MIME box put "application/vnd.oma.dd+xml"

  • SIS Download method without DRM

In the "File name extension" box put ".sisx" In the MIME box put "application/vnd.symbian.install"

  • Recognise Nokia Web Runtime Widgets (WRT) ".wgz"

in the "File name extension" box put ".wgz" in the MIME box put "application/x-nokia-widget"

  • FlashLite MIME

If you do not already have FlashLite MIME add

in the "File name extension" box put ".swf" in the MIME box put "application/x-shockwave-flash"

Setting up the files on the local file system for the web server

In the left hand Connetions pane Click the Arrow on the PCname(netname) to expand Click "Sites" to expand to "Default Web Site" Click "Default Web Site" In the Middle "Default Web Site Home" Click "Default Document"

In the right hand Actions pane Click "Explore" The wwwroot directory opens

Paste in to this directory including your created index.html and DRM files you created

using "How to package Flash content in a Widget" article

Double click the Default document in the middle pane. Click on "index.html". On the right Action pane. Click the up arrow and increase priority to the topmost. In the middle pane "index.html" should now be at the top of the list.

Open the browser and browse to "http://myPC" The value of "my PC" comes from In the left hand Connections pane The top left world Globe has the name of server, basically the PC network name

If this does not work use the TCP/IP address allocated by the router e.g "http://192.168.1.64" by typing "ipconfig" in Vista Command Shell

Now try accessing the same address via a WRT enabled phone. Remember to clear the phone browser cache/privacy data of all data or the last connection will appear without connecting to the server!.

index.html webpage for the wwwroot directory of webserver

<!DOCTYPE html PUBLIC "-//WAPFORUM//DTD XHTML Mobile 1.0//EN" "http://www.wapforum.org/DTD/xhtml-mobile10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>OMA DRM 1.0</title>
</head>
 
<body>
Download and save this file to your handset to test OMA DRM 1.0 Forward Lock:
<br />
<a href="testdrm.dm">testdrm.dm</a>
<br />
 
</body>
</html>

References

How to protect WRT widgets with OMA DRM 1.0

Acknowlegements

This article would not have been possible without the work of the other Nokia Developer Champion's who have provided ideas and inspiration to write this article

This page was last modified on 13 May 2013, at 23:52.
1061 page views in the last 30 days.

Was this page helpful?

Your feedback about this content is important. Let us know what you think.

 

Thank you!

We appreciate your feedback.

×