C H A P T E R 1

Introduction

The Content Delivery Server is a software solution that helps you manage and deliver applications and static content over-the-air (OTA) to your subscribers. Due to the flexibility of the architecture, you do not need to change the way that you do business to accommodate a proprietary solution. You can configure the Content Delivery Server to work within your existing infrastructure.

Adapters are used in the following areas to integrate the Content Delivery Server with your setup.

Billing. Billing adapters convert the information provided by the Content Delivery Server to the format needed by your billing system.

Subscriber data. Subscriber adapters map external subscriber data to the data required by the Content Delivery Server when processing subscriber-related functions.

WAP gateway. Wireless application protocol (WAP) gateway adapters parse the HTTP header from a WAP gateway to retrieve the MSISDN number, device profile, and other attributes needed by the Content Delivery Server.

Push delivery. Push adapters serve as the interface between the Content Delivery Server and your push implementation.

Content validation. Content validation adapters perform any preprocessing of submitted content that is required before the content is accepted by the Content Delivery Server.

You can also write customized adapters using the Content Delivery Server APIs if none of the adapters provided meets your needs. The APIs are described in the Sun Java System Content Delivery Server Customization Guide.

In addition to the adapters used to integrate the Content Delivery Server with existing external systems, the following features enable you to integrate the Content Delivery Server with existing processes:

The device-specific user interface framework enables you to tailor the pages of the Subscriber Portal to suit the capabilities of the device on which it is viewed. This framework helps to ensure the best possible experience for your subscribers.

Content validation workflows enable you to customize the process for accepting content that is submitted to the Content Delivery Server. You can create different workflows for specific types of content. You can use content validation adapters provided with the Content Delivery Server or write your own adapters to perform such functions as verifying the content or adding code for digital rights management.

Integration with a digital rights management (DRM) server enables content to be protected from unauthorized distribution and use based on the Open Mobile Alliance (OMA) DRM 1.0 guidelines.