Content and Submission Formats

C H A P T E R 16

To accept submissions of iAppli applications, you must submit the required library to Content Delivery Server. To accept content submissions in a PAR file, you must configure Content Delivery Server for this option.

This chapter includes the following topics:

Configure iAppli Support

Configure PAR File Support

16.1 Configure iAppli Support

To support iAppli applications, add an entry in the database for the DoJa library and submit the library to Content Delivery Server.

16.1.1 Add the DoJa Library to the Database

An entry for the DoJa library is added to the Catalog Manager schema by default when the schema is created unless you removed the iappli.sql file from the $CDS_HOME/dist/cds/database/cs directory at the time you created the Catalog Manager schema. If you included iAppli support when you created the Catalog Manager schema, you just need to submit the DoJa library as described in Section 16.1.2, Submit the DoJa Library.

If you did not include iAppli support when you created the Catalog Manager schema, perform the following steps on the host where the Catalog Manager is deployed before submitting the library:

1. Remove all files with the extension .sql from the $CDS_HOME/dist/cds/database/cs directory.

Save these files in another location.

2. Copy the iappli.sql file into the $CDS_HOME/dist/cds/database/cs directory.

3. Run the following command:

cdsi db data [-conf db-configuration-file] -cs

db-configuration-file is the name of the database configuration file that contains the information for creating the schemas. If db-configuration-file is not provided, the value specified for the DEFAULT_DB variable in the init_env.sh script is used. The switch -cs indicates that only the schema for the Catalog Manager is created.

4. Restart Content Delivery Server.

To verify that an entry exists in the database, log in to the Catalog Manager Administration console and display the list of device libraries to see the entry for the DoJa 1.0 library.

16.1.2 Submit the DoJa Library

Submit libraries through the Catalog Manager administration console. See the online help for additional information.

Make sure an entry for the DoJa library exists in the Catalog Manager database. If not, see the instructions in Section 16.1.1, Add the DoJa Library to the Database for creating the entry. To submit the DoJa library, follow these steps:

1. Start the Catalog Manager administration console from a browser window by typing the following address:

http://hostname:port/admin/main

The Catalog Manager Log In page is displayed.

2. Enter your administrator name and password.

3. Click Log In.

The Catalog Manager main page is displayed.

4. Click Devices in the main menu bar.

The Device Management page is displayed.

5. Click the Libraries tab.

The Device Libraries page is displayed.

6. Click DOJA-1.0.

The Library Definition page is displayed.

7. Click Upload JAR.

The library properties are displayed.

8. For Select JAR File, enter the path of the library file or click Browse to locate the library file.

Do not change the name of the library.

9. Click Next.

The items available for inclusion in the library are displayed.

10. Select Global Package.

11. Click OK.

The library is added to the database and is available for use in Developer Plans to restrict the APIs used by developers.

12. Click OK to close the confirmation page.

Note - The library must be resubmitted whenever you reinstall your database.

16.2 Configure PAR File Support

Content Delivery Server accepts content in either Zip files or Provisioning Archive (PAR) files when submitted to Content Delivery Server. To support PAR files, you must set properties in the $CDS_HOME/deployment/deployment-name/conf/DeveloperPortal.properties file to map the PAR bundle types to Content Delivery Server content types.

Add a property for each type of content that you want to support using the following format:

par.bundle-type.type=content-type

type identifies the type of PAR bundle that is submitted. PAR bundle types are defined in the Java Specification Report (JSR) 124, which is available at http://www.jcp.org/aboutJava/communityprocess/final/jsr124/.

content-type identifies the type of content in the PAR bundle and must be one of the content types defined in Content Delivery Server. For example, the following statement shows the property for submitting image content in an image bundle:

par.bundle-type.image=image

You must restart Content Delivery Server after you make changes to the properties.