Here is a recap. of our system development and test env...
I have three nearly identical environments setup. The
most accessible is on my leased system honsys.com
http://www.honsys.com:9090 (Fedora 3.1) and 8080 (Fedora 2.2.4)
with minimal security enabled (just user and password). Another
instance of 3.1 is running off port 7070 with additional security features
under evaluation. I will add new users 'brian', 'don' and a generic
'librarian' soon.

I have the same arrangement on frigate.lib.noaa.gov. But on
smoky.nodc.noaa.gov I am only running Fedora 3.1 on 7070 and 9090.
I have left 8080 free for Andy to deal with the Muradora and
Fez (8088) Fedora 2.x instance.

The FedoraCommons download page is:

http://www.fedora.info/developers/downloads.php

While the current releases of Fez and Muradora proved sophisticated
Browser GUI interfaces to the I.R., they only support the 2.x release.
The base Fedora releases provide a simple Browser interface
that supports search and retrieve, but not ingest. Ingest, as we discussed
yesterday, is supported via a fairly sophisticated Java application GUI,
and by batch script tools.

One can downloaded the 3.1 and 2.2.4 Java 'installer' jars from the Fedora
download page and perform installations on Windows and Linux systems.
I discuss the Windows installation below, via command shell. This
assumes a full Java environment is available. One must preset the
FEDORA_HOME environment variable before running the installs.

For example one can first install 3.1 (names are approximate):

set FEDORA_HOME=c:\FedoraCommons3.1
java -jar fedora3.1-installer.jar

It prompts to select 'quick', or 'custom', or 'client' and at the prompt
select 'client' and confirm the installation folder (FEDORA_HOME) etc.

then install 2.x:

set FEDORA_HOME=c:\FedoraCommons2.2.4
java -jar fedora2.2.4-installer.jar

and respond to the prompt, etc.

Each install seems to be completely self-contained, with separately runnable admin-client jar.
As I mentioned, while the Java admin GUIs from either version can connect to either
version of the Fedora webservices and conduct search and browse and retrieve, ingest
is more restricted. Evidently the Java admin GUI in the 3.1 release will only ingest into
3.1 webserver, while the 2.x will only ingest into the 2.x. This is due to the substantial
change in the Fedora object content model and its XML representation.