Sun Java System Application Server Platform Edition 8.1 2005Q2 Update 2 Upgrade and Migration Guide

- Previous: EJB Migration
- Next: Migrating Enterprise Applications

## EJB Changes Specific to Application Server Platform Edition 8.1

Migrating EJBs from Application Server 6.x to Application Server 8.1 is done without making any changes to the EJB code. However, the following DTD changes are required.

### Session Beans

- The `<!DOCTYPE>` definition must be modified to point to the latest DTDs with J2EE standard DDs, such as `ejb-jar.xml`.

- Replace `ias-ejb-jar.xml` file with the modified version of this file, named `sun-ejb-jar.xml,`created manually according to the DDs. For more details, see http://wwws.sun.com/software/dtd/appserver/sun-ejb-jar_2_1-1.dtd

- In the `sun-ejb-jar.xml` file, the JNDI name for all the EJBs must be added before ”`ejb/`’ in all the JNDI names. This is required because, in Application Server 6.5, the JNDI name of the EJB can only be `ejb/<`ejb-name`>` where `<`ejb-name`>` is the name of the EJB as declared inside the `ejb-jar.xml` file.

  In the Application Server, a new tag has been introduced in the `sun-ejb-jar.xml`. This is where the JNDI name of the EJB is declared.

Note –

To avoid changing JNDI names throughout the application, declare the JNDI name of the EJB as `ejb/<`ejb-name`>` inside the `<`jndi-name`>` tag.

### Entity Beans

- The `<!DOCTYPE>` definition must be modified to point to the latest DTDs containing J2EE standard DDs, such as `ejb-jar.xml`.

- Update the `<cmp-version>` tag with the value 1.1, for all CMPs in the `ejb-jar.xml` file.

- Replace all the `<`ejb-name`>-ias-cmp.xml` files with the manually created `sun-cmp-mappings.xml` file. For more information, see http://wwws.sun.com/software/dtd/appserver/sun-cmp-mapping_1_2.dtd

- Generate `dbschema` by using the `capture-schema` utility in the Application Server installation’s bin directory and place it above `META-INF` folder for Entity beans.

- `Replace the ias-ejb-jar.xml` with the `sun-ejb.jar.xml` in Application Server.

- In Application Server 6.5, the finder's SQL was directly embedded into the `<`ejb-name`>-ias-cmp.xml`. In Application Server, mathematical expressions are used to declare the `<query-filter>` for the various finder methods.

### Message Driven Beans

Application Server provides seamless Message Driven Support through the tight integration of Sun Java System Message Queue with the Application Server, providing a native, built-in JMS Service.

This installation provides Application Server with a JMS messaging system that supports any number of Application Server instances. Each server instance, by default, has an associated built-in JMS Service that supports all JMS clients running in the instance.

Both container-managed and bean-managed transactions, as defined in the Enterprise JavaBeans Specification, v2.0, are supported.

Message Driven Bean support in iPlanet Application Server was restricted to developers, and used many of the older proprietary APIs. Messaging services were provided by iPlanet Message Queue for Java 2.0. An LDAP directory was also required under iPlanet Application Server to configure the `Queue Connection Factory` object.

The `QueueConnectionFactory`, and other elements required to configure Message Driven Beans in Application Server are now specified in the `ejb-jar.xml` file.

For more information on the changes to deployment descriptors, see Migrating Deployment Descriptors For information on Message Driven Beans see Using Message-Driven Beans in Sun Java System Application Server Platform Edition 8.1 2005Q2 Update 2 Developer’s Guide.

- Previous: EJB Migration
- Next: Migrating Enterprise Applications

- © 2010, Oracle Corporation and/or its affiliates