Using the Synapta Services Builder for Screens component of MCS, you can package your task as a J2EE Session EJB, which lets you provide the host access functionality (built into your task) through a Java 2 Enterprise Edition (J2EE)-compliant application server.


Once you've published your project to MCS, you can package it as a J2EE Session EJB, and then deploy it to a supported application server. Attachmate Synapta Services Builder support the following J2EE-compliant application servers: BEA WebLogic 8.1 and 7.04, IBM WebSphere 5.0, Oracle 9i AS, and Sun's SunOne AS7.

Before You Start

This How-To assumes that you have created and published a Synapta Services Builder for Screens task (or set of tasks). Also, you must have installed one of the supported J2EE-compliant application servers.

Note This How-To refers to a connector as part of the architecture. This is a J2EE specification term and should not be confused with Synapta Services Builder. Attachmate's implementation of the J2EE connector is a system-level software driver used by an application server or client to connect to an enterprise system. It plays a central role in the integration and connectivity between your enterprise system and an application server — it is the point of contact between application components, application servers, and enterprise information systems.


Following are the main steps you need to complete for this How-To:

  1. Configure your run-time server with right number of session pools.

  2. Register an application server.

  3. Package a task as a J2EE Session EJB.

  4. Deploy your J2EE Session EJB to the selected application server.

  5. Integrate your J2EE Session EJB with an application.