240 likes | 351 Views
Ebusiness Infrastructure Platform. Server acting as Integration Broker. Client. Client. Data 2. Data 2. Data 1. Data 1. Logic 1. Logic 2. Logic 1. Logic 2. Executive Summary. Requirement : enable a distributed application environment
E N D
Server acting as Integration Broker Client Client Data 2 Data 2 Data 1 Data 1 Logic 1 Logic 2 Logic 1 Logic 2 Executive Summary • Requirement: enable a distributed application environment • Challenge: enable scattered stovepipe applications to work harmoniously across an extended enterprise • Reality: Servers act as integration broker to provide network-based integration services • The big idea: Network becomes the “Virtual Integration Server”
Agenda • Ebusiness Infrastructure Opportunities • Evolution to Ebusiness • Infrastructure Requirements • Infrastructure Platform Proposal
Ebusiness Opportunities Ebusiness Ebusiness-enabled Business-enabled Legacy Enterprises Internet Enterprises
Applications Logic Data Application Connectivity Network Connectivity Infrastructure Infrastructure Users Ebusiness Infrastructure Components Focus of the Infrastructure Platform
Ebusiness Infrastructure Deployment • Enterprise Data Centers • Internet Data Centers • Exchanges • Application Service Providers
Agenda • Ebusiness Infrastructure Opportunities • Evolution to Ebusiness • Infrastructure Requirements • Infrastructure Platform Proposal
Data Data Data Shipment Process Invoice Process Order Process Logic Logic Logic Legacy Enterprises - Stovepipe Each Business Process has its own App. (Logic and Data)
Data Data Data Shipment Process Invoice Process Order Process Logic Logic Logic Application Integration WEB-based Front-office Application Phase 1 Driver - Web-enabled Enterprise Increased Market Share
Data Data Data Shipment Process Invoice Process Order Process Logic Logic Logic Application Integration WEB-based Front-office Application Process Automation Phase II Driver - Lights-out Enterprise Enhanced Customer Satisfaction
Data Data Data Data Data Shipment Process Partner Process Invoice Process Partner Process Order Process Logic Logic Logic Logic Logic Application Integration Process Automation WEB-based Front-office Application Phase III Driver - Virtual Enterprise Improved Business Performance Partner Integration
Today Phase II Phase III Phase I • Unintegrated Business processes • Uncoordinated applications • Uncontrolled proliferation of data views • What • Web-enabled Enterprise • Why • Increased Market Share • How • Integrate Web front-end with legacy back-end app. • What • Lights-out Enterprise • Why • Enhanced Customer Sat • How • Synchronize business events • Automate workflow • What • Virtual Enterprise • Why • Improved Business Performance • How • Externalize business processes • Integrate with partners’ business processes Stove-pipe Integrate Applications Automate Business Processes Integrate Partners Infrastructure for Ebusiness-enablement
Agenda • Ebusiness Infrastructure Opportunities • Evolution to Ebusiness • Infrastructure Requirements • Infrastructure Platform Proposal
Infrastructure Services Requirements • Application Integration Technologies • Object Brokers (CORBA) • Connectors/Adapters • Information Brokers • Message Transport • Process Automation Technologies • Process Modeling (development tools and not deployment tools) • Publish/Subscribe • Event Management and Synchronization • Workflow Routing • Partner Integration Technologies • “Public” Process Integration • EDI • XML Vocabulary (Rosettanet, BizTalk, BPF, FML)
Ebusiness Infrastructure - The Big Idea Old WorldNew World Application Model Client-Server Network Network Role Packet Routing Application Routing Network Services Layers 1-3 API Security Object Switching Policy Information Switching Event Management Workflow Routing “Public” Process Integration
Agenda • Ebusiness Infrastructure Opportunities • Evolution to Ebusiness • Infrastructure Requirements • Infrastructure Platform Proposal
Ebusiness Infrastructure Platform Vision Transform the Network Utility from a Packet Routing Infrastructure to a Distributed Business Application Environment
Old WorldNew World Client-Server Network Packet Routing Application Routing Layers 1-3 API Security Object Switching Policy Information Switching Event Management Workflow Routing “Public” Process Integration Application Services Module • Application Integration • API • Object Switching • Information Switching • Process Automation • Event Management • Workflow Routing • Partner Integration • “Public” Process Integration Application Switch Open Interface Network Switching Module • Fanout • Physical Interface • WAN, MAN, Campus, LAN • Routing, Switching, Bridging, Multicast, Security, Policy Ebusiness Infrastructure Platform
New Application 2 Directory (Namespace)Services New Application 1 New Data Legacy Application 2 Legacy Application 1 Legacy Data Application Integration Application Workflow Sequence Public Process Integration Partner Services Industry Exchange Internet Procurement Application Partner Application 2 Partner Application 1 HPA for Ebusiness Infrastructure Ebusiness Process • High-performance • Traffic Mgmt • Multicast • Firewall • Encryption • Policy Enforcement Auto Network Switching Switching
Internet Intranet Application Services Campus Switch Application Services WAN Switch WAN Switch Campus Switch Campus Switch Partner WAN Switch Application Services WAN Switch Application Services Service Provider Ebusiness Infrastructure Platform Deployment Extranet Site
Application Services Module • Application Integration • API • Object Switching • Information Switching • Process Automation • Event Management • Workflow Routing • Partner Integration • “Public” Process Integration Open Interface Network Switching Module • Fanout • Physical Interface • WAN, MAN, Campus, LAN • Routing, Switching, Bridging, Multicast, Security, Policy Implementation Framework for Reuse & TTM • Industry-standard Platform such as Java • Optimized to integrate 3rd party products • Optimized for flexible software implementation • Optimized for real-time performance
Application Services Module • Application Integration • API • Object Switching • Information Switching • Process Automation • Event Management • Workflow Routing • Partner Integration • “Public” Process Integration Open Interface Network Switching Module • Fanout • Physical Interface • WAN, MAN, Campus, LAN • Routing, Switching, Bridging, Multicast, Security, Policy Implementation Framework for Reuse & TTM • XML and Java based interface to easily integrate 3rd party implementation • Interface for management • Interface for dynamic configurability
Value Proposition of the Application Switch • Distributed applications are supported by “integration services” at the points of entry into the network • Application Switching occurs at the network entry as opposed to a remote server resulting in better application performance • Integration services are available to all all entities attached to the network utility • Application developers can focus on business logic and data as opposed to configuring networking functions in the servers • Network-switching functions and application services functions are closely coupled • Application switching can gain the same performance levels as the networking gear
Next Steps • Subject to approval to go head • Team structure • Decision on platforms on which Application Switch is based • Prioritization of activities • Architectural Work • Product Phasing • What to build, What to buy, where to partner, etc