Package a Task as a J2EE Session EJB

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.

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 task as a J2EE Session EJB
  1. From the Services Builder for Screens tree in the MCS left pane, expand the Deployments tree, then choose J2EE Session EJBs.

  2. From the J2EE Session EJB Deployments page, click the New button.

  3. In the New J2EE Session EJB Wizard, select the project containing the task or tasks you want to package as an EJB.

  4. Under State Management Mode, select Stateful or Stateless.

    For details about any of the settings, click the Help link in the upper right hand corner of the page.

  5. Click Next, then, under Choose Deployment Options, you may change the default values if necessary.

  6. Click Next.
    If you are deploying to
    		 Do this
    WebLogic or SunOne Provide server application and connector server application settings to configure your deployment. Click the the Help link in the upper right hand corner of the wizard pages for more detailed information on these settings.
    WebSphere or Oracle Because you manually deploy packages to WebSphere and Oracle, there are no configuration settings needed. See step 7.
  7. 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.
  Attachmate