Migrating BEA Beehive to Apache Beehive

Although the BEA Beehive and Apache Beehive frameworks are no longer supported by Oracle or Apache, to continue using the Beehive framework, you must migrate from BEA Beehive to Apache Beehive before you deploy your applications in a WebSphere Application Server environment. After this migration, evaluate the use of the framework components and migrate either to another supported framework or to Java™ APIs.

The migration toolkit assists in detecting the following BEA Beehive components for migration to Apache Beehive.

• Java Control Extension (JCX) files
• Java Page Flow (JPF) files
• Java Web Services (JWS) files
• Global.app files
• Use of NetUI in JSP files

Some migration steps, like file refactoring and build scripts, are currently not supported by the migration toolkit and must be performed manually. Other actions, like migrating BEA Beehive annotations to Apache Beehive annotations, are supported by the migration toolkit.

To migrate from BEA Beehive to Apache Beehive, perform the following steps:

1. Remove the BEA Beehive JAR files from the application classpath and replace them with the Apache Beehive JARs from http://beehive.apache.org.
2. Identify files specific to BEA Beehive and convert them to Java source files.
   • Identify the Java Page Flow (.jpf) files using the Do not use Java Page Flow (JPF) files rule. Move these files to the Java source path in your project and change the file extensions to .java.
   • Identify the Java Control Extension (.jcx) files using the Do not use Java Control Extension (JCX) files rule. Move these files to the Java source path in your project and change the file extensions to .java.
   • Identify the Java Web Services (.jws) files using the Do not use Java Web Services (JWS) files rule. Move these files to the Java source path in your project and change the file extensions to .java.
   • Identify the Global.app file using the Do not use BEA Global.app files rule. Move this file to the Java source path in your project and change the file extensions to .java.
3. Rerun the BEA Beehive to Apache Beehive rules to analyze the Beehive Java components.
4. Review and apply the provided Java quick fixes.
   • The automated fix will create @JPF annotations from the Java Page Flow information extract annotation values from the Javadoc block to build the corresponding @JPF annotation. In some cases, the value of path might need to be preceded by "/".
5. Review and apply the provide JSP quick fixes.
6. Add the Apache Beehive filters and listeners to the web.xml descriptor.
7. Configure the Apache Beehive build scripts.