Embed Size (px)
Citation preview
How to build Composite Application How to build Composite Application How to build Composite Application How to build Composite Application
AgendaAgendaAgendaAgenda
Why do we need composite Application Base object Composite Object Composite application Obstacles Solution principles
Why do we need composite Why do we need composite Applications Applications Why do we need composite Why do we need composite Applications 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
Base Object Base Object Base Object Base Object
encapsulate relevant process as components
Composite ObjectsComposite ObjectsComposite ObjectsComposite 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
Encapsulation of Legacy Process Encapsulation of Legacy Process into WS/J2EE/.NETinto WS/J2EE/.NETEncapsulation of Legacy Process Encapsulation of Legacy Process into WS/J2EE/.NETinto WS/J2EE/.NET
Composite Application Composite Application Composite Application 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
ObstaclesObstaclesObstaclesObstacles
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…)
Solution principlesSolution principlesSolution principlesSolution 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
