Packaging J2EE Session EJBs

All deployment and management functions are accessed from MCS. Under the appropriate Services Builder, select Deployments, then select J2EE Session EJBs. Any EJBs you have already packaged are listed by their JNDI names, along with their deployment status and location.

EJBs are created and packaged with a connector, to be deployed as an EJB JAR file and a connector RAR file, to your selected application server on a per project basis. Projects can contain multiple tasks.

Note If you using Oracle 9i AS as your application server, then applications are downloaded as an EAR file, which contains both the EJB JAR and connector RAR files.

Each packaged EJB is configured for a specific instance of an application server and each application server has a different set of configuration settings. The J2EE Session EJB wizard walks you through the configuration and deployment process for each type of application server.

If you are
Then do this
Creating a new EJB Choose New.
Editing existing EJB configurations Choose Edit.

When you choose Edit, you step through the same series of dialog boxes as you do when you are creating a new EJB. All previously configured settings are displayed and you can simply edit those options that need modification.

How do I package an EJB?

From the Session EJB Deployments list, you can package a new EJB, edit existing EJBs, deploy, un-deploy, and delete your EJBs. EJBs are listed by their JNDI names, which is the unique identifier used for packaging and deploying.


In order to package an EJB for deployment to a particular application server you must enter the following application server-specific information. Options vary depending on whether you are creating stateful or stateless EJBs.

For more information on stateful and stateless EJBs, see Configuring J2EE Session EJBs.

Application Server EJBs that maintain state Stateless EJBs

  • Maximum cache size
  • Resize quantity
  • Maximum wait time in milliseconds
  • Cache idle timeout in seconds
  • Removal timeout in seconds
  • Victim selection policy

  • Resize quantity
  • Steady pool size
  • Maximum pool size
  • Removal timeout in seconds
  • Pool idle timeout

  • Maximum beans in cache
  • Idle timeout in seconds
  • Cache type
  • Persistent store directory
  • Replication type
  • Allow concurrent calls

  • Maximum beans in free pool
  • Initial beans in free pool
  • Stateless bean is clusterable
  • Stateless bean load algorithm
  • Stateless bean call router class name

Choose Help on the WebLogic and SunOne Application Server Options dialog boxes for more detailed information on these options.

Note This information is available from your application server administrator and suggestions and limitations for each setting are available in the application server documentation. Because you manually deploy packages to WebSphere and Oracle, there are no configuration settings needed.
To package or edit an EJB
  1. From the J2EE Session EJB Deployments list page, choose New or Edit.

  2. The first panel in the J2EE Session EJBs wizard displays. When you are editing, the options that were previously set are displayed. Only modify those settings that need changing.

  3. There are a series of panels that walk you through the packaging and deployment process. Choose Help from any of these dialog boxes for detailed information on each panel.

    To deploy a package to WebSphere or Oracle, the download dialog box displays. You must manually deploy to both WebSphere and Oracle.

    If this application server
    Then download this
    WebSphere EJB JAR and connector RAR files
    Oracle EAR file, containing both the JAR and RAR files.

    After the downloading is complete you can deploy the files to the application server.

    Note You can deploy, download, undeploy, or delete any EJB from the J2EE Session EJB Deployments list by selecting the EJB, by its JNDI name, and then clicking the appropriate command button.
  4. After packaging and deploying, a Deployment Status page displays. The status of your deployment, either successful or not is available, including complete details on the deployment. All deployment errors are logged to MCS.

For more information about accessing the log and common errors that can occur, see Session EJB Errors.

Related Topics
Bullet Using J2EE Connector Architecture, Overview
Bullet Configuring J2EE Session EJBs
Bullet Session EJB Errors
Bullet Registering Application Servers
Bullet Deploying J2EE Session EJBs