#Apache River Release Getting Started & More
##Examining the Distribution
Once you have unarchived this release, your installation folder
should contain most if not all of the following items.
- DISCLAIMER
- The disclaimer regarding the fact that this project is currently under incubation at The Apache Software Foundation.
- LICENSE
- The Apache License.
- NOTICE
- The file containing contributor acknowledgments.
- configentry
- The directory that contains configuration entry description files> all of the River services and utilities
- doc
- The directory that contains specifications, API documentation, manual pages, release notes, license information, and other documentation
- 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
- src
- The directory where source code may be located if installed via the separate source release, which is only available as a separate download.
- examples/hello
- The directory where the Hello example is located
##Installing the `jsk-policy.jar` file
This 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 Apache River release 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 Apache River release 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.
##Example program documentation
The hello example is included in both the source and binary releases. Once the release is downloaded and unarchived, the example documentation will be located:
$RIVER_HOME/examples/hello/index.html
##Background Material
- [Notes on Java(TM) RMI Activation and How it is Used in the Apache River release](release-notes/activation.html)
- [Security Requirements on Activation Group Descriptors used with `phoenix` or `rmid`](release-notes/execpolicy.html)
- [Note on JavaSpaces Technology, Persistent Outrigger Services, and Event Sequence Numbers](release-notes/evseqnums.html)
- [specs/html/devicearch-spec.html](Device Architecture)
##Getting Help
There are a number of additional great resources (besides the [the Jini Community area on Java.net](http://incubator.apache.org/river">Apache River project) to get information on River technology. Two places are: [Jini.org](http://www.jini.org), a community site with news and information, and mailing lists page. In addition, the river-user mailing list is a resource to find out more about general use of River technology and JavaSpaces technology.