EJB is the Sun's server-side component model, and the most useful is deploying distributed applications. With the advantages of Java Cross-platform, distributed systems deployed with EJB technology can be limited to a specific platform. The EJB 3.0 specification makes EJB development easier and more popular with enterprise-class users. With more support for EJB 3.0 and EJB 2.1 in WebSphere Application Server 7.0, users can easily publish their SCA services as an EJB service via the WPS 7 new features EJB export binding Without the programmer doing a series of cumbersome EJB development. This article combines the development tools in WebSphere WID 7 with a concrete example step-by-step instruction on how to develop the EJB export binding service, while introducing EJB B in WebSphere Process Server 7 Inding related new features. I believe this article will be helpful for programmers who are ready to use EJB to publish their SCA services.
Introduction
EJB is the Sun's server-side component model, and the most useful is deploying distributed applications. With the advantages of Java Cross-platform, distributed systems deployed with EJB technology can be limited to a specific platform. The EJB 3.0 specification makes EJB development easier and more popular with enterprise-class users.
WebSphere Application Server 7.0 provides more support for EJB 3.0 and EJB 2.1, which makes it easy for users to publish their SCA services as an EJB service through the new features of the WPS7 version of EJB export binding Without the programmer doing a series of cumbersome EJB development. The WPS7 version supports Remote and local two EJB interfaces, follows the EJB3.0 and EJB2.1 two specifications, and users can use the corresponding EJB services according to their business needs. Based on the typical business requirements of domestic enterprise application, this paper, by implementing a simple EJB echo SCA service called by Dynamic Web client, teaches readers how to use WID7 to develop the EJB export binding service, and at the end of this paper also describes how to run To configure and view the EJB service-related properties deployed, and finally to summarize the new features associated with EJB export binding in Websphere Process Server 7.
EJB Service Scenario Description
The scenarios used in this article are quite typical. It consists of a serviced component Architecture (Service Component Architecture,sca) module that contains a Java component that will be published through EJB3.0 export binding as a EJB3.0 ser Vice. In this case, we will build an Echo system, the user in the terminal interface input customer ID and customer address and other related information, after entering the EJB service, the system will print its input information to the terminal interface and return the corresponding customer object. The system architecture is illustrated as follows:
Figure 1. EJB Service System Architecture diagram