Packaging J2EE Session EJBs

EJBs are created and packaged with a resource adapter, to be deployed as an EJB JAR file and a resource adapter RAR file, to your selected application server on a per task file basis. Task files can contain multiple tasks.

Note If you are using Oracle 9i AS as your application server, then applications are downloaded as an EAR file, which contains both the EJB JAR and resource adapter 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.

To package a J2EE session EJB
  1. In the MCS left pane, point to Products and then click Services Builder for CICS.

    This procedure assumes that you've already added an application server.

  2. Under Deployments, click J2EE Session EJBs.

    The J2EE Session EJB Deployments page appears, listing any EJBs already packaged, by their JNDI names, along with their deployment status and location.

  3. From the J2EE Session EJB Deployments page, choose the New button.

    The J2EE Session EJB wizard opens. Use this wizard to choose deployment and application server options for your packaged bean and resource adapter.

    To see what files are generated during packaging, and their locations, click the Show details button.

    At the J2EE Session EJB wizard, your choices for a finish action will depend on the application server you're working with. For all servers, you can choose "Do Nothing At This Time," and the finish action options will be available later from the J2EE Session EJB Deployments page.

    For detailed information on each panel in the wizard, choose Help from the upper right corner of the window.

Caution Tasks with very long names may cause deployment errors when deploying session EJBs to WebSphere or Sun ONE application servers. Use task names of ten characters or less.
Note WebSphere Studio has certain issues relating to Java naming conventions. When generating WebSphere Web services, these issues can be minimized by following these guidelines:
  • When naming tasks in the designer, use lower case letters.
  • When naming J2EE session EJBs, use short names and start each name with an upper case letter.
  • When naming J2EE session EJB packages, use short names and start each name with a lower case letter.
  • Avoid using underscores when creating names.
Related Topics
Bullet Using J2EE Architecture
Bullet Registering Application Servers
Bullet Deploying J2EE Session EJBs
Bullet How to Provide Tasks in a J2EE App Server
  Attachmate