Create an EJB client using the Eclipse Rich client platform and Rad V6 (i)

Create an EJB client using the Eclipse Rich client platform and the rational application Developer V6 (i)

Introduction

In recent years, the popularity of the--eclipse platform as a framework for developing interactive development environment (IDE) tools has grown significantly. With regard to Eclipse version 3.0, the same technology has been extended to support rich client development, giving Java™ developers the ability to write rich-client code using an extensible platform with their own sense of view.

The platform for developing rich clients is commonly known as Eclipse rich client Platform (RCP). Why the emphasis on rich clients? Over the years of the n-tiered architecture, it is clear that it is difficult to develop applications that give end users rich experience in using browsers. browser-based applications often try to simulate some usability by combining JavaScript with HTML. However, it is clear that it is better for an application to seek richer experience than to use a richer client-side technology platform. Similarly, Eclipse RCP gives developers the ability to create extensible client applications, and these extensible client applications can still be added to the n-tiered architecture. Eclipse RCP enables the next generation of rich clients and is the foundation of a rich client platform, such as IBM Workplace client technology.

IBM Rational Application Developer V6 (formerly IBM Websphere®studio Application Developer) is based on the Eclipse 3.0 platform. This release allows Java developers to create rich client applications that interact with the Java EE application. In this article, we will build the Eclipse RCP client using the Eclipse 3.0 feature in Rational application Developer (hereinafter called Application Developer), which invokes the configuration in Appli Cation the EJB component in the Developer WebSphere application Server test environment.

To build the Eclipse RCP application, it invokes the enterprise bean running inside the WebSphere application Server V6, and the general steps we will follow include:

Install the IBM application Client that is appropriate for WebSphere application Server. When you deploy a Java client to a workstation, you need to use the WebSphere client software to interact appropriately with the remote enterprise bean running in the WebSphere application Server. We demonstrate the configuration process in this step.

Use the j2ee™ perspective in Application Developer to deploy a temperature converter EJB application in WebSphere Application server that includes the full functionality of WebSphere Application Server Version to test your application. With application Developer, you can communicate with the default WebSphere application Server instance, pull up the management console and deploy the application (you will not need to Enterprise for this demo Archive (EAR) to import your workspace). (For convenience we use Application Developer; If you are using a separate WebSphere application Server, the steps are the same)

Build RCP clients using the Eclipse plug-in development environment. We will configure the Eclipse plug-in launcher to interact with the WebSphere Application server Java thin client, which is just an IBM JDK with server extensions, and needs to be linked to the WebSphere application server Letter. We chose this in the entire Java application Client Container because it provides a simpler configuration.

Export the RCP application and run as a stand-alone application. You need to know how to configure your plug-in dependencies and JRE to use the WebSphere application Server thin client.

In order to do this exercise, you need:

Rational application Developer V6 (or Eclipse 3)

WebSphere Application Server V6 (with some slight changes, you can also use Eclipse 3 and WebSphere Application Server V5)

IBM application Client for WebSphere Application server (already includes WebSphere Application server V6)

Included in the download file within this article. These instructions assume that the download file is decompressed to the C:\ root directory.

Setting up the Java EE application

The first thing we need to do is install the IBM application Client for WebSphere Application Server, which is already included in the WebSphere Application Server V6 (if you don't have a client, you can Your configuration changes to the server JDK in the application Developer test environment, and then deploys the application to the running WebSphere Application server:

The Java EE application client is installed by using the Setup Wizard interface. After running the start interface for your WebSphere installation, select IBM Client for IBM WebSphere application Server.

Follow the wizard and we'll install it on C:\WebSphere6ND\AppClient directory. The Windows® batch (BAT) file in the download ZIP file uses this classpath, and if you select another directory, you must modify the batch file to refer to the new directory instead. Figure 1 shows the directory you selected for the third interface of the wizard.

Figure 1. Setup Wizard