System capabilities - Capabilities primarily used by the Content Delivery Server. They define capabilities that a device must have to perform Content Delivery Server functionality. For instance, system capabilities define whether a device supports Short Message Service (SMS) or Wireless Application Protocol (WAP) Push.

Mandatory capabilities - Capabilities that must be defined for a device to accept MIDlet applications.

Content Delivery Server-specific capabilities - Non-industry standard capabilities that are specific to the server’s functionality. For example, the Supported Libraries capability enables you to set the libraries that the device supports. Libraries define the API sets that are supported. The Supported Libraries capability enables the Content Delivery Server to match an application to a device that supports the libraries used by the MIDlet.

User interface and software capabilities - Capabilities that specify the characteristics of the device. The Content Delivery Server uses these capabilities to refine the capability matching process.

To determine which devices can access the submitted content, the Content Delivery Server performs a capability match comparing the capabilities of the devices defined in the Catalog Manager with the capabilities required by the content submitted by the developer. Only subscribers with devices capabilities that match the capabilities required by the content can access the content.

Define the devices that you want to support before you make the Content Delivery Server available to developers and subscribers.

The following device management tasks are described in this section:

Managing Device Libraries

Managing Content Descriptor Templates

Managing Device Definitions

Managing Server Locales

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 in this session. See “Getting Job Status” on page 126 for more information.

Managing Device Libraries

Device libraries identify the APIs that are supported by a device. Libraries are also used in Developer Profiles to define the set of APIs that developers can use in the applications that they submit. See “Managing Developer Plans” on page 114 for information on plans and profiles.

70 Administrator Guide • 2005Q4

Page 88
Image 88
Sun Microsystems 5 manual Managing Device Libraries