| Sun Java System Content Delivery Server Reference Manual |    
|
| C H A P T E R 1 |
|
Overview |
This chapter provides an overview of the Sun Java
System Content Delivery Server. The Content Delivery Server provides a system for acquiring content from content providers, managing and protecting that content, delivering it to subscribers, and charging for its use. It is a flexible system that enables you to define the devices and the types of content that you want to support.
This chapter includes the following topics:
The component-based architecture of the Content Delivery Server separates content aggregation, presentation, and delivery. The flexibility of this architecture enables you to centrally manage content, customize multiple subscriber interfaces, and provide fast downloads. Integration with existing systems such as billing or a Short Message Service Center (SMSC) is managed with either adapters provided with the Content Delivery Server or adapters that you write yourself using the Content Delivery Server APIs.
The overall system provides end-to-end connectivity between content providers and subscribers. FIGURE 1-1 provides a high-level overview of the path content takes through the Content Delivery Server.
The following steps describe the flow of content:
1. The content provider creates some type of content, such as a Java technology-based application (Java application), and submits it to the Catalog Manager using the Developer Portal.
2. The Catalog Manager automatically validates the content and accepts the content from the developer if it passed the validation.
3. The Catalog Manager administrator publishes the content to make the content available to one or more Vending Managers.
4. The Vending Manager administrator stocks content published by the Catalog Manager to make the content available to subscribers.
5. Subscribers review and download available content using either the PC-based or device-based Subscriber Portal.
The Content Delivery Server architecture is organized such that the Catalog Manager must approve all content submitted by content providers. The Vending Manager has an automated stocking option that enables the Vending Manager to take all content published to it by the Catalog Manager and stock the content on the subscriber site. This option can be disabled to allow Vending Manager administrators to manually select the content to stock for their subscribers.
FIGURE 1-2 illustrates the functional architecture of the Content Delivery Server.
FIGURE 1-2 Functional Architecture
The Content Delivery Server architecture is highly scalable. Additional instances of the components can be added as your subscriber base grows. The Content Delivery Server includes the following functional components:
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:
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.
FIGURE 1-3 Catalog Manager Process
1. Developers submit content to the Catalog Manager. The Catalog Manager runs an automated validation process on the content to ensure that it is not malicious and that it 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.
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.
The Vending Manager administrator manages the following functions:
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:
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.
FIGURE 1-4 Vending Manager Process
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.
The Fulfillment Manager controls and delivers content to subscribers. For better performance, content is cached locally in the Fulfillment Manager. If the version in the database is the same as the local version, subsequent download requests are filled using the local copy. The Fulfillment Manager also manages the digital rights for content. When an instrumented application is started, it contacts the Fulfillment Manager to verify that the subscriber is authorized to continue using the application.
FIGURE 1-5 Fulfillment Manager Architecture
The Content Delivery Server includes the following services that perform specialized functions for the Content Delivery Server:
The database is used for the following purposes:
The Catalog Manager and each Vending Manager has its own database. If desired, the Catalog Manager and Vending Manager can share the same database server. Each Event Service shares the database of the Vending Manager with which it is deployed. If the Event Service is deployed with only a Catalog Manager, the service shares the database of the Catalog Manager.
Administer the Catalog Manager using the Catalog Manager administration console. You administer the Vending Manager using the Vending Manager administration console. These consoles are accessed through a web browser.
Developers can submit content to Content Delivery Server using the Developer Portal. Subscribers can download content from the Content Delivery Server using the Subscriber Portal from either a PC or a mobile device.
To access the Catalog Manager and Vending Manager administration consoles for the first time, use the default login ID and password that were created when you installed Content Delivery Server. The default values for the Login ID and Password for both consoles are admin and admin.
Change the password after you initially log in (note that the password is case sensitive). After you log in to the Catalog Manager and Vending Manager, you can add additional accounts as needed.
See “Adding Catalog Manager Administrator Accounts” in the Catalog Manager online help and “Adding Vending Manager Administrator Accounts” in the Vending Manager online help for more information.
FIGURE 1-6 illustrates the different types of users who use the Content Delivery Server. Developers submit content to the Catalog Manager through the Developer Portal. Catalog Manager administrators publish accepted content to one or more Vending Managers. Vending Manager administrators stock selected content to make the content available to subscribers. Subscribers choose from the content offered through the Subscriber Portal.
FIGURE 1-6 User Roles in the Content Delivery Server
One deployment scenario consists of a publisher acting as Catalog Manager administrator, accepting and rejecting content from content providers. Each Vending Manager, perhaps representing different carriers, has a Vending Manager administrator who chooses the content to make available to subscribers.
If the Catalog Manager and the Vending Manager share a single administrator, auto-stocking can be enabled in the Vending Manager administration console. Auto-stocking automatically stocks all Catalog Manager-approved content that is available to the Vending Manager.
| Sun Java System Content Delivery Server Reference Manual | 820-1946-10 |
|
Copyright © 2008, Sun Microsystems, Inc. All Rights Reserved.