Release NotesSun Java™ System
|
[Skip TOC]
The Sun Java™ System Content Delivery Server provides a system for acquiring content from content providers, managing and protecting that content, delivering it to subscribers, and charging for its use. The Sun Java System Content Delivery Server is a flexible system that enables you to define the devices and the types of content that you want to support. Integration with existing systems such as a billing system or a subscriber database is managed with either adapters provided with the Content Delivery Server or adapters that you write yourself using the Content Delivery Server APIs.
The component-based architecture of the Content Delivery Server separates content aggregation, presentation, and delivery. The flexibility of this architecture enables you to centrally manage content, customize multiple subscriber interfaces, and provide fast downloads. The overall system provides end-to-end connectivity between content providers and subscribers.
[Top]
This release of the Sun Java System Content Delivery Server includes new features and improvements in the following areas of the product:
The following features are included in this release:
The following features are included in this release:
The following features are included in this release:
The following features are included in this release:
The following features are included in this release:
The following features are included in this release:
The following features are included in this release:
[Top]
System requirements are described in Section 2.1, "Verify Prerequisites," of the Installation Guide. Documentation is available in the $CDS_HOME/Documentation directory after you extract the contents of the product Zip file.
[Top]
The product CD or Zip file that you received contains the following files and directories:
Unzip the Sun_Java_System_CDS_5.0_2005Q4.zip file into the directory of your choice using the following command:
unzip Sun_Java_System_CDS_5.0_2005Q4.zip -d cds-home
cds-home is the directory used as the home directory for the product. After the files are extracted, this directory contains the files and directories for the Sun Java System Content Delivery Server, including the Documentation directory that contains the documentation for the product.
[Top]
See the Installation Guide for instructions on installing the Sun Java System Content Delivery Server. This guide is available in the $CDS_HOME/Documentation directory after you extract the contents of the product Zip file.
[Top]
This section covers the following topics:
This section describes updates to the documentation found in the $CDS_HOME/Documentation directory after you extract the contents of the distribution file.
In the Vending Manager chapter, Step 3 in the section "Viewing Published Content" explains what types of content sorting are available. Sorting by status is no longer available from the Catalog tab.
[Top]
The Descriptor Text in Table 3 in the section, "Creating the XML File for the Content Aggregator Interface," shows an incorrect tag name and incorrect syntax for the RecurringDownload tag. The correct Descriptor Text should be <RecurringDownload price="0.79">. The tag does not contain a recurring or interval attribute.
[Top]
The following sections describe updates to the Installation Guide.
The PostpaidService.properties file in the $CDS_HOME/deployment/deployment-name/conf directory was restructured. The following handlers are now supported:
Properties for the Postpaid Service can be set as needed by each handler. See Section 4.12, "Configure Support for Customized Reports" for information on the reporting handler.
Step 2, is replaced by the following steps:
To set a header at the top of the output file, set the postpaid.handler.PostpaidDefaultHandler.output.header property as described by the comments in the PostpaidService.properties file.
In Step 3, the following properties have changed:
In Step 4, the following properties have changed:
In addition, set the postpaid.handler.PostpaidDefaultHandler.recovery.file.suffix property to the string appended to the recovery file that is created. The default is .recover.
In Step 5, the postpaid.output.refresh.empty_file property is replaced by postpaid.handler.PostpaidDefaultHandler.output.refresh.empty_file.
Step 7 belongs in its own section titled "Configuring External Content and Group IDs."
The sms.bundle.items.threshold property is added to Table 4-6. This property identifies the maximum number of items that are pushed directly to a device at one time. If a bundle contains more items for SMS delivery than this property specifies, the subscriber is provided with a link to the list of items to be downloaded individually. For example, if this property is set to 4 and the subscriber purchases a bundle that contains four or fewer items, all items are sent directly to the subscriber's device. If the subscriber purchases a bundle that contains more than four items, a link to the list of items is sent to the subscriber.
Before you disable a DRM method, make sure that method is not assigned to a content type. Submission of content fails if the type of content submitted is protected by a disabled DRM method.
More than one DRM agent can be set for the DRMAgent property in the $CDS_HOME/deployment/deployment-name/conf/cdsdrmagent.properties file. Separate the values by a comma, for example, DRMAgent=DisconnectedTime, SmallConnectedUseTime, or specify multiple instances of the DRMAgent property with each instance set to a different agent. A derived edition is created for each DRM agent in the order in which the agents are specified. To have an edition with a smaller agent available only if the edition with the larger agent is too large, specify the DRM agents in order from smallest to largest.
For Step 1, in the $CDS_HOME/deployment/deployment-name/conf/PostpaidService.properties file, remove the pound sign (#) from the statement postpaid.handler=ReportingHandler to enable the reporting handler. Also, set the following properties:
The following information is added to this section:
See the updated sample files in the $CDS_HOME/cfg directory.
In Section 2.2, "Working with the Postpaid Service," the following properties have changed:
The following properties are added to Table 2-1, "Billing Event Parameters:"
| Parameters | Description |
|---|---|
| limited-time-price | Price to use the content for a specified time period. |
| limited-time-start | Start date from which the content can be used. |
| limited-time-end | End date until which the content can be used. |
See Section 4.1.2, "Configure the Postpaid Service" for more information on changes to the Postpaid Service.
[Top]
This section identifies known bugs by the following categories:
This section identifies bugs related to overall system operation or to more than one component.
| BUG ID | DESCRIPTION |
|---|---|
| 4975088 | The system does not prevent you from
duplicating the names of bundles or items of content. Action: Use unique names for the content and bundles added to the system. |
| 5067414 | Events generated while Java Message Service
(JMS) is not running are lost. Action: Set up a highly available JMS using techniques such as replication or clustering. |
| 5096033 | Unable to preview a ring tone when the
display name contains a quote. Action: Remove the quote from the name. |
| 5097974 | Unable to create a developer account or
Catalog Manager administrator account. Error message indicates that
an account with the specified login ID exists, but it does not appear
in the list of accounts. Action: Use a different login ID. The ID must be unique across all account types in the Catalog Manager. |
| 6203474 | Category name truncated at the open angle
bracket symbol (<) when the symbol is used in the name Action: Remove the special character from the name. |
| 6223971 | Message entered by the Catalog Manager
administrator when an edition is published is not shown to the content
provider in the Developer Portal. Action: Email the information to the content provider. |
| 6327087 | Unable to load the applet for bulk copy
and move operations in the Vending Manager or Catalog Manager administration
console. Action: Clear the cache for your browser to remove any reference to an invalid session. |
| 6336888 | When using a customized subscriber
adapter or billing adapter with Sun Java System Application Server,
access control exceptions are received. Action: Make sure that the application server is configured to allow access to all of the classes used by the adapter. Permissions are set in the server.policy file. To configure this file for all deployments, edit this file in the $CDS_HOME/dist/cds/appservers/sun/domaintemplate/config directory before deploying. To configure this file for a single deployment, edit this file in the $CDS_HOME/deployment/deployment_name/sun/domains/server-domain/server-name/config directory after deployment. For example, to allow access to insertProvider.SunJSSE and specifyStreamHandler, include the following statements in the file: grant { ;
permission java.security.SecurityPermission "insertProvider.SunJSSE";
permission java.net.NetPermission "specifyStreamHandler";
}; |
| 6337135 | When using Sun Java System Application
Server, the system runs out of disk space due to the growth of the
application server logs. Action: Set up a process for monitoring the application server logs and deleting old logs when space becomes critical. See the Sun Java System Application Server documentation for more information. |
| 6342366 | Exception received when a subscriber attempts
to access a campaign. Action: Check the names of the categories that contain content that is included in the campaign. If any category name contains a dollar sign ($), remove that character. Do not use dollar signs in category names. |
[Top]
| BUG ID | DESCRIPTION |
|---|---|
| 6203459 | Cannot submit content when a category name
that contains a colon (:) is selected. Action: Remove the colon from the category name in the Catalog Manager or have the developer select a different category when submitting content. |
| 6226013 | When a PAR file is used to submit multiple
items in a single submission, content for the first item is used for
all items. Action: Use the Zip format for all files instead of the PAR format to submit multiple items in a single submission. See the Content Developer Guide in the $CDS_HOME/Documentation directory for information. |
| 6286673 | Zip file rejected during submission with the message "Expected to
find content as a file at the root of the
zip to be named with one of the following extensions: list-of-extensions" Action: Make sure that all files at the root in the Zip file have valid extensions. |
| 6308214 | Null pointer exception received when submitting content to the Content
Aggregator Interface. Action: Make sure that you specified valid pricing models for the PriceDescriptor element. The supported pricing models vary by content type based on the type of DRM method used to protect the content. Contact the Catalog Manager administrator if you are not sure what models are valid for the content that you are submitting. |
[Top]
| BUG ID | DESCRIPTION |
|---|---|
| 5067467 | GUI error when creating a device. The Supported
Libraries field is disabled when a field in the Device Capabilities
section is selected. Action: Select MicroEdition-Profile or MicroEdition-Configuration to enable the Supported Libraries field. |
| 6211701 | Unable to remove a vending manager account
from the default vending plan or unable to remove a developer account
from the default developer plan. Action: Assign the vending manager account to a different vending plan before removing the account from the default plan. Assign the developer account to a different developer plan before removing the account from the default plan. |
| 6218881 | A developer that was removed from a Developer
Plan is still associated with the plan instead of being reassigned
to the default plan. Action: Assign the developer to the default Developer Plan before removing that developer from the other plan. |
| 6233472 | Creating a device takes a long time
and no work can be done with the device until the creation process
completes. Action: The length of time needed to create a device depends in part on the amount of content against which capability matching must be performed. For example, in a system with 3000 items of content, it can take approximately 20 minutes to add a device. Make sure that you set all of the attributes for the device as needed when you first add the device. Otherwise, you must wait for the device to be created before making additional changes. Also, the capability matching process can slow performance for subscribers, so add devices during periods of low use. |
| 6272989 | Unable to edit a vending plan when a plan
exists that contains a quotation mark in the name. Action: Delete the plan that contains the quotation mark in the name and recreate it without the quotation mark. |
| 6299255 | Unable to edit an administrator account
when the Login ID contains a single quote (') or double quote ("). Action: Delete the account and create an account without quotation marks in the Login ID. |
| 6312135 | Content developer does not receive notification of a change to the
content status. Action: If notification is required, email the information to the content developer. |
| 6316577 | Pricing options that are available do not change when the pricing
model preference is changed. Action: After you change the pricing model preference, click Done, then return to the page to work with the updated pricing options. |
| 6316587 | New pricing option wasn't saved when OK clicked. Action: You must click Save when you create a pricing option. Data is not saved when OK is clicked. |
| 6342407 | A category that was moved to a different location using the Copy/Move
Content feature still appears in the original location in the source
tree after the operation completes. Action: The move operation is successful, but the page is not properly updated. To refresh the page, click Cancel to exit the feature, then return to the Copy/Move Content page. |
[Top]
| BUG ID | DESCRIPTION |
|---|---|
| 4978930 | Campaign expiration date is misleading.
Campaign price is not available on the date shown as the expiration
date. Action: Understand that content expires at 00:00 on the date shown as the expiration date. Therefore, the expiration date for a campaign is the date on which the content is no longer available at the special price. For example, if the expiration date is November 30, 2005, the last date that content can be purchased at the campaign price is November 29, 2004. |
| 5074919 | Memory errors occurred and events were
lost. When events are generated faster than they can be processed,
the backlog can exceed available memory. Action: Add enough memory and disk space to handle surges in usage. If multiple Vending Managers are sharing the message queue broker for JMS, consider setting up separate brokers where each broker is dedicated to a single Vending Manager. |
| 6186696 | Content removed from a bundle still appears
in the bundle. Action: To remove an item of content from a bundle, you must clear the selection of the item from all categories in which the item appears. Expand all categories in the selection tree and make sure the item is not selected in any category. |
| 6189351 | Unable to edit an administrator account
when the Login ID contains a single quote or double quote. Action: Delete the account and create an account without quote marks in the Login ID. |
| 6232683 | An error message is received when a subscriber
account is assigned the same mobile ID that is used for another
account, however, the properties page still shows the duplicate mobile
ID. Action: Click OK to exit the properties page. The information is not saved due to the error received previously. Reopen the properties for the account and make your changes again. Be sure that you enter a unique mobile ID. |
[Top]
| BUG ID | DESCRIPTION |
|---|---|
| 5040147 | When the server
and subscriber are in different time zones and the content is priced
as a daily subscription, it is possible that the subscriber has
more or fewer hours than expected to use the content during the first
day of use. Action: Understand that subscriptions expire according to the time zone in which the Sun Java System Content Delivery Server is installed, not the time zone in which the subscriber is located. This bug occurs only when using the "Disconnected Time" or the "Disconnected Use and Time" DRM agent. This problem does not occur when using any of the "Connected Use and Time" DRM agents. |
| 5046093 | In the Downloads by Phone Model list,
two entries for the same manufacturer appear. Action: Edit the device profiles in the Catalog Manager and use the same spelling for the manufacturer name for all phones from the same manufacturer. The field is case sensitive. |
| 5066306 | Subscriber sees a different price than
the price set by the Vending Manager administrator. Action: None. The system is working as designed. If a subscriber purchases content or tries content on a trial basis, the subscriber is shown the price at the time of purchase or trial use, not the current price, when viewing content details. The subscriber sees the change in price only in the following situations:
|
| 6189597 | Subscriber is unable to log in when the
unique device ID maps to multiple fields in the LDAP subscriber repository. Action: Make sure that the values specified in the fields that map to the unique device ID are not used for any other subscriber. |
| 6267834 | Subscriber account that was created by the Subscriber API UserHandler class
contains invalid data. Data
validation is not performed by this class. Action: Make sure that each item of information provided to UserHandler to create the subscriber account is in the correct format and does not exceed the maximum allowed length. |
| 6319236 | A mobile originated (MO) push request for content is rejected with
the error message, "The message format received is incorrect content-ID." Action: Verify that the request is correct. Also, verify that the user is known to the system. This message is also issued if the user is not a registered subscriber and the autoCreate.newUser property in the $CDS_HOME/deployment/deployment-name/conf/SubscriberPortal.properties file is
set to false. |
| 6328751, 6329150 | The item count shown for a category in the My Categories list
is different than the number of items shown when the category is
opened. This is due to one of the following situations:
|
| 6333108 | Subscribers do not see some of the content that is compatible
with their device. This might occur when they are using a new device
that was created by the auto-provisioning feature or by importing
a device profile. Action: Force the data for the device to be refreshed using one of the following methods:
|
| 6334703 | A system error was received while browsing content
from a device and selecting the next page. This might be caused by
an administrator unpublishing an item in the category that the subscriber
is browsing. Action: Go back to the previous page or return to the main menu to continue browsing. Have administrators unpublish content during periods of low use to reduce the chance of this problem occurring. |
| 6337225 | Subscriber uses all purchased rights for
an item of content in a bundle and wants to repurchase the item. The
repurchase option is not offerred from the bundle details page when
logged in to the PC-based Subscriber Portal. Action: Log in to the Subscriber Portal from the device and repurchase the item. If the device does not support browsing, use the PC-based Subscriber Portal to locate the item of content in the category tree outside of the bundle and repurchase the content as an individual item. |
| 6337260 | Subscriber with a device that supports
the delivery of content in an SMS message purchased a bundle that contains
only SMS content. A link to the details page for the bundle was received
instead of the content. This result occurs when the number of items
in the bundle exceeds the value specified for the sms.bundle.items.threshold property
in the $CDS_HOME/deployment/deployment-name/conf/SubscriberPortal.properties file.Action: If the subscriber's device does not support browsing, have the subscriber download the content from the PC-based Subscriber Portal. To avoid the problem, make sure that the Vending Manager administrator does not create bundles that include more items than the number set for the threshold. |
[Top]
Copyright © 2005 Sun Microsystems, Inc. All rights reserved. Use subject to license terms.