Application Integration - PowerPoint PPT Presentation

1 / 31
About This Presentation
Title:

Application Integration

Description:

Sales App. sends Credit Approval Request (CAR) Sales App. gets back Credit Approval Ack (CAA) E-mail notification to Sales Person ... – PowerPoint PPT presentation

Number of Views:90
Avg rating:3.0/5.0
Slides: 32
Provided by: Jagann
Category:

less

Transcript and Presenter's Notes

Title: Application Integration


1
(No Transcript)
2
Oracle 9iAS Application Integration Part-I
Prepared for IT620 February 25 , 2003
3
Talk Outline
  • Application Integration Overview
  • Types of Integration
  • Oracle 9iAS Integration Overview(9.0.4)
  • Pointers to More Information

4
Overview

5
What is a Application Integration?
  • The ability to link different types of enterprise
    applications and business processes together so
    that they can smoothly and effectively
    communicate to conduct e-business.
  • These applications can reside within a company's
    enterprise boundaries or across multiple company
    boundaries connected over the Internet.

6
Definitions
  • A2A is the integration of applications and
    business processes within an enterprise
  • B2B is the integration of a company's
    applications and business processes with external
    business systems operated by
  • Customers
  • Suppliers
  • Trading partners
  • Exchanges
  • Marketplaces
  • B2B extends A2A integration to the Internet

7
Why Application Integration (A2A) is needed?
  • Integration needs arise from business process and
    procedural redundancies created by
  • Existence of several independently developed
    applications within an enterprise dealing with
    different aspects of the same entities
  • Acquisitions and mergers (Health care, Phone
    companies, Banks http//www.snl.com/bank/manda/)

8
An Application Integration Example
Resource Management System (MCA Trainees, 2001)
KreSIT Services (M. Tech., 2002)
Teaching Assistant Allocation System (M.Tech.,
2001)
People Mgmt. System
Complaint Tracking System
KreSIT Folks
  • Two independently developed applications each
    having
  • individual PostgreSQL databases
  • Third under development

9
Integration Challenges
  • Different applications use different technologies
    and architectures.
  • Applications constantly evolve, thus complicating
    implementation and maintenance of application
    integration.
  • Costs and schedules are often difficult to
    predict.

10
Why B2B Integration is needed?
  • Virtual Dynamic supply chains
  • Customer relationship management (CRM)
  • Emerging Web services opportunities

11
Another Integration Example
Credit Approval Web service
2
Customer Relationship Management Customer DB
Sales Application Prospects DB
3
5
Sales person
4
1
  • Enter Prospective Customer
  • Sales App. sends Credit Approval Request (CAR)
  • Sales App. gets back Credit Approval Ack (CAA)
  • E-mail notification to Sales Person
  • Getting CAA should lead to addition of customer
    to Customer DB

12
Integration Questions
  • How long does it take to automate this scenario?
    Days or weeks or months?
  • How many products are required to model, deploy
    and monitor the solution? One or several?
  • How do you find out what the status of the
    overall process is? Are there predefined reports
    or do you have to code your reports yourself
    learning yet another programming language?
  • How much coding do you have to do? Do you code
    nothing or is it a full-blown engineering
    project?

13
Oracles Integration Strategy
  • Single product set
  • Modeling, no or only adapter specific code
  • Unified architecture for
  • Enterprise Application Integration
  • B2B integration
  • WebServices
  • Provide short-term long-term productivity

14
Types of Integration Solutions

15
Types of Integration Solutions
  • Data Integration
  • Function Integration
  • Process Integration
  • Event driven Business Process Integration

16
Data Integration Solutions
  • Address the need for providing a simple,
    integrated view of data from disparate systems
    and infrastructures
  • The guiding principle behind data integration is
    that the key asset of the enterprise is its data.

17
Data Integration Solutions
  • Common schema
  • Example payroll data in an Oracle DB and a
    Legacy DB
  • Typically done via Database replication
  • Global schema
  • Example Information in different DB with
    different schema, but need to present a global
    view
  • Typically done via Distributed Database System

18
Data Integration Solutions
  • Homogenous data integration
  • Example Integrating data between two applications
    or systems
  • Using Message Queues
  • Message Brokers add transformation, routing, and
    rule-based filtering to the integration
    capabilities
  • Heterogeneous data integration
  • Extract Transform Load
  • Data integration servers

19
Drawbacks of Data Integration Solutions
  • Does not capture the differences in application
    logic present in different applications
  • This can result an slightly different view of the
    data by the other application

20
Function (Application Logic) Integration Solutions
  • Integrates application logic as well as data
  • Leverages interfaces exposed by custom and
    packaged applications (e.g. SAPs BAPI)
  • Allows for tighter integration
  • Drawback Solution becomes complex as several
    applications are integrated

21
Process (workflow) Integration Solutions
  • Sequence of steps performed on data
  • Defining all the business operations pertaining
    to business processes in an organization helps IT
    understand the semantics of the integration
    independent of the endpoints of integration
  • This greatly increases the ability of the
    organization to provide solutions to integration
    needs in the future

22
Process (workflow) Integration Solutions
  • Process integration is agnostic to data format or
    semantics of end points of integration
  • Requires point-to-point integration between
    enterprise applications and the workflow solution
  • Developers usually hard-code process semantics
    between individual applications

23
Drawback of Process Integration Solutions
  • Difficult to change once deployed
  • Does not distinguish between behavior such as
    transformation, translation, validation, etc.
  • All are modeled as a sequence of activities

24
Event Driven Business Process Integration
Solutions
  • Event driven
  • Captures
  • Data Syntax (format)
  • Data Semantics
  • Captures
  • Semantics of Business Process
  • Integrates
  • Data
  • Business process

25
Oracle 9iAS Integration (9.0.4)

26
Oracle9iAS Integration Overview
  • All your events
  • Receiving a Purchase Order (PO)
  • Sending a credit approval requests
  • All your processes
  • Purchase processes (e.g. handle PO with amount gt
    10,000 differently)
  • Approval processes
  • Supply chain replenishment processes
  • All your end points (parties)
  • Like Backend Applications, Trading Partners, etc.

27
Oracle9iAS Integration contd..
  • Application integration
  • B2B integration
  • Business Process management
  • Lifecycle and configuration management
  • Transformation, translation and event validation
  • Correlation of events
  • Business activity monitoring

28
Oracle9iAS Approach
  • 9iAS integration
  • Meta model
  • Declarative language
  • Interpreted
  • Alternative
  • No model
  • Programming language
  • Technology components

29
Oracle9iAS Advantages
  • Single, integrated product that enables seamless
    Application and B2B integration
  • Modeled no or only adapter specific code
  • One tool to learn
  • Single relational normalized schema
  • Validation of integration before deployment
  • Reuse of data and process definitions
  • Easier to maintain integration

30
For more Information
  • Main Page http//otn.oracle.com/tech/integration/c
    ontent.html

31
(No Transcript)
Write a Comment
User Comments (0)
About PowerShow.com