Getting Started with WebSphere Application Server

92 Getting Started with WebSphere Application Server Community Edition
}
public void sayHello() {
}
System.out.println("Hello!");
Listing 5.4 - Implementing the EJB class
In the listing, we implement the only method sayHello() in HelloEJB. This EJB has
been completed.
5.2.2 Deploying an EJB
To deploy an EJB you need to:
1. Create a deployment plan for the EJB
2. Package the EJB
3. Deploy the EJB
5.2.2.1 Creating a deployment plan for the EJB
Just in the same way a servlet included in a Web project is accompanied with a
deployment plan named geronimo-web.xml, for an EJB project in Community Edition
the deployment plan is called openejb-jar.xml which is placed in the META-INF
directory. All the dependencies should be declared in the deployment plan.
In Community Edition, every deployable artifact must have a unique configuration id. A
Configuration id is a combination of a group id, artifact id, and artifact version and artifact
type. A Configuration id is defined in the deployment plan. As a deployable artifact, the EJB
also needs to define a configuration id in its deployment plan stored in openejbjar.xml.
Other resources or dependent artifacts can also be stated in the deployment
plan. More details about an EJB deployment plan can be found in the deployment section
of the Community Edition user guide at
http://publib.boulder.ibm.com/wasce/V2.1.1/en/developing-deployment-plans.html
To deploy EJBs, developers need to add an EJB namespace in the deployment plan.
Listing 5.5 provides a simple example of an EJB deployment plan; it only defines the
configuration id of the EJB.
com.ibm.wasce.start
testejb
1.0