Information systems modelling UML and service description languages

Transcription

1 Internet Engineering Tomasz Babczyński, Zofia Kruczkiewicz Tomasz Kubik Information systems modelling UML and service description languages

2 I. Design patterns used to build the Integration Tier D.Alur, J.Crupi, D. Malks, Core J2EE. Desin Patterns 1. The definition of the IntegrationTier a fivetiered model of logical separation of tasks 2. Basic Integration Tier design issues 3. Bad practices when designing the Integration Tier 4. Analysis of basic design issues

3 Design patterns used to build the Integration Tier D.Alur, J.Crupi, D. Malks, Core J2EE. Desin Patterns 1. The definition of the IntegrationTier a fivetiered model of logical separation of tasks

4 MultitieredInformationSystem by D.Alur, J.Crupi, D. Malks, Core J2EE. Desin Patterns Client Tier Customer applications, applets, elements of the graphical user interface Presentation Tier JSP Pages, servlets, and other user interface elements Business Tier EJB components and other business objects Integration Tier JMS, JDBC, connectors and connections with external systems Resource Tier Databases, external systems and other resources Interacting with the user, device and user interface presentation Login, session management, content creation and delivery, formatting and validation Business logic, transactions, data and services Resource adapters, external systems, mechanisms for resource, control flow Resources, data and external services

5 EIS (Enterprise Information System) Tier (Tutorial Java EE 5) Application Client And Optional JavaBeans Components Web Browser, Web Pages, Applets, and Optional JavaBeans Components Client Tier JavaBeens Components (Optional) Web Pages Servlets Web Tier Java Persistence Entities Session Beans Message-Driven Beans Business Tier Java EE Server Database and Legacy Systems EIS Tier

6 Design patterns used to build the Integration Tier D.Alur, J.Crupi, D. Malks, Core J2EE. Desin Patterns 1. The definition of the IntegrationTier a fivetiered model of logical separation of tasks 2. Basic Integration Tier design issues

7 Basic issues of Integration Tier design 1. Managing access to data 2. Managingconnections to a database -the poolcalls

8 Managing access to data(1) Data access code is embedded in the PresentationTieror Business Tier, which is used for other purposes such as: Servlet, EJB component As a result, these classes are occupied withadditional functions, performanceand scalability. It would be better to introducethe IntegrationTierand affectingplace the code to access data there. Data access code is located in a tier of integration, but does not cache the resultsobtained during the various accesses to databases. If you need to increase scalability and improve performance, cache processing resultsin a database, avoiding duplication of operations directly at the database level.

9 Managing access to data(2) Data access code is extractedfrom the classes that are used to meet other objectives Data access code should be placed logically and physically closer to a datasource Any class Any class Code of Data Access Data Bases Code of Data Access Data Bases Client, Presentation or Business Tier Resource Tier Client, Presentation or Business Tier Integration Tier Resource Tier

10 Manage connections to a database - the pool calls Database connections are not shared, which decreases performance and scalability. The pool of shared connections improves performance and scalability DAO Active connections DAO Connections returned to connection pool Active connections DAO Data Bases DAO Data Bases DAO Used active connection DAO Used active connection Client, Presentation or Business Layer Resource Layer Client, Presentation or Business Layer Resource Layer

11 Design patterns used to build the Integration Tier D.Alur, J.Crupi, D. Malks, Core J2EE. Desin Patterns 1. The definition of the IntegrationTier a fivetiered model of logical separation of tasks 2. Basic Integration Tier design issues 3. Bad practices when designing the Integration Tier

12 Bad practices Performing data validation Datastructures from PresentationTierare available Datastructures from BusinessTiersare available Sharing the Presentationand BusinessTiersof objects an active connection to the database Direct integration of exception handling in the tiersof the presentation and business To transmit data between Presentationand BusinessTiersand the tier of integration is not used auxiliary object class No encryption of sensitive data

13 Design patterns used to build the Integration Tier D.Alur, J.Crupi, D. Malks, Core J2EE. Desin Patterns 1. The definition of the IntegrationTier a fivetiered model of logical separation of tasks 2. Basic Integration Tier design issues 3. Bad practices when designing the Integration Tier 4. Analysis of Basicdesign issues

14 Design cases 1. Hiding data access logic in a separate tier 2. Separationof persistence mechanisms from the object model 3. Asynchronic calls of services 4. Facility of access to services by using the XML Langugew and internet protocols

15 Problem1 Hiding data access logic in a separate tier. Data Access Object Servlets and JSP with presentation logic and controller to separate layers Session Component with business logic Data Acces logic with direct accesss to databases Client Servlets, JSP Business Delegate 1 Session Component Code of Data Access Data Base Client Tier Presentation Tier Business Tier Integration Tier Resource Tier Architecture of information system relational or object-oriented database, LDAP, file system, repository XML

16 Requirements You needto implement data access mechanismsto retrieve and modify data in the permanent storage The persistent storage system should be separated from the rest of application -itdoesnot disclose exceptions, data structures, objects related to types of sql libraries Youshould create anuniform interface to access datastored in various sources for example. in RDBMS, LDAP, OODB, XML repository, flat file Data access logics should be organized and data access functions should be hiddenin one location toachieve greater portability and ease of maintenance code It can be stateless It does not cache data obtained during data collection

17 Implementation Custom data access object Data Access Factory A collection of transfer objects Buffered collection of lines Collection of read-only lines Wrapper List (Wrapper Rowset List)

18 Result Hides data access Createsobject-orientedmechanisms for data access and conceals of database schemas Facilitates data migration by replacing the DAO Tier Reduces the complexity of client code Introduces an additional tier Putsall the data access code inside a separate tier A design requires a hierarchy of classes Introducescomplexity for the use of object-oriented data access methods

19 implements the CRUD operations relational or objectoriented database, LDAP, file system, repository XML result of a query

20 Download data

21 Insert data

22 Update data

23 Delete data

24 Problem 2 The separation of persistence mechanisms from the object model. Domain Store Possible solutions of persistence mechanisms No object model exists-a solution to the problem 1 Persistence mechanism is implemented in containers, which are objects of "entity" (strategy-cmp Container-Managed Persistence) - no inheritance in the object model Persistence mechanism is implemented at the premises of "entity" (strategy BMP -Bean-Managed Persistence);code of persistence mixed with the object model (no inheritance) The mechanism of persistence is placed in the object model of "entity" - code of persistence mixed with the object model The mechanism of persistence is separated from the object model of "entity" based on all object-oriented patterns

25 Model of BusinessTierbasedon 2, 3, 5 solutionsof persitsence C lie n t Se ssio n F a c a de as Se ssio n F a cad e B u sin ess lo gic T ra nsa c tio n L ogic m a na g ed by Se ssio n C o m pon e nt, s pe cia l com pon en ts Co m pon e nt E nti ty A C o m p o ne nt E n tity B Co m pon e nt E nti ty C C lie nt or P re sen ta tion Tie r o r C o n te ne r B usin e ss T ier

26 Architecture of 5-tiered information system Servlets and JSP with presentation logic and controller to separate layers Session Component with business logic, Entity Components as persistence transaction objects Data Acces logic with JPA accesss to databases Client Servlets, JSP Business Delegate 1 Session Component Entity Component Code of Data Access Data Base Client Tier Presentation Tier Business Tier Integration Tier Resource Tier

27 Requirements Implementation of persistencemechanisms in business objects such as "entity "shouldbe avoided It should be refrainedfrom objects of type "entity"that use the persistence mechanisms of the container. The application can run in a web container. Object models use inheritance and complex relationships. The mechanism of persistence can be realized in two ways: make your own skeleton of persistence or use a out-of-boxsolutions based on JDO or own O-R solutions,

28 Implementation Custom implementation of persistence Downloading of the on-demand JDO (Java Data Object) Result Create custom implementation of persistence is a complex task Loading and saving multi-level tree of objectsrequires optimization Allows you to better understand the mechanisms of persistence principles Advanced mechanisms for persistence may be too powerful for a simple object model Facilitated testing of object model Separation of business object modelfrom the persistence logic

29 Business Tier Data model

30 Create and persist business object

31 Download data

32 Create and perform the Query

33 II. Exampleof multitieredwebapplication 1. Two examples of architectures of the multitiered application as the Visual Web Java Server Pages applications 2. The Visual Web Java Server Pages application based on synchronization data by application 2.1. Structure of project 2.2. Business Service Subtier 2.3. Application Service of Business Tier 2.4. Integration Tier 2.5. Presentation Tier

34 Exampleof multitieredwebapplication 1. Two examples of the architectures of the multitieredapplicationas thevisual Web Java Server Pages applications

35 JavaServer Faces Standard Request-Response Life Cycle

36 Data base Library Directory Exampleof thearchitectureof webapplicationbasedon synchronization data by databases(1) Integration Layer (EntityManager, ) TopLink Gof and Sun Patterns: Domain Store Transfer Object Facade (XXXController) Factory Integration Layer (EntityManager, ) TopLink Gof and Sun Patterns: Domain Store Transfer Object Facade (XXXController) Factory Integration Layer (EntityManager, ) TopLink Gof and Sun Patterns: Domain Store Transfer Object Facade (XXXController) Factory Resource Tier Integration Tier Object Model Gof Patterns: Facade: TFacade Factory: TFactory Flyweight: TTitle_book Object Model Gof Patterns: Facade: TFacade Factory: TFactory Flyweight: TTitle_book Object Model Gof Patterns: Facade: TFacade Factory: TFactory Flyweight: TTitle_book Business Tier ApplicationBean1 Application Service Sun pattern SessionBean1 Session Facade Sun pattern SessionBean1 Session Facade Sun pattern SessionBean1 Session Facade Sun pattern JSF Pages JSF Pages JSF Pages Presentation Tier Client1 Client2 Client3 Client Tier

37 Architectureof webapplicationbasedon synchronization data by databases(2) many clientsof theclienttieras thewwwpages many JSF pagesof thepresentationtier eachclienthasown pages many Session Facade Components of the Business Tier (SessionBean1) as remotefacadesof thebusiness Service Subtier(Java Application project) based on the POJO objects eachclienthasownsessionbean1and theownbusiness Service Subtier own Domain Store Components of the Integration Tier

38 Exampleof thearchitectureof webapplicationbasedon synchronization data by application(1) Data Base Library Directory Integration Layer (EntityManager, ) TopLink Gof and Sun Patterns: Domain Store Transfer Object Facade (XXXController) Factory Resource Tier Integration Tier ApplicationBean1 Application Service Sun pattern Object Model Gof Patterns: Facade: TFacade Factory: TFactory Flyweight: TTitle_book Business Tier SessionBean1 Session Facade Sun pattern SessionBean1 Session Facade Sun pattern SessionBean1 Session Facade Sun pattern JSF Page JSF Page JSF Page Presentation Tier Client1 Client2 Client3 Client Tier

39 Architectureof webapplicationbasedon synchronization data by application(2) many clientsof theclienttieras thewwwpages many JSF pagesof thepresentationtier eachclienthasown pages common Application Service Component of the Business Tier (ApplicationBean1) as theremotefacadeof thebusiness Service Subtier(Java Application project) basedon thepojo objects eachclientusesthecommonapplicationbean1 common Domain Store Components of the Integration Tier

40 Exampleof multieredwebapplication 1. Two examples of architectures of the multitiered applicationas thevisual Web Java Server Pages applications 2. The Visual Web Java Server Pages application based on synchronization datas by application 2.1. Structure of project

41 Integration Tier: Facades of Domain Store Business Tier: Business Service Subtier as Application Service with Object model Presentation Tier: JSF pages Business Tier: Application Service

42 Presentation Tier Business Tier: Session Façade Application Service

43 Classes of Presentation Tier Business Tier Integration Tier

44 Exampleof multitieredwebapplication 1. Two examples of architectures of the multitiered applicationas thevisual Web Java Server Pages applications 2. The Visual Web Java Server Pages application based on synchronization datas by application 2.1. Structure of project 2.2. Business Service Subtier

45 Classes of Business Service Subtier

46 Facade of Business Service Subtier as POJO class (1): business logic methods of subtier

47 Facade of Business Service Subtier as POJO class (2): business logic methods of subtier

48 Facade of Business Service Subtier as POJO class (3): summarization of business logic

49 Example of Entity class from Object Model of Business Service Subtier (1): Persistence Annotation

50 Example of Entity class from Object Model of Business Service Subtier (2): business logic methods

51 Exampleof multitieredwebapplication 1. Two examples of architectures of the multitiered applicationas thevisual Web Java Server Pages applications 2. The Visual Web Java Server Pages application based on synchronization datas by application 2.1. Structure of project 2.2. Business Service Subtier 2.3. Application Service of Business Tier

52

53 remote method for methods of Business Service Subtier binding data of JSF Component

54 Exampleof multitieredwebapplication 1. Two examples of architectures of the multitiered applicationas thevisual Web Java Server Pages applications 2. The Visual Web Java Server Pages application based on synchronization datas by application 2.1. Structure of project 2.2. Business Service Subtier 2.3. Application Service of Business Tier 2.4. Integration Tier

55 Example of Controller class as Facade of Integration Tier

56 Tables generated from Entities of Object Model of Business Service Subtier by Domain Store Components of Integration Tier

57 Exampleof multieredwebapplication 1. Two examples of architectures of the multitiered applicationas thevisual Web Java Server Pages applications 2. The Visual Web Java Server Pages application based on synchronization datas by application 2.1. Structure of project 2.2. Business Service Subtier 2.3. Application Service of Business Tier 2.4. Integration Tier 2.5. Presentation Tier

58

59 Links to other pages of web application

60

61 addtitle_action

62 Method of www response Method of event: the click of the addtitle button

63 Methods the FragmentBox Component as the subview of the Titles form view

64

65 storetitle_action

66 Method of www response Method of event: the click of the storetitle button