1. 1 SOA and Enterprise Computing Enterprise Java Beans

2. 2 Advanced Java 2 Platform How to Program by Deitel, Deitel, & Santry Thinking in Enterprise Java Bruce Eckel et. Al. EJB 3.0 API Sun documentation http://java.sun.com/products/ejb/docs.html Java Enterprise In A Nutshell Farley, Crawford & Flanagan Some Useful Resources

3. 3 From The Java EE Tutorial Servlets JSP’s Axis2 HTML Session beans Entity beans Message Driven Beans

4. 4 From The Java EE Tutorial

5. 5

6. 6 SOAP and Java EE Slide from JAXM/JMS tutorial at Sun Microsystems

7. 7

8. 8 Benefits of Enterprise Beans(1) Simplify development of large, distributed applications. The developer can concentrate on business problems. The EJB container handles transaction management, security, and authorization. Portable – may be moved to other Java EE containers.

9. 9 Benefits of Enterprise Beans(2) Scalable – the components may be distributed across many machines. Support for Location Transparency – the client need not be concerned with the location of the bean. Support for Transaction management - ensures data integrity (over concurrent access of shared resources). Promotes thin clients and web services.

10. 10 Main Concept: Interposition Application stub skeleton examine security credentials start or join transaction call any necessary persistence functions trigger various callbacks call business logic more work with transactions, persistence and callbacks send back result or an exception EJB Container

11. 11 The Container Implements the component interface (From Eckel)

12. 12 Enterprise Java Beans Part of Java EE Enterprise Application Technologies Currently at EJB3.0 (Big simplification of code with annotations – less concern with configuration files) Server-side managed components Server-Side EJB objects may offer a remote view (via a remote procedure call protocol) a local view (direct procedure call) or both Managed EJB container services are more involved than the plain old JVM Components distributed in binary format and are configurable

13. 13 Server-Side Implications In order to pull off the RPC trick we need: A naming service -- Recall how RMI clients make requests on the rmiregistry. -- A stand alone EJB client would use a global JNDI name. InitialContext ic = new InitialContext(); // provider properties Foo foo = (Foo) ic.lookup("FooEJB"); // and address of // naming service // found in // jndi.properties RPC proxies -- communications code along with the appropriate interface

14. 14 Managed: EJB Container Services Object Persistence Declarative Security Control Declarative Transaction Control Concurrency Management Scalability Management The programmer need not worry about the details. Think “JVM on steroids”.

15. 15 EJB Types Entity Beans Session Beans Message-Driven Beans

16. 16 EJB Types Entity Beans Session Beans Message-Driven Beans } } RMI-based server side components Accessed using distributed object Protocols (RMI IIOP) New since EJB 2.0 Asynchronous server side component that responds to JMS asynchronous messages (Think provider like JAXM)

17. 17 Entity Beans (1) Represent a row of a relation. O/R mapping. Represent real world entities (customers, orders, etc.). Persistent objects typically stored in a relational database using CMP (Container Managed Persistence) or BMP (Bean Managed Persistence). The client sees no difference between CMP and BMP beans. CMP promotes component portability (more reliant on the container to handle detail). CMP uses its own Query Language EJB QL. CMP relies on an Abstract Schema in the deployment descriptor.

18. 18 Entity Beans (2) Define a primary key class: –Required for entity beans. –Provides a pointer into the database. –Must implement Java.io.Serializable. The EJB instance represents a particular row in the corresponding database table. The home interface for the entity EJB represents the table as a whole (has finder methods.)

19. 19 Entity Beans (3) The primary key can be used by the client to locate the bean Rows may have columns that reference other entity beans (e.g. an order has a buyer) These relationships may be managed by the bean or by the container (container managed relationships)

20. 20 Entity Bean(4) OrderEJB CusomerEJB 1 Many 1 Many LineItemEJB ProductEJB Many 1 A relationship field is like a foreign key in a database. If a b then a “knows about” or “holds a pointer to” b.

21. 21 Session Beans Are an extension of the client application. Manage processes or tasks. Are not persistent. Often employ several different kinds of entity beans. Implement business logic. May be used as a web service. Come in two types: –Stateless session beans (no memory between calls) purchase(severalIems,creditCardNo); –Stateful session beans (remember earlier calls) addToCart(item); purchase(creditCardNo);

22. 22 Session Bean Quiz Which session bean promotes loose coupling? –Stateless session beans (no memory between calls) purchase(severalIems,creditCardNo); –Stateful session beans (remember earlier calls) addToCart(item); purchase(creditCardNo); Answer: Stateless session beans.

23. 23 Implementing Entity and Session Beans Define the component interfaces –The remote interface specifies how the outside world can access the bean’s business methods –The remote home interface specifies how the outside world can access the bean’s life-cycle methods (for creating, removing and finding) –The local interface specifies how the inside world (same EJB container) can access the bean’s business methods –The local home interface specifies how the inside world can access the bean’s life-cycle methods EJB 3.0 Makes this process much easier.

24. 24 Message-Driven Beans (1) Work in cooperation with Java Messaging System (JMS). JMS is an abstraction API on top of Message- Oriented Middleware (MOM) – like JDBC is an abstraction API on top of SQL databases or like JAXR is an abstraction API on different types of XML registries or like JNDI is an abstraction API on directories. Each MOM vendor implements things differently. MDB’s allow the developer to program using the publish-subscribe messaging model based on asynchronous, distributed message queues. The MOM vendor need only provide a service provider for JMS (IBM’s MQSeries or Progress’ SonicMQ).

25. 25 Message-Driven Beans (2) Are like session beans. Have no persistent state. Coordinate tasks involving other session beans or entity beans. Listen for asynchronous messages. Unlike Session beans, provide no remote interface describing the methods that can be called.

26. 26 Message-Driven Beans (3) Are receivers of MOM messages coming through the JMS API. Usually take action when a message is received. Unlike session and entity beans, Message-Driven Beans expose no remote or local view. They are not called directly by a client.

27. 27 Message-Driven Bean (4) Has no local, local home, remote, or remote home interfaces to define. The container will call the onMessage() method when an asynchronous message arrives. (Like JAXM message provider.) Extends the EnterpriseBean class and implements the javax.ejb.MessageDrivenBean and javax.jms.MessageListener interfaces

28. 28 Message-Driven Bean (5) Two basic messaging-system models (1) point-to-point model allows messages to be sent to a message queue to be read by exactly one message consumer. (2) publish/subscribe model allows components to publish messages on a topic to a server to be read by zero or more subscribers. Subscribers register for a topic.

29. 29 In Both Messaging Models The messages hold: -- a header containing the destination and the sending time. -- message properties to allow the receiver to select which messages they would like to receive. These may be set by the sender. -- the message body itself.

30. 30 Point-to-point on the Client Side import javax.jms.*; QueueConnection qCon; QueueSession qSes; QueueSender qSen; Through JNDI get access to a QueueSender. Build messages and send them to the queue. The queue is responsible for transporting the message to another queue on the server.

31. 31 Point-To-Point on the Server Side import javax.jms.*; QueueConnection qCon; QueueSession qSes; QueueReceiver qRec; Through JNDI get access to a QueueReceiver. Build a MessageListener with an onMessage method.

32. 32 Message Driven Beans (6) Handles asynchronous messages. Normally acts as a JMS message listener. The message may have originated from an application client, another enterprise bean, a web component or a non-Java application that can generate messages. Like a stateless session bean but with no interfaces. All operations within onMessage may be in a transaction context.

33. 33 From Sun

34. 34 On The Client // locate the connection factory and queue connectionFactory = (ConnectionFactory) jndiContext.lookup ("java:comp/env/jms/MyConnectionFactory"); destination = (Queue) jndiContext.lookup("java:comp/env/jms/QueueName");

35. 35 // Next, the client creates the queue connection, session, and sender: connection = connectionFactory.createConnection(); session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); messageProducer = session.createProducer(destination); // Finally, the client sends several messages to the queue: message = session.createTextMessage(); for (int i = 0; i < NUM_MSGS; i++) { message.setText("This is message " + (i + 1)); System.out.println("Sending message: " + message.getText()); messageProducer.send(message); }

36. 36 JMS Message Types(1) The Message Body Contains: TextMessage A java.lang.String object (for example, an XML document). MapMessage A set of name/value pairs, with names as String objects and values as primitive types in the Java programming language. The entries can be accessed sequentially by enumerator or randomly by name. The order of the entries is undefined.

37. 37 JMS Message Types(2) BytesMessage A stream of uninterpreted bytes. This message type is for literally encoding a body to match an existing message format. StreamMessage A stream of primitive values in the Java programming language, filled and read sequentially. ObjectMessage A Serializable object in the Java programming language.

38. 38 Listening to the Queue public void onMessage(Message inMessage) { TextMessage msg = null; try { if (inMessage instanceof TextMessage) { msg = (TextMessage) inMessage; System.out.println("MESSAGE BEAN: Message received: " +msg.getText()); } else { System.out.println("Message of wrong type: " + inMessage.getClass().getName()); } } catch (JMSException e) { e.printStackTrace(); mdc.setRollbackOnly(); } catch (Throwable te) { te.printStackTrace(); } }

39. 39 Web Services A Web service client can access Java EE applications in two ways. First, the client can access a Web service created with JAX-RPC. Behind the scenes, JAX-RPC uses a servlet to implement the SOAP Web Service. Second, a Web service client can access a stateless session bean through the service endpoint interface of the bean. Other types of enterprise beans cannot be accessed by Web service clients.

40. 40 A Stateless Session Bean as a Web Service The client need not know that its interacting with a Java EJB. It calls the bean like it calls any other web service. Thus,.NET interoperates with Java EE using XML on the wire.

41. 41 The Web Service Endpoint Interface package helloservice; import java.rmi.RemoteException; import java.rmi.Remote; public interface HelloIF extends Remote { public String sayHello(String name) throws RemoteException; } The client cannot see that it’s interacting with an EJB

42. 42 The Web Service Session Bean package helloservice; import java.rmi.RemoteException; import javax.ejb.SessionBean; import javax.ejb.SessionContext; public class HelloServiceBean implements SessionBean { public String sayHello(String name) { return "Hello " + name + "from HelloServiceEJB"; } public HelloServiceBean() {} public void ejbCreate() {} public void ejbRemove() {} public void ejbActivate() {} public void ejbPassivate() {} public void setSessionContext(SessionContext sc) {} } If we added remote and home Interfaces then this bean could also be called using in the traditional manner – with remote references. No change to the bean would be necessary. WSDL can be generated and all of the previous clients will work.