Method-Oriented B2B Application Integration Chapter 4 Sungchul Hong.

Slides:



Advertisements
Similar presentations
MicroKernel Pattern Presented by Sahibzada Sami ud din Kashif Khurshid.
Advertisements

Object-Oriented Application Frameworks Much of the cost and effort stems from the continuous re- discovery and re-invention of core concepts and components.
3 Copyright © 2005, Oracle. All rights reserved. Designing J2EE Applications.
When is Orientated Programming NOT? Mike Fitzpatrick.
COM vs. CORBA.
WEB SERVICES DAVIDE ZERBINO.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 12Slide 1 Software Design l Objectives To explain how a software design may be represented.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 12 Slide 1 Distributed Systems Design 2.
Ch 3 System Development Environment
CORBA - Common Object Request Broker Architecture.
Distributed components
Chapter 17: Client/Server Computing Business Data Communications, 4e.
Portal-Oriented B2B Application Integration Chapter 5 Sungchul Hong.
Sapana Mehta (CS-6V81) Overview Of J2EE & JBoss Sapana Mehta.
CS 501: Software Engineering Fall 2000 Lecture 16 System Architecture III Distributed Objects.
Service Oriented Application Integration (SOAI) IT 490 NJIT.
Object-Oriented Databases
Ch 12 Distributed Systems Architectures
Component Based Systems Analysis Introduction. Why Components? t Development alternatives: –In-house software –Standard packages –Components 60% of the.
Visual Basic Introduction IDS 306 from Shelly, Cashman & Repede Microsoft Visual Basic 5: Complete Concepts and Techniques.
Software Engineering Module 1 -Components Teaching unit 3 – Advanced development Ernesto Damiani Free University of Bozen - Bolzano Lesson 2 – Components.
About the Presentations The presentations cover the objectives found in the opening of each chapter. All chapter objectives are listed in the beginning.
Distributed Systems: Client/Server Computing
© 2001 by Prentice Hall8-1 Local Area Networks, 3rd Edition David A. Stamper Part 3: Software Chapter 8 Client/Server Architecture.
Visual Basic 6.0 Derived from BASIC Developed by Microsoft in 1998 An event driven programming language Associated with a development environment.
B2B Application Integration COSC643 Sungchul Hong.
The Design Discipline.
What is Architecture  Architecture is a subjective thing, a shared understanding of a system’s design by the expert developers on a project  In the.
An Object-Oriented Approach to Programming Logic and Design
Jaeki Song ISQS6337 JAVA Lecture 16 Other Issues in Java.
COM vs. CORBA Computer Science at Azusa Pacific University September 19, 2015 Azusa Pacific University, Azusa, CA 91702, Tel: (800) Department.
©Ian Sommerville 2000 Software Engineering, 6th edition. Slide 1 Component-based development l Building software from reusable components l Objectives.
Enterprise JavaBeans. What is EJB? l An EJB is a specialized, non-visual JavaBean that runs on a server. l EJB technology supports application development.
Component Architecture (CORBA – RMI) -Shalini Pradhan.
1 Distributed Systems Distributed Objects & Remote Invocation II (CORBA VS DCOM) Dr. Sunny Jeong. With Thanks to.
1 Computing Fundamantals With thanks to Laudon & Laudon Session 2.
R R R 1 Frameworks III Practical Issues. R R R 2 How to use Application Frameworks Application developed with Framework has 3 parts: –framework –concrete.
ENTERPRISE APPLICATION INTEGRATION
Middleware for FIs Apeego House 4B, Tardeo Rd. Mumbai Tel: Fax:
Architectural Design Identifying system components and their interfaces.
5 - 1 Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
Frameworks CompSci 230 S Software Construction.
CS 501: Software Engineering Fall 1999 Lecture 12 System Architecture III Distributed Objects.
ProActive components and legacy code Matthieu MOREL.
An Introduction to Web Services Web Services using Java / Session 1 / 2 of 21 Objectives Discuss distributed computing Explain web services and their.
1 Lecture 3 Major Architectural Models View (Cont’d) Architectural Models/Patterns Architecture Case Study Software Architecture & Design Pattern.
TM 8-1 Copyright © 1999 Addison Wesley Longman, Inc. Client/Server and Middleware.
Lecture 21: Component-Based Software Engineering
A service Oriented Architecture & Web Service Technology.
1 CS 501 Spring 2002 CS 501: Software Engineering Lecture 15 System Architecture III.
Dr D. Greer, Queens University Belfast ) Software Engineering Chapter 7 Software Architectural Design Learning Outcomes Understand.
Database Architectures and the Web
Common Object Request Broker Architecture (CORBA)
N-Tier Architecture.
Introduction to Design Patterns
The Improvement of PaaS Platform ZENG Shu-Qing, Xu Jie-Bin 2010 First International Conference on Networking and Distributed Computing SQUARE.
PRINCIPALES OF OBJECT ORIENTED PROGRAMMING
Inventory of Distributed Computing Concepts and Web services
3 Cloud Computing.
Component--based development
Object Oriented Programming
WEB SERVICES DAVIDE ZERBINO.
Chapter 1: The Database Environment
The Database Environment
Quality Assurance for Component-Based Software Development
SOFTWARE DEVELOPMENT LIFE CYCLE
Chapter 6: Architectural Design
OBJECT STORAGE AND INTEROPERABILITY
Types of Application Integration
Service-Oriented Application Integration
Presentation transcript:

Method-Oriented B2B Application Integration Chapter 4 Sungchul Hong

Method-Oriented B2B Application Integration Share common business logic or methods Defining methods that can be shared Providing the infrastructure for such method sharing. Hosting methods on a central server Accessing methods inter-application (distributed objects)

Sharing Processes Multitier client/server –A set of shared services on a common server that provided the enterprise with the infrastructure for reuse and integration. Distributed object movement Reusability (objective) Expand intra-enterprise sharing to trading partners Sharing common logic to process credit requests

Characteristics This method requires changes in application. Invasive B2B application integration. Political problems

Advantages and Disadvantages Share business logic allows integration of application. Efficiency Expense of implementation, testing, and redeployment of application

When to leverage Method- Oriented B2B Application Integration When two or more companies need to share common program logic. When two or more companies wants to share the development costs and the value of a common application. When the trading community is small and specialized and is able to collaborate on a common application that all companies share.

Example Simple binding One application is C++ based and runs on a Linux. The other is an NT-based client/server application written in Java on the front-end, with Sybase serving as the back-end database.

Example – cont. 1. Move much of the business logic to a shared server (application server) 2. Rebuild each application using a method- sharing mechanism ( distributed object technology like CORBA, COM+) It allows easy cross-accessing of methods. Use tools

System Development Understand all the processes, methods, and programs that exist within the enterprise. Break the process down to their scenarios. –Rules, logic, data, and obkects

Rules A rule is an agreed-upon set of conditions –Travel reimburse rules Control the flow of information. –Inside of the organization –Trading partners These rules will become accessible to manu applications

Logic Logic is a sequence of instructions in a program. –Sequential processing –Iteration –Selection

Data Data is sharing information between trading partner applications. Objects –Data –Methods

Method Warehousing Identifies the methods Centralized entity (like data warehouse) Remotely invoking processes, or methods, for any application. Integrate all enterprise applications between trading partners. –Tax law changes  changes automatically propagate to all lined applications –Expense  method warehouse + change all applications

Framework Consist of abstract classes and their object collaboration as well as concrete classes. Many definitions Shared objects and processes Provide the infrastructure for sharing methods

The Value of Frameworks Ability to reuse existing code Contains rebuilt objects Objects can be shared among many applications Reuse code throughout an industry Pre-designed and pre-tested application architectures Problem: incompatibility among frameworks, cost

Framework Functionality Pre-built subsystems, architecture, and code –Inheriting, customizing by adding set of classes Components come with interface not code. –Change their look, feel, behavior by altering their properties. Object frameworks work with other frameworks. Object frameworks generally provide access to their services through APIs. Provide complete framework

Framework Types Object frameworks are made up of both abstract and concrete classes. –Encapsulation, polymorphism, inheritance, and abstraction Service frameworks –Distributed object framework –CORBA DCOM and COM Procedural frameworks –Black box

Framework Categories Application service frameworks –Encapsulate enterprise application functionality –GUI interface framework Domain frameworks –Certain problem domains –Common application architectures Support frameworks –Network support, device access