Presentation on theme: "Architectures and Techniques for modern E-business Systems"— Presentation transcript:
1Architectures and Techniques for modern E-business Systems
2Agenda E-Business, E-Commerce, C-Commerce E-business Architecture Integration issues and solutionsE-business Integration PatternsebXML – the Newest Global StandardPositioningMain conceptsState of the ArtQuality of Business Service
3E-Business and E-Commerce The two concepts do not mean the sameThey are often confusedE-commerce is a part of E-business along with:InfrastructureCustomer Relationship Management (CRM)Business IntelligenceSupply Chain Management
4E-Business and E-Commerce E-commerce, or electronic commerce, is conducting business communications and transactions via computers and over networks. It is buying and selling of goods and services through digital communication. E-commerce also includes transactions on the World Wide Web and Internet, and modes such as electronic funds transfer, smart cards, and digital cash. Introduced around 1994 (Amazon.com).E-business, or electronic business, derived (the term) from 'e-commerce'. It is conducting business on the Internet, but not just buying and selling but also servicing customers and collaborating with business partners. The term conveys that the business conducts its business entirely online. Introduced around 1997 (IBM).
5E-business Systems Evolution Proprietary corporate solutionsEDI – E-business for the bigAd-hoc solutions using the InternetThe XML promise and realityThe need for E-business standardsebXML – the latest focal point of E-business standardisation efforts
6Collaborative Commerce Opening-up ERP systems and business application of SMEsIntegrating them into multi-enterprise collaborative commerce frameworkInteraction between businesses independent on size and geographical location
7It is All about Integration The High-Level Goals:Independence of business operations from underlying technologyFlexibilityEase of access for businesses of various sizeCost effectivenessInvestment protection
8Types of Integration (scope) With regard to integration scope there are two major classes:Enterprise Application Integration – EAITypically occurs within an enterpriseKnown as Application-to-Application – A2ABusiness-to-Business Integration – B2BiTypically used for inter-enterprise integrationKnown as Extended Enterprise
10Business Process Integration Commercial Products:TIBCOVitriaBEASybaseOracle...From
11E-business Integration Patterns Mentioned positioning of Integration types theoretically yields 3D classification matrixNot all combinations are equally viableMost frequently used proven approaches are referred to as patternsIBM did a good job describing E-business patterns
12E-business Integration Patterns The document exchange patternThe exposed applications patternThe exposed business services patternThe managed public processes patternThe managed public and private processes pattern
14Document Exchange Pattern Suited for partners replacing papers by electronic data interchangeData formats and communication channels must be agreed by partnersTight coupling between external and internal processesTypically batched processing – classic EDI
16Exposed Application Pattern Application tier exposed directly to the outside worldMessage Queuing or Component Framework as middlewareDirect coupling among partner applications leads to poor flexibility
18Exposed Business Services Pattern A layer between the backend enterprise system and partner tierThis layer exposes an e-business oriented interfaceBusiness service interface to be agreed by partnersWeb Services technology is an example
20Managed Public Process Pattern Private and Public processes are separated more strictlyPublic processes are identified, analysed and formally describedIntegration occurs at Business Process levelRosettaNet is an exampleTrading Partner Agreements TPA
22Managed Private/Public Process Unified management environment for public and private processesAn ambitious effort, requires redesigning of internal applications to externalise the business process state and the process flow logic
24ebXML FrameworkA framework of specifications for E-business integration based on state-of-the-art software architecture concepts and on experience in development of E-business systemsE-business interactions between organizations are modelled, standardised and published via E-business registriesThe use of XML-based, declarative specification languages provides configurability and interoperabilityArchitectural separation of business and information technology aspects of e-business systems
25ebXML and Integration Patterns ebXML is intended to support managed public processes pattern:Various middleware types are supportedFocus on E-business application rather application integrationDeclarative definition of public business processesSupport of partner agreements
27ebXML Business Operational View The BOV Addresses:The semantics of business data in transactions and associated data interchangesThe architecture for business transactions, including:Operational conventionsAgreements and arrangementsMutual obligations and requirements
28ebXML Functional Services View The FSV Addresses:Functional capabilitiesBusiness Service InterfacesProtocols and Messaging Services
29ebXML Framework cont‘d Business Process Specification Schema (BPSS) is an XML-based specification language that formally defines "public" business processes. It focuses on the collaboration of trading partners, and the business transaction activities they perform in the context of those collaborations.
30ebXML Framework cont‘d Core Components: Those provide the business information that is encoded in business documents that are exchanged between business partners.Registry/Repository: This is useful for more than merely conducting business searches. Some business scenarios depend heavily on registries to support setting up business relationships.
31ebXML Framework cont‘d Collaboration Protocol Profiles (CPP) and Agreements (CPA): These are XML documents that encode a party's e-business capabilities or two parties' e-business agreements, respectively.Transport, Routing and Packaging: The ebXML messaging services provide an elegant general-purpose messaging mechanism. The ebXML messaging service is layered over SOAP (Simple Object Access Protocol) and can transport arbitrary types of business content.
33ebXML State of the ArtStarted in November 1999 sponsored by OASIS and UN/CEFACTFramework specifications delivered in May 2001Steady adoption by commercial vendors, government organisations and Open Source community
34ebXML State of the Art cont‘d ebXML in productionHL7ebXML pilotsSun Microsystems with SabreSun Microsystems with GMUS CDC –British Telecom
35ebXML State of the Art cont‘d Not all the parts of the framework are adopted equallyebXML Messaging gets most of the attentionCore Components are of wide interestFull-scale support of business process modelling and run-time interpretation is still to come
36Towards Quality of Service Integration-level QoSBusiness-level QoSService Level AgreementsResearch directions
37Integration-level QoS Collective measure of the level of service a provider delivers to its customers or subscribersAvailability (downtime)Response time and throughputAbandoned transactionsSpeed of fault detection and correction...
38Business-level QoS Based on business metrics and profit models A simple profit model:Time = W - the response time constraintRevenue = r * (number of completed transactions)Cost = c * (number of responses longer than W)Profit = Revenue - costClosely related to the integration-level QoS via profit-oriented feedback control
39SLA – Main AspectsLegal: Provides for the negotiations between customer and service providerOperational: Provides for the execution of the services under the SLAFinancial: Provides an assessment of the financial implications in the SLA
40Research DirectionsModelling of inter-relation between the integration-level and business-level QoSMonitoring, measurement and management of business processes based on QoS levelsInstrumenting of the above in ebXML or similar environmentImplementing in practice
41Related Work Integration-level QoS and BP management SLA specification language
42Q2B (QoS to Biz) Framework Developed by HP Labs, 2001Intended to:Monitor and correlate QoS with business metricsVisualise resultsIssue alerts according to defined thresholdsAdapt and optimise business processes based on the
43Q2B (QoS to Biz) Framework Key points of importance for us:SOA based approach – HP e-speak middleware, similar to Web ServicesConceptual similarity to RBVO – federated e-servicesNon-intrusive interceptor based monitoringXML-based data exchange
44Q2B - Monitoring of QoSFrom HPL , HP Laboratories
45SLAng – an SLA LanguageDeveloped by Department of Computer Science, University College LondonPart of an EU IST project
46SLAng GoalsProducing a formal language, with a well defined syntax and semantics for describing service level specifications (SLSs)Specification of non functional features (service level) of contracts between independent parties to allow the integration with the functional design of a distributed component systemParameterisation, compositionality, validation of service level agreements
51SLAng Importance Modelling and reasoning about SLAs Translating an SLA into another format (XML-based)Monitoring compliance to SLAToolkit for service composition and analysis (assist ASP in determining what SLSs they can undertake to meet)
52ConclusionsSignificant standardisation effort is being carried out in E-Business areaCollaborative commerce is supported by promising architectural frameworksQuality of Business Services becomes more and more importantQuestions, comments:Adomas SvirskasBob Roberts