Principles of Service Oriented Architecture

صفحه 1:
Priwiples oP Gervice Oriested @rchitecture Ook Baky Geoimr Gye Orc kat Geom, Governed, & kProsinctue INTERGRAPH ©2000 “eter qropks Oorporcarm 

صفحه 2:
سسسسا 2 دب لد64يف ‏ *أقءع ‎ae‏ ‏یت مس0 * Dowrates Por Gervice Orietied @rchieoare (GO) = GOO Oefred * ۵00 ‏یوسب‎ * ۳۳۷۱ سس | 

صفحه 3:
ae ‏سسسسا 2 دب لد64يف *أقءع‎ Oued Covircavedt “INTERGRAPH The 5th Wave By Rich Tennant on the corporate nelworl eens, ee 

صفحه 4:


صفحه 5:
9 “INTERGRAPH 7 سم ببس و ۵0 ever ‏مرن‎ sti wits be drawback ‏مس له مد‎ ‏ابصد ماس‎ رید وی بیط ‎t.‏ تج وا تساو نمی و | 

صفحه 6:


صفحه 7:
] Gorvice Oowsers Quiles Oster Processes Ontiple Decree Rezowroee Ontile Oorviow Providers جا رل مج را مج م6 ‎perPorcred, cf were ocd by soo the‏ ‎resources are proved, eadbkey couple‏ ‎providers cad powers 1 partopte exper‏ ‎shored boxer cote.‏ ‎Dee Bacar BP, are‏ سود ‎ ‎ ‏0 ‏لبوج اه جيه بجا دحي ا ‎Orrvere, oreectard ki Gervee Orckiechre‏ © ‏يه سرمت مي جما ,6000© ‎ ‎ ‎ ‎ ‎ 

صفحه 8:
@eFore GOO — PPter 6068 ‘Application Dependent Business Functions ۱ 55-5 

صفحه 9:
تسم 9 با 9 ‏عطاوي‎ (Pexible, Pederaed Ousivess Processes: (Banbhsny 0 urna Peder of ‏مصحر باط عمج لب‎ perternnts ty cokborte mn ‏مه سس‎ 8 سم ها ولو ‎(bec ens‏ ميمت لمي جما ,2000© 

صفحه 10:
Ok GOO? Vo euuble Busivess Process Opticotzaion 7 ف ا ات 1 0 oO ay vad the Red Dior Cuterprise (REC) 1 Prarie Omevord 

صفحه 11:
‎of‏ 0 بیس م0 سس ‎ ‎ ‎ ‏۷ محم | | اس ]| 6060© ‎0 ‏یو‎ Ooty ‎ ‏سس سس سسده ‎reruns ‏ی ۳ ‎oo 0 9 ‏0007 ‏ع ‎ ‎ ‎ ‎ ‎ ‎ ‎hy GOW? Conble Siructiral Ihoprovewent ‎ ‎ ‎ ‎ ‏سس مه وس )یا ‏اسم سسا دج ‎ ‎ ‎ ‎ ‎۳ ca ono oan ae ‏سره مه‎ ‏ی‎ ‏یبن سس‎ ‎| ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ 

صفحه 12:
سسسسا 2 دب لد64يف ‏ *أقءع ‎ae‏ ‎“INTERGRAPH‏ لمتلء() 5009 * GOO ‏ویو و‎ orchterture wodel ‏رومیت سا سای وا‎ are babu ‏صم لسستخصصت لمت لحي‎ + oo ‏بای‎ ‏سم‎ od reverie ‏صب‎ ‎ved erates tot ‏ححصت ساسحا مضا كلها د مسو‎ ‏نو و بلاط مساو‎ + soa be ‏ساوسو نس و و لس‎ ‏مت‎ podirad wih oproPicaioa of he ‏)سوه رطخ ,سم‎ arco), 000 رطع ... سس سم حرمت لوي جما ,نات ها 

صفحه 13:
Oket is Gervice @rohiterture? * O coteviva oF services hissed tao pes اه مت ۱ مااي احج م موسر سج ,00 نامع سمح | {ti <= 

صفحه 14:
سسسسا 2 دب لد64يف ‏ *أقءع ‎ae‏ ‎GOB INTERGRAPH‏ (إعصم) جلا .صب (جنم) بط ‎Architecture = engagementand $ Architecture = engagenene and ‎‘information sharing process that $nformaton sharing process chat works enterprise-wide, driven by} works encerprise-wite, driven by ‎users need utes need “Big SOA a3 : - Not many 8 people are E ‏مه مه‎ £ Service=delyery ‏ضمت واه‎ | thie ‏ع‎ ‘component with open, remocely line wich a published and agreed ‏و‎ 0 0 2 . Architecture = tecnolony 3 ‘mapping and standardisation process g ‘that focuses on maximising = : consisreney aerons software $8 dlevelopmene project, a3 ‎Service = delivery ofa capability ‏م‎ ‎ ‎ ‎line with a published and agreed contract ‎ ‎Narow Broad ‎Service concept scope ‏سس ميمت لمي جما ,2000© 

صفحه 15:
GOO és ua ‏رسممشطورو‎ step "Por orchterture 3-Tier Architecture ‏املعت‎ + + + 4 و2 ان Homogenous ۱ Language Dependent eto Centralized Application Tiers | Code Centric Applications ‏را‎ eens Request/Reply Driven eet aa ae كمهناه امهم هماما لماع للهلم ‎HTML Pages‏ سس | 

صفحه 16:
GOO és ua ‏رسممشطورو‎ step Software Reusability Communication Services Distributed source: Sam Gentile سپ ميمت لمي جما ,2000© 

صفحه 17:
00 ‏مه مشاه موی‎ “INTERGRAPH خعامم معامم ‎“too centralized “too decentralized” “just right”‏ 9006 رو 0 مب | 

صفحه 18:
‎“INTERGRAPH‏ وا را لسن ص0۳ مس ‎Crook byrne‏ وا مس بسي ومست یه و ‎Rewer.‏ .8 ی ی ‎bier bevels‏ 0 مسق موه ‎Punter‏ ,6 وا ها مین ۵ ‎Sa Bn‏ 0 6 ‎Poke oy vay by Laer‏ ,6 ‎on‏ ‎ ‎ ‎ ‎Tee Bexar BO,‏ بس جه ‎art hr‏ ‏سب ميمت لمي جما ,2000© ‎ ‎ ‎ ‎ ‎ ‎ 

صفحه 19:
ae ‏سسسسا 2 دب لد64يف *أقءع‎ QOvior service pes ~INTERGRAPH * Cate Corvices: ‏رت توا لین و(‎ نت را رت مق میس لجی اوه مق ‎@eexpovkte dats behavior ond‏ = ‎bockesnl).‏ = Cot verices or okies services wit hide deoree of reverb. = Represedt Puadawectd GOO waturty bevel gad ‏رما بحاص با من تلا مت رام‎ (canker asm service) * Opwpoved Gorey : بسجميلي ,سجميحسي) ‎teohwkay‏ مه تا تم © وه لوا وروی ( اه خسوا وميا لعي جطصييا روسنس طلست تاه مسا لوصو سب | 

صفحه 20:
و ‎Senive wediative, muller, Inst‏ voublewmat, OSD, ‏ترا سم‎ ult chorwae! ‏وروی‎ Dobe, Gpart, The, hick oleate, Portals عم میت یه شتفي سسا مسي سب ۳ [] م ما اجه میت ‎Data‏ ساماد ادس اا 

صفحه 21:
یر 9 اسب ۵00 ۰ ‏للم‎ Gervice Orctiracts بممه() سرا ۶ مسا ۰ سس | 

صفحه 22:
Grantardzed Service Ovcirarts “INTERGRAPH 8 Geruices wikia the sue service iveuiory ane ke ooophoace wits he sure orutrat " Genuices use service ‏اما‎ = Ones her pre E ‏لین عمط موه‎ “Sars pupae and ‏د‎ ليسي اي "Poms va the areas ‏خام‎ مت امس - Pohay اه سا تیه | 

صفحه 23:
* ‏سوه زا و و مور‎ cork requrewets ond or hewerker choked Brow tee suronnkry PUI. Peseta = Ores ‏بم حم ات و یی حيس‎ SK a ۳ ۱ aah a a oS | ون روصت( یی — Genter vectra تابن موق ۳ axennvers: 

صفحه 24:
سسسسا 2 دب لد64يف ‏ *أقءع ‎ae‏ ‎“INTERGRAPH‏ و eo t* " " ‏جاص قد سطتح8)‎ vay cvutaa esseutd tPoruraicn ood ieforiutca abou services ts ‏لا‎ te ural te publeted ta service couiracts” ۶ Quod the profPeraica of ‏و واه وی موی‎ ۱ امه اروت اما بط مس لوف الم روت مت تاه ‎postbotey ued deste‏ دا جا صاصر لام ‎hye a‏ = اه سا تیه سس | 

صفحه 25:
سسسسا 2 دب لد64يف ‏ *أقءع ‎ae‏ ‏یت سا موه لهج چه لصتم ع موه له وا اوه وه لو موه زرم ۰ تشرط( ۲ ما مرو لهج( ۶ ات له نوی و توا لاب ‎crore:‏ لها سا تسا Ihe 3 qeuerte ced extecmibk octet ‏هر‎ ‎— Oa be ‏راو وم‎ اه سا تیه سس | 

صفحه 26:
سسسسا 2 دب لد64يف ‏ *أقءع ‎ae‏ ‎“INTERGRAPH‏ سس ‎8 "Gervices exercise u high level oP ovoid! over their ‏اوجن‎ rocks Exerc 32222000 ‏جعصجد تام جلححدج خاه بلمجلمصمصلم صما جا نج تعمج صا موه و اه راك سا و ۶ ‏امه وی ها ام ججصتصهد ركلا صبصخاصه 2105 " لیمیا مسب( ۰ ‎G‏ ایک ها ‎ ‏اه سا تیه ‏سب | 

صفحه 27:
يإ :3 1 لب ۳۲[ 0 جوع اوه ره مس جع سول رو موجه ‎Conizes ortote resource‏ "© وهی ما مهم و مسو ‎exexeice wiht server‏ ره ۰ ‎"Code‏ ره موه سس ‎ree‏ مه وود لجو تسا موی ‎oP‏ وم رو اه سا تیه 

صفحه 28:
‎INTERGRAPH‏ ~ تسیل سب ‎"Geruices a supplewernied‏ 8 مب سارت ‎chats by‏ ماس سر ف طسو لم لسمصحححك امس شلد با موم تا ‎COO‏ ‏© © © ‏و وت موس 0 1 ‏وه ارت رم وم مت © © © @ ‎x 7 ‏عمط هر 5 ‎bud new > xe ‏وا‎ ‎2 N@~ “service? ‏عن رو موه و و مد مه بو« 1 ‎et‏ ‎pote hes pres‏ ‎il ‎ ‏اه سا تیه ‏سس | 

صفحه 29:
وراه بو موم 0 که ۶ ولمم و ‎he‏ بت مره ی این ساره ها اوه طاولی و وشن مهد 9 سم 6 اس ها ‎“nomad ih‏ — ‎(Rekted to Revecbhiy prick‏ requireweuts Por sitar Pucca Gove: ‏لظا سس‎ 

صفحه 30:
سسسسا 2 دب لد64يف ‏ *أقءع ‎ae‏ 11۲5۳6 مهو - ۵00 باه ‎do what ts ‘right’‏ موم وه عصه نم مور وت ‎Govern‏ 8 ماه اه موه امه معط سا موه حهصص واه اس موم و ول ۶ ‎ad‏ و۳( 200 مق لح 200) مسب توص 600 لوط لوق سم رو خممسمت بهن سساتجوي سم تا ‎ ‎ ‏سس | ‎ ‎ ‎ 

صفحه 31:
سسسسا 2 دب لد64يف ‏ *أقءع ‎ae‏ ‎“INTERGRAPH‏ سوه - ۵00 مسا ‏بش ۰ امسر اما لجی سعططهی سرت ,نو ‎CadPicata oP hive,‏ = ‎= Dot ackheoy all anne oP he serine Weoyok (eohookxp selva, cei, ‏ام‎ ‎preter, A PRMIG ‏ارجام سس مور‎ MARINE ‏جوم‎ £40.) ‎۰ ‏یه‎ ‎- ‏سحام مس0‎ = Oppewsbves provemern (onde checkers, crn bk, stl rots) = Arete process (reno, deokg reviews, vine reviews, thread ‏عضت ابا رجو تسوت‎ review, rekswe mniteernn, service reybiratint, et) ۰ ‏و‎ ‎= Drwurewets ‏تا بان نت هریت ,جح موه ان‎ ‏سمل‎ ‎- Bovernnene proyran shoud be rt by GOO Ovard, whick should ave ‏اهتیاس‎ ‏رطس‎ ‏سس | 

صفحه 32:


صفحه 33:
سس | 

صفحه 34:
Oppbicy GOO — Reavation Roakvay “INTERGRAPH Agility 1 Ability to Deliver SOA Paralysis Greenfield 86۱0۵ yeh dred, Onl Decker, ol Ook hr, 

صفحه 35:
سسسسا 2 دب لد64يف ‏ *أقءع ‎ae‏ ‎~INTERGRAPH‏ ی *» AR doo corrent, GOO ts “oot jxet carter orchierturd Pad” * COO seeks ty bricke he sar bewwera bskess ond teckorkxy promot buskess oily © ‏يجيه لحماك اد‎ ohare) ومه = ری و مس ‎Requires‏ ~ ها موی مهس تفج ‎Renee courted uth resouroen (peuple exnd $$)‏ = سپ ميمت لمي جما ,2000© 

صفحه 36:
Priwiples oP Gervice Oriested @rchitecture Ook Baky Geoimr Gye Orc kat Geom, Governed, & kProsinctue INTERGRAPH ©2000 “eter qropks Oorporcarm 

Principles of Service Oriented Architecture Mark Bailey Senior System Consultant Security, Government, & Infrastructure mark.bailey@intergraph.com © 2008 Intergraph Corporation Agenda  Motivation for Service Oriented Architecture (SOA)  SOA Defined  SOA Principles  Applying SOA © 2008, Intergraph Corporation Page 2 Current Environment © 2008, Intergraph Corporation Page 3 Application Centric © 2008, Intergraph Corporation Page 4 Application Centric Business scope Narrow Consumers Limited Business Processes Ap p l i ca t i o n Finance Ap p l i ca t i o n Integration Supply Ap p l i ca t i o n Architecture bound to EAI vendor Redundancy Manufacturing Distribution Overlapped resources Overlapped providers Business functionality is duplicated in each application that requires it. EAI ‘leverage’ application silos with the drawback of data and function redundancy. © 2008, Intergraph Corporation Page 5 Goal - Service Centric © 2008, Intergraph Corporation Page 6 Service Centric Business scope Multiple Service Consumers Multiple Business Processes Finance Service Service Supply Service Architecture Service Shared Services Service Manufacturing Distribution Multiple Discrete Resources Multiple Service Providers SOA structures the business and its systems as a set of capabilities that are offered as Services, organized into a Service Architecture Service virtualizes how that capability is performed, and where and by whom the resources are provided, enabling multiple providers and consumers to participate together in shared business activities. © 2008, Intergraph Corporation source:TietoEnator AB, Kurts Bilder Page 7 Before SOA – After SOA © 2008, Intergraph Corporation source:IBM Page 8 Why SOA? To enable Flexible, Federated Business Processes Enabling alternative implementations Enabling a virtual federation of participants to collaborate in an end-to-end business process Enabling reuse of Services Service Identification Service Ticket Collection Service Ordering Ticket Sales Service Service Service Inventory Logistics Service Service Service Service Availability Manufacturing Enabling virtualization of business resources Enabling aggregation from multiple providers source:TietoEnator AB, Kurts Bilder © 2008, Intergraph Corporation Page 9 Why SOA? To enable Business Process Optimization and the Real Time Enterprise (RTE) BPM Expressed in terms of Services Provided/Consumed Seamless End to End Process Service to Customers Enterprise Service from Multiple Suppliers Smart Clients Stores POS Mobile 3rd Party Agents Portal Internal Systems SOA Patterns: Single, Multi-Channel Service for consistency source:TietoEnator AB, Kurts Bilder © 2008, Intergraph Corporation SOA Pattern: Standardized Service provided by multiple suppliers Page 10 Why SOA? Enable Structural Improvement ERP X Process Z Standardizing capabilities ERP Z Process Y Information Consistency e.g. Single Customer Details Service Reducing impact of change Partner A Policy Consistency Service Consolidation/ Selection process CRM System 2 Encapsulating implementation complexity CRM System 1 Product System e.g. Multiple Sources of Customer Details Policy Rationalization and Evolution Resource Virtualization © 2008, Intergraph Corporation Page 11 SOA Defined  SOA is a software architecture model – in which business functionality are logically grouped and encapsulated into • self contained, • distinct and reusable units • • • • called services that represent a high level business concept can be distributed over a network can be reused to create new business applications contain contract with specification of the purpose, functionality, interfaces (coarse grained), constraints, usage ... of the business functionality Services Servicesare areautonomous, autonomous,discrete discreteand andreusable reusableunits unitsof ofbusiness businessfunctionality functionalityexposing exposingitsits capabilities capabilitiesininaaform formof ofcontracts. contracts. Services Servicescan canbe beindependently independentlyevolved, evolved, moved, moved, scaled scaledeven even ininruntime. runtime. © 2008, Intergraph Corporation Page 12 What is Service Architecture? • A collection of services services • classified into types • arranged into layers • Governed by architectural patterns and policies type ide ica ntif © 2008, Intergraph Corporation tion type r ula n a gr type ity de n pe n de cy source:TietoEnator AB, Kurts Bilder Page 13 Big (outer) vs. Little (inner) SOA © 2008, Intergraph Corporation Page 14 SOA is an evolutionary step  for architecture © 2008, Intergraph Corporation Page 15 SOA is an evolutionary step  in reusability and communication © 2008, Intergraph Corporation Page 16 SOA is an evolutionary step  in distributed communications EAI Project-ware © 2008, Intergraph Corporation SOA source:Sam Gentile Page 17 Service Architecture Organized by Layers Reasons for Layering 1. Flexible composition. Example Layers Presentation & workflow 2. Reuse. 3. Functional standardization in lower levels Composed Services 4. Customization in higher layers 5. Separation of Concerns. Basic Services 6. Policies may vary by Layer Underlying API © 2008, Intergraph Corporation according to:TietoEnator AB, Kurts Bilder Page 18 Major service types  Basic Services: – Data-centric and logic-centric services – Encapsulate data behavior and data model and ensures data consistency (only on one backend). – Basic services are stateless services with high degree of reusability. – Represent fundamental SOA maturity level and usually are build on top existing legacy API (underlying services)  Composed Services : – expose harmonized access to inconsistent basic services technology (gateways, adapters, façades, and functionality-adding services). – Encapsulate business specific workflows or orchestrated services. © 2008, Intergraph Corporation Page 19 Service Types SOA Ma na g ement & Securi t y service medi a t io n , ro ut i ng , t rust ena bl ement . ESB, Service Reg ist ry Mul t i cha nnel a p p l i ca t i o ns: Mo bi le , Sma rt , Thi n , Thi ck cl i ent s, Po rt a l s. In S fra e r st vi c ru e ct ur e Business cent ric services, orchest ra t ed workflo ws. Int ermedia t e servi ces (g a t ewa ys, fa ca des ) Da t a cent ric a nd log ic cent ric consist ent services. Highly reusa ble , st a t eless servers Fo unda t i on Servi ce Blo cks rra Te re a Sh Bu si n ess Ca p a b i l i t i es G/T e ch I/CAD Co re APIs © 2008, Intergraph Corporation In r Se rv t he Page 20 SOA Principles  Standardized Service Contracts  Loose Coupling  Abstraction  Reusability  Autonomy  Statelessness  Discoverability  Composability © 2008, Intergraph Corporation Page 21 Standardized Service Contracts  “Services within the same service inventory are in compliance with the same contract design standards."  Services use service contract to – Express their purpose – Express their capabilities  Use formal, standardized service contracts  Focus on the areas of – Functional expression – Data representation – Policy Source: Thomas Erl © 2008, Intergraph Corporation Page 22 Loose Coupling  “Service contracts impose low consumer coupling requirements and are themselves decoupled from their surrounding environment."  Create specific types of relationships within and outside of service boundaries with a constant emphasis on reducing (“loosening”) dependencies between – Service contract – Service implementation – Service consumers Source: Thomas Erl © 2008, Intergraph Corporation Page 23 Abstraction  “Service contracts only contain essential information and information about services is limited to what is published in service contracts”  Avoid the proliferation of unnecessary service information, meta-data.  Hide as much of the underlying details of a service as possible. – Enables and preserves the loosely coupled relationships – Plays a significant role in the positioning and design of service compositions Source: Thomas Erl © 2008, Intergraph Corporation Page 24 Reusability  “Services contain and express agnostic logic and can be positioned as reusable enterprise resources."  Reusable services have the following characteristics: – Defined by an agnostic functional context – Logic is highly generic – Has a generic and extensible contract – Can be accessed concurrently Source: Thomas Erl © 2008, Intergraph Corporation Page 25 Autonomy  "Services exercise a high level of control over their underlying runtime execution environment."  Represents the ability of a service to carry out its logic independently of outside influences  To achieve this, services must be more isolated  Primary benefits – Increased reliability – Behavioral predictability Source: Thomas Erl © 2008, Intergraph Corporation Page 26 Statelessness    "Services minimize resource consumption by deferring the management of state information when necessary." Incorporate state management deferral extensions within a service design Goals Increase service scalability – Support design of agnostic logic and improve service reuse – Source: Thomas Erl © 2008, Intergraph Corporation Page 27 Discoverability  "Services are supplemented with communicative meta data by which they can be effectively discovered and interpreted."  Service contracts contain appropriate meta data for discovery which also communicates purpose and capabilities to humans  Store meta data in a service registry or profile documents Source: Thomas Erl © 2008, Intergraph Corporation Page 28 Composability  "Services are effective composition participants, regardless of the size and complexity of the composition."  Ensures services are able to participate in multiple compositions to solve multiple larger problems  Related to Reusability principle  Service execution should efficient in that individual processing should be highly tuned  Flexible service contracts to allow different types of data exchange requirements for similar functions Source: Thomas Erl © 2008, Intergraph Corporation Page 29 Applying SOA - Governance   Governance is a program that makes sure people do what is ‘right’ In conjunction with software, governance controls the development and operation of software Goal: Establish SOA organization governance (SOA Board) that governs SOA efforts and breaks down capabilities into non-overlapping services © 2008, Intergraph Corporation Page 30 Applying SOA - Governance  Policies – Codification of laws, regulations, corporate guidelines and best practices – Must address all stages of the service lifecycle (technology selection, design, development practices, configuration management, release management, runtime management, etc.)  Processes – Enforce policies – System-driven processes (code check-in, code builds, unit tests) – Human-driven process (requests, design reviews, code reviews, threat assessment, test case review, release engineering, service registration, etc.)  Metrics – Measurements of service reuse, compliancy with policy, etc. – Organization – Governance program should be run by SOA Board, which should have cross-functional representatives © 2008, Intergraph Corporation Page 31 Fo unda t i o n Servi ce Bl o cks Applying SOA – Governance In r Se rv i c e Ot h e ch Bu s i n e s s Ca p a b i l i t i e s G/T e I/CAD Co re APIs So ft wa re a n d IT Arch i t e ct s Ent erprise Archi t ect s Service Desig ners Servi ce speci fica t ion model Business service model © 2008, Intergraph Corporation y lic ds Po a r d s an St d e l Mo rn s te Pa t SOA Bo a rd Se rvi ce i mp l e me n t a t i o n a n d d e p l o yme n t mo d e l Page 32 Applying SOA - Challenges  Service Orientation  Reuse  Sharing of Responsibilities  Increased complexity! Business functionality has to be made available as services. Service contracts must be fixed Implemented services must be designed with reuse in mind. This creates some overhead. Potential service users must be involved in the design process and will have influence on the service design © 2008, Intergraph Corporation Page 33 Applying SOA – Renovation Roadmap (Source: Enterprise SOA: Service Oriented Architecture Best Practices by Dirk Krafzig, Karl Banke, and Dirk Slama, Prentice Hall 2004) © 2008, Intergraph Corporation Page 34 Conclusion and Summary  If done correct, SOA is “not just another architectural fad”  SOA seeks to bridge the gap between business and technology promoting business agility (its all about managing change)  SOA – Is complex – Requires governance – Requires executive management buy-in – Requires commitment with resources (people and $$) © 2008, Intergraph Corporation Page 35 Principles of Service Oriented Architecture Mark Bailey Senior System Consultant Security, Government, & Infrastructure mark.bailey@intergraph.com © 2008 Intergraph Corporation