Migrate enterprise bean code to the supported specification

Note: This topic does not describe how to migrate your entire configuration to Version 5. For more information about migrating your configuration, see Migration for migration instructions and tools.

Support for Version 2.0 of the Enterprise JavaBeans (EJB) specification is new for Version 5. EJB version 1.1 is also supported. Perform these steps to migrate enterprise beans to newer version levels:

1. Modify enterprise bean code for changes in the specification.
   • For Version 1.0 beans, migrate at least to Version 1.1. For more information, see Migrate enterprise bean code from Version 1.0 to Version 1.1.
   • Optionally, Migrate enterprise bean code from Version 1.1 to Version 2.0. For more information, see Migrate enterprise bean code from Version 1.1 to Version 2.0.

     Note: The EJB Version 2.0 specification mandates that prior to the EJB container's executing a findByMethod query, the state of all enterprise beans enlisted in the current transaction be synchronized with the persistent store. (This is so the query is performed against current data.) If Version 1.1 beans are reassembled into an EJB 2.0-compliant module, the EJB container synchronizes the state of Version 1.1 beans as well as that of Version 2.0 beans. As a result, you might notice some change in application behavior even though the application code for the Version 1.1 beans has not been changed.

2. You might have to modify code for some EJB 1.1-compliant modules that were not migrated to EJB 2.0. Use this information to help you decide.
   • Some stub classes for deployed enterprise beans have changed in the Java 2 SDK, Version 1.3.
   • The task of generating deployment code for enterprise beans changed significantly for EJB 1.1-compliant modules relative to EJB 1.0-compliant modules.
   • If the CMP beans write to databases with mixed-case table or column names and you used IBM VisualAge for Java, Version 3.5.x, to generate the original deployment code, you cannot simply reassemble the beans in this product. You must export the original EJB project from the VisualAge for Java product as an EJB 1.1 JAR. This preserves the metadata needed to generate the correct deployment code for mixed-case database tables and columns.

3. Reassemble and redeploy all modules to incorporate migrated code.

See these topics for more EJB migration considerations:

Change and install a new EJB dbschema database name
If the EJB dbschema name was hard coded to database EJB, see this topic to change and install a new EJB dbschema database.

Enable security on EJB method group authority
EJBs with security enabled do not migrate method group authorities, see this topic to enable security.