| Administration Guide |     |
| Administration Guide | |
|
Glossary |
This glossary defines the terms and acronyms used in the context of this guide.
The individuals who have access to the Sun Java System Content Delivery Server. Four types of accounts are available: Developer Accounts, Vending Manager Accounts, Subscriber Accounts, and Administrator Accounts.
Stocked content that is available to the Vending Manager and to subscribers. The Vending Manager administrator can change the status of content that is active.
Person responsible for administration of the Catalog Manager or Vending Manager component of the Content Delivery Server.
Accounts for individuals who administer the Catalog Manager or the Vending Manager. Administrator Accounts can be disabled when you no longer want an individual accessing the Catalog Manager or the Vending Manager.
Executable content submitted to the Content Delivery Server.
A billing type, either prepaid or postpaid, in the billing system supported by the Content Delivery Server.
In the prepaid billing model, the billing system is contacted for authorization before a subscriber is permitted to purchase and download content. For postpaid billing models, the billing system receives purchase information after the transaction occurs. See Pricing Model.
A collection of related files (for example, an application and any associated audio, video, or image files). Bundled content is created and managed by the Vending Manager.
A collection of attributes for promoting or selling content. The Vending Manager can create marketing campaigns.
A sequence of characters and numbers used to identify a campaign. With a coupon, a subscriber can purchase content that has been promoted or discounted for a specific campaign.
Criteria that the Catalog Manager uses to define the devices that can download specific content. Capabilities are defined in the following categories: Mandatory Capabilities, System Capabilities, Content Delivery Server-Specific Capabilities, and User Interface and Software Capabilities.
The content aggregator or warehouse. The Catalog Manager manages all the content submitted by the developer community and publishes the content to the Vending Managers.
Purchase Price of content set by the Catalog Manager administrator. See Content Provider Price and Vending Price.
A logical container or bucket that holds individual Applications, Ring Tones or Pictures. Content categories are central to content management. Categories in the Catalog Manager control access to the content by Vending Managers. Categories in the Vending Manager control access to the content by Subscribers.
Connected Limited Device Configuration (CLDC)
A part of the Java 2 Platform, Micro Edition platform. CLDC is the foundation of the Java runtime environment targeting small, resource-constrained devices, such as mobile phones, mainstream personal digital assistants, and small retail payment terminals.
Combined with a device-specific Java class library, such as the Mobile Information Device Profile (MIDP), CLDC provides a complete runtime environment for small resource-constrained devices.
The applications, ring tones, and pictures that are submitted by developers and eventually downloaded by subscribers.
A high performance software solution that allows operators to manage the complexity of delivering wireless Java applications over-the-air (OTA) to their subscribers. The Sun Java System Content Delivery Server separates content aggregation, presentation, and delivery into separate Managers--Catalog Manager, Fulfillment Manager, and Vending Manager. This enables an operator to centrally manage content, customize multiple subscriber interfaces, and ensure fast downloads.
Content Delivery Server-Specific Capabilities
The server's functionalities, which are not industry standard.
A description of content other than MIDlets (such as Ring Tones, Pictures, and Symbian applications) similar to the way a JAD File describes a MIDlet.
The individual or corporation who submits content to the Catalog Manager.
Purchase price of content set or selected by the content provider. The content provider price can be overridden by the Catalog Manager administrator. See Catalog Price and Vending Price.
A definition of corporations or individuals that submit content to the Catalog Manager. Developer Accounts are associated with one or more Developer Plans.
A definition of the set of APIs that developers can use in applications that they submit. A Profile defines the classes in a specific library that developers can use. A Developer Plan contains one or more Profiles.
A mobile device model supported by the Catalog Manager.
See Content Descriptor Template.
Alternate versions of an application, picture, or ring tone that run on devices with different capabilities.
Digital Rights Management (DRM)
Usage protection of content. Rights protection can be delivered separately from content or with content.
The Fulfillment Manager provides a dedicated, high-performance, scalable solution for delivering OTA content to subscribers.
Initial currency and initial price equivalents as set in the configuration properties file by the System Administrator. At deployment time, the system administrator can set the purchase prices (monetary values) in the Vending Manager. After deployment, the Vending Manager administrator can change the purchase prices as needed.
Stocked content that is available to the Vending Manager but not available to subscribers. The Vending Manager administrator can change the status of content that is inactive.
A Java Application Descriptor (JAD) file describes a MIDlet and its associated JAR File.
A Java ARchive (JAR) file contains the class, image, and sound files for a MIDlet gathered into a single file and compressed for faster downloading to your device. By putting the MIDlet components in a single file and compressing that file, download time is saved.
An API set that a device model supports.
A geographic or political region or community that shares the same language, customs, or cultural convention. In software, a locale is a collection of files, data, and code, which contains the information necessary to adapt software to a specific geographical location.
Required capabilities for a device to accept MIDlet applications.
A MIDlet is a Java technology-based application written for MIDP. MIDlet applications are subclasses of the javax.microedition.midlet.MIDlet class that is defined by the MIDP specification.
Mobile Information Device Profile (MIDP)
A set of Java technology-based APIs that, together with the Connected Limited Device Configuration (CLDC), provides a complete Java 2 Platform, Micro Edition (J2METM platform) software application runtime environment targeted at mobile information devices, such as mobile phones and entry level PDAs. The MIDP specification addresses issues such as user interface, persistent storage, networking, and application life cycle.
A technique used to protect source code. Obfuscation makes code more difficult to understand when it is decompiled, but it has no affect on the functionality of the code. In addition, obfuscation makes the JAR file as small as possible, enabling devices with smaller memories to support large JAR files.
A standard for the transmission and reception of application-related information in a wireless communications system.
Background images against which menus, icons, and other elements are displayed. Also a type of content supported by the Content Delivery Server.
A plan defines content access rights. Plans can also be nested within other Plans. Three types of plans are available: Vending Plans, Developer Plans, and Subscriber Plan.
Controls that enable the Catalog Manager administrator to select the list of available pricing models that can be applied to the selected content type by either a content provider or a Catalog Manager.
Condition of purchase associated with content. Supported pricing models are: free always, first download only, every download, trial, per use, per period, per subscription, and per interval.
Pricing characteristics of content that is presented to the subscriber at purchase time. The pricing option consists of the following elements: Pricing Option ID, Pricing Option Name, Pricing Model, and Purchase Price.
The Pricing Option ID is a unique identifier for the pricing option. The Pricing Option Name is an external pricing option name used by external systems to identify the content items.
A Profile defines a set of APIs that a developer can use in applications submitted to the Content Delivery Server. See also Developer Plans.
A monetary value assigned to an item of content. The currency type as seen by subscribers is determined by individual Vending Managers. The monetary value is initially assigned by the Catalog Manager administrator in the local currency of that administrator.
Record Management System (RMS)
A simple record-oriented database that allows a MIDlet to persistently store information and retrieve it later. Different MIDlets can also use the RMS to share data.
A content type that is supported by the Content Delivery Server. Also, the sound heard by someone receiving a call.
A service for sending messages of up to 160 characters (224 characters if using a 5-bit mode) to mobile phones that use Global System for Mobile (GSM) communication.
Content that is stocked on a Vending Manager and is available to subscribers for download.
An individual who downloads content from the Vending Manager.
An account that defines an individual who subscribes to a service plan that provides them with the download service. Subscriber Accounts are associated with one or more Subscriber Plan.
A plan that determines the content that a subscriber can access and download. Subscriber Accounts are assigned to Subscriber Plans. 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.
Content supported in one Subscriber Plan can be included in another Subscriber Plan by nesting plans. This allows you to create a hierarchy of Subscriber Plans.
Person responsible for installation, configuration, deployment, and performance of the Content Delivery Server.
System capabilities are primarily used by the Content Delivery Server. They define capabilities that a device must have in order to perform Content Delivery Server functionality. For instance, system capabilities define whether a device supports SMS or WAP Push.
Content currently undergoing or requiring testing prior to being published. The status of Testing is assigned by the Catalog Manager administrator. Testing content is available to Vending Managers for distribution only to subscribers with testing roles (assigned by the Vending Manager).
Stocked content on the Vending Manager that is unpublished by the Catalog Manager. Unavailable content is not available to the Vending Manager or to subscribers. The Vending Manager administrator cannot change the status of content that is unavailable. The Vending Manager administrator can only unstock it.
Published content received from the Catalog Manager that is not currently stocked in the Vending Manager. Unstocked content is available in the Vending Manager catalog. The Vending Manager administrator can stock published content received from the Catalog Manager and unstock content with stocked status in the Vending Manager.
Stocked content whose catalog property information has changed.
A unique identifier for a mobile device model. The user-agent is a regular expression that usually contains hardware, browser, and model information about the device.
User Interface and Software Capabilities
The Content Delivery Server uses the user interface and software capabilities to refine the capability matching process.
The Vending Manager manages content published by the Catalog Manager. The Vending Manager controls subscriber access and purchase pricing and provides daily statistical reports on the Content Delivery Server.
Vending Managers are generally configured to serve separate enterprises and a single Catalog Manager can serve multiple Vending Managers.
A Vending Manager account is for a specifically branded vending manager that stocks content from the Catalog Manager. It is associated with one or more Vending Plans.
Vending Plans define content access rights. When creating a Vending Plan, you can define the categories that a Vending Manager can access. Vending Plans can also be nested within other Vending Plans.
Monetary value set in the local currency for content set by a Vending Manager administrator. Also known as retail price. See Catalog Price and Content Provider Price.
Wireless Application Protocol (WAP)
A specification for a set of communication protocols to standardize the way that wireless devices, such as cellular telephones and radio transceivers, can be used for Internet access, including e-mail, the World Wide Web, unscrupulous, and Internet Relay Chat (IRC).
| Administration Guide | 819-3209-10 | |
Copyright © 2005, Sun Microsystems, Inc. All Rights Reserved.