WIXLIB

The Central Role ofRegistriesManaging SOA MetadataStefan Tilkov, t/Copyright 2006 innoQ Deutschland GmbH

‣ Technology Consultancy for Fortune 1000‣ Offices in Zürich & Düsseldorf‣ Founded in 1998/1999‣ Focus on‣ SOA consulting‣ Rational Software Production(MDE/MDSD/MDA)Copyright 2006 innoQ Deutschland GmbH2

Stefan Tilkov‣ Managing Director innoQ Deutschland GmbH‣ Principal Consultant‣ Involved in IT Architecture since 199x‣ Personal History with‣ Distributed Objects: CORBA‣ Components: J2EE/EJB‣ SOA: Web ServicesCopyright 2006 innoQ Deutschland GmbH3

What everyone can agree about:SOA Core TruthsCopyright 2006 innoQ Deutschland GmbH4

tsomalWhat everyone can agree about:SOA Core TruthsCopyright 2006 innoQ Deutschland GmbH4

‣ An (at least) company-wide, consistent style ofintegration‣ Services as core concept‣ Separation of interface and implementationCopyright 2006 innoQ Deutschland GmbH5

Some controversial SOAstatementsCopyright 2006 innoQ Deutschland GmbH6

SOA can be based on anytechnologyCopyright 2006 innoQ Deutschland GmbH7

SOA can be based on anytechnology. but it shouldn't beCopyright 2006 innoQ Deutschland GmbH7

‣ Reasonable Candidate Technologies for SOA are‣ Web services‣ RESTful HTTP or POX‣ Asynchronous MessagingCopyright 2006 innoQ Deutschland GmbH8

SOA can be built onCORBA, RMI, DCOMCopyright 2006 innoQ Deutschland GmbH9

SOA can be built onCORBA, RMI, DCOM. but that's not worth the troubleCopyright 2006 innoQ Deutschland GmbH9

‣ CORBA, RMI, DCOM all designed for tightcoupling‣ Tight coupling is fine if‣ client and server evolve simultaneously‣ client and server are not autonomous‣ both are controlled by the same domain‣ Use it where needed, but don't claim it's SOACopyright 2006 innoQ Deutschland GmbH10

An ESB is at heart of SOACopyright 2006 innoQ Deutschland GmbH11

An ESB is at heart of SOA. if you believe a vendor’s sales representativeCopyright 2006 innoQ Deutschland GmbH11

‣ SOA should not depend on any product‣ Favor intelligent endpoints over intelligentmiddleware‣ ESB as a product is not 90% of an SOA, despiteclaims‣ ESB as a virtual concept is perfectly fineCopyright 2006 innoQ Deutschland GmbH12

Hub & SpokeCopyright 2006 innoQ Deutschland GmbH13

(Enterprise Service) BusCopyright 2006 innoQ Deutschland GmbH14

SOA-based Technical InfrastructureCopyright 2006 innoQ Deutschland GmbH15

More ControversyKey SOA ConceptCopyright 2006 innoQ Deutschland GmbHIrrelevant/Misleading16

More ControversyKey SOA ConceptIrrelevant/Misleading‣ Loose couplingCopyright 2006 innoQ Deutschland GmbH16

More ControversyKey SOA ConceptIrrelevant/Misleading‣ Loose coupling‣ XML DocumentinterchangeCopyright 2006 innoQ Deutschland GmbH16

More ControversyKey SOA ConceptIrrelevant/Misleading‣ Loose coupling‣ XML Documentinterchange‣ Asynchronous MessagingCopyright 2006 innoQ Deutschland GmbH16

More ControversyKey SOA ConceptIrrelevant/Misleading‣ Loose coupling‣ XML Documentinterchange‣ Asynchronous Messaging‣ Standards Support &Vendor IndependenceCopyright 2006 innoQ Deutschland GmbH16

More ControversyKey SOA ConceptIrrelevant/Misleading‣ Loose coupling‣ EAI-style OOTB Adaptors‣ XML Documentinterchange‣ Asynchronous Messaging‣ Standards Support &Vendor IndependenceCopyright 2006 innoQ Deutschland GmbH16

More ControversyKey SOA ConceptIrrelevant/Misleading‣ Loose coupling‣ EAI-style OOTB Adaptors‣ XML Document‣ ESB Productsinterchange‣ Asynchronous Messaging‣ Standards Support &Vendor IndependenceCopyright 2006 innoQ Deutschland GmbH16

More ControversyKey SOA ConceptIrrelevant/Misleading‣ Loose coupling‣ EAI-style OOTB Adaptors‣ XML Document‣ ESB Productsinterchange‣ Protocol independence‣ Asynchronous Messaging‣ Standards Support &Vendor IndependenceCopyright 2006 innoQ Deutschland GmbH16

More ControversyKey SOA ConceptIrrelevant/Misleading‣ Loose coupling‣ EAI-style OOTB Adaptors‣ XML Document‣ ESB Productsinterchange‣ Protocol independence‣ Asynchronous Messaging‣ IDE Support‣ Standards Support &Vendor IndependenceCopyright 2006 innoQ Deutschland GmbH16

More ControversyKey SOA ConceptIrrelevant/Misleading‣ Loose coupling‣ EAI-style OOTB Adaptors‣ XML Document‣ ESB Productsinterchange‣ Protocol independence‣ Asynchronous Messaging‣ IDE Support‣ Standards Support &‣ Stubs & SkeletonsVendor IndependenceCopyright 2006 innoQ Deutschland GmbH16

Non-controversialA clear strategy for creating,maintaining and using metadata is akey aspect of a successful enterpriseSOA and the basis for SOAgovernance.Copyright 2006 innoQ Deutschland GmbH17

tsomalNon-controversialA clear strategy for creating,maintaining and using metadata is akey aspect of a successful enterpriseSOA and the basis for SOAgovernance.Copyright 2006 innoQ Deutschland GmbH17

SOA & GovernanceCopyright 2006 innoQ Deutschland GmbH18

governance ˈgəvərnəns Copyright 2006 innoQ Deutschland GmbH19

governance ˈgəvərnəns nounthe action or manner of governing : a more responsivesystem of governance will be required.archaic sway; control : what, shall King Henry be a pupilstill, under the surly Gloucester's governance ?ORIGIN Middle English : from Old French, fromgoverner (see govern ).Copyright 2006 innoQ Deutschland GmbH20

The act of affecting government andmonitoring (through policy) the long-termstrategy and direction of an organization. Ingeneral, governance comprises the traditions,institutions and processes that determinehow power is exercised, how citizens aregiven a voice, and how decisions are made onissues of public sector/glossary.htmlCopyright 2006 innoQ Deutschland GmbH21

In the context of SOA, governance definesthe model to ensure optimal reuse of servicesand enforcement of corporate policies (eg,business design, technical design, andapplication security).http://www.skywaysoftware.com/resources terminology.htmCopyright 2006 innoQ Deutschland GmbH22

SOA Governance is the process, model andorganization that ensures compliance to theservice-oriented architecture as defined forthe company.Copyright 2006 innoQ Deutschland GmbH23

3 Goals:Copyright 2006 innoQ Deutschland GmbH24

1.Architectural ControlCopyright 2006 innoQ Deutschland GmbH25

2.Subsidiarity Copyright 2006 innoQ Deutschland GmbH26

3.KnowledgeCopyright 2006 innoQ Deutschland GmbH27

SOA & MetadataCopyright 2006 innoQ Deutschland GmbH28

SOA Metadata Examples‣ Service descriptions‣‣ Reusable documentcomponentsService status‣ Service owner‣ Policies‣‣ ContractsDomains‣ Service interface‣ Addresses‣‣ Organization unitsInterface documents‣ Versions‣ BPEL Scripts (?)Copyright 2006 innoQ Deutschland GmbH29

innoQ SOA Metamodel: ExcerptCopyright 2006 innoQ Deutschland GmbH30

An integrated SOA registry/repository can be used as thesingle point of information aboutSOA metadata.Copyright 2006 innoQ Deutschland GmbH31

Registry vs. RepositoryRegistries storeRepositories store‣ references (pointers)‣ actual data‣ metadata‣ metadataOne person's data is the other person's metadataCopyright 2006 innoQ Deutschland GmbH32

UDDI‣ UDDI Universal Description, Discovery andIntegration‣ Standard for registry, not repository‣ A must-have feature for interop reasons - butnot sufficient‣ Every solution requires both registry andrepository‣ There is no single accepted repository standardCopyright 2006 innoQ Deutschland GmbH33

Usage ScenariosDesign &DevelopmentRuntime‣‣‣‣What services/operations are available?What is the message format?Which versions? (What changes?)Who is responsible?‣ What is the service endpoint (address)?‣ Is a service running?‣ Can consumer and provider policies bematched appropriately?GovernanceCopyright 2006 innoQ Deutschland GmbH‣‣‣‣‣Who uses which service?What is the impact of change?Are services reused?Is documentation & usage compliant?Are SLAs being met?34

Service Life cycle estingProductionEnd-of-LifeCopyright 2006 innoQ Deutschland GmbH35

SolutionsCopyright 2006 innoQ Deutschland GmbH36

Vendors?Copyright 2006 innoQ Deutschland GmbH37AcquisitionOEM License

Reg/Rep ProductsVendor(s)SystinetMercuryHPSoftware AGFujitsuInfraviowebMethodsCopyright 2006 innoQ Deutschland GmbHProductSystinet http://www.infravio.com/products/38

Interoperability InitiativesGovernanceInteroperabilityFramework (GIF)Systinet/Mercury/HPSOA are AG/FujitsuAmberpointXXComposite SoftwareXXForum SoftwareXXXHPXXLayer ods, Intalio, IONA,JBoss, LogicBlaze, .IDS Scheer, arcplan, Seagull,VORDEL, .Service Integrity, MetaMatrix, .Copyright 2006 innoQ Deutschland GmbH39

What’s at the core of arepository?Copyright 2006 innoQ Deutschland GmbH40

Copyright 2006 innoQ Deutschland GmbH41

RDBMS-based Reg/RepCASE ToolService Design ToolSOA MetamodelAccess LayerGeneratorGeneratorRepositoryMeta ModelTemplatesCopyright 2006 innoQ Deutschland GmbHMeta ModelTemplates42Artifacts

Decentralized WebSolution‣ Ubiquitous protocol for resource access: HTTP‣ RESTful (rely on GET, PUT, POST, DELETE)‣ Decentralized‣ Federated‣ XQuery over HTTP‣ RSS, ATOM (Syndication & Publishing)Copyright 2006 innoQ Deutschland GmbH43

Challenges‣ Integration with CMDB & PortfolioManagement‣ Overlap with configuration management duringdeployment‣ Interfacing with externally controlled servicesCopyright 2006 innoQ Deutschland GmbH44

Conclusion‣ If you do SOA, you have to manage yourmetadata‣ You don’t need to do everything at once‣ A product is possibly more a problem than asolutionCopyright 2006 innoQ Deutschland GmbH45

Mandatory Steps‣ Define your metadata and metamodel‣ Make sure you have a process in place‣ Balance general applicability with YAGNI lessons‣ Decide on some way of IT support‣ Decouple physical and logical addressesCopyright 2006 innoQ Deutschland GmbH46

Purely optional‣ Evaluate and buy products‣ Develop your own large-scale metadatarepository‣ Introduce advanced and/or runtime lookupsCopyright 2006 innoQ Deutschland GmbH47

The single most important statement:You can’t buy SOACopyright 2006 innoQ Deutschland GmbH48

Thank you!Questions?innoQ Deutschland GmbHHalskestraße 17D-40880 RatingenTel 49 2102 77 1620Fax 49 2102 77 1601innoQ Schweiz GmbHGewerbestrasse 11CH-6330 ChamTel 41 41 743 01 11Fax 41 41 743 01 19http://www.innoq.comCopyright 2006 innoQ Deutschland GmbH49

‣ UDDI Universal Description, Discovery and Integration ‣ Standard for registry, not repository ‣ A must-have feature for interop reasons - but not sufficient ‣ Every solution requires both registry and repository ‣ There is no single accepted repository standard 33