Batch Uploading with CMX

Contents

• About this document
• Limitations of the service
• Naming the files
• Creating the ZIP file
• Uploading to CMX
• Suggestions
• Appendix: Capabilities
• Appendix: File Types

About this document

This document assumes that you have a good understanding of CMX and your services you are running. It assumes you have services that are currently functioning and configured correctly. By the end you should be able to create the appropriate files to batch upload content into your CMX services.

Limitations of the service

The batch upload feature can only upload to one service at a time, and only one type of content at a time. You can upload unlimited numbers of content items within a single service, and you can also update content with this feature. The maximum size of the zip file created must be less than 2.5Mb, or the upload will not complete.

The restriction to one type of content means one specific file type, e.g. Polyphonic Ringtone (SMAF format) or Images (JPEG format). The only exception to this is midlets, where you may upload both the JAR and the JAD file in one upload.

Naming the files

Files to be uploaded to CMX have a special naming convention.

<order-code>-<purposing-data>.<file-extension>

Each of the three components are covered in a section below.

1. Order Code is the identifier used within CMX to refer to your content, for people to order it and for you to manage it. Examples include "0,1,2,3,..." for subscription based content, or "ANGELS,MILLENIUM,..." for a ringtones service.

2. Purposing-Data is used to declare which device should receive this file. There are three ways to specify this data:

   • User-Agent

     This is the HTTP user agent that the phone supplies when it requests the wap push content. This can be specified to any degree of looseness required, except that a "%"sign must always complete the useragent.

     Examples:

     Nokia6600%	= all Nokia 6600s
     Nokia%	= all Nokia 6600s
     SonyEricssonT610%	= all T610s

   • Image Resizing

     This is achieved by activating an option in the service configuration. The image used is the one with the Default user-agent ("%"), so this needs to be set as the purposing-data.

     Examples:

     %	For all automatic image resizing.

   • Capability Matching

     This is achieved by specifying which capability you wish to upload for. Both Audio files (including Polyphonics) and Midlets require simply that you have the capability name as the purposing-data. See the appendix for a list of capabilities and their function.

     Examples:

     NOKIA60	= For all Nokia Series 60 phones.
     WAV	= For all phones that support Wave files

     
     

3. File Extension is simply the extension for the filetype. See the appendix for well known filetypes.

Creating the ZIP File

Place all your content in one directory and use your favourite zip program to create the archive. Make sure that all the files are named correctly, and that they are all in a flat directory structure located at the root of the zip file. Directories will not be processed, and may cause errors.

Example Zip File:

Archive: purposed.zip
   100-CLDC1.jar
   100-%.jar
   100-MIDP2.jar
   100-NOKIA40.jar
   100-Nokia6600%.jar
   100-CLDC1.jad
   100-%.jad
   100-MIDP2.jad
   100-NOKIA40.jad
   100-Nokia6600%.jad
   101-CLDC1.jar
   101-%.jar
   101-MIDP2.jar
   101-NOKIA40.jar
   101-Nokia6600%.jar
   101-CLDC1.jad
   101-%.jad
   101-MIDP2.jad
   101-NOKIA40.jad
   101-Nokia6600%.jad

This zip contains two items of content, numbered 100 and 101 . It contains both jad and jar files. All entries use the Capability Matching system of purposing, except for the Nokia6600% which is User-agent purposed, and the default entry %.

Uploading to CMX

Proceed as normal for uploading a single item of content. When you reach the final screen where it asks you for your files, click the "Batch Upload" option, and use your ZIP file instead.

Suggestions

Always keep a copy of the data you upload on your computer as well as on the service. This avoids potential loss of data if services are accidentally deleted. It also enables you to have a local record of what content you have already uploaded to CMX to avoid duplicates.

Don't upload too many at once. Uploading 500 files and finding an error in them will mean there are a lot of files to search through.

Make sure you are not going to overwrite old copies of content when you upload, unless you really mean to.

You can also upload thumbnail images for use with midlets, to enable quickly locating the correct midlet. These need to be uploaded separately, with file names similar to the following:

Archive: thumbnails.zip
    100-Thumbnail.jpg
    101-Thumbnail.jpg

Appendix: Capabilities

Appendix: File Types