Overview of client-component development

This section provides the following information about the development process for a J2EE client component:

Stages in client-component development

To develop a J2EE client component that communicates with an ICS-managed EIS through a WebSphere Access EJB, you code the client-component source file(s) and complete other tasks. The task of creating a client component that communicates with an ICS-managed EIS includes the following general steps:

  1. Set up the development environment. Install the application-server software and WebSphere InterChange Server Access for EJB, including configuring the development environment for use with an Access EJB. For more information, see Installing Server Access for EJB.
  2. Within ICS, configure ports of the collaboration to be used as access and execution by call-triggered flows. This step involves configuring external collaboration ports, which handle access clients.
  3. Implement and debug the client component that uses an Access EJB to execute a collaboration. Implement Java code to create input data, request execution of a collaboration, and access the returned output data.

Figure 10 provides a visual overview of the client-component development process and provides a quick reference to chapters where you can find information on specific topics.

Figure 10. Overview of the client-component development task

The figure shows an overview of the development of client-components. On the left is a vertical flow of tasks. Each of these tasks is connected to a node under the heading "steps" and each of these steps has a location indicated on the right-hand side where the step is discussed. The first row has the following: Task = Set up development environment. Steps = Install development software, Install IBM WebSphere InterChange Server for Enterprise JavaBeans. Location = Chapter 3. The second row has the following elements: Task = Configure IBM WebSphere Collaborations. Steps = Configure collaboration object properties, designate collaboration ports for call-triggered flow. Location = Access Development Guide. The penultimate row comprises: Task = Code the application component. Steps = Create a session of a WebSphere Access EJB, Create input data to act as the triggering event, Send input data to an ICS-managed EIS application, Access the received output data. Location = Chapter 4. The final row has: Task = Test and debug. Steps = Invoke the client component, Verify that connection is established, Verify that requested data is obtained.

Development support for client components

To support development of a client component that requires communication with an ICS-managed EIS through an Access EJB, Server Access for EJB provides the features in Table 5.

Table 5. Support for client componets and an Access EJB

Server Access for EJB support Description

WebSphere Access EJB:

cwsession_ejb-jar.jar
Provides the client component with ICS-specific implementation of:
  • The SessionBean interface
  • Definitions of the Access EJB's home and remote interfaces
  • Deployment descriptor

For more information, see "Server Access for EJB support for EJB technology".

EJB samples Includes the following:
  • Sample client application that issues requests to the sample EJB
  • Sample servlet that executes business methods of WebSphere Access EJB
  • Sample EJB

To support development of a J2EE client component that uses an Access EJB, Server Access for EJB provides the solutions in the following subdirectory of the product:

DevelopmentKits\j2ee\ejb

This directory contains deployable code and samples for Server Access for EJB. The samples help you integrate a WebSphere Access EJB into the J2EE application.

The sample provides an EJB that runs within the context of the application server. The sample client application demonstrates how a client component requests the execution of a collaboration through a sample EJB. This sample contains code to perform the following tasks:

Copyright IBM Corp. 1997, 2004