Presentation is loading. Please wait.

Presentation is loading. Please wait.

How to build Composite Application AgendaAgenda  Why do we need composite Application  Base object  Composite Object  Composite application  Obstacles.

Similar presentations


Presentation on theme: "How to build Composite Application AgendaAgenda  Why do we need composite Application  Base object  Composite Object  Composite application  Obstacles."— Presentation transcript:

1

2 How to build Composite Application

3 AgendaAgenda  Why do we need composite Application  Base object  Composite Object  Composite application  Obstacles  Solution principles

4 Why do we need composite Applications  In every organization we can find variety of: home made, packages and vertical applications. (HR, financial app, inventory…)  Solutions were based on specific technologies and sometimes on different hardware systems.  Today organizations are looking for ways to maximize the value of all those technologies and applications  Most of business processes that are needed today, already been implemented with the organization systems  For example: merger of few insurance companies with CRM systems, would like to enable one point of customers support

5 Base Object  encapsulate relevant process as components

6 Composite Objects  Base objects are the building blocks for Composite objects  Different flow of base objects creates different Composite objects  Example: credit card application encapsulate the private base object and the company base object into single composite object

7 Encapsulation of Legacy Process into WS/J2EE/.NET

8 Composite Application  A new application based on: Existing business logic (internal web services/com objects/J2EE) External web services (exposed by other organizations) Other data resources (ODBC/JDBC) New business logic

9 ObstaclesObstacles  Most of large organizations assets do not have standard API to be exposed  Heterogeneous environments (MF, Unix, MS, J2EE…)  Time to market is critical parameter  Huge risk in changing existing applications  There are business rules that can’t be re-write (banking, insurance…)

10 Solution principles  Composite application should be based only on standard tools, follows the organization strategic decisions (J2EE/.NET/COM)  The composite objects/Applications should be defined and kept as abstract definition  This abstraction layer creates separation between the origin and the new application technologies  This layer helps the new developer to be free from having the skills of previous technologies and applications

11 Thank You orna@sabratec.com


Download ppt "How to build Composite Application AgendaAgenda  Why do we need composite Application  Base object  Composite Object  Composite application  Obstacles."

Similar presentations


Ads by Google