Chapter 30. JOnAS Migration

The guide contains the following:

30.1. JOnAS 4.3.x to JOnAS 4.4.1

Applications developed for JOnAS 4.3.x do not require changes; The main changes occur within the JOnAS configuration files, and it is recommended that you report your customizations in the new JOnAS 4.4.1 configuration files, especially for the ones mentioned below.

30.1.1. Application redeployment

This JOnAS's version offers a new mechanism to ensure application redeployment during the migration. At the deployment time, GenIC is automatically launched by the server whether a version change is detected.

30.1.2. Configuration changes

The most visible configuration change is Tomcat 5.0 moves to Tomcat 5.5. See the wiki about Tomcat https://wiki.objectweb.org/jonas/Wiki.jsp?page=Tomcat-To-JOnAS.

30.1.3. Update your $JONAS_BASE

  • If starting from an existing JONAS_BASE, it must be updated in order to upgrade to the last built-in provided EAR/WAR/JAR/RAR files (for example, new versions of the JORAM or JDBC RARs).

    cd $JONAS_ROOT
    ant update_jonasbase
  • mejb is packaged as an ear in the new version while it was delivered in an ejbjar in the previous version. So the old ejbjar must be deleted.

    cd $JONAS_BASE/ejbjars/autoload
    rm mejb.jar

30.1.4. JORAM 4.3.0

JOnAS 4.4.1 integrates the new JORAM 4.3.0 which contains:

  • Performance optimizations

  • New feature: SSL for client-server communications

  • New feature: SoftReference Messages allowing swap out, the ability to send large messages, the destinations can store more and more messages, and the messages are not held in memory.

The latest implementation required changes to the message persistance module. Therefore, JORAM's stored messages from the previous versions are not compliant with this new version; you must delete JORAM's persistance directory (s0 by default) before the migration.