MindTelligent, Inc. EJB 2.0 Design and Development with JDeveloper 9i and stand alone OC4J (Oracle Components for Java) A Technical White Paper.

Transcription

1 MindTelligent, Inc. EJB 2.0 Design and Development with JDeveloper 9i and stand alone OC4J (Oracle Components for Java) A Technical White Paper.

2 Published by MindTelligent 2034, Lamego Way, El Dorado Hills, CA Copyright 2003 by MindTelligent. All rights reserved. No part of this turial may be reproduced or utilized in any form or by any means, electronic or mechanical including photo-copying, recording, or by an information storage retrieval system, without permission in writing from the publisher. Inquiries should be addressed to MindTelligent, Inc Lamego Way El Dorado Hills, CA (916) All brand names, product names, trademarks, and registered trademarks are the property of their respective owners.

3 TABLE OF CONTENTS JDEVELOPER 9I, AN OVERVIEW....4 ORACLE9I JDEVELOPER, NEW FEATURES...5 JDEVELOPER 9I & J2EE DEVELOPMENT...7 BUSINESS COMPONENTS FOR JAVA FEATURES...9 SETUP...11 CONFIGURING AND STARTING THE ORACLE9I APPLICATION SERVER CONTAINERS FOR J2EE...18 CREATING AN EJB APPLICATION...27

4 JDeveloper 9i, an overview. Oracle9i JDeveloper is a J2EE development environment with end-toend support for developing, debugging, and deploying e-business applications and Web Services. To maximize developer productivity, JDeveloper provides a comprehensive set of integrated tools to support the complete development lifecycle, from source control, modeling, and coding through debugging, testing, profiling, and deploying. JDeveloper simplifies J2EE development by providing wizards, editors, visual design tools, and deployment tools to create high-quality, standard J2EE components including applets, JavaBeans, JavaServer Pages (JSP), servlets, and Enterprise JavaBeans (EJB). JDeveloper also provides a public Addin API to extend and customize the development environment and to seamlessly integrate with external products. To simplify the development of scalable, high-performance J2EE applications, JDeveloper offers an open and extensible J2EE framework called Business Components for Java (BC4J). BC4J is an object-relational mapping tool that implements Sun's J2EE design patterns, allowing developers to quickly build sophisticated J2EE applications In a single development environment, JDeveloper provides all the tools needed to design, develop, test, debug, tune, deploy, and version J2EE applications and Web services.

5 Oracle9i JDeveloper, New Features Oracle9i JDeveloper offers many new and exciting features that focus on delivering a complete, tightly integrated, standards based, performant, and collaborative development environment. The Oracle9i JDeveloper IDE is written in Java to provide a stable and high-performance development environment on multiple platforms. Oracle9i JDeveloper version focuses on four major themes: o Support for the latest J2EE 1.3 standards o Improved Web services support with.net interoperability o Integration with leading open source tools such as Ant, JUnit, and Struts o Personalizable and Extensible IDE using the Extension Manager Key new features of Oracle9i JDeveloper include: o Class Modeling of EJB and Web services o Full J2EE 1.3 design-time of EJB 2.0, JSP 1.2, Servlet 2.3 o Broader support for Web services including publishing PL/SQL packages as Web services, calling document style and RPC Web services, passing complex parameters, browsing UDDI registries to create client stubs and importing WSDL into your project. Enhanced Software Configuration Management o Enhanced IDE including an extension manager that gives developers control over which extension are enabled, innovative UI Debugger to visual debug Swing and AWT applications, editor bookmarks, calling external tools, auto-hide dockable windows. o Powerful Database Integration including debugging PL/SQL, ability to create tables, views, and triggers, improved SQL worksheet with history, simple registration and use of third party database drivers. o Comprehensive Struts web development support o Integrated support for the Ant open source build tool o JUnit Integration with wizards to easily develop Test Cases, Test Suites, and Test Fixtures. o Business Components for Java (BC4J) framework includes EJB 2.0 mappings and deployment support, improved security, simple

6 validation error customization, utilities to easily configure pooling and scalability parameters, Struts enabled BC4J JSP application generation wizard o Framework for the development of JSP applications with Oracle Look and Feel using uixml. Improvements include partial page rendering, integration with Struts, binding to BC4J including intermedia support o XML Editor supporting schema-driven editor for editing XML languages including uixml, uixml Template (UIT), XSQL, XSL, XHTML and WSDL files. o Rich Client development using JClient with improvements such as lazy loading of controls, drag and drop of panels from component panel, running panels standalone for incremental testing and development.

7 JDeveloper 9i & J2EE Development The tutorial guides the students through the process of developing an end-to-end J2EE Internet application with Oracle9i JDeveloper. The high-level steps involved in this tutorial are: 1. Hardware and Software Setup a. Oracle 9i b. JDeveloper i. Installation ii. Setup c. OC4J (Oracle Components for Java) d. ANT i. Installation i. Installation 2. JDeveloper General Components a. Projects b. ANT c. Connections d. Deployment Descriptors e. Deployment Profiles f. UML Diagrams g. Web Services h. XML 3. Overview of Business Components a. Generate EJBs b. Generate Business Components for JAVA (BC4J) Detailed Concepts c. Generate CORBA Files d. Generate Entity Bean Data Bindings 4. Client Tier a. Generate Java Beans

8 b. Generate SWING/AWT c. Generate SWING/JClient for BC4J 5. Database Tier 6. Web Tier a. Database Files b. Database Objects a. HTML Files b. Java Server Pages (JSP) c. Struts d. Struts Based JSP Components e. Servlets 7. Connections a. Application Servers i. OC4J b. Database Connections i. Oracle 9i With Scott/Tiger Database. 8. Developing a Struts JSP front-end bound to the BC4J middletier application. 9. Deploying the entire application onto Oracle9i Application Server Oracle Containers for J2EE (OC4J)

9 Business Components for Java Features Complete Set of J2EE Design Pattern Implementations BC4J implements the following popular J2EE Design Patterns: Model/View/Controller, Session Facade, Data Access Objects, Value Object, Value List Handler, Page-by-Page Iterator, Fast-Lane Reader, Service Locator, and Business Delegate. It also provides support for patterns like Entity Facade, Factory, and Value Messenger. Full Power of SQL Data Access with Reuse of Business Objects BC4J allows development teams to quickly assemble a "business model" encapsulating business objects, business rules, and relationships between them, and then lets developers reuse the business model components in any number of application-specific data models. To build a data model developers use the power of SQL to join, filter, project, and sort business information into the "shape" appropriate for the user interface of the task at hand. The BC4J data model can also be bound to EJB 2.0 Local Entity Beans, for developers who have committed to using entity beans as their business model. Easily Target Both J2EE Web and/or EJB Tiers BC4J encourages a well-architected, coarse-grained "service facade" application architecture and allows the same application code to be deployed either as a Session Bean Facade to the EJB Tier, or as a simple set of components for use in the J2EE Web Tier. Developers can deploy the same application to the Web Tier or EJB Tier without making coding changes to either the server or client. This lets developers choose the deployment architecture that best suits the needs of a particular application. Simplified Value Object Collections and Data Binding The BC4J data model layer provides collections of value objects that are fully updateable and automatically coordinate with the underlying business components to enforce business rules without having to write code. Additional data binding features simplify using the application's data model with JSP, UIX, XSQL, Swing, or XML-messaging-style interfaces.

10 High Productivity IDE Integration Developers using BC4J with Oracle9i JDeveloper benefit from interactive wizards, editors, testing tools, performance profilers, UML modelers, Java and XML editors with context-sensitive coding assistance and fullyautomated J2EE application packaging and deployment. Rich User Interface Support BC4J makes it easy to bind JSP, Java Swing, wireless, other XML clients, and web services to business components. The tier independent programming model ensures that the same application can be bound to different user interfaces without changing any code in the business logic tier. Tight Integration with Struts For developers using the Apache Struts framework as their MVC Controller framework, BC4J provides BC4J-aware Struts actions and a BC4J-aware Struts Request Processor, automates the creation of Struts data form beans that bind to BC4J view objects, and integrates with Oracle9i JDeveloper support for editing Any J2EE Application Server, Any Relational Database While applications built with BC4J run extremely well with Oracle9iAS and the Oracle9i database, they can be deployed in any J2EE-compliant application server and can work with any SQL92-compliant relational database. BC4J has been tested and documented against the SQL*Server and DB2 databases; and a BC4J application can be deployed to WebLogic from within JDeveloper.

11 SETUP The tutorial requires the following software components: Oracle8i (8.1.7) or Oracle9i Database Oracle9i JDeveloper version Oracle9iAS Containers for J2EE (OC4J) (part of Oracle9iAS) version and also embedded in Oracle9i JDeveloper. You can opt to use the embedded OC4J within JDeveloper. The instructions for using the embedded OC4J server in stand-alone mode is located below under Configuring and Starting the Oracle9i Application Server Containers for J2EE. Please consult the installation guides of the above products as required for help with the setup. After installation and setup of the required products, you will need to create and populate the reviewers schema tables.

12 Creating and Populating Schema Tables Although for the purpose of this tutorial, you will only use the OE schema, various dependencies have been established among the schemas. Therefore, the schemas are created in the following order: HR, OE, PM, and SH. Installation notes The SQL installation scripts have been included as a JDeveloper workspace called setup.jws with a project named demosetup.jpr, so that you can run the scripts directly from JDeveloper. The physical files for the installation scripts are included on the CD with the Oracle9i JDeveloper Reviews resource mini-website, in a zip file under the link SQL scripts for Tutorial. Select this link, then select and extract all the files in the workspace to a directory on your PC. We suggest keeping them with other workspaces, for example under <jdeveloper_root>\jdev\mywork\ where <jdeveloper_root> is the root directory that you installed Oracle9i Jdeveloper. When you run the installation script, the following tasks will be accomplished: Any previously installed HR, OE, PM, and SH schema is erased. If the schema is being installed for the first time, you will see SQL error messages, which you can ignore. The users HR, OE, PM, QS, and SH are created and the necessary privileges are granted. The tables associated with the above schemas are populated with data. The OE schema requires the database to be enabled for spatial data. The PM schema requires the database to be enabled for the Java Virtual Machine (JVM) and intermedia. The SH schema can only be installed on Oracle 8i Enterprise Edition database with the Partitioning Option installed. The scripts are designed for a local database. If you want to install them on a remote database, you must edit all the scripts that contain connect statements so that: connect <username>/<password> becomes: connect <username>/<password>@<machinename> If the password of your system database user is not manager, you must change the password in the following files: hr_main.sql oe_main.sql

13 pm_main.sql sh_main.sql Warning: Installing the reviewers schemas will destroy any previously installed schemas that use the following user names: HR, OE, PM, QS, SH. To install the reviewers schemas: 1. Start Oracle9i JDeveloper. 2. Connect to the database as system/manager or Follow the instructions below to connect directly from JDeveloper. Create a database connection In the System Navigator window, expand the Connections folder. Right click the Database folder and choose New Connection. In the Database Connection Wizard, review the information on the Welcome page and click Next.

14 In the Connection name field type Connection1 Click Next. On the Authentication page: a. In the Username and Password fields, type system and manager, respectively. b. Click Next. On the Connection page: c. In the Host name field, type the name (or IP address) of the computer where the database is located. d. In the SID and Port fields, type the information for this connection. If you do not know these values, check with your database administrator. (The default SID is ORCL and the default port is 1521 ) e. Click Next.

15 Click Test Connection. If the database is available and the connection details are correct, you will see the message "Success!. If an error occurs, verify the settings with your database administrator. Click Finish.

16 3. In the System Navigator, find and double-click the master installation script setup.sql to open it in the Oracle9i JDeveloper edit window. 4. To define a new tablespace named demo, ensure to remove the rem to un-comment lines 1 and 2 of the script, and replace the path in line 2 (C:\demo.dbf) with the path to the tablespaces (.dbf files) on your computer. 5. Right click the setup.sql script in the System Navigator window, and select Run in SQL*Plus under the system_jdbc_connection account. The first time you run sqlplus in JDeveloper, you will be prompted for the path to the SQL*Plus executable. Type or browse to the fully qualified location of the SQL*Plus executable. Running this script will set up all the necessary accounts, grant appropriate privileges, install the schemas and populate all the tables. This process may take a couple of minutes. Note: The SH schema can only be installed on Oracle 8i Enterprise Edition database with the Partitioning Option installed. If you attempt to install it on a database without partitioning enabled you will see SQL error messages, and the partitioning objects will not be created. However, for the purpose of this guide, you will not need the SH schema. After you have installed the schemas, you can examine them and view their objects from within Oracle9i JDeveloper by creating a connection to the

17 database, and then opening the nodes in the System Navigator. Before continuing with this step, you ll create a JDBC connection to the database. This connection can be reused across the product.

18 Configuring and Starting the Oracle9i Application Server Containers for J2EE OC4J v Setup and Installation Instructions This document describes the download and installation instructions for Oracle OC4J v OC4J is a lightweight container that is J2EE-compliant. It is configured with powerful and practical defaults and is ready to execute after installation. How To Install? Down load the OC4J installation kit from The product documentation can be downloaded from If downloaded for Windows NT or Windows 2000 or Windows XP o Unzip the oc4j_extended.zip to an installation directory. Let us refer to this directory as ${OC4J_INSTALLATION_DIR}. o The home directory of OC4J is ${OC4J_INSTALLATION_DIR}\j2ee\home. We can refer to this as ${OC4J_HOME}

19 cd ${OC$J_HOME} o java -jar oc4j.jar -install o The steps will involve a password and confirmation of the password. o We will refer to the password as the ${password}

20 Manage OC4J This section discusses the management of OC4J Start the Server cd ${OC4J_HOME) java -jar oc4j.jar To automatedly deploy the new "ear", "war" files, please include the files in the server.xml file. This file can be found the "config" directory. The config directory is the ${OC4J_HOME}/config. We will refer to this file as ${OC4J_CONFIG} file. On successful startup, OC4J displays the message "Oracle9iAS ( ) Containers for J2EE initialized"

21 Verification of the Server Status, it is up and running o Using your preferred browser, go to the url Stop the Server cd ${OC4J_HOME) java -jar admin.jar ormi://localhost admin ${password} - shutdown A successful start up will display the following: Oracle9iAS ( ) Containers for J2EE initialized

22 Create an Oracle9i Application Server Connection 1. In the System Navigator, expand the Connections folder. 2. Right click the Application Server folder and choose New Connection In the Application Server Connection Wizard, review the information on the Welcome page and click Next

23 4. Accept the default connection name, Connection3. Choose Standalone OC4J from the Connection type list box. Click Next.

24 5. In the Username field, enter the user name: admin. 6. In the Password field, enter the administrator's password. By default it is welcome if you didn t customize it in the section entitled Configuring and Starting the Oracle9i Application Server Containers for J2EE. 7. Select the Deploy Password check box. Then click Next. 8. In the URL field, enter the location of the Oracle9iAS server machine. If you have followed the Configuring and Starting the Oracle9i Application Server Containers for J2EE.instructions, the url will be: ormi:// / or ormi://<machine_name>/ where <machine_name> is the TCP/IP DNS name of the development machine.

25 9. Leave the Target Web Site and the Local Directory Where admin.jar for OC4J is Installed with the defaults provided by Oracle9i JDeveloper. 10. Click Next. 11. Click Test Connection. If your connection is successful, click Finish. Otherwise, click Back to return to the previous wizard pages and fix any configuration settings.

26 The configuration to deploy your J2EE applications on Oracle9iAS is complete.

27 Creating an EJB Application In the following section you will create two Entity Enterprise Java Beans based on two database tables that will use Container Managed Persistence. You will also construct a session bean to access the entity beans and a Java client to call the session bean. Create a New Workspace and Project 1. Choose File New to create a workspace for your files.

28 2. In the New object gallery, open the category General, click the Projects node and select the Workspace item. Then click OK. 3. In the resulting New Workspace dialog box, select directory name as devlab and enter jdev.jws as the file name.

29 4. Ensure that Add a new empty project is checked and click OK to create the workspace. 5. In the New Project dialog box accept the directory name, enter jdevlab.jpr as the project filename and click OK to create the project. The project should look as follows: The System Navigator Window will look like:

30 Model and create two CMP Entity Enterprise Java Beans 1. Right-click the jdevlab.jpr project and select New UML Diagram... and in the New object gallery, select the Class Diagram item. Then click OK. 2. Enter employee as the package name, accept the default diagram name and click OK.

31 3. At this stage, it is possible to draw session, entity and message driven beans on the UML diagram and generate the underlying code. This tutorial will first create two entity beans directly from database tables and then create a session bean interface to the entity beans.

32 4. Expand the Connections node in the System Navigator pane. 5. Expand the node for the connection database connection in which the table definition you want to reverse-engineer is stored. 6. Expand the SCOTT user on that connection and expand the Tables node. 7. Click the EMP table and drag it to the open class diagram. 8. When the table is dropped onto the class diagram you will be asked if you want to generate a Business Component Entity Object, an EJB 1.1 Entity Bean or an EJB 2.0 Entity Bean. Select EJB 2.0 Entity Bean.

33

34 Next, click the salgrade table and drag it to the open class diagram. Again select EJB 2.0 Entity Bean when queried. Note that the association between the two underlying tables is automatically picked up. Your new UML class diagram should appear similar to that shown below: You can customize the visual appearance of each element using the mouse to change the location and size of each element as well as by right-clicking on any element and choosing Visual Properties.... From the File menu, choose Save All.

35 Build A Session Bean Interface to the Entity Beans 1. Locate the UML component palette and from the drop down list box, select the EJB palette page profile. The component palette may appear to the right of the UML diagram canvas or on the document bar of Oracle9i JDeveloper. Both configurations are shown in the figure below: 2. Click on the Session Bean icon and draw a square to the left of the Dep entity bean. 3. The Enterprise JavaBean wizard will appear. Click Next to dismiss the Welcome screen.

36 4. In step 1 of the wizard, enter EmployeeApp as the EJB name. Take the defaults for EJB Type (Session Bean), Session Type (Stateless) and Transaction Type (Container). Click on Next. 5. In step 2 of the wizard, accept the defaults for Bean Class and Source Directory and click on Next.

37 6. In step 3 of the wizard, accept the defaults for Home Interface and Remote Interface. Click on the Include Local Interfaces option and accept the defaults for Local Home Interface and Local Interface. Click on Finish to complete the wizard. 7. On the component palette locate the EJB Local Reference component. Click on it and draw a line between the EmployeeApp Session EJB and the Dep Entity EJB as shown below. This should produce a local reference from the session EJB to the entity EJB named ejb/local/dep.

38 8.

39 Click in the EmployeeApp EJB in the third box of its UML representation and add a method findemployees by clicking in the diagram itself. Enter the method characteristics such that it will take a parameter named deptno of type Long and have the method return a parameter of type Collection parameter as shown below.

40 Note you can right mouse click on the UML components and select Properties (or double click on the UML component) to get a declarative EJB editor rather than the UML EJB editor used in these steps.

41 In the System Navigator of Oracle9i JDeveloper (on the left side of the IDE), double-click on the file EmployeeAppBean.java. This is the EJB bean implementation that has been generated from the UML model. Navigate to the method findemployees and implement the method as follows: public String [] findemployees(long deptno) { Collection coll=null; } try{ DeptLocalHome dlh = getdeptlocalhome(); DeptLocal dl = dlh.findbyprimarykey(deptno); coll = dl.getemp_deptno(); String [] lst = new String[coll.size()]; Iterator ite= coll.iterator(); int i=0; while(ite.hasnext()) { EmpLocal el =(EmpLocal) ite.next(); lst[i++]=el.getename(); } return lst; } catch (NamingException nex) { nex.printstacktrace(); }catch (FinderException fex) { fex.printstacktrace(); } return null;

42 Please note that the complete set of code for the Session EmployeeAppBean should look like: package mypackage1.impl; import javax.ejb.sessionbean; import javax.ejb.sessioncontext; import mypackage1.deptlocalhome; import mypackage1.deptlocal; import javax.naming.initialcontext; import javax.naming.namingexception; import java.util.collection; import javax.ejb.*; public class EmployeeAppBean implements SessionBean { public void ejbcreate() { } public void ejbactivate() { } public void ejbpassivate() { } public void ejbremove() { } public void setsessioncontext(sessioncontext ctx) { } private DeptLocalHome getdeptlocalhome() throws NamingException { final InitialContext context = new InitialContext(); return (DeptLocalHome)context.lookup("java:comp/env/ejb/local/Dept"); } public String [] findemployees(long deptno) { Collection coll=null; } try{ DeptLocalHome dlh = getdeptlocalhome(); DeptLocal dl = dlh.findbyprimarykey(deptno); coll = dl.getemp_deptno(); String [] lst = new String[coll.size()]; Iterator ite= coll.iterator(); int i=0; while(ite.hasnext()) { EmpLocal el =(EmpLocal) ite.next(); lst[i++]=el.getename(); } return lst; } catch (NamingException nex) { nex.printstacktrace(); }catch (FinderException fex) { fex.printstacktrace(); } return null;

43 Notice that as a result of drawing the EJB local reference between the EmployeeApp session bean and the Dept entity bean, the method GetDeptLocalHome was automatically generated. By using UML to model EJBs, the amount of code necessary to get data from the Dept entity bean to the EmployeeApp session bean has been reduced. 9. Right mouse click on the project J2EE.jpr and select Rebuild J2EE.jpr. Correct any syntax errors that are highlighted.

44 Test Your Enterprise Java Bean using Oracle9i JDeveloper's Embedded Oracle9iAS J2EE Server To test your EJBs you need to run a client program that can call methods on the EJB. JDeveloper provides a sample client utility that will help you create clients quickly. You can run and test EJBs using either the embedded Oracle Containers for J2EE (OC4J) or a remote J2EE server. The sample client utility can be used to create a client for either type. To run a sample client on the embedded OC4J server: 1. Right mouse click on the EmployeeApp node of the EJB and select Run OrderApp. This will start the J2EE containers embedded in Oracle9i JDeveloper and deploy the Orders and Customers entity beans along with the OrderApp to that container. Notice in the Message pane that OC4J has been launched.

45 EmployeeAppClient.java package mypackage1; import java.util.*; import javax.naming.context; import javax.naming.initialcontext; import javax.rmi.portableremoteobject; import mypackage1.employeeapp; import mypackage1.employeeapphome; import javax.naming.namingexception; import java.io.serializable; public class EmployeeAppClient implements Serializable { public static void main(string [] args) { EmployeeAppClient employeeappclient = new EmployeeAppClient(); try { Context context = getinitialcontext(); EmployeeAppHome employeeapphome = (EmployeeAppHome)PortableRemoteObject.narrow(context.lookup("EmployeeApp"), EmployeeAppHome.class); EmployeeApp employeeapp; // Use one of the create() methods below to create a new instance employeeapp = employeeapphome.create(); String [] lst = employeeapp.findemployees(new Long(20)); for (int i=0; i<lst.length; i++)

46 { System.out.println("The Employee Name is::"+ lst[i]); } } catch(throwable ex) { ex.printstacktrace(); } } private static Context getinitialcontext() throws NamingException { Hashtable env = new Hashtable(); env.put(context.initial_context_factory, "com.evermind.server.rmi.rmiinitialcontextfactory"); env.put(context.security_principal, "admin"); env.put(context.security_credentials, "welcome"); env.put(context.provider_url, "ormi://localhost:23891/current-workspaceapp"); } } return new InitialContext(env);

47 2. In the System Navigator, right-click the EmployeeAppClient.java and select Run. The Log pane shows the result: The Employee Name is::smith The Employee Name is::jones The Employee Name is::scott The Employee Name is::adams

48 Deploy Your J2EE Application to a Remote Server 1. In the System Navigator, right-click on jdevlab.jpr and choose New In the New Object dialog box, select the General category, click on the Deployment Profiles category, and select EJB JAR file--j2ee EJB Module. Click OK.

49

50 3. In the Save Deployment Profile dialog box, rename the File name to EmployApp.deploy and click Save.

51 4. In the EJB JAR Deployment Profile Settings dialog box, accept the defaults and click OK. Your new EmployeeApp deployment profile is added to the System Navigator. 5. Ensure your external OC4J server is started. If you have been following the evaluation guide, it should already running. If not, the steps necessary to do this are described in the Configuring and Starting the Oracle9i Application Server Containers for J2EE section of this guide. 6. In the System Navigator, right click the deployment profile you just created (OrderApp) and choose Deploy to oc4j. This will deploy the EJB application containing the Orders and Customers entity EJB and the OrderApp session EJB to Oracle9iAS.

52 Test Your Enterprise Java Bean using the Remote Oracle9i Application Server 1. In the System Navigator, right-click the EmployeeApp EJB and choose New Java Client from the context menu. 2. In the Sample EJB Client dialog box, select the option to Connect to Remote App Server. 3. In the J2EE Application Name field enter EmployeeApp 4. In the Oracle9iAS Connection Name field choose oc4j. 5. Click OK. 6. Edit the sample client created, EmployeeAppClient1.java by adding the following line after the comment:

53 package mypackage1; import java.util.hashtable; import javax.naming.context; import javax.naming.initial Context; import javax.rmi.portablere moteobject; import mypackage1.employeea pp; import mypackage1.employeea pphome; import javax.naming.naminge xception; import java.io.serializable ; public class EmployeeAppClient1 implements Serializable { public static void main(string [] args) { EmployeeAppClient1 employeeappclient1 = new EmployeeAppClient1(); try { Context context = getinitialcontext(); EmployeeAppHome employeeapphome = (EmployeeAppHome)PortableRemoteObject.narrow(context.lookup("EmployeeApp"), EmployeeAppHome.class); EmployeeApp employeeapp; // Use one of the create() methods below to create a new instance employeeapp = employeeapphome.create();

54 // Call any of the Remote methods below to access the EJB // employeeapp.findemployees( java.lang.long deptno ); String [] lst = employeeapp.findemployees(new Long(20)); for (int i=0; i<lst.length; i++) { System.out.println("The Employee Name is::"+ lst[i]); } } catch(throwable ex) { ex.printstacktrace(); } } private static Context getinitialcontext() throws NamingException { Hashtable env = new Hashtable(); env.put(context.initial_context_factory, "com.evermind.server.rmi.rmiinitialcontextfactory"); env.put(context.security_principal, "admin"); env.put(context.security_credentials, "admin"); env.put(context.provider_url, "ormi://mt-server1/employapp"); } return new InitialContext(env); } The resulting code should look as below:

55 7. In the System Navigator, right-click the sample client, EmployeeAppClient1.java and choose Run. The Message pane shows the result, The Employee Name is::smith The Employee Name is::jones The Employee Name is::scott The Employee Name is::adams The Employee Name is::ford Process exited with exit code 0.

56