Skip Headers
Oracle® Java Micro Edition Connected Device Configuration Runtime Guide
Release 1.1.2 for Oracle Java Micro Edition Embedded Client
A12345-01
  Go To Table Of Contents
Contents

Previous
Previous
 
Next
Next
 

2 Software Layout

A CDC Java runtime environment contains the software necessary to run Java applications on a target platform. The software contents of a CDC Java runtime environment can vary, especially during product development when different testing options may be selected at build-time. This chapter describes the organization of a CDC Java runtime environment, including standard files in addition to optional security, developer and test files.

2.1 Standard Files

After installation of CDC 1.1.2, the CDC Java runtime environment is located in its installation directory. Because the location of this installation directory can be anywhere in the local file system, the CDC Java runtime environment specifies this location with the java.home system property. Table 2-1 describes the standard files located in the installation directory based on the default build options.

Table 2-1 Standard Files

File Description

bin/cvm

The CDC Java application launcher loads and executes Java applications.

Note: For the Oracle Java Micro Edition (Java ME) Embedded Client, cvm is located in InstallDir/Oracle_JavaME_Embedded_Client/binaries/bin. See the Oracle Java Micro Edition Embedded Client Reference Guide for detailed information about cvm for the Oracle Java ME Embedded Client.

lib/class-lib.jar

Optional. The CDC Java class library is used by the CDC Java runtime environment to locate and load core Java classes. The actual name of the archive file indicates the supported CDC specifications, e.g. cdc.jar, foundation-rmi.jar.

Note: lib/class-lib.jar is only present for non-preloaded builds.

lib/content-types.properties

The MIME content type system property table used by the sun.net.www package. Each entry maps a MIME content type to a native application that can handle it. Files are associated with a MIME content type by either the MIME content type returned by an HTTP header or their file name extension.

lib/security/java.policy

System-wide security policies.Foot 1 

lib/security/java.security

Master security properties.Foot 2 

lib/zi/America/Los_Angeles
lib/zi/Asia/Calcutta
lib/zi/Asia/Novosibirsk
lib/zi/GMT
lib/zi/ZoneInfoMappings

Time zone data files used by sun.util.calendar.ZoneInfoFile.


Footnote 1 See Inside Java 2 Platform Security, Second Edition: Architecture, API Design, and Implementation by Li Gong (Addison-Wesley, 2003) for more information about Java SE security features.

Footnote 2 See Inside Java 2 Platform Security, Second Edition: Architecture, API Design, and Implementation by Li Gong (Addison-Wesley, 2003) for more information about Java SE security features.

2.2 Security Files

Table 2-2 describes optional security files in versions of the CDC Java runtime environment that include the security optional packages. See Inside Java 2 Platform Security: Architecture, API Design, and Implementation by Li Gong (second edition, Addison-Wesley, 2003) for more information about Java SE security features.

Table 2-2 Security Files

File Description
lib/jaas.jar

Java Authentication and Authorization Service (JAAS) Optional Package is a part of JSR-219 which is a framework for enforcing access control to resources using a CodeSource-based and Subject-based security model. jaas.jar contains the JAAS Optional Package implementation and the KeyStoreLoginModule authentication module, which is a subset of what is available in J2SE version 1.4.2.

lib/jce.jar
lib/ext/sunjce_provider.jar
lib/sunrsasign.jar

Java Cryptography Extension (JCE) Optional Package is a part of JSR-219 which extends the Java Cryptography Architecture (JCA) to include key generation and agreement, encryption and message authentication code (MAC) generation services. jce.jar contains the JCE Optional Package implementation which is fully compatible with J2SE version 1.4.2.

sunjce_provider.jar contains the default provider implementation of the JCE service provider interface (SPI) and is fully compatible with J2SE version 1.4.2. Note that lib/ext is part of the extension class search path, but not part of the system class search path. See Section 3.3, "Class Search Path Basics" for more information about class search paths.

sunrsasign.jar contains the default provider implementation of the RSA signature SPI and is fully compatible with the default provider implementation in J2SE version 1.4.2. See "How to Implement a Provider for the Java Cryptography Architecture" in JSR-219.

lib/jsse-cdc.jar

Java Secure Socket Extension (JSSE) Optional Package is a part of JSR-219 which provides support for secure communication. jsse.jar contains both the JSSE Optional Package implementation and the default provider implementation, which is fully compatible with the default provider implementation in J2SE version 1.4.2.

lib/security/cacerts

Certificate authority (CA) keystore file. The default keystore password is "changeit". See keytool(1) for more information about how to use the Java SE SDK key and certificate management tool to change the keystore password.

lib/security/local_policy.jar
lib/security/US_export_policy.jar

Security jurisdiction policy files.


2.3 Development Files

Table 2-3 describes files that can be used with developer tools like compilers and debuggers. These files are further described in Chapter 6.

Table 2-3 Development Files

File Description
lib/btclasses.zip

The CDC Java class library can be used for compiling application source code.

Note: Because the contents of these archive files can vary depending on the selected build options, application development must be based on a target development version of the CDC Java class library. See the companion document CDC Build System Guide for information about how to build a target development version of the CDC Java class library.

lib/libdt_socket[_g].so
lib/libjdwp[_g].so

The Java Debug Wire Protocol (JDWP) shared libraries are necessary for remote debugging.