Once you have installed this release, your installation folder should contain some or all of the following items. The actual items installed depend on the features selected during installation.
- index.html
- The starting page for all documentation
- configentry
- The directory that contains configuration entry description files for all of the starter kit services and utilities
- classes
- The directory that contains class files from the JAR files that are in the
libandlib-dldirectories- doc
- The directory that contains specifications, API documentation, manual pages, release notes, license information, and other documentation
- installverify
- The directory that contains configurations and an executable for starting a service browser and six contributed Jini services
- lib
- The directory where the non-download JAR files are located
- lib-dl
- The directory where the download JAR files for the services are located
- lib-ext
- The directory where the dynamic security policy provider is located
- source
- The directory that contains all of the source code and build files for the release and the hello example
- uninstall
- The directory that contains the uninstaller for the release
jsk-policy.jar fileThis release includes a security policy provider which supports dynamic granting of permissions at run-time. Although use of this policy provider is not required, its use is highly recommended when deploying secure applications and services. To permit effective use of this policy provider, it must first be installed as an extension in the Java 2 SDK (or JRE) that you will be using. Note that installing this provider does not automatically cause it to be used, and its installation should not alter the operation of existing applications.
To install this policy provider, providing you didn't do so during your initial installation,
you must copy the jsk-policy.jar file from the lib-ext
subdirectory of your Jini(TM) Technology Starter Kit (starter kit) installation to
the extensions directory of your Java(TM) 2 SDK (or JRE) installation.
An alternative to copying jsk-policy.jar to the extension directory is
to use the system property java.ext.dirs. This property specifies one or
more directories to search for extensions, each separated by File.pathSeparatorChar.
To use jsk-policy.jar in this manner, the system property
must be set to include both the path to the Java 2 JRE extension directory
(or directories) and the path to the lib-ext subdirectory of
your starter kit installation.
Note that in Java(TM) 2 Standard Edition (J2SE(TM)) 1.4, only the original extension directory
is granted permissions via the system policy file, so you will have to explicitly grant
permissions to jsk-policy.jar in your own policy files. In J2SE 5.0, all the
directories specified in java.ext.dirs are granted permissions so the explicit
permission grant is not needed.
This release is licensed under the Apache License, Version 2.0.
phoenix or rmid