|C H A P T E R 2|
Catalog and Vending Managers
This chapter describes the processes of the Catalog and Vending Managers use to manage content, devices, accounts, and plans. The synchronization between the Catalog Manager and Vending Managers is also described.
This chapter includes the following topics:
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:
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:
The instrumented code maintains licensing information on the device and periodically communicates with Content Delivery Server to verify that the subscriber is authorized to run the application. If a license is expired, the subscriber is given the opportunity to renew the license.
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:
See “Managing Content” in the Catalog Manager online help for more information.
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” in the Catalog Manager online help describes how to manage the devices supported for your network.
Accounts define access to the Catalog Manager. The Catalog Manager has three types of accounts:
See “Managing Accounts” in the Catalog Manager online help for more information.
The Catalog Manager uses vending plans to define content access rights to Vending Manager administrators. Specific content categories can be defined per plan and each Vending Manager server accounts can be associated with one or multiple vending plans.
Developer plans define the API set that content providers can use in the content they submit to the Catalog Manager. Each developer plan includes one or more profiles that specifies the libraries used for content development.
The previous figure illustrates the Vending Manager processes. The Vending Manager is responsible for the following practices:
The Catalog Manager publishes content to the Vending Manager. The Vending Manager is responsible for stocking this content to make it available to the subscriber. The Vending Manager administrator can change the subscriber pricing of the content, allow trial usage, and assign the content to a new category. The administrator can also change the category assignments and add new categories to control subscriber access to content.
See “Setting Up Content” in the Vending Manager online help for more information.
Accounts define access to the Vending Manager. The Vending Manager is responsible for two types of accounts:
See “Managing Subscriber Accounts” in the Vending Manager online help for more information.
See “Managing Vending Manager Accounts” in the Vending Manager online help for more information.
The Vending Manager uses Subscriber Plans to control subscriber access to content. Each Subscriber Account is assigned to one or more Subscriber Plans. Subscriber Plans determine what content a subscriber can access and download.
A Subscriber Plan is mapped to selected categories in the Vending Manager. The content in the selected categories is made available to plan members. If content is in a category that is not supported by the Subscriber Plan, the subscriber cannot access it for download.
See “Managing Subscriber Plans” in the Vending Manager online help for more information.
The Vending Manager provides daily statistical reports that enable you to view and track application download information and usage statistics downloads. See “Viewing Reports” in the Vending Manager online help for more information.
The Catalog Manager and each Vending Manager has its own database. Information such as the status of content or the types of devices supported must be maintained across databases. The Catalog Manager database is considered the master and Vending Manager databases are synchronized with Catalog Manager database.
As changes are made in the Catalog Manager, notifications are sent to the Vending Managers identified by the Vending Manager Server accounts. A Vending Manager synchronizes with the Catalog Manager in the following situations:
The Catalog Manager must be able to communicate with the Vending Manager. If the Vending Manager is down, the Catalog Manager holds the notifications until the Vending Manager is brought back up. The Catalog Manager then sends any pending notifications.
If a Vending Manager Server account is deleted or inactivated, the Catalog Manager stops sending notifications of changes to that Vending Manager. If the Vending Manager Server account is later recreated or reactivated, the Vending Manager must be restarted to initiate synchronization. Content that was published by the Catalog Manager while the Vending Manager was inactive must be manually stocked by the Vending Manager administrator.
When the Vending Manager receives a notification of change from the Catalog Manager, the Vending Manager attempts to synchronize with the Catalog Manager. If synchronization fails, the Vending Manager retries the operation. The number of times and how often the operation is retried is based on properties in the $CDS_HOME/deployment/deployment-name/conf/RemoteVending.properties file. See Section 1.3, “Configuring Synchronization,” in the Sun Java System Content Delivery Server Integration and Configuration Guide for information on these properties.
Notifications of change from the Catalog Manager are expected to be processed in the order in which they are issued. This requires that there be only one instance of the Catalog Manager that issues notifications. Multiple instances of the Catalog Manager that use the same Catalog Manager database is not a supported configuration.
However, multiple instances of a Vending Manager that use the same Vending Manager database is a supported configuration as long as only one instance listens for and processes the notifications. Updates to the database by that instance of the Vending Manager are available to all other instances.