Sun Microsystems Content Delivery Server 5 User Manual

Sun Java™ System

Content Delivery Server 5.0

Administration Guide

2005Q4

Sun Microsystems, Inc. www.sun.com

Part No.: 819-3209-10 2005Q4

Submit comments about this document at: http://docs.sun.com/app/docs/form/comments

Sun Microsystems,Inc. has intellectual property rights relatingto technology embodied in theproduct that isdescribed inthis document. In particular,and without limitation, these intellectualproperty rights mayinclude oneor more ofthe U.S. patents listed at

http://www.sun.com/patents and one or more additional patents or pendingpatent applicationsin the U.S.and inother countries.

U.S. GovernmentRights -Commercial software. Government users are subject to the SunMicrosystems, Inc. standardlicense agreement and applicable provisionsof the FAR and its supplements.

This distributionmay includematerials developed by third parties.

Sun, SunMicrosystems, the Sun logo, Java,and J2ME aretrademarks or registeredtrademarks of SunMicrosystems, Inc. in the U.S.and other countries.

UNIX isa registered trademarkin the U.S. and othercountries, exclusively licensed through X/Open Company, Ltd.

Netscape andNetscape Navigatoris a trademark or registered trademarkof Netscape Communications Corporation inthe United States and other countries.

Products covered by and informationcontained in this service manualare controlled byU.S. Export Controllaws and may be subjectto the export orimport lawsin other countries. Nuclear, missile, chemical biologicalweapons or nuclear maritime enduses orend users, whether direct orindirect, are strictly prohibited.Export orreexportto countriessubject to U.S. embargo or to entities identiﬁedon U.S. export exclusion lists, including,but notlimited to, the denied personsand specially designated nationals listsis strictly prohibited.

DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESSFOR APARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.

Sun Microsystems,Inc. détient les droits de propriétéintellectuels relatifs àla technologieincorporée dans leproduit qui est décrit dansce document. Enparticulier, et ce sanslimitation, ces droitsde propriété intellectuellepeuvent inclure unou plusdes brevets américainslistés à l’adresse http://www.sun.com/patents et unou lesbrevets supplémentaires ou les applications debrevet en attenteaux Etats- Unis et dans lesautres pays.

Cette distributionpeut comprendre descomposants développés par des tierces parties.

Sun, SunMicrosystems, le logo Sun, Java,et J2ME sont des marques de fabrique oudes marques déposéesde SunMicrosystems,Inc. auxEtatsUnis etdans d'autres pays.

UNIX estune marque déposée aux Etats-Uniset dans d’autrespays et licenciée exlusivement parX/Open Company, Ltd.

Netscape etNetscape Navigatorest une marquede Netscape Communications Corporation auxEtats-Unis et dans d'autres pays.

Les produitsqui font l'objet de cemanuel d'entretien etles informations qu'il contient sontregis par lalegislation americaineen matiere de controle desexportations et peuvent etre soumis au droit d'autres paysdans ledomaine des exportationset importations.Les utilisations ﬁnales, ouutilisateurs ﬁnaux,pour des armes nucleaires, des missiles, des armesbiologiques et chimiques ou dunucleaire maritime, directement ouindirectement, sont strictementinterdites. Les exportationsou reexportations versdes payssous embargo desEtats-Unis, ou vers desentites ﬁgurantsur les listes d'exclusion d'exportationamericaines, y compris, mais demaniere non exclusive,la liste de personnes qui font objetd'un ordre dene pas participer, d'une facon directe ouindirecte,aux exportationsdes produits oudes services qui sont regi par la legislation americaineen matiere de controle des exportations et laliste de ressortissantsspeciﬁquement designes, sont rigoureusement interdites.

LA DOCUMENTATION ESTFOURNIE "EN L'ETAT" ET TOUTES AUTRES CONDITIONS, DECLARATIONSET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES, DANSLA MESURE AUTORISEEPAR LA LOI APPLICABLE, YCOMPRIS NOTAMMENT TOUTE GARANTIEIMPLICITE RELATIVEA LAQUALITE MARCHANDE, AL'APTITUDE AUNE UTILISATIONPARTICULIERE OU A L'ABSENCE DECONTREFACON.

Preface xv

1. Introduction 1

Sun Java System Content Delivery Server 1

Catalog Manager 3

Catalog Manager Processes 4

Automated Content Validation 5

Content Management 5

Device Management 6

Account Management 6

Plan Management 6

Fulfillment Manager 7

Vending Manager 7

Vending Manager Processes 9

Content Management 9

Plan Management 9

Account Management 9

Reporting 10

Administration Consoles 10

Browser Requirements 10

iii

Accessing the Administration Consoles 11

▼ Logging in to the Catalog Manager 11

▼ Logging in to the Vending Manager 12

2. Catalog Manager 13

Managing Content 13

Managing Content Categories 14

▼ Viewing Categories 14

▼ Adding a Category 16

▼ Editing a Category 17

▼ Deleting a Category 18

Managing Content Types 19

Content Submissions 19

Content Protection 20

Inapplicable Content 21

Using CDS DRM Agents and CDS OMA

Forward Lock 21

Using OMA DRM 1.0 23

OMA DRM 1.0 and Non-Compliant Devices 24

MIME Types for OMA DRM 1.0 24

Associating Content Types with DRMs 25

Enabling and Disabling a DRM 26

Pricing Content 26

Pricing Options 29

Changing the Pricing of Content 29

Disassociating Content From Pricing Options 30

▼ Viewing Supported Content Types and MIME Types 31

▼ Viewing Properties for a Supported MIME Type 32

▼ Adding a Content Type 32

iv Administrator Guide • 2005Q4

▼ Editing a Content Type 34

▼ Creating a Pricing Option 35

▼ Editing a Pricing Option 37

▼ Deleting a Content Type 39

▼ Disabling a Pricing Option 39

▼ Registering a MIME Type 40

▼ Editing a MIME Type 41

▼ Deleting a MIME Type 43

Managing Submitted Content 44

▼ Viewing Submitted Content 44

▼ Viewing Submitted Editions 47

▼ Removing an Edition 48

▼ Searching for Content 49

▼ Changing the Status of Content 50

▼ Changing the Status of Editions 52

▼ Editing Content 52

Managing Published Content 55

▼ Viewing Published Content 56

▼ Removing Content 57

▼ Viewing Published Editions 57

▼ Copying or Moving Categories of Content 58

▼ Copying or Moving Content Items 62

Setting Custom Prices for Published Content 66

Managing Devices 68

Managing Device Libraries 69

▼ Viewing Device Libraries 70

▼ Viewing Properties for a Specific Device Library 70

▼ Adding a Device Library 71

Contents v

▼ Editing a Device Library 73

▼ Deleting a Device Library 74

Managing Content Descriptor Templates 74

▼ Viewing Content Descriptor Templates 76

▼ Adding a Content Descriptor Template 77

▼ Editing a Content Descriptor Template 78

Managing Device Definitions 78

Viewing Devices 78

▼ Adding a Device 80

▼ Specifying Device Capabilities 83

▼ Activating New or Quarantined Devices 85

▼ Mapping MIME Types to a Device 86

▼ Setting a Compatible Device 88

▼ Adding Supported Devices to Existing Content 89

▼ Editing a Device 89

▼ Setting the Default Device 90

▼ Deleting a Device 91

▼ Importing Devices 91

▼ Exporting Devices 92

Managing Server Locales 92

▼ Adding a New Locale 92

▼ Changing a Locale 94

Deleting a Locale 94

Managing Accounts 94

▼ Viewing Accounts 95

Managing Vending Manager Accounts 97

▼ Viewing Vending Manager Accounts 97

▼ Adding a Vending Manager Account 97

vi Administrator Guide • 2005Q4

▼ Editing a Vending Manager Account 99

▼ Deleting a Vending Manager Account 100

Managing Developer Accounts 101

▼ Viewing Developer Accounts 101

▼ Adding a Developer Account 101

▼ Editing a Developer Account 103

▼ Deleting a Developer Account 104

Managing Catalog Manager Administrator Accounts 104

▼ Viewing Catalog Manager Administrator Accounts 104

▼ Adding a Catalog Manager Administrator Account 105

▼ Editing a Catalog Manager Administrator Account 106

▼ Deleting a Catalog Manager Administrator Account 106

Managing Plans 107

Managing Vending Plans 107

▼ Viewing Vending Plans 107

▼ Adding a Vending Plan 108

▼ Editing a Vending Plan 110

▼ Viewing Vending Plan Members 111

▼ Adding a Member to a Vending Plan 111

▼ Removing a Member from a Vending Plan 112

▼ Setting the Default Vending Plan 112

▼ Deleting a Vending Plan 113

Managing Developer Plans 114

▼ Viewing Profiles 114

▼ Adding a Profile 115

▼ Editing a Profile 117

▼ Deleting a Profile 118

▼ Viewing Developer Plans 119

Contents vii

▼ Adding a Developer Plan 119

▼ Editing a Developer Plan 120

▼ Viewing Developer Licensees 121

▼ Adding a Developer Licensee to a Developer Plan 122

▼ Removing a Developer Licensee from a Developer Plan 123

▼ Setting the Default Developer Plan 123

▼ Deleting a Developer Plan 124

Getting Background Job Status 125

▼ Getting Job Status 126

Examining Job Details 127

Clearing a Failed Job 128

3. Vending Manager 129

Administrator Tasks 130

Managing Categories 130

▼ Adding a Category 130

▼ Editing a Category 132

▼ Deleting a Category 133

Managing Catalog Content 134

▼ Viewing Published Content 134

▼ Searching for Published Content 137

▼ Viewing the Properties of Published Content 137

▼ Viewing Editions of Published Content 139

Setting Stocking Options 141

▼ Stocking Content Manually 142

▼ Stocking Multiple Content Items 144

Viewing Stocking Jobs 149

Clearing the Stocking Jobs list 150

▼ Stopping a Stocking Job 150

viii Administrator Guide • 2005Q4

Checking the Status of a Stocking Job 151

▼ Updating the Catalog for Stocked Content 152

Pricing for Content for a Locale 153

▼ Setting Local Pricing 153

Price Update Notification 155

▼ Changing the Price of Individual Content Items 156

Managing Stocked Content 156

Viewing Stocked Content 156

▼ Searching for Stocked Content 156

▼ Changing the Status of Stocked Content 157

▼ Unstocking Content 158

▼ Editing Stocked Content 159

▼ Editing External Content IDs 161

Updating Stocked Content 162

▼ Copying or Moving Categories of Content 163

▼ Copying or Moving Content Items 167

▼ Customizing Prices for Stocked Content 170

Managing Bundles 173

Bundle Pricing 174

▼ Creating a Bundle 175

▼ Viewing Bundle Information 179

▼ Deleting a Bundle 181

▼ Editing External Content IDs 181

▼ Changing the Status of a Bundle 182

▼ Editing a Bundle 183

▼ Managing Testing Content 183

▼ Stocking Testing Content 184

Creating Customized Marketing Campaigns 184

Contents ix

▼ Creating a Campaign 185

▼ Specifying a Campaign Type 185

▼ Specifying Campaign Options and Target Audience 186

▼ Specifying a Campaign Message 187

▼ Specifying Content for the Campaign 188

▼ Specifying Campaign Pricing Characteristics 189

▼ Specifying Campaign Scheduling 190

▼ Viewing Campaign Details 191

▼ Editing a Campaign 193

▼ Testing a Campaign 193

Working with Subscriber Segments 194

▼ Displaying Subscriber Segments 195

▼ Creating a Subscriber Segment 195

▼ Editing a Subscriber Segment 197

Working with Campaign Templates 197

▼ Displaying Available Campaign Templates 197

▼ Creating a Campaign Template 197

▼ Editing a Campaign Template 201

Managing Vending Manager Administrator Accounts 201

▼ Viewing Vending Manager Administrator Accounts 201

▼ Adding a Vending Manager Administrator Account 202

▼ Editing a Vending Manager Administrator Account 204

▼ Deleting a Vending Manager Administrator Account 205

Customer Care Agent Tasks 205

▼ Viewing Stocked Content 206

▼ Setting the Display of Stocked Content for Subscribers 207

▼ Viewing the Properties of Stocked Content 208

▼ Viewing Editions of Stocked Content 209

x Administrator Guide • 2005Q4

Managing Subscriber Accounts 209

▼ Viewing Subscriber Accounts 210

▼ Adding a Subscriber Account 210

▼ Editing a Subscriber Account 212

▼ Viewing a Subscriber’s Download History 213

▼ Managing Subscriber Licenses 213

▼ Extending Trial Usage 214

▼ Issuing a Refund 215

▼ Deleting a Subscriber Account 215

Managing Subscriber Plans 216

▼ Viewing Subscriber Plans 216

▼ Adding a Subscriber Plan 217

▼ Editing a Subscriber Plan 218

▼ Viewing Subscriber Plan Members 219

▼ Adding Members to a Subscriber Plan 220

▼ Removing Members from a Subscriber Plan 221

▼ Setting a Default Plan for New Subscribers 221

▼ Deleting a Subscriber Plan 222

▼ Editing Your Administrator Account 223

▼ Viewing Reports 223

Sending MMS Messages 225

▼ Choosing MMS as the Content Delivery System 225

Displaying MMS Messages 225

▼ Creating an MMS Message 226

▼ Editing an MMS Message 228

▼ Testing an MMS Message 229

Testing a New MMS Message 229

▼ Testing an Existing MMS Message 230

Contents xi

▼ Deleting an MMS Message 230

▼ Using the MMS Test Log 231

A. Device Capabilities 233

Descriptions of the Capabilities 233

System Capabilities 233

Mandatory Capabilities 234

Content Delivery Server-Specific Capabilities 234

Browser Capabilities 235

User Interface and Software Capabilities 235

Specifying a Capability Value 236

List 237

Integer 237

Boolean 237

Device Specifications 237

Nokia 6310i 238

User-Defined Devices 239

B. Content Pricing 241

Pricing Scenarios 243

Glossary 247

Index 255

xii Administrator Guide • 2005Q4

Tables

TABLE 2-1 DRM Types 20

TABLE 2-2 CDS DRM Agents 21

TABLE 2-3 OMA DRM 1.0 Formats 23

TABLE 2-4 Required MIME Types for OMA DRM 1.0 24

TABLE 2-5 DRM Options and Associated DRM Types and Content Types 25

TABLE 2-6 Content Delivery Server Pricing Models 27

TABLE 2-7 DRM Options and Pricing Models 28

TABLE 2-8 Content Status Types 44

TABLE 2-9 Content Status Types 50

TABLE 2-10 Content Delivery Server Pricing Models 54

TABLE 2-11 Content Attributes for Content Descriptor Templates 75

TABLE 2-12 Account Types 95

TABLE 2-13 Search and Display Operations 96

TABLE 2-14 Plan Types 107

TABLE 2-15 Background Job Indicators 125

TABLE 3-1 Content Status Symbols 136

TABLE 3-2 Properties Available for Notification Templates 198

TABLE A-1 Mandatory Capabilities 234

TABLE A-2 Content Delivery Server-Specific Capabilities 234

TABLE A-3 User Interface and Software Capabilities 235

xiii

TABLE A-4 Nokia 6310i Device Specifications 238

TABLE A-5 Device Specifications for a User-Defined Device 1 239

TABLE A-6 Device Specifications for a User-Defined Device 2 239

TABLE B-1 Associated DRMs, Content Types, and Pricing Models 241

TABLE B-2 Initial Pricing Set for Items 1 and 2 244

TABLE B-3 Resulting Pricing for Items 1 and 2 in Scenario 1 244

TABLE B-4 Resulting Pricing for Items 1 and 2 in Scenario 2 244

TABLE B-5 Resulting Pricing for Items 1 and 2 in Scenario 3 245

TABLE B-6 Resulting Pricing for Items 1 and 2 in Scenario 4 245

TABLE B-7 Resulting Pricing for Items 1 and 2 in Scenario 5 245

TABLE B-8 Resulting Pricing for Items 1 and 2 in Scenario 6 246

xiv Administrator Guide • 2005Q4

Preface

This guide provides an overview of the Sun Java™ System Content Delivery Server. It describes how to administer the Catalog Manager and Vending Manager components. It describes the device capabilities and the content pricing models supported by the Sun Java System Content Delivery Server.

Before You Read This Document

This guide is written for system administrators who are responsible for administering the Catalog Manager or Vending Manager. It assumes some knowledge of networking, database, and web technologies.

Note – Sun is not responsible for the availability of third-party web sites mentioned

in this document, and does not endorse and is not responsible or liable for any content, advertising, products, or other materials available through such sites.

How This Document Is Organized

This guide is divided into the following chapters:

■ Chapter 1 introduces the Content Delivery Server and describes the content life

cycle as it relates to the Catalog Manager and Vending Manager. It describes the automatic content validation process that the Content Delivery Server performs on submitted content. It also describes how to log in to the Catalog Manager and Vending Manager administration consoles.

■ Chapter 2 describes how to administer the Catalog Manager. It provides

instructions on how to review, categorize, and publish content. It describes how to define the mobile devices supported and their capabilities. It also describes how to manage access for developers and Vending Managers.

■ Chapter 3 describes how to administer the Vending Manager. It describes how to

stock content, manage Administrator and Subscriber Accounts, and run system reports.

■ Appendix A describes the capability matching process and defines the device

capabilities currently supported by the Content Delivery Server.

■ Appendix B provides a description of the digital rights management types

supported in the Content Delivery Server and provides a set of business scenarios involving content pricing and availability in the Catalog and Vending Managers.

■ The Glossary defines the terms used in the context of this guide.

Typographic Conventions

The following tables define the typographical conventions and terms used throughout this guide:

Typeface

AaBbCc123 The names of commands, files,

AaBbCc123

AaBbCc123 Book titles, new words or terms,

a The settings on your browser might differ from these settings.

xvi Administrator Guide • 2005Q4

Meaning Examples

Edit your .login file. and directories; on-screen computer output

What you type, when contrasted with on-screen computer output

words to be emphasized

Command-line variable; replace with a real name or value

Use ls -a to list all files.

% You have mail.

% su

Password:

Read Chapter 6 in the User’s Guide.

These are called class options.

Yo u must be super user to do this.

To delete a file, type rm filename.

Introduction

This chapter provides an overview of the Sun Java™ System Content Delivery Server. It describes the content lifecycle and provides an overview of the Catalog Manager, Fulfillment Manager, and Vending Manager components. It describes the automatic content validation process that takes place when content is submitted to the Content Delivery Server.

This chapter also describes how to log in to the Catalog Manager and Vending Manager administration components.

Sun Java System Content Delivery Server

The Sun Java System Content Delivery Server is a high-performance software solution that lets operators manage the complexity of delivering virtually any type of wireless content over-the-air (OTA) to their subscribers. The Content Delivery Server separates content aggregation, presentation, and delivery into two distinct managers, the Catalog Manager and the Vending Manager. With these managers, operators can centrally manage content, customize multiple subscriber interfaces, and provide fast downloads.

The following figure provides a high-level overview of the Content Delivery Server.

Content

Providers

Java Applications Ringtones Wallpapers

GamesMusic Videos Extensible...

Operator

Subscriber

Java System Content Delivery Server

Catalog Manager

Vending Manager

Subscriber

Portal

Fulfillment

Manager

Vending Manager

Subscriber

Portal

Fulfillment

Manager

Vending Manager

Subscriber

Portal

Fulfillment

Manager

1. The content provider creates an application and submits it to the Catalog Manager using the web-based Developer Portal.

2. The Catalog Manager validates the content.

2 Administrator Guide • 2005Q4

3. The Catalog Manager administrator publishes the content, making it available to the Vending Manager.

4. The Vending Manager administrator selects content published from the Catalog Manager and stocks the content, making it available to subscribers.

Catalog Manager

The Catalog Manager is the content aggregator or warehouse. It manages all the content coming from the developer community. After the content is authorized, the Catalog Manager makes the content available to the Vending Managers. The Vending Managers then sell the content to their unique subscriber community.

The Catalog Manager supports any type of content. The Catalog Manager administrators define the type of content that they want to accept for their enterprise.

The Catalog Manager administrator manages these functions:

■ Submitted and published content

■ Supported mobile devices

■ Content provider access and pricing

■ Vending Manager access and content

■ Administrator access

The following figure provides a high-level overview of the role of the Catalog Manager in the lifecycle of an application. It also illustrates the Catalog Manager processes.

Chapter 1 Introduction 3

1. Developers submit content to the Catalog Manager. The Catalog Manager runs an automated validation process on the content to ensure there is no malicious content and that the content matches the supported devices.

2. The content goes to the Submitted Content section of the Catalog Manager for review by the administrator. The administrator reviews the content and, if required, edits the content and modifies the pricing and category assignments. The administrator can accept or reject the content.

3. The Catalog Manager publishes the content, which makes it available to the Vending Manager.

Catalog Manager Processes

As shown in the previous figure, the Catalog Manager manages content submitted by developers and controls which Vending Managers access which content. The Catalog Manager is responsible for the following functions:

■ Automated Content Validation

■ Content Management

■ Device Management

■ Account Management

■ Plan Management

4 Administrator Guide • 2005Q4

Automated Content Validation

The Sun Java System Content Delivery Server performs an automated validation of content. If an application fails at any stage of validation, it is not submitted to the Catalog Manager.

Note – The default implementation of content validation performs automated

validation on MIDlets only. You can customize the validation process to validate other types of content.

Content validation includes the following tasks:

■ API Filtering. The API Filter checks that the APIs used in the MIDlet application

are allowed. Developer Plans define the set of APIs allowed. When a developer submits content, the API Filter checks the APIs used by the submitted application. If any API is not allowed by the Developer Plans associated with the developer, the content fails.

■ Instrumentation. The instrumentation process inserts code into the MIDlet

application to interpret the pricing model assigned. For example, the inserted code interprets whether the application is priced per download, on first download only, by subscription, or any combination of these.

The instrumented code maintains licensing information on the device and periodically communicates with the Sun Java System Content Delivery Server to verify that the subscriber is authorized to run the application. If a license has expired, the subscriber is given the opportunity to renew the license.

■ Customized Steps. You can customize the validation process to meet the needs of

your organization. You can disable selected processes or add processes as needed. For example, you might want to add a step to obfuscate an application. Obfuscation makes the code difficult to understand when it is decompiled and can reduce the size of the Java Archive (JAR) file.

Content Management

Once content passes the automated validation process, it goes to the submitted content section for review by the Catalog Manager administrator. This section describes the content and categories managed by the Catalog Manager:

Chapter 1 Introduction 5

■ Submitted Content. The administrator reviews submitted content and, if

required, edits the content and modifies the pricing and category assignments. The administrator can accept or reject the content.

■ Published Content. After accepting the content, the administrator publishes the

content to make it available to the Vending Manager.

■ Categories. Content categories are central to content management. They are

logical containers or buckets that hold the content managed by the Sun Java System Content Delivery Server. The Catalog Manager uses content categories to control Vending Manager access.

See “Managing Content” on page 13 for more information.

Device Management

The Catalog Manager defines the devices and the device capabilities supported by the Content Delivery Server. As a Catalog Manager administrator, you can add new devices, delete devices no longer supported, and edit the characteristics and capabilities of any device model. “Managing Devices” on page 68 describes how to manage the devices supported for your network.

Account Management

Accounts define access to the Catalog Manager. The Catalog Manager has three types of accounts:

■ Vending Manager. A Vending Manager Account is for a specifically-branded

Vending Manager that stocks content from the Catalog Manager. It is associated with one or more Vending Plans.

■ Developer. Developer Accounts are for corporations or individuals that submit

content to the Catalog Manager. Developer Accounts are associated with one or more Developer Plans.

■ Administrator. Administrator Accounts are for individuals who administer the

Catalog Manager.

See “Managing Accounts” on page 94 for more information.

Plan Management

The Catalog Manager uses the following plans to control content submission for developers and content access for Vending Managers:

6 Administrator Guide • 2005Q4

■ Vending Plans. Vending Plans define the categories that a Vending Manager can

access. Vending Plans can contain a nested hierarchy of other Vending Plans. Each Vending Manager Account is associated with one or more Vending Plans.

■ Developer Plans. Developer Plans define the set of APIs that developers can use

in applications that they submit. Profiles define the classes in a specific library that developers can use. A Developer Plan contains one or more Profiles.

See “Managing Plans” on page 107 for more information.

Fulfillment Manager

The Fulfillment Manager controls and delivers content to subscribers through a high-performance and cost-effective download architecture. The following figure provides a high-level overview of the Fulfillment Manager processes.

No administration tasks are associated with the Fulfillment Manager.

Vending Manager

The Vending Manager handles selling and pricing content. Vending Managers are generally configured to serve separate enterprises. A single Catalog Manager can serve multiple Vending Managers.

The Vending Manager manages content published by the Catalog Manager. Content stocked on the Vending Manager is available for subscribers to download.The Vending Manager also controls subscriber access and purchase pricing, and provides daily statistical reports on the Content Delivery Server.

Chapter 1 Introduction 7

The Vending Manager administrator manages the following functions:

■ Stocked content

■ Subscriber access and subscriber licenses

■ Purchase pricing and trial periods

■ Administrator access

■ Statistical reports

In addition to the Vending Manager administrator, the Content Delivery Server can have Vending Manager Customer Care Agents. Customer Care Agents have limited administrator privileges. A Customer Care Agent manages the following functions:

■ Subscriber access and subscriber licenses

■ Statistical reports

The following figure provides a high-level overview of the role of the Vending Manager in the lifecycle of an application. It also illustrates the Vending Manager processes.

1. The Catalog Manager publishes content and makes it available to the Vending

Manager.

2. The Vending Manager administrator accesses the content published by the

Catalog Manager. The administrator can change the subscriber pricing of the content, assign it to a new category, and change the properties of the content.

3. The Vending Manager administrator stocks the content and makes it available to

the subscriber. The administrator uses Subscriber Plans to define the content categories that subscribers can access.

8 Administrator Guide • 2005Q4

Vending Manager Processes

The previous figure illustrates the Vending Manager processes. The Vending Manager is responsible for the following practices:

■ Content Management

■ Plan Management

■ Account Management

■ Reporting