THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| No Format | ||
|---|---|---|
| ||
Release Notes -- Apache Geronimo -- Version 2.1 Geronimo URLs ------------- Home Page: http://geronimo.apache.org/ Downloads: http://geronimo.apache.org/downloads.html Documentation: http://geronimo.apache.org/documentation.html Mailing Lists: http://geronimo.apache.org/mailing.html Source Code: http://geronimo.apache.org/svn.html Bug Tracking: http://issues.apache.org/jira/browse/GERONIMO Wiki: http://cwiki.apache.org/geronimo Updated Information ------------------- Please see http://cwiki.apache.org/GMOxDOC20/release-notes-21txt.html for the latest information on this release. System Requirements ------------------- You need a platform that supports the Sun JDK 5.0+ (J2SE 1.5.0+). Other Java VMs should work as well. Most testing has been done on Linux, Mac OS X, and Windows. Significant Changes in the 2.1 Release -------------------------------------- Certification Status -------------------- Apache Geronimo v2.1 have passed 100% SUN's Java Enterprise Edition 5.0 Certification Test Suite. See "Distributions" for further details. Distributions ------------- 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 model elements of the Java EE 5.0 Specification are available. Some of the non-specification related elements such as clustering are still being worked on. Building Geronimo ----------------- See http://cwiki.apache.org/GMOxDEV/building-apache-geronimo.html for information about building Geronimo from source. Installing & Starting Geronimo ------------------------------ To install, simply unpack the .zip (Windows) or tar.gz (Unix) file containing Geronimo. If you wish to modify the default ports that Geronimo will use, edit the file <geronimo_home>/var/config/config-substitutions.properties Geronimo now provides a command shell for running some commands. To start and stop the server run "gsh" first to call the shell and then run start-server or stop-server as appropriate for the action you want to perform. It is necessary to set JAVA_HOME to the copy of your Sun 5 JDK/JRE prior to executing the command. Here is an example to set JAVA_HOME: export JAVA_HOME=<JDK/JRE_home> To see the available command options type: <geronimo_home>/bin/geronimo.sh or <geronimo_home>\bin\geronimo.bat The command will display help text instructing you as to how to start and stop the Geronimo server. 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 Geronimo Administration Console at http://localhost:8080/console/ . The default user name is "system" and the default password is "manager". Note for Windows platforms: 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. Administration Console Security Configuration --------------------------------------------- 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. As an alternative, you can make the same changes by editing the <geronimo_home>/var/security/users.properties and <geronimo_home>/var/security/groups.properties files. Access to the var/security directory should be appropriately secured on systems where you install Geronimo. Passwords in users.properties 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 users.properties file. The password(s) will be encrypted the next time the server is started. To prevent potential security exposures, we strongly recommend you update the default user names and passwords on your system. Deploying Applications ---------------------- Geronimo comes with deploy scripts and batch files to deploy J2EE modules or applications. You can use the scripts or simply invoke the executable jar by running the following command (note that you need to start Geronimo first): <geronimo_home>/bin/java -jar deployer.jar deploy my-web-app.war [deploy plan] You will need to use the username "system" and password "manager" unless you customized those as described above. 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. You can also use the "Login" command to avoid entering a user name and password every time you use the deploy tool 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] You can also graphically deploy applications and resources via the Geronimo Administration Console available at http://localhost:8080/console/ Other Deployment Options ------------------------ 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. Additionally, Geronimo provides a Maven plugin that can deploy applications to Geronimo as part of a Maven build. Configuration ------------- Most configuration attributes can be updated in the <geronimo_home>/var/config/config.xml file. The attributes most likely to be changed are already included in the supplied config.xml file, while others may need to be added manually. Known Issues and Limitations ---------------------------- |