geronimo-scm mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r619793 - in /geronimo/server/branches/2.1: README.txt RELEASE_NOTES-2.1.txt
Date Fri, 08 Feb 2008 07:34:09 GMT
Author: kevan
Date: Thu Feb  7 23:34:07 2008
New Revision: 619793


    geronimo/server/branches/2.1/RELEASE_NOTES-2.1.txt   (with props)

Modified: geronimo/server/branches/2.1/README.txt
--- geronimo/server/branches/2.1/README.txt (original)
+++ geronimo/server/branches/2.1/README.txt Thu Feb  7 23:34:07 2008
@@ -1,139 +1,195 @@
-Apache Geronimo v2.0  (August 7, 2007)
+Apache Geronimo v2.1  (February 7, 2008)
+Release Notes
+ Please read the RELEASE_NOTES-2.1.txt for a complete list of new features 
+ available in this release. 
- This README serves as five minute overview of Geronimo, but better
- documentation can be found here:
+ This README serves as quick introduction to Geronimo. More complete documentation 
+ can be found here:
-   -
+   -
-Release Notes
+Installing Geronimo
- Please read the RELEASE NOTES for a complete list of features that are
- available in this release, as well as improvements and bug fixes. 
+ To install Geronimo, simply unpack the .zip (Windows) or tar.gz (Unix) file containing
+ Geronimo.
+ Note for Windows platforms:
+ The maximum path length for a directory path is 255 characters. Installing
+ Geronimo into a long directory path may cause the installation or server start up to fail.

+ It is recommended that you use a short directory name, such as "c:\g\".
+Starting Geronimo 
- If you've downloaded and unpacked a binary distribution of Geronimo,
- then you are finished with installation.
+ There are three general techniques for starting Geronimo (assuming the current directory
+ is <geronimo_home>):
+ 1. GShell -- "./bin/gsh geronimo/start-server"
+ 2. Script -- "./bin/ run" (Must first set the JRE_HOME or JAVA_HOME environment
+ 3. Java   -- "java -Djava.endorsed.dirs=lib/endorsed -javaagent:bin/jpa.jar -jar bin/server.jar"
- If you wish to modify the default ports that Geronimo will use, edit the file
- <geronimo_home>/var/config/
- Note for Windows platform:
- ==========================
- Windows users keep in mind the directory path length limitation of 255 characters.
- Defaulting installation to predefined directories such as "My Documents" or 
- "Program Files" may cause the installation or the server start up to fail. Try a 
- <geronimo_home> at a root level instead.
+Additional information on command environments can be found below.
-Starting and Stopping
+Application Deployment
- Geronimo comes with batch and script files to control server start and stop
- functions.  To see usage examples simply type geronimo.bat or
- command as appropriate for your platform.  It is necessary to set JAVA_HOME 
- to the copy of your Sun 5 JDK/JRE prior to executing the command.
- To see the available command options type:
+ Applications can be deployed to a Geronimo server in several ways:
- <geronimo_home>/bin/
- or
- <geronimo_home>\bin\geronimo.bat
+ 1. Administrative commands -- "./bin/gsh deploy/deploy MyApp.war MyDeploymentPlan.xml"
+ 2. Admin console -- login to the admin console and click "Deploy New" under Applications
+ 3. Hot deploy -- copy your archive(s) into the "<geronimo-home>/deploy" directory.
+    hot deploy service will automatically deploy these artifacts.
+ 4. maven -- applications can be installed as part of a maven build
- The command will display help text instructing you as to how to start and stop
- the Geronimo server.
+ When you deploy an application using an administrative command, you will need
+ to supply an administrator's username/password. If you do not specify the username
+ and password, you will be prompted for them.
- If you prefer to start the server without a script file you can simply type
- the following command from <geronimo_home> directory:
- java -Djava.endorsed.dirs=lib/endorsed -javaagent:bin/jpa.jar -jar bin/server.jar
- Once the server has started, you can access the welcome application by
- pointing your browser to:
+ Commonly modified configuration parameters, such as port numbers, can be set by 
+ editing the file:
-   http://localhost:8080/
+ <geronimo_home>/var/config/
- To access the Geronimo Administration Console point your browser to:
+ Additional configuration attributes can be updated in the file:
+ <geronimo_home>/var/config/config.xml
+ Once the server has started, you can access the Geronimo Administration Console
+ at http://localhost:8080/console/ . The default user name is "system" and the
+ default password is "manager".
-   http://localhost:8080/console/ 
- The default user name is "system" and the default password is "manager".
+Security Configuration
- Geronimo comes with deploy scripts and batch files to deploy JEE modules or
- applications. You can either use the scripts or simply invoke the executable
- jar by running the following command:
- <geronimo_home>/bin/java -jar deployer.jar deploy my-web-app.war [deploy plan]
+ The default administration user/password for the Geronimo Administration Console
+ and command line deployment tool is system/manager.  You can change these defaults
+ directly from the Geronimo Administration Console by accessing Security -> Console
+ Realm and change the user name and password from the Console Realm Users portlet.
- If you use the scripts provided then the command would be as follows:
+ As an alternative, you can make the same changes by editing the
+ <geronimo_home>/var/security/ and
+ <geronimo_home>/var/security/ files.
- <geronimo_home>/bin/deploy deploy my-web-app.war [deploy plan]
+ Access to the var/security directory should be appropriately secured on systems where
+ you install Geronimo.
- You will need to use the username "system" and password "manager" unless you
- changed the defaults.  
+ Passwords in are encrypted by the server. Passwords can be changed 
+ using the Geronimo Administration Console. They can also be changed using a text
+ editor. While the server is stopped, simply edit the file. The 
+ password(s) will be encrypted the next time the server is started. 
- The deployment plan argument is optional -- you can pack a deployment plan 
- into the application module, provide it on the command line, or in some cases
- omit it entirely.
+ To prevent potential security exposures, we strongly recommend you update the 
+ default user names and passwords on your system.
- For more information on the commands and options supported by the deploy tool,
- run from within the Geronimo directory <geronimo_home>/bin:
- java -jar deployer.jar help [command]
- As an alternative to the command-line deployer, you can copy application  
- modules into the <geronimo_home>/deploy/ directory and the hot deployer 
- service will deploy them automatically.
- The command-line deployer has some advantages, as it will output any
- deployment errors to its own console rather than just the server log.
+ Geronimo provides a command shell environment for executing commands, called GShell. 
- Additionally you can also graphically deploy applications and resources via 
- the Geronimo Administration Console available at:
-   http://localhost:8080/console/
+ To start a GShell environment, from the <geronimo_home> directory, execute "./bin/gsh"
+ or "bin\gsh" windows. This will start a GShell command environment. From here,
+ you can execute Geronimo administrative commands as well as general GShell commands.
+ Alternatively, you can invoke a GShell command at the same time that you invoke gsh, for
+ example:
+   ./bin/gsh geronimo/stop-server
+ A list of common gsh commands are:
+   help
+   geronimo/start-server
+   geronimo/stop-server
+   deploy/deploy 
+   deploy/undeploy 
+   deploy/list-modules
+   deploy/install-plugin
+   deploy/assemble
+ Usage information for any command can be obtained by using the --help option. For example:
+   geronimo/start-server --help 
+ For more information on GShell and GShell commands, see the Geronimo 2.1 documentation.
+ Geronimo provides a number of .sh or .bat scripts that can be used to administer Geronimo
+ servers. To use most of these scripts, you must first set either the JAVA_HOME 
+ or JRE_HOME environment variable:
+   export JAVA_HOME=<path-to-JDK>
+  or
+   export JRE_HOME=<path-to-JRE>
+ Unix scripts provided by Geronimo (there are .bat equivalents):
+ -- used to start and stop servers; either as a foreground or background process.
+ -- start a Geronimo server running as a background process
+ -- stop a running Geronimo server
+ -- deploy, list, and undeploy plugins and applications
+ -- used to generate wsdl from java code or java code from wsdl
+ For example, "./bin/ list-modules"
+ The and scripts have multiple sub-commands. Executing the scripts
+ any arguments will generate usage information. Executing "help <sub-command>" will
+ usage information for that particular command.
- Any problems with this release can be reported to the Geronimo
- mailing list or Jira issue tracker.
+ Any problems with this release can be reported to the Geronimo user mailing list 
+ or Jira issue tracker.
  Mailing list archive:
- Mailing list subscription:
+ User mailing list:
+ User mailing list subscription:
- ---------------------------------------
+ _______________________________________
  Notice Regarding Cryptographic Software
  This distribution includes cryptographic software.  The country in 
@@ -165,4 +221,4 @@
    The URL above is a reference to the Apache Geronimo Server source
-   tree for all development (and released) source trees.
\ No newline at end of file
+   tree for all development (and released) source trees.

Added: geronimo/server/branches/2.1/RELEASE_NOTES-2.1.txt
--- geronimo/server/branches/2.1/RELEASE_NOTES-2.1.txt (added)
+++ geronimo/server/branches/2.1/RELEASE_NOTES-2.1.txt Thu Feb  7 23:34:07 2008
@@ -0,0 +1,127 @@
+Release Notes -- Apache Geronimo -- Version 2.1
+Geronimo URLs
+Home Page:
+Mailing Lists:
+Source Code:
+Bug Tracking:
+Please see for the
+latest documentation on this release.
+System Requirements
+You need a platform that supports the Sun JDK 5.0+ (J2SE 1.5.0+) or greater.
+Most testing has been done on Linux, Mac OS X, and Windows.
+Geronimo 2.1 Enhancements
+Custom server assemblies
+- Lightweight server assemblies may be created that contain only the functional 
+  components required by your application(s).
+Flexible admin console
+- The admin console is now component-based to mirror the server capabilities. 
+  This allows the admin console to provide flexible administrative capabilities 
+  that will mirrors the capabilities of a custom server assembly.
+- GShell is a command-line processing environment that can be used for the execution
+  of Geronimo commands. GShell is an extensible environment and includes support
+  for editing, command history, and tab completion. 
+Clustering Support
+- WADI can now be used to support clustering of web applications for Geronimo configurations
+  use the Tomcat Web Container (WADI support for Jetty was in previous releases). 
+- Applications can be deployed to administratively-defined groups of Geronimo servers
+Monitoring Console Plugin
+- The monitoring console plugin provides monitoring support in the Geronimo admin console.

+  The monitoring console can gather statistics and performance data from multiple Geronimo

+  servers and graphically display this data to users.
+Certification Status
+Apache Geronimo v2.1 has passed 100% of SUN's Java Enterprise Edition 5.0 
+Certification Test Suite. See "Distributions" for further details.
+Apache Geronimo v2.1 is available in five distributions so you can pick the 
+one that better fits your environment.
+The available distributions are as follows:
+Certified distributions:
+- Apache Geronimo with Tomcat web container, AXIS2 for Web Services and OpenJPA
+  for persistence.
+- Apache Geronimo with Jetty web container, CXF for Web Services and OpenJPA 
+  for persistence.
+Non-Certified distributions:
+- Little-G with Tomcat web container, minimal configuration.
+- Little-G with Jetty web container, minimal configuration.
+- Micro-G, stripped down Geronimo pluggable framework.
+Note: Non-Certified distributions do not contain a complete JavaEE5 stack and so 
+cannot be certified.  Certified distributions can be reconfigured by the user 
+(such as Tomcat web container with CXF for Web Services). 
+Supported features
+All programming elements of the Java EE 5.0 Specification are available.  
+Known Issues and Limitations
+** Bug
+    * [GERONIMO-2246] - Why resource-env-ref:admin-object-module?
+    * [GERONIMO-2340] - Network Listener state not persisted across server startups
+    * [GERONIMO-2622] - Implement PolicyContextHandlerSOAPMessage
+    * [GERONIMO-3124] - Reminder:  Switch Axis2 stack back to axis2-saaj from Sun SAAJ Impl
+    * [GERONIMO-3243] - ActiveMQ violates System Properties
+    * [GERONIMO-3354] - Exception thrown by MDB involved in XA transaction
+    * [GERONIMO-3392] - CA Helper App - Unable to find HTTPS Connector configured for ClientAuth
+    * [GERONIMO-3440] - DB2-XA: when trace file is not specified, it caused error when running
the sample
+    * [GERONIMO-3442] - Tomcat exception reports reference non-existent log files
+    * [GERONIMO-3483] - Redeploy should start any dependent configurations it stops.
+    * [GERONIMO-3503] - DBPool wizzard creates plans only for local-transactions
+    * [GERONIMO-3685] - Monitoring Console should display TimeStatistics and BoundedRangeStatistics
+    * [GERONIMO-3687] - classloader deadlock during server startup
+    * [GERONIMO-3700] - alias command fails
+    * [GERONIMO-3719] - Monitoring agent uses sun classes
+    * [GERONIMO-3762] - Web Applications displayed during server startup include "system"
console plugins
+    * [GERONIMO-3768] - deployment failure is not logged in either geronimo.log or deployer.log
+    * [GERONIMO-3781] - Plugin Installer, CRSF issue when attempting to install a new plugin
+    * [GERONIMO-3815] - ContextManager.getCurrentContext() throws NullPointerException
+    * [GERONIMO-3831] - Incomplete classpath fed to wsgen
+** Improvement
+    * [GERONIMO-3399] - Need JSR88 DConfigBeans for GerSecurityType
+    * [GERONIMO-3408] - Clean up deployer login code in ServerConnection
+    * [GERONIMO-3545] - Upgrade Apache Derby to
+    * [GERONIMO-3651] - gshell should make it dead simple to run geronimo with remote debugging
+    * [GERONIMO-3661] - Optimize GShell libs for G server assemblies
+    * [GERONIMO-3759] - Geronimo Tomcat Clustering - No GBeans for adding Static Members
+    * [GERONIMO-3796] - Upgrade to 3.3 version of xbean-finder, xbean-naming, and xbean-reflect
+    * [GERONIMO-3798] - Upgrade Geronimo to newly released geronimo-transaction 2.1 and geronimo-connector
2.1 components
+    * [GERONIMO-3802] - In plugin installer, assembling a server, add a page at the end to
confirm or deny the assembly of a server package.
+** New Feature
+    * [GERONIMO-3432] - Admin Console Wizard to auto generate openejb-jar.xml
+    * [GERONIMO-3433] - Admin Console Wizard to auto generate geronimo-application.xml

Propchange: geronimo/server/branches/2.1/RELEASE_NOTES-2.1.txt
    svn:eol-style = native

Propchange: geronimo/server/branches/2.1/RELEASE_NOTES-2.1.txt
    svn:keywords = Date Revision

Propchange: geronimo/server/branches/2.1/RELEASE_NOTES-2.1.txt
    svn:mime-type = text/plain

View raw message