Update 1 performancetuning, sizing, and scaling guide (132 pages)
Summary of Contents for Sun Microsystems Security and Trust Services APIs 1.0
Page 1
Security and Trust Services APIs for Java 2 Platform, Micro Edition Version 1.0 Reference Implementation Installation Guide Sun Microsystems, Inc. 4150 Network Circle Santa Clara, California 95054 U.S.A. 650-960-1300 July 2004...
Who Should Read This Guide This Installation Guide should be read by J2ME developers working with the Security and Trust Services APIs 1.0 Reference Implementation. Before You Read This Guide In order to fully use the information in this document, you must have thorough knowledge of the topics discussed in these guides: Java Card Platform, Version 2.2.1 Development Kit, User’s Guide...
How This Guide Is Organized Chapter 1 describes the supporting software needed to install the SATSA 1.0 Reference Implementation, how to test if the SATSA 1.0 installation is successful, and information about SATSA 1.0 configuration. Typographic Conventions Typeface Meaning Examples The names of commands, files, Edit your .login file.
Related Documentation Application Title Release Notes Security and Trust Services APIs Reference Implementation: Release Notes Accessing Sun Documentation Online The Source for Java Developers web site enables you to access Java™ platform technical documentation on the Web: http://java.sun.com/reference/docs/index.html Sun Welcomes Your Comments We are interested in improving our documentation and welcome your comments and suggestions.
Page 8
viii SATSA Installation Guide • July 2004...
C H A P T E R Installing the SATSA Reference Implementation The Reference Implementation for the Security and Trust Services APIs (SATSA) for Java 2 Platform, Micro Edition Specification provides an implementation of the four optional packages defined in that specification. These are: SATSA-APDU - Defines an API to support communication with smart card applications using the Application Protocol Data Unit (APDU) protocol.
Locating and Downloading Supporting Software The default platform for the SATSA 1.0 Reference Implementation is the Windows 2000/x86 platform. The SATSA 1.0 Reference Implementation is based on the Mobile Information Device Profile (MIDP) 2.0 code base. Before downloading and installing the SATSA 1.0 RI distribution, you must have the following software installed and configured: Java 2 Platform, Standard Edition (J2SE) SDK, version 1.4.2, or the Java 2 ™...
Installing the SATSA Packages The Security and Trust Services 1.0 Reference Implementation is based on the Mobile Information Device Profile (MIDP) version 2.0 code base. Therefore, no separate installation of MIDP 2.0 is required; everything you need is contained in the SATSA 1.0 RI distribution.
Running the SATSA 1.0 Reference Implementation Running the SATSA 1.0 Reference Implementation involves two steps: Starting the MIDP 2.0 emulator Starting the Java Card (CRef) emulator Starting the MIDP 2.0 Emulator The SATSA 1.0 Reference Implementation is based on the MIDP 2.0 code base. To start the MIDP 2.0 emulator that incorporates the SATSA API, do the following: 1.
Page 13
CODE EXAMPLE CRef Output CODE EXAMPLE 1 __________________________________________________________________ Java Card 2.2.1 C Reference Implementation Simulator (version 0.41) 32-bit Address Space implementation - no cryptography support Copyright 2003 Sun Microsystems, Inc. All rights reserved. Memory Configuration Type Base Size MAX Addr...
SATSA 1.0 Configuration Files The SATSA 1.0 Reference Implementation contains two configuration files that, under most circumstances, can be left as-is and do not need to be altered or changed. These files are the following: The internal.config File The system.config File Both of these configuration files are found in the directory: %MIDP_HOME%\lib The internal.config File...
The optional internal.config file parameters are: keygen - specifies that a key be generated. Setting this parameter to false specifies that no key be generated. opaquesig - specifies that opaque signatures be used. Setting this parameter to false does not allow the use of opaque signatures. certsig - specifies that a certificate signature be used.
Glossary Advanced Encryption Standard. The successor to the DES algorithm. It has a fixed block size of 128 bits and a key size of 128, 192, or 256 bits. APDU Application Protocol Data Units. A protocol used to define the structure of data messages exchanged between smart cards and smart card readers.
Page 18
Reference Implementation. A software package created to illustrate the concepts and APIs provided in a programming specification. Security and Trust Services APIs. A set of four J2ME optional packages that SATSA provide communication protocols, such as APDU and JCRMI, and security capabilities, such as PKI and encryption, for ensuring secure transactions between J2ME programs and a security element.
Need help?
Do you have a question about the Security and Trust Services APIs 1.0 and is the answer not in the manual?
Questions and answers