1 / 61

SOA Part1 Lecture 4

SOA Part1 Lecture 4. Dr. Withalm 3-Jan-20. Lectures at the University of Bratislava/Autumn 2017. 03.10.2017 Lecture 1 The long Way from OO to SOA & WEB- Services 17.10.2017 Lecture 2 Semantic WEB & SOA-Technological Basis

albertlong
Télécharger la présentation

SOA Part1 Lecture 4

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SOA Part1 Lecture 4 Dr. Withalm 3-Jan-20

  2. Lectures at the University of Bratislava/Autumn 2017 03.10.2017 Lecture 1 The long Way from OO to SOA & WEB- Services 17.10.2017 Lecture 2 Semantic WEB & SOA-Technological Basis 14.11.2017 Lecture 3 SOA-Basing on J2EE & SOA-Focus on Business Processes 21.11.2017 Lecture 4 B2B Frameworks and related Standards 28.11.2017 Lecture 5 WEB 2.0 & GRID & Cloud Computing Dr.Withalm

  3. Summary of lecture 3/1 • Both new business processes and new technologies • Are drivers of architecture change • Service bus facilitates • The co-operation of different applications • Which are themselves aggregated by services • In SOA you are only concerned with three parties • Service Provider, Service Requestor, Service Broker • Reuse is in the spotlight of SOA • Services are aggregated by other services • Orchestration & Choreography • Business components contain business services • Business processes are aggregated by different business services • Each business component has service interfaces • Technical service interface • Business service interface • Data entity • Service integration adapter Dr.Withalm

  4. Summary of lecture 3/2 • Servlets are influenced by applets and CGI • Are provided by a class library • Are executed on the Web Server • Portlets provide a user interface • Which allows an end user to interact directly with the service • JSR 168 standard is available • Some obstacles should be taken into account • IT management of SOA is challenging • Many service level agreements must be concluded • Disputes between enterprises may arise • If services are highly profitable • Danger of system chaos exists • Millions of networked services are hardly comprehensible • Implications of SOA • i.e. different kinds of SW developers Dr.Withalm

  5. Summary of lecture 3/3 • ARIS (ARchitecture of intergated Information Systems) • Not only an architecture but also a platform • For business process modeling • Especially applied in large companies in Germany, Austria, and Switzerland • ARIS business function (service) may directly mapped onto a SOA service • Most important elements for modeling a business process are: • Events, functions, resources, functional units, information objects, entitities, product/services,… • Event-control-event driven process chains • Showing the chronological – logical procedere of a business process • Each function has a start and end event Dr.Withalm

  6. Summary of lecture 3/4 • Different event and function operators are: • AND, OR, XOR • A triggering event must not be linked using OR or XOR • Events have no decision making power • Function allocation diagrams are illustrating • the transformation of input data into output data • Information flow diagrams are used • To show the flow of data between functions • Are supported by special ARIS tools • Event diagrams show the structuring of events • Also organizations may be linked to events, functions, and data Dr.Withalm

  7. Today’s Agenda • Overview of B2B Frameworks • Electronic Business XML (ebXML) • RosettaNet • Commerce XML (cXML) • OBI • BizTalk • ARIS & BizTalk • Example • bolero.net • tpaML • eCo architecture (CommerceNet) • XML Common Business Library (XCBL) • Universal Business Language (UBL) • Introduction: Collaborative Networked Organizations i.e. Supply Networks • Conclusions Dr.Withalm

  8. B2B Frameworks and related standards/1 • The first step towards this goal has already been taken in the past using Electronic Data Interchange (EDI) concept. • However, the increasing use of Web protocols, such as HTTP, and the remarkable success of HTML • have favoured more flexible solutions, notably XML. • Hence, most B2B frameworks are built heavily on XML. • Typically a B2B framework is a XML-based and middleware-neutral document specification • though most of the B2B frameworks require the use of Internet and Web protocols • such as HTTP, SSL, and MIME. Dr.Withalm

  9. B2B Frameworks and related standards/2 • Originally, B2B frameworks focused solely on developing vendor-independent specifications • for a set of documents to be exchanged between business partners. • Lately, the frameworks realised the need to coordinate the actions of different business partners • so that, business partners should definitely agree on the structure of documents they exchange • but they should also know when to exchange those documents • and how to articulate those external exchanges with their internal business processes. Dr.Withalm

  10. B2B Frameworks and related standards/3 • As a result, B2B frameworks have begun focusing both on document format and on CBP’s (Cross organizational Business Processes) • that concern the exchange of those documents. • Some of these B2B frameworks specify the infrastructure required for business partners • to implement those exchanges. • In other words, some frameworks specify both message format and exchange sequence • and some specify the message format and an infrastructure • which allow business partners to define and implement their own interactions. Dr.Withalm

  11. B2B Frameworks and related standards/4Electronic Business XML (ebXML)/1 • ebXML (Electronic Business XML) is a project to use the Extensible Markup Language (XML) • to standardise the secure exchange of business data. • It provides a modular suite of specifications • for standardising XML globally in order to facilitate trade between organisations • regardless of size. • The specification gives businesses a standard method to exchange XML-based business messages • conduct trading relationships • communicate data in common terms • define and register business processes. Dr.Withalm

  12. B2B Frameworks and related standards/17RosettaNet/1 • The RosettaNet framework is one of the most comprehensive and successful B2B frameworks. • The RosettaNet framework, like ebXML framework, employs a top-down approach • requiring business partners to specify their business processes in detail • before defining the XML messages they will exchange. • RosettaNet includes a set of standards that aim at supporting information exchange • throughout the whole supply chain • particularly within the Information Technology, Electronic Components and Semiconductor Manufacturing industry sectors. Dr.Withalm

  13. B2B Frameworks and related standards/18RosettaNet/2 • For this purpose, the RosettaNet framework defines a set of common dictionaries • that establish the properties to be used in business processes between supply chain partners. • These inter-enterprise business processes are called Partner Interface Processes (PIPs) more or less equivalent to CBP • which define the message exchange between partners. • The RosettaNet Implementation Framework specifies • the packaging, routing and transport details for these messages. Dr.Withalm

  14. B2B Frameworks and related standards/25Commerce XML (cXML)/1 • Commerce XML (cXML) is a standard for the online exchange of business transaction information in common formats. • It defines the structure of purchase orders, order acknowledgements, and other core e-business documents. • cXML is a document type definition (DTD) based on XML tags • that defines fields for a specific type of document, like a purchase order. • The XML structure enables an application program to easily extract data • and deliver it to another application program. Dr.Withalm

  15. B2B Frameworks and related standards/30OBI (Open Buying on the Internet) • Similarly to cXML, the purpose of the Open Buying on the Internet (OBI) specification • is to develop a common framework • to guide companies in implementing interoperable, Internet-based purchasing systems. • OBI focuses on high-volume and low-value transactions • that are believed to account for about 80% of most organisations’ purchasing activities. • The OBI framework is based on a particular model of business-to-business interaction, which entails a buying organisation • a requisitioner belonging to that buying organisation • a selling organisation • and a payment authority. Dr.Withalm

  16. B2B Frameworks and related standards/31BizTalk • The BizTalk framework (MS), like cXML, specifies the message format that encloses documents • to be exchanged between applications at different sites. • At each site, BizTalk assumes that there is a server • which is able of producing and consuming messages • according to the specified format. • In addition, BizTalk suggests using particular protocols for communication between these servers. • This is referred to as transport bindings, i.e., the exchange of BizTalk messages • using certain transport protocols. • However, the BizTalk framework is independent of the implementation details of those protocols Dr.Withalm

  17. ARIS & BizTalk/1 • Borderline between business and IT department • ARIS for MS BizTalk supports both departments • Business employees are modeling their processes in the user friendly ARIS notion • Employees of IT Department are working in their common environment • In order to develop technical services out of the business ones • Two methods are provided to transform business process in technical executable ones Dr.Withalm

  18. ARIS & BizTalk/2Method 1 • In case of using EPC to model graphically the process flow • the process model may be enlarged by SOA relevant aspects • as calling of Web Services or I/O data • With help of an automatic model transformation • a technical BPEL (Business Process Execution Language) will be generated out of the EPC • which may be refined on request (i.e. copying of data) Dr.Withalm

  19. ARIS & BizTalk/3Method 2 • In case of preferencing the BPMN (Business Process Modeling Notation) for modeling functionalities • Process flow and technical details (i.e. sending of messages, conditions for iterations ) may be modeled • By the modelTyp Business Process Diagram Dr.Withalm

  20. ARIS & BizTalk/4Visio Studio Project Generation/1 • As soon as a ready BPEL or BPMN – model is established • ARIS for MS- BizTalk generates automatically a visual studio project • which may be further refined by the respective IT department • that’s why the transformation/redesign of business processes is higly fastened • as the SW engineer must not orchestrate a BizTalk application from scratch • so only the generated visual studio project must be opened • without any retarding the established work of the business department continues • adding some technical details Dr.Withalm

  21. ARIS & BizTalk/5Visio Studio Project Generation/2 • finally the project is compiled, tested and on the respective BizTalk server installed • the close collaboration between the ARIS- SOA architect and the MS BizTalk environment • increases the productivity of IT department • and saves time and costs for implementation of processes Dr.Withalm

  22. ARIS & BizTalk/6Overview of usage and benefits • Fast and intuitive modeling of business processes in EPC and BPMN • BizTalk specific model validation ensures • that a BPEL and BPMN- model in a BizTalk orchestration is mapped successful • automatic transformation of EPC models to BPEL and furthermore • export of BPEL or BPMN as visual studio projects for BizTalk • optimal integration with ARIS process performance manager for continuous process monitoring Dr.Withalm

  23. ARIS & BizTalk/7 Solution Scenario Dr.Withalm

  24. ARIS & BizTalk/8Integration Overview Process Performance Manager Dr.Withalm

  25. ARIS & BizTalk/9Export of BPEL/BPMN as Visual Studio Project Dr.Withalm

  26. ARIS & BizTalk/10Process2Automation Dr.Withalm

  27. ARIS & BizTalk/11From BP Modeling to the Process Execution • ARIS for MS BizTalk enables enterprises a seamless integration • between business and technical business process modeling • after a BP is very fast and simple modeled with help of the ARIS SOA architect • automatically it will be exported as a MS Visual Studio project Dr.Withalm

  28. ARIS & BizTalk/12MS BizTalk Server/1 • Is worldwide one of the prevailing products in the area of EAI and workflows • It enables the integration of different back end systems • and is the core component in a SOA environment within an enterprise • Moreover MS BizTalk provides the possibility • to define technical business processes (so called orchestrations) • and providing them as consumable Web Services Dr.Withalm

  29. ARIS & BizTalk/13MS BizTalk Server/2 • the definition of an orchestration is usually executed by SW engineers • after the business department have established the design • in many cases a loss of information happens • which has bad consequences in the later process execution Dr.Withalm

  30. ARIS & BizTalk/14Reference Project/1Description/1 • How do you get a passport in SK ? • What must be organized following the birth of a child? • Which office is responsible for which belonging? • What are the opening hours of your district office? • Citizens are thoughout life forced to spend hours of their valuable time seeking answers to these and many other questions Dr.Withalm

  31. B2B Frameworks and related standards/32Bolero.net/1 • Whereas the BizTalk framework can be implemented by acquiring and installing a BizTalk-compliant server for each site • bolero.net is a running system owned by an independent third-party. • Created as a joint effort of a transporter insurer (TT Club) and a financial community (SWIFT) • bolero.net allows trading parties to exchange contractual and fulfilment data online in a secure environment. • The bolero.net systems was designed to support trading processes and information exchange • between importers, exporters, freight forwarders, port authorities, • inspection agencies, carriers, ship agents, customs agencies, and financial institutions. Dr.Withalm

  32. B2B Frameworks and related standards/33Bolero.net/2 • The system has two main components: • the Core Messaging Platform and the Title Registry. • The Core Messaging Platform allows those entities to securely exchange business documents through the Internet. • The purpose of the Title Registry is to record and transfer the rights and obligations • described in a bill of lading, which is a legal document • that contains information about the items or rights being transferred from one party to another. Dr.Withalm

  33. B2B Frameworks and related standards/34tpaML/1 • Several B2B frameworks have realised the need to express agreements between business partners. • For example, cXML introduces the concept of master agreements • ebXML specifies how to build Collaboration Protocol Agreements (CPAs) • and RosettaNet has created a project to standardise Trading Partners Agreements (TPAs). • The tpaML language is the basis of a B2B framework • which focuses exclusively on executable trading partner agreements. • According to this framework • a trading partner agreement (TPA) is a document • that describes the terms and conditions for the interaction between two business partners. Dr.Withalm

  34. B2B Frameworks and related standards/35 tpaML/2 • A set of several related interactions between any two parties is referred to as a conversation. • The main issue about executable TPAs is that they allow business partners at both ends • to automatically generate code • that will implement the interactions between them. • Executable TPAs are written with tpaML • an XML-based language that can be processed by a special-purpose code-generating tool. • Each party maintains complete independence from the other party • with respect to implementation details and internal business processes • because an executable TPA describes the interactions • that will take place between two parties. Dr.Withalm

  35. B2B Frameworks and related standards/36eCo architecture(CommerceNet)/1 • The eCo architecture is not a concrete framework • but rather an abstract architecture for B2B frameworks. • The main purpose of the eCo architecture is to enable interoperability • between heterogeneous e-business systems • which may be based on different B2B frameworks. • The eCo architecture realises • that e-business system implementations vary widely and • instead of restricting them to a specific framework • the goal of eCo is to allow each enterprise to define and expose meta-data descriptions of its e-business system. • These meta-data descriptions allow interested parties • to understand the e-business system • and to configure their resources in order to interoperate with the system. Dr.Withalm

  36. B2B Frameworks and related standards/37eCo architecture(CommerceNet)/2 • In essence, the eCo architecture specifies how to build an XML file • to be placed at the root of a Web site • describing the interoperability capabilities of the e-business system • available on that Web site. • Several queries can be performed in order to retrieve information about • the interoperability capabilities of the e-business system. • These HTTP queries are performed by submitting requests to different URIs. • All these requests, regardless of the URI they refer to • lead to responses that are based on information • contained in the eCo-compliant XML file. Dr.Withalm

  37. B2B Frameworks and related standards/38XML Common Business Library (XCBL)/1 • The XML Common Business Library (xCBL) is a set of XML building blocks and a document framework • that allows the creation of robust, reusable, XML documents to facilitate global trading. • It essentially serves as the "mother code," providing one language • that all e-marketplace participants can understand. • This interoperability allows businesses everywhere to easily exchange documents • across multiple e-marketplaces • giving global access to buyers, suppliers, and providers of business services. Dr.Withalm

  38. B2B Frameworks and related standards/39XML Common Business Library (XCBL)/2 • xCBL 3.0 provides a smooth migration path from EDI-based commerce • because of its origins in EDI semantics. • xCBL will be able to support all essential documents and transactions for global e-commerce • including multi-company supply chain automation, direct and indirect procurement • planning, auctions, and invoicing and payment in an international multi-currency environment. • xCBL is the result of extensive collaboration between Commerce One. and the leading XML standards bodies • e-commerce enterprises, and hardware and software vendors • as well as analysis of existing e-commerce standards • including Electronic Data Interchange (EDI), RosettaNet, and Open Buying on the Internet (OBI). • Industry leaders Compaq, Microsoft, SAPMarkets, and Sun Microsystems will leverage xCBL 3.0 • as a key standard in the development and delivery of business-to-business solutions. Dr.Withalm

  39. B2B Frameworks and related standards/40Universal Business Language (UBL)/1 • The UBL initiative originated in efforts beginning in mid-1999 • to create a set of standard XML "office documents" within OASIS (Organization for the Advancement of Structured Information Standards). • UBL 1.0 was released as an OASIS Standard on 8 November 2004 • following three years of open development and public review. Dr.Withalm

  40. B2B Frameworks and related standards/41Universal Business Language (UBL)/2 • UBL, the Universal Business Language, defines a royalty-free library of standard electronic XML business documents • such as purchase orders and invoices. • Developed in an open and accountable OASIS Technical Committee • with participation from a variety of industry data standards organisations • UBL is designed to plug directly into existing business, legal, auditing, and records management practices • eliminating the re-keying of data in existing fax- and paper-based supply chains • and providing an entry point into electronic commerce for small and medium-sized businesses. Dr.Withalm

  41. Why B2B ? • Organizations have need to collaborate • Resource Sharing • Example ELGA in Health Care • Competence Sharing • Example Airbus Suppliers • Capacity Sharing • Example in large companies i.e. SW Development Dr.Withalm

  42. ECOLEAD 1) Project funded by the European Community under the "Information Society Technology" Programme.Presented at ENTER’05 and ENTER’07 Preconditions for collaborations • Developed for companies, which are interested to join a collaborative network. • These reference models encompass • Checklists, templates, interfaces, tools, specifications, architectures, SW components and services. • These artifacts may be applied to facilitate the agreement concerning • Business strategies • Business models and above all • Business processes Dr.Withalm

  43. SOA & The Need for Collaboration • SOA was the first paradigm in developing SW systems • which shifted away from technical to business concerns. • The conclusion of this matter • not start to implement business processes • but begin with considerations about Business Strategy (BS) and Business Models (BM). • The need to collaborate is very high in many domains • as for instance in automotive or transportation/travel • collaboration follows one of these forms • i.e. supply chain, collaborative networks, business ecosystems. Dr.Withalm

  44. Different Kinds of Services • Primarily you must distinguish between Horizontal and Vertical Business Services. • Horizontal Services (as e.g. procurement) may be applied in many domains • Whereas Vertical Services are dedicated to a specific domain. • A further dimension of Business Services focusing on Collaboration/Interoperability issues are • Enterprise Collaboration (EC) Services which are mainly interested in • establishing guidelines, rules and tools to settle issues • how to agree on common business strategies (BS), common business models (BM) and the primary modeling of common business processes (BP). • Enterprise Interoperability (EI) Services. which focus on issues as how to • implement Cross organizational Business Processes (CBP) and their integration / synchronization with existing Private business Processes (PP) of the single members (of a CNO). • These kinds of services are the primary enabler of Collaborative Networked Organizations. • Web services on the other hand are the most important enabler for implementation of business services • whereas Semantic Web Services describe the context of the web service semantically. • basing on an agreed/standardized ontology • Note that the establishment and especially the agreement of ontology is a troublesome task. Dr.Withalm

  45. Corresponding EU Projects with Siemens Participation • ECOLEAD • Focus on EC Issues • ATHENA • Focus on EI Issues • COIN • Synopsis of EC and EI • Semantic annotation of these services • which will enable- mid term- the semi automatic discovering and composition of services • Quality of semantic web services will be evaluated • a well proven and accepted approach will be pursued • the ECMM (Enterprise Collaboration Maturity Model) assessment adapted to EC/EI services Dr.Withalm

  46. Measuring the Success of Semantic Web Services • Process Areas must be defined wich are positively contributing to your business • i.e. your BS, BM, and BP must ultimately drive to positive company results • very postive results concerning process areas to meet common BS and BM were accomplished by ECOLEAD • wheras both ATHENA and ECOLEAD added such results concerning BP • Process Areas require specific attributes of Semantic Web Services • the better ontology meets the business requirements of a specific domain • the higher the maturity level of such an organization (organizations) will be. • in the specific goals of the process areas such issues must be introduced • how many attempts you need to find the right web service • in the meaning of successful web service • in the sense of success for your business. Dr.Withalm

  47. Definitions concerning the different kinds of Enterprise Collaboration • A field of activity with the aim to support Networked Enterprises to do business together through ICT • Focus on core competencies • Expose proper views of internal competencies • Discover collaborative business opportunities • Look for complementary competencies by accessing others’ views • First Issue: competencies • Ability to apply skills/capabilities to a business situation • Human vs. Enterprise Competencies • Networked Enterprise Competencies • Competencies assessment, management and governance • Competencies alignment and semantic reconciliation • Second Issue: business opportunity • Generation and/or Discovery • Modelling and Characterisation (demand modelling) • Structuring and planning • Matching with competencies • Scheduling, enactment, BO management Dr.Withalm

  48. C1. Enterprise Collaboration in Supply Chains • First Issue: competencies • OEM determines the SC competencies • Almost Static H/E Models • Identification OEM-Network • Human periodical assessments • Aligned by construction • Second Issue: business opportunity • OEM generates BOs for the SC • Top-down modelling • Top-down structuring and planning • Full scale competencies visibility • Centralised enactement and management Dr.Withalm

  49. C2. Enterprise collaboration in CNO • First Issue: competencies • Service Center (VBE) as a competencies collector • More dynamic H/E Models • Specific VBE competencies • Autonomous assessments + inheritance + trust mgmt • Manual Alignment process • Second Issue: business opportunity • Crawlers to discover market BOs • Top-down modelling • Top-down structuring and planning • Negotiation for scheduling (different views and visibility rights) • Centralised enactement and management Dr.Withalm

  50. C3. Enterprise Collaboration in Business Ecosystems • First Issue: competencies • P2P competencies system • Fully dynamic H/E Models • Specific BE competencies • Peer assessment, Web 2.0 • Intelligent Alignment process (Agents) • Second Issue: business opportunity • BO Miners to discover internally-generated BOs • Top-down bottom-up modelling • Participative and collaborative structuring and planning • Semantic spaces for demand-offer • P2P enactement and management Dr.Withalm

More Related