Use the navigation bar on the left to find the information you need. Click on

• Quick Start for the information you need to get the product installed and ready to evaluate
• Concepts to see sections that explain important system concepts
• Tasks to see sections that contain step-by-step instructions for performing important system tasks
• Reference to see sections that provide detailed syntax for the commands, Java applications, and deployment plan schemas.

There is no license fee for using WebSphere Application Server Community Edition, but you can purchase world-class support from IBM. Three support options enable you to purchase the support level most appropriate for your business and technical needs. By using WebSphere Application Server Community Edition, you can reap the benefits of open source with the peace of mind that your applications are backed by IBM Support. Visit the product site for more information.

April 11, 2006

WebSphere Application Server Community Edition Version 1.0.1.1 is now available. Significant enhancements include

• Compatibility with PowerPC processors
• Compatibility with additional operating systems
• Compatibility with additional database managers
• Compatibility with additional LDAP servers
• Updated Eclipse tooling
• Additional samples
• Hot deployment
• Remote deployment
• Web tier clustering
• The web console.
• A new offline documentation bundle that is updated whenever the online documentation is updated so that the content is always identical.

In addition to these enhancements, this release includes a number of patches and minor changes. For details, install the new release and review the contents of installDir/CHANGES.txt where installDir is your server's installation directory.

February 15, 2006

WebSphere Application Server Community Edition Version 1.0.0.1 is now available. To determine the fixes and features included

• Go to the Apache Geronimo JIRA site and use the Find Issues link to display the JIRA issues were incorporated between 2005/10/07 and 2006/01/27.
• Install the server and examine the list of additional changes in
  • installDir\CHANGES.txt where installDir is replaced with the server's installation directory.
  • installDir/CHANGES.txt where installDir is replaced with the server's installation directory.

To fix as many defects as possible, the Apache Geronimo version chosen to build this refresh is more advanced than the version used to build Version 1. As a result, there are a number of incompatibilities between Version 1 and Version 1.0.0.1 that may require a migration effort.

• The startServer launcher is no longer included. It has been replaced by the improved startup script and the new geronimo script taken from the Apache Geronimo project.
• Closing the command prompt window or terminal session where the server is running is no longer the recommended way to stop the server. To stop the server gracefully, use the new shutdown script taken from the Apache Geronimo project.
• The conventions for specifying a configuration ID for a Geronimo component has changed. The new convention is geronimo/component/version/car where component is a unique component name and version is version number (for example 1.0). To use the deployment plans from WebSphere Application Server Community Edition V1 in the new version, you will have to modify all the configId attributes that reference system components to use the new names. The names of the components currently installed in your server can be found in
  • installDir\config-store\index.properties
  • installDir/config-store/index.properties
  where installDir is the directory where the server was installed.
• Starting with Version 1.0.0.1, users should not modify the configuration of a system component by editing its deployment plan and redeploying the component. Instead, all configuration changes should be made in the server's config.xml document. The initial deployment plans are no longer included in the server's installation directory. If you need to examine the initial deployment plans, to understand the initial attribute values or to find the configuration identifier and attribute name that you need to override in config.xml, you must obtain the installation bundle that contains the samples.

The file names of the installation bundles for Version 1.0.0.1 are different and include a version identifier. See Choosing an installation bundle for details.

The versionInfo utility has been added to display detailed version information for the server and its Java environment. In addition, the genVersionReport utility will generate a report file in an HTML document.