Development Kit for the Java Card™ 3 Platform
Version 3.0.2, Connected Edition
These release notes describe the development kit for the Java Card™ 3 Platform, Version 3.0.2, Connected Edition, binary release.
Java Card technology combines a subset of the Java™ programming language with a runtime environment optimized for smart cards and similar small-memory embedded devices. The goal of Java Card technology is to bring many of the benefits of the Java programming language to the resource-constrained world of smart cards. The Java Card API is compatible with international standards such as ISO 7816, and industry-specific standards such as Europay, Master Card, and Visa (EMV).
Java Card platform version 3.0.2 is the latest evolution of Java Card technology. This development kit is based on the Version 3.0.1 of the Java Card Specifications, which includes their errata sheets located here. The Java Card 3 Platform consists of versions 3.0 and 3.0.1 of the specifications and versions 3.0.1 and 3.0.2 of the development kit.
For the first time, the Java Card platform is available in two editions, both of which are backward compatible with previous versions and share key security features:
The following software must be installed for the Java Card development kit to work:
Note — Do not install any software in a directory that contains a space in its name. For example, do not install software in any subdirectory of
c:\program files because of the space in the
program files element.
This source release contains both binary and source code. Note that the Java Card specifications are not included in this release. The specifications must be downloaded separately.
This release contains features required to support classic applets, web applications, and extended Java Card applet applications on the card. Specifically, this release includes the following:
installer.bat) is functional
packager.bat) can be used to both validate and create classic, web and extended Java Card applets applications
debugproxy.bat) can be used to debug applications in an IDE (such as the NetBeans™ IDE)
apdutool.bat) can be used to send APDU scripts to the extended Java Card applet applications
romizer.bat) can be used to create custom ROM image files to create customized Java Card runtime environment (
converter.bat) can be used to create classic applet application bundles
For a more thorough description of the installation, contents and use of the development kit, see Development User's Guide, Java Card Platform, Version 3.0.2, Connected Edition included in the download bundle for this release.
An automatic installer tool can be used to unpack the download file containing this release. During download, you can choose to let the installer tool unpack the download file into a directory of your choice on your system or you can save the download file itself to your system.
Note — Do not install development kit software in any directory that has a space in its name. For example, on a Windows platform, do not install software in the
c:\program files directory, or any subdirectory of
c:\program files, because the
program files element contains a space.
To install the Java Card development kit and associated software, follow these steps:
Alternatively, you can use the command line to unpack the JAR file using the following command:
Where Bundle-Filename is the downloaded development kit JAR file.
By default, the development kit is installed in
c:\jcdk3.0.2_ConnectedEdition and its associated sub-directories. You can specify a different directory if you wish.
c:\jcdk3.0.2_ConnectedEdition (or the alternate directory you specify during installation) is referred to as
JC_CONNECTED_HOME in these release notes. When the development kit installation is complete,
JC_CONNECTED_HOME contains the following:
platform.properties - contains information about the Java Card Platform for use by developer tools such as the NetBeans IDE.
UserGuide_html\index.html - HTML version of the user's guide.
||The development kit's API files.|
||Javadoc TM tool files for use with APDU I/O described in the user's guide.|
||Contains java, javacard, and javacardx directories of API export files.|
||Development kit executable files.|
||HelloWorld sample using a classic applet. The complete set of samples is available through the NetBeans IDE, each as a Kenai Project. Running this sample requires the NetBeans IDE and its Java Card technology-specific plugin.|
||HelloWorld sample using an extended applet. The complete set of samples is available through the NetBeans IDE, each as a Kenai Project. Running this sample requires the NetBeans IDE and its Java Card technology-specific plugin.|
||Keystore and certificate files for use by the samples.|
||HelloWorld sample using a servlet. The complete set of samples is available through the NetBeans IDE, each as a Kenai Project. Running this sample requires the NetBeans IDE and its Java Card technology-specific plugin.|
||Configuration and JAR files for the API, tools.
||Deletes the development kit.|
Set System Variables and Paths
System variables and paths must be set before running the development kit. See the Development Kit User's Guide more details on how to set them. Note that if you choose to set the variables and paths each time you run the development kit rather than permanently in your system, you can place the appropriate commands in a batch file.
JAVA_HOME. You must set the
JAVA_HOMEsystem variable to the JDK root directory before running the development kit.
JAVA_HOMEfrom the command line, enter the command:
set JAVA_HOME=c:\ pathbefore running the development kit. For example, if the Java platform software is stored in your
=c:\jdk6before running the development kit.
JC_CONNECTED_HOME. You must set the
JC_CONNECTED_HOMEsystem variable to the directory in which the development kit is installed before running the development kit.
JC_CONNECTED_HOMEfrom the command line, enter the command:
set JC_CONNECTED_HOME=c:\ pathbefore running the development kit. For example, if the Java Card development kit is stored in your
jcdk3.0.2_ConnectedEditionbefore running the development kit.
ANT_HOMEfrom the command line, enter the command:
set PATH=c:\ pathbefore running the development kit. For example, if Apache Ant is stored in your
ant\apache-ant1.6.5before running the development kit.
MinGWbefore running the development kit. Note that the path has to point to the
\binsubdirectory of the
MinGWinstallation directory where the
gcc.exefile is located.
set PATH=c:\ MinGW_path;%PATH%. For example, if MinGW is installed in
c:\MinGW, enter the command
set PATH=c:\MinGW\bin;%PATH%before running the development kit.
Configure the Java Card Runtime Environment for the Samples
Note that the Java Card RE ( cjcre) implementation is not optimized for memory or performance and, therefore, requires more memory than an actual optimized implementation on a card. To run the samples provided with the development kit, the Java Card RE must be configured with at least 1M of RAM, 4M of EEPROM, and 4K of COR (Clear-On_Reset). These parameters can be provided to the Java Card RE using the Java Card RE command line as follows:
cjcre.exe -ramsize 1M -e2psize 4M -corsize 4K
For details see the Java Card RE command reference in the Development Kit User's Guide for the Java Card Platform, Version 3.0.2, Connected Edition.
To remove this development kit, an automatic uninstaller tool is provided in the directory Uninstaller. You can also completely remove the development kit by deleting the
JC_CONNECTED_HOME directory along with all of its contents.
|6906665||Error msg is incorrect when instance with already existing name is being created.|
|6903372||Package visible shareable interfaces should not be included into SIO Proxy classes|
|6902985||In some cases incorrect 0x6700 (wrong length) status is returned for T1 case 4E|
If you are a Licensee, visit the product web site at https://java-partner.sun.com/portal/service/ent/platform/javacardgroup This site has the most up-to-date information on the following:
We greatly appreciate your feedback on the specifications.
Copyright © 2009 Sun Microsystems, Inc. All rights reserved.
Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries.
U.S. Government Rights - Commercial Software. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements.
Use is subject to license terms. Sun, Sun Microsystems, the Sun logo, Java, Solaris, Javadoc, Java Card and NetBeans are trademarks or registered trademarks of Sun Microsystems, Inc. or its subsidiaries, in the U.S. and other countries.
UNIX is a registered trademark in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd.