Sun Microsystems Sun Java System Content Delivery Server 5 - Manual (Page 126)

108 Administrator Guide • 2005Q4
Managing Plans
Vending Manager and Developer accounts are assigned to plans. The Catalog
Manager uses plans to control content submission for developers and content access
for Vending Managers.
TABLE 2-14 describes the two types of plans used by the
Catalog Manager.
The following device management tasks are described in this section:
■ Managing Vending Plans
■ Managing Developer Plans
When an operation is performed (editing, deleting, adding, and so on), the Content
Deliver Server puts a background job notification in the main menu bar. You can
click on the notice to see details of jobs that were or are running. See
“Getting Job
Status” on page 126 for more information.
Managing Vending Plans
The Vending Manager handles the selling of content. Since a single Catalog Manager
can serve multiple Vending Managers, you can potentially have many Vending
plans. A Vending Manager can be assigned to more than one Vending plan, so
ensure your Vending plans are limited enough to give you the control you need.
▼ Viewing Vending Plans
1. From the Catalog Manager, click Plans in the main menu bar.
The Vending Plan Management page displays a list of the Vending plans.
TABLE 2-14 Plan Types
Plan Type Description
Vending Vending plans define content access rights. For example, if you have
a Vending Manager branded to sell content to teenagers, you don’t
want it stocking adult content. When creating a Vending plan you
can define which categories a Vending Manager can access. Vending
plans can also be nested within other Vending plans. Each Vending
Manager account is associated with one or more Vending plans.
Developer 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.