EAServer can host Enterprise JavaBeans (EJB) components developed according to version 2.0, 1.1, or 1.0 of the Enterprise JavaBeans specification. EAServer supports session beans and entity beans with bean-managed persistence or container-managed persistence. EAServer uses CORBA 2.3 as the basis for the EJB component support, allowing interoperability with other client and component models and with ORBs from other vendors that are compliant with CORBA 2.3.
You can run Enterprise JavaBeans as EAServer components using any of these techniques:
Use Jakarta Ant to develop an EJB-JAR file and deploy it to EAServer with jagant. For more information on using jagant, see Chapter 12, “Using jagtool and jagant,” in the EAServer System Administration Guide.
If using the Borland JBuilder IDE, use the EAServer plugin to deploy the components to EAServer.
If using another IDE, create an EJB-JAR file and use EAServer Manager or jagtool to import an EJB-JAR file that contains the classes and deployment descriptors for one or more EJB components. EAServer Manager defines components with properties matching the deployment descriptor settings.
Import compiled versions of a home interface, remote interface, implementation class, and (for entity beans) the primary key class. EAServer Manager defines IDL interfaces for the interfaces and the primary key, and defines an EJB component with default settings. You can configure additional settings such as transaction attributes and database resource references using the EAServer Manager Component Properties dialog box.
Define an EJB component from scratch in EAServer Manager, using EAServer Manager’s IDL generation tools to define the home interface, remote interface, and primary key type. EAServer Manager generates Java classes for the home and remote interfaces and primary key class, as well as a template for the implementation class.
EAServer also supports the Enterprise JavaBeans client model. You can generate EJB-style proxies for any IDL interface, and use the proxies to call methods on components that implement that interface.
