You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 26 Next »

Release Notes – Apache Geronimo – Version 2.0 - Milestone 2

Geronimo URLs


This is a Milestone release, that means that is not the final version of Apache Geronimo v2.0 Take a look at #Known Issues and Limitations section for furhter details.

System Requirements

You need a platform that supports the Sun JDK 5.0+ (J2SE 1.5.0+).

Most testing has been done on Linux, Mac OS X, and Windows.

Significant Changes in the 2.0 -M2 Release

Major additions to this milestone are indicated as Target = 2.0-M2 in the following table.

Unable to render {include} The included page could not be found.

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.xml

Geronimo comes with batch and script files to control server start and stop functions. To see usage examples simply type geronimo.bat or geronimo.sh 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.

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:

java -jar <geronimo_home>/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".

Administration Console Security Configuration

The default administration user/password for the Geronimo Administration Console and 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.

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 during the install process. 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 once and avoid to enter 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.

Certification Status

Apache Geronimo v2.0-M2, being a MILESTONE release is not a certified yet certified.

Known Issues and Limitations

Live content, all Open Bug JIRAs against Geronimo v2.x

Key Summary Resolution Status
Loading...
Refresh

Specific Issues, Features and Improvements fixed in Version 2.0-M2

Live content, all Closed/Fixed JIRAs against Geronimo v2.x

T Key Summary Resolution Status
Loading...
Refresh

  • No labels