3 Java(TM) Platform, Standard Edition
\r
8 The Java(TM) Platform, Standard Edition Runtime Environment (JRE(TM)),
\r
9 excluding the JavaFX(TM) runtime, is intended for software developers
\r
10 and vendors to redistribute with their applications.
\r
12 The Java SE Runtime Environment contains the Java virtual machine,
\r
13 runtime class libraries, and Java application launcher that are
\r
14 necessary to run programs written in the Java programming language.
\r
15 It is not a development environment and does not contain development
\r
16 tools such as compilers or debuggers. For development tools, see the
\r
17 Java SE Development Kit (JDK(TM)). The JRE installation triggers the
\r
18 download of the JavaFX runtime. The JavaFX runtime is also available
\r
19 separately, and is not part of the JRE. For information on JavaFX, and
\r
20 how to make changes, go to: http://java.com/javafx
\r
23 =======================================================================
\r
24 Deploying Applications with the Java SE Runtime Environment
\r
25 =======================================================================
\r
27 When you deploy an application written in the Java programming
\r
28 language, your software bundle will probably consist of the following
\r
31 Your own class, resource, and data files.
\r
32 The Java SE Runtime Environment.
\r
33 An installation procedure or program.
\r
35 You already have the first part, of course. The remainder of this
\r
36 document covers the other two parts. See also the Notes for Developers
\r
37 page on the Java Software website:
\r
39 http://java.sun.com/javase/6/webnotes/runtime.html
\r
41 -----------------------------------------------------------------------
\r
42 Java Platform, Standard Edition Runtime Environment (JRE)
\r
43 -----------------------------------------------------------------------
\r
45 To run your application, a user needs the Java SE Runtime Environment,
\r
46 which is freely available from Sun. Or, you can redistribute the
\r
47 Java SE Runtime Environment for free with your application, according
\r
48 to the terms of the Java SE Platform Runtime Environment's license. The
\r
49 JavaFX runtime is only required to run applications written in the
\r
50 JavaFX scripting language; it is freely available from Sun, and must
\r
51 not be redistributed with your application.
\r
53 The final step in the deployment process occurs when the software is
\r
54 installed on an individual user's system. Installation consists of copying
\r
55 software onto the user's system, then configuring the user's system
\r
56 to support that software. You should ensure that your installation
\r
57 procedure does not overwrite existing JRE installations, as they may
\r
58 be required by other applications.
\r
61 =======================================================================
\r
62 Redistribution of the Java SE Runtime Environment (JRE)
\r
63 =======================================================================
\r
65 --------------------------------------------------------
\r
66 NOTE - The license for this software does not allow the
\r
67 redistribution of beta and other pre-release versions.
\r
68 --------------------------------------------------------
\r
70 Subject to the terms and conditions of the Software License
\r
71 Agreement and the obligations, restrictions, and exceptions set
\r
72 forth below, You may reproduce and distribute the Software (and
\r
73 also portions of Software identified below as Redistributable),
\r
76 (a) you distribute the Software complete and unmodified and only
\r
77 bundled as part of your applets and applications ("Programs"),
\r
79 (b) your Programs add significant and primary functionality to the
\r
82 (c) your Programs are only intended to run on Java-enabled general
\r
83 purpose desktop computers and servers,
\r
85 (d) you distribute Software for the sole purpose of running your
\r
88 (e) you do not distribute additional software intended to replace
\r
89 any component(s) of the Software,
\r
91 (f) you do not remove or alter any proprietary legends or notices
\r
92 contained in or on the Software,
\r
94 (g) you only distribute the Software subject to a license agreement
\r
95 that protects Sun's interests consistent with the terms
\r
96 contained in this Agreement, and
\r
98 (h) you agree to defend and indemnify Sun and its licensors from
\r
99 and against any damages, costs, liabilities, settlement amounts
\r
100 and/or expenses (including attorneys' fees) incurred in
\r
101 connection with any claim, lawsuit or action by any third party
\r
102 that arises or results from the use or distribution of any and
\r
103 all Programs and/or Software.
\r
105 The term "vendors" used here refers to licensees, developers, and
\r
106 independent software vendors (ISVs) who license and distribute the
\r
107 Java SE Runtime Environment with their programs.
\r
109 Vendors must follow the terms of the Java SE Runtime Environment Binary
\r
110 Code License agreement.
\r
112 -----------------------------------------------------------------------
\r
113 Required vs. Optional Files
\r
114 -----------------------------------------------------------------------
\r
116 The files that make up the Java SE Runtime Environment are divided into
\r
117 two categories: required and optional. Optional files may be excluded
\r
118 from redistributions of the Java SE Runtime Environment at the
\r
119 vendor's discretion.
\r
121 The following section contains a list of the files and directories that
\r
122 may optionally be omitted from redistributions with the Java SE Runtime
\r
123 Environment. All files not in these lists of optional files must be
\r
124 included in redistributions of the runtime environment.
\r
126 -----------------------------------------------------------------------
\r
127 Optional Files and Directories
\r
128 -----------------------------------------------------------------------
\r
130 The following files may be optionally excluded from redistributions.
\r
131 These files are located in the jre1.6.0_<version> directory, where
\r
132 <version> is the update version number. Solaris and Linux filenames
\r
133 and separators are shown. Windows executables have the ".exe" suffix.
\r
134 Corresponding files with _g in the name can also be excluded.
\r
135 The corresponding man pages should be excluded for any excluded
\r
136 executables (with paths listed below beginning with bin/ ,
\r
137 for the Solaris(TM) Operating System and Linux).
\r
140 Character conversion classes
\r
142 sunjce_provider.jar - the SunJCE provider for Java
\r
144 localedata.jar - contains many of the resources
\r
145 needed for non US English locales
\r
146 ldapsec.jar - contains security features supported
\r
147 by the LDAP service provider
\r
148 dnsns.jar - for the InetAddress wrapper of JNDI DNS provider
\r
150 Java RMI Activation System Daemon
\r
152 Java Remote Object Registry
\r
154 Java IDL Name Server
\r
156 Key and Certificate Management Tool
\r
158 Used to obtain and cache Kerberos ticket-granting tickets
\r
160 Kerberos display entries in credentials cache and keytab
\r
162 Kerberos key table manager
\r
164 Policy File Creation and Management Tool
\r
166 Object Request Broker Daemon
\r
168 Java IDL Server Tool
\r
169 bin/javaws, lib/javaws/ and lib/javaws.jar
\r
172 When redistributing the JRE on Microsoft Windows as a private
\r
173 application runtime (not accessible by other applications)
\r
174 with a custom launcher, the following files are also
\r
175 optional. These are libraries and executables that are used
\r
176 for Java support in Internet Explorer and Mozilla family browsers;
\r
177 these files are not needed in a private JRE redistribution.
\r
187 bin\NPJPI*.dll (The filename changes in every release)
\r
206 lib\javaws\messages.properties
\r
207 lib\javaws\messages_de.properties
\r
208 lib\javaws\messages_es.properties
\r
209 lib\javaws\messages_fr.properties
\r
210 lib\javaws\messages_it.properties
\r
211 lib\javaws\messages_ja.properties
\r
212 lib\javaws\messages_ko.properties
\r
213 lib\javaws\messages_sv.properties
\r
214 lib\javaws\messages_zh_CN.properties
\r
215 lib\javaws\messages_zh_HK.properties
\r
216 lib\javaws\messages_zh_TW.properties
\r
217 lib\javaws\miniSplash.jpg
\r
220 -----------------------------------------------------------------------
\r
221 Redistributable JDK(TM) Files
\r
222 -----------------------------------------------------------------------
\r
224 The limited set of files from the Java SE Development Kit (JDK)
\r
225 listed below may be included in vendor redistributions of the Java SE
\r
226 Runtime Environment. All paths are relative to the top-level
\r
227 directory of the JDK. The corresponding man pages should be included for
\r
228 any included executables (with paths listed below beginning with bin/ ,
\r
229 for the Solaris(TM) Operating System and Linux).
\r
231 jre/lib/cmm/PYCC.pf
\r
232 Color profile. This file is required only if one wishes to
\r
233 convert between the PYCC color space and another color space.
\r
235 All .ttf font files in the jre/lib/fonts directory.
\r
236 Note that the LucidaSansRegular.ttf font is already contained
\r
237 in the Java SE Runtime Environment, so there is no need to
\r
238 bring that file over from the JDK.
\r
240 jre/lib/audio/soundbank.gm
\r
241 This MIDI soundbank is present in the JDK, but it has
\r
242 been removed from the Java SE Runtime Environment in order to
\r
243 reduce the size of the Runtime Environment's download bundle.
\r
244 However, a soundbank file is necessary for MIDI playback, and
\r
245 therefore the JDK's soundbank.gm file may be included in
\r
246 redistributions of the Runtime Environment at the vendor's
\r
247 discretion. Several versions of enhanced MIDI soundbanks are
\r
248 available from the Java Sound web site:
\r
249 http://java.sun.com/products/java-media/sound/
\r
250 These alternative soundbanks may be included in redistributions
\r
251 of the Java SE Runtime Environment.
\r
253 The javac bytecode compiler, consisting of the following files:
\r
254 bin/javac [Solaris(TM) Operating System
\r
256 bin/sparcv9/javac [Solaris Operating System
\r
257 (SPARC(R) Platform Edition)]
\r
258 bin/amd64/javac [Solaris Operating System (AMD)]
\r
259 bin/javac.exe [Microsoft Windows]
\r
260 lib/tools.jar [All platforms]
\r
262 The Annotation Processing Tool, consisting of the following files:
\r
263 lib/tools.jar [All platforms]
\r
264 bin/apt [Solaris(TM) Operating System
\r
266 bin/sparcv9/apt [Solaris Operating System
\r
267 (SPARC(R) Platform Edition)]
\r
268 bin/amd64/apt [Solaris Operating System (AMD)]
\r
269 bin/apt.exe [Microsoft Windows]
\r
272 The Jconsole application. NOTE: The Jconsole application requires
\r
273 the dynamic attach mechanism.
\r
275 The dynamic attach mechanism consisting of the following files:
\r
276 lib/tools.jar [All platforms]
\r
277 jre/lib/sparc/libattach.so
\r
278 [Solaris(TM) Operating System (SPARC(R) Platform Edition) and Linux]
\r
279 jre/lib/sparcv9/libattach.so
\r
280 [Solaris(TM) Operating System (SPARC(R) Platform Edition) and Linux]
\r
281 jre/lib/i386/libattach.so
\r
282 [Solaris(TM) Operating System (x86) and Linux]
\r
283 jre/lib/amd64/libattach.so
\r
284 [Solaris(TM) Operating System (AMD) and Linux]
\r
285 jre\bin\attach.dll [Microsoft Windows]
\r
287 The Java Platform Debugger Architecture implementation consisting of the
\r
288 files shown in the dynamic attach section above, and the following files:
\r
289 lib/tools.jar [All platforms]
\r
290 lib/sa-jdi.jar [All platforms]
\r
291 jre/lib/sparc/libsaproc.so
\r
292 [Solaris(TM) Operating System (SPARC(R) Platform Edition) and Linux]
\r
293 jre/lib/sparcv9/libsaproc.so
\r
294 [Solaris(TM) Operating System (SPARC(R) Platform Edition) and Linux]
\r
295 jre/lib/i386/libsaproc.so
\r
296 [Solaris(TM) Operating System (x86) and Linux]
\r
297 jre/lib/amd64/libsaproc.so
\r
298 [Solaris(TM) Operating System (AMD) and Linux]
\r
301 On Microsoft Windows platforms, the JDK includes both
\r
302 the Java HotSpot(TM) Server VM and Java HotSpot Client VM.
\r
303 However, the Java SE Runtime Environment for Microsoft Windows
\r
304 platforms includes only the Java HotSpot Client VM. Those wishing
\r
305 to use the Java HotSpot Server VM with the Java SE Runtime
\r
306 Environment may copy the JDK's jre\bin\server folder to a
\r
307 bin\server directory in the Java SE Runtime Environment. Software
\r
308 vendors may redistribute the Java HotSpot Server VM with their
\r
309 redistributions of the Java SE Runtime Environment.
\r
312 -----------------------------------------------------------------------
\r
313 Unlimited Strength Java Cryptography Extension
\r
314 -----------------------------------------------------------------------
\r
316 Due to import control restrictions for some countries, the Java
\r
317 Cryptography Extension (JCE) policy files shipped with the Java SE
\r
318 Development Kit and the Java SE Runtime Environment allow strong but
\r
319 limited cryptography to be used. These files are located at
\r
321 <java-home>/lib/security/local_policy.jar
\r
322 <java-home>/lib/security/US_export_policy.jar
\r
324 where <java-home> is the jre directory of the JDK or the
\r
325 top-level directory of the Java SE Runtime Environment.
\r
327 An unlimited strength version of these files indicating no restrictions
\r
328 on cryptographic strengths is available on the JDK web site for
\r
329 those living in eligible countries. Those living in eligible countries
\r
330 may download the unlimited strength version and replace the strong
\r
331 cryptography jar files with the unlimited strength files.
\r
333 -----------------------------------------------------------------------
\r
334 The cacerts Certificates File
\r
335 -----------------------------------------------------------------------
\r
337 Root CA certificates may be added to or removed from the Java SE
\r
338 certificate file located at
\r
340 <java-home>/lib/security/cacerts
\r
342 For more information, see The cacerts Certificates File section
\r
343 in the keytool documentation at:
\r
345 http://java.sun.com/javase/6/docs/tooldocs/solaris/keytool.html#cacerts
\r
347 =======================================================================
\r
348 Endorsed Standards Override Mechanism
\r
349 =======================================================================
\r
351 From time to time it is necessary to update the Java platform in order
\r
352 to incorporate newer versions of standards that are created outside of
\r
353 the Java Community Process(SM) (JCP(SM) http://www.jcp.org/) (Endorsed
\r
354 Standards), or in order to update the version of a technology included
\r
355 in the platform to correspond to a later standalone version of that
\r
356 technology (Standalone Technologies).
\r
358 The Endorsed Standards Override Mechanism provides a means whereby
\r
359 later versions of classes and interfaces that implement Endorsed
\r
360 Standards or Standalone Technologies may be incorporated into the Java
\r
363 For more information on the Endorsed Standards Override Mechanism,
\r
364 including the list of platform packages that it may be used to
\r
367 http://java.sun.com/javase/6/docs/technotes/guides/standards/
\r
369 -----------------------------------------------------------------------
\r
370 The Java(TM) Runtime Environment (JRE) and the JavaFX(TM) runtime are
\r
371 products of Sun Microsystems(TM), Inc.
\r
373 Copyright © 2008 Sun Microsystems, Inc.
\r
374 4150 Network Circle, Santa Clara, California 95054, U.S.A.
\r
375 All rights reserved.
\r