This chapter describes the device capabilities that you can specify for the devices that you use with Content Delivery Server. See “Managing Devices” in the Catalog Manager online help for information on how to specify device capabilities.
Descriptions of the Capabilities
Device capabilities are defined in the following categories:
See Specifying a Capability Value for more information.
System Capabilities
System capabilities are primarily used by 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 WAP Push.
Push Type takes a string value that specifies the device’s delivery mechanisms: mms, sms, or wap.
Mandatory Capabilities
Mandatory capabilities are capabilities that must be specified for a device to accept MIDlet applications. TABLE 8-1 lists the mandatory capabilities for devices used with Content Delivery Server.
TABLE 8-1 Mandatory Capabilities
|
Name
|
Type
|
Description
|
Example Value
|
|
MicroEdition-Configuration
|
String
|
Software Platform specific: Connected Limited Device Configuration (CLDC) version.
|
CLDC-1.0
|
|
MicroEdition-Profile
|
String
|
Software Platform specific: Mobile Information Device Profile (MIDP) version
|
MIDP-1.0
|
Content Delivery Server-Specific Capabilities
Content Delivery Server-specific capabilities apply to the server’s functionality and are not industry standard. Devices must have Content Delivery Server-specific capabilities listed in TABLE 8-2 if they are to be used with the server.
TABLE 8-2 Content Delivery Server-Specific Capabilities
|
Name
|
Type
|
Description
|
Example Value
|
|
Supported Libraries
|
List
|
System capability for API validation.
Enables you to set the libraries that the device supports. Libraries define the API sets supported. This capability enables the Content Delivery Server to match an application to a device that supports the libraries used by the application.
|
MIDP-1.0
|
|
Descriptor Template
|
List
|
System capability for two-step download of content.
The template specified is used to generate the descriptor file for content other than MIDlets, if two-step download is specified. If this option is not selected, content is delivered as either OTA one-step or as an SMS message.
|
General Content Descriptor
|
Browser Capabilities
Browser capability refers to the browser type specified for a device. A string value specifying the browser that is rendering markup on the device is given. For example, Browser Type can have one of the following values:
- WML-1_2
- XHTML-NokiaSeries40
- XHTML-Symbian
- XHTML-UP
User Interface and Software Capabilities
Content Delivery Server uses the user interface and software capabilities to refine the capability matching process.
TABLE 8-3 lists the user interface and software capabilities.
TABLE 8-3 User Interface and Software Capabilities
|
Name
|
Type
|
Description
|
Example Value
|
|
Bits Per Pixel
|
Integer
|
Hardware platform-specific: Bits Per Pixel
Defines the minimum number of bits per pixel that a device must have to run the application.
|
16
|
|
Ccpp Accept String
|
List
|
Software platform-specific: List of MIME types that the device supports for OTA download.
|
application/java-archive
text/plain
image/gif
|
|
Ccpp Accept Language
|
List
|
Software platform-specific: Locale
Defines the locale supported by the device. Select one or more entries from the list.
|
en_US
|
|
Color Capable
|
Boolean
|
Hardware platform-specific: Color Capable
Defines whether or not the device has a color screen.
|
Yes or No
|
|
Confirm Capable
|
Boolean
|
Software platform-specific: Confirm Capable
Defines whether or not the device sends a confirmation (MIDlet-Install-Notify) after a MIDlet is installed.
|
Yes or No
|
|
Delivery Type
|
List
|
Software platform-specific: Delivery Type
Defines the content delivery mechanism the device supports.
|
OTA
NSM
EMS
|
|
Image Capable
|
Boolean
|
Hardware platform-specific: Image Capable
Defines whether or not the device supports images.
|
Yes or No
|
|
Input CharSet
|
List
|
Hardware platform-specific: Input CharSet
Defines the list of character sets that the device can accept.
|
US-ASCII
ISO-8859-1
|
|
Maximum Application Size
|
Integer
|
The maximum size of an application, in bytes, that can be supported by the device.
|
30000
|
|
Maximum Content Size
|
Integer
|
The maximum size of content (non-MIDlet), in bytes, that can be supported by the device.
|
30000
|
|
Number of softkeys
|
Integer
|
Software platform-specific: Defines the number of soft keys the device requires.
|
2
|
|
Output CharSet
|
List
|
Hardware platform-specific: Defines the list of character sets supported by the device for output to the display.
|
US-ASCII
ISO-8859-1
|
|
Screen Height
|
Integer
|
Hardware platform-specific: The size of the device’s screen height in units of pixels.
|
128
|
|
Screen Width
|
Integer
|
Hardware platform-specific: The size of the device’s screen width in units of pixels.
|
128
|
Specifying a Capability Value
Depending on the capability, you can specify the value as a List, Integer, or Boolean.
List
A list value can contain one or more values. To select multiple values from the list provided, hold the Control key while clicking each item that you want to include. Each value is shown on a separate line when the items are displayed as a string. For example, Supported Libraries takes a list value that can be either DOJA-1.0, MIDP-1.0, or MIDP-2.0.
Integer
An integer value is a numeric value. The integer must be a whole number. The value does not support decimal points. For example, Number of Softkeys takes an integer value, such as 2.
Boolean
A valid Boolean value for a device capability is either yes or no. For example, Image Capable can take a Boolean value of Yes.
| Sun Java System Content Delivery Server Reference Manual
|
820-1946-10
|
   
|
Copyright © 2008, Sun Microsystems, Inc. All Rights Reserved.