Developer's-Panther WebSphere

Appendix D. Deploying Enterprise JavaBeans in WebSphere 3.5

This chapter describes the process for deploying Enterprise JavaBeans in WebSphere Application Server 3.5.

Installing Enterprise JavaBeans

How to Install an EJB in WebSphere

  1. Start the WebSphere Administrative Console.
  2. Create an application server (if one does not already exist for the application).

    For the steps to create an application server and a container, refer to "Creating an Application Server."

  3. Create an EJB container (if one does not already exist).
  4. With the container selected, prepare to deploy the EJB you created in Panther by right-clicking and choosing CreateEnterprise Bean.

  5. Choose Browse to select the jar file containing the deployable bean. (By selecting the jar file, WebSphere automatically fills in the Name field.)

    For local and native clients, the jar file is located in the directory specified in the Directory field of the EJB section of the Component Interface window.

    For remote clients, the jar file is located where you ran the makeejb utility on the server's application library.

  6. After selecting the jar file, WebSphere displays deployment messages for the jar and its associated beans. Choose Yes in response to the messages. WebSphere converts the Panther-generated jar file into a deployedBean jar file.

  7. To install the EJB, choose Create.

  8. If the bean installs successfully, WebSphere displays the following message. Choose OK.

  9. The EJB is now installed in WebSphere. You need to start the bean for it to be available. For information on how to use this bean in a runtime application, refer to Chapter 8, "Deploying Your Application."

Changes to the Jar File

As part of its EJB generation, Panther creates a jar file containing the EJB's Java files, deployment descriptor, and environment settings needed by the bean.

When you deploy and install the EJB in WebSphere Administrative Console, it creates a jar file in its Deployed EJBs directory (typically $WAS_HOME/deployedEJBs). This changes the name of the jar file, prepending Deployed to the jar file name.