Knowledge (XXG)

Service Component Architecture

Source 📝

356:. An SCA System represents a set of services providing an area of business functionality that is controlled by a single organization. As an example, for the accounts department in a business, the SCA System might cover all financial-related functions, and it might contain a series of modules dealing with specific areas of accounting, with one for customer accounts and another dealing with accounts payable. To help build and configure the SCA System, Composites can be used as component implementations, in the same way as Java classes or 334:. References can either be linked to services provided by other components in the same module, or references can be linked to services provided outside the module, which can be provided by other modules. References to services provided outside the module, including services provided by other modules, are defined by External Services in the module. Also contained in the module are the linkages between references and services, represented by 310:
consists of a series of artifacts, which are defined by elements contained in XML files. An SCA runtime may have other non-standard representations of the artifacts represented by these XML files, and may allow for the configuration of systems to be modified dynamically. However, the XML files define
376:
After several years of incubation under an informal industry collaboration, early (V1.0) implementations of the specification are now coming to market. The collaboration partners indicated that formal industry standardization would be the appropriate next step and announced their intentions in March
388:
Member Section has been established. Charters for six new Technical Committees (TCs) have been submitted to OASIS and a Call for Participation for Technical Committee members has been issued within the OASIS organization. The Technical Committees planned to start their work in September 2007.
389:
Participation in these OASIS SCA TCs remains open to all companies, non-profit groups, governments, academic institutions, and individuals. Archives of the work will be accessible to both members and non-members, and OASIS will offer a mechanism for public comment.
326:, which contain the business function provided by the module. Components offer their function as services, which can either be used by other components within the same module or which can be made available for use outside the module through 363:
The capture and expression of non-functional requirements, such as security, is an important aspect of service definition, and affects SCA throughout the life-cycle of components and compositions. SCA provides the
53:, encompasses a wide range of technologies and as such is specified in independent specifications to maintain programming language and application environment neutrality. Many times it uses an 290:
SCA was said to provide interoperability through an approach called "Activation". It is the method that provides the highest degree of component autonomy, compared to older "mediation" (e.g.,
349:
declared by the implementation. The component can also configure the implementation with wiring of references declared by the implementation to specific target services.
781: 345:, where an implementation is the piece of program code implementing business functions. The component configures the implementation with specific values for settable 144:
On March 21, 2007, the OSOA Collaboration released the first version of specification. The specifications said that an application designed with SCA should have:
886: 600:"ACM Queue - the Rise and Fall of CORBA: The story behind this once-promising distributed computing technology-why it fell short, and what we can learn from it" 582: 881: 599: 551: 368:
to support specification of constraints, capabilities and Quality of Service (QoS) expectations, from component design through to concrete deployment.
523: 810: 433: 744: 663: 734: 401: 357: 412: 360:
processes. In other words, SCA allows a hierarchy of composites that is arbitrarily deep – such a nested model is termed recursive.
754: 625: 825: 444: 197: 201: 94: 38: 495: 181:
The ability to work with various communications constructs including one-way, asynchronous, call-return, and notification
295: 259: 156: 580: 771: 766: 866: 559: 439: 291: 603: 279:
Specification does not address performance of SOA applications, which continues to be a detractor of adoption.
330:. Components may also depend on services provided by other components — these dependencies are called 102: 820: 767:
Mail of 2013-02-19 with Death of OASIS SCA Assembly technical committee, on that mail the amazing SCA died
230: 54: 802: 205: 817:
An open source C++ SCA container based on inversion-of-control (IoC) and domain-specific-modeling (DSM)
520: 807: 651: 539: 428: 382: 378: 268: 241: 223: 193: 189: 114: 184:
The ability to "bind" to legacy components or services, accessed normally by technologies such as
216: 78: 46: 750: 740: 730: 659: 407: 106: 90: 74: 17: 629: 786: 122: 845: 707: 840: 814: 586: 527: 418: 282:
Focusing on portability (instead of interoperability), making it vulnerable to repeating
708:"Six OASIS Committees Form to Standardize Service Component Architecture (SCA) for SOA" 133:
joined the collaboration of companies working on the technology on September 18, 2006.
126: 50: 861: 148:
Decoupling of application business logic from the details of its invoked service calls
875: 252: 237: 37:) is a software technology designed to provide a model for applications that follow 185: 725: 693: 118: 98: 66: 826:
A French public research project, which includes a SCA runtime called FraSCati
772:
Mail of 2015-02-20 with the leader Jim Marino telling about Oracle killing SCA
219:
requirements, such as security, transactions and the use of reliable messaging
130: 240:
published a short brief that promoted the SCA and its included technology of
850: 136:
In addition to the partners, the SCA community had some formal supporters.
233:, flexibly incorporating reusable components in an SOA programming style. 41:
principles. The technology, created by major software vendors, including
846:
Introducing SCA – A tutorial by David Chappell, Chappell & Associates
835: 694:"Six Technical Committees Proposed for the OASIS Open CSA Member Section" 423: 110: 856: 656:
Service-Oriented Modeling: Service Analysis, Design, and Architecture
519:
Technology srinivas vendors extend collaboration on SOA technologies
86: 82: 798:
Apache Tuscany – Open Source implementation of the SCA specification
521:
http://www.hoise.com/primeur/06/articles/monthly/AE-PR-08-06-92.html
853:
An Open Source Eclipse project that provides a set of tools for SCA
830: 679: 152: 803:
SALT - Enterprise ready SCA runtime for C++, Python, Ruby, and PHP
540:
http://www.osoa.org/display/Main/Current+OSOA+Supporters+Community
283: 209: 160: 322:
that can be accessed remotely. A composite contains one or more
176: 172: 791: 469: 385: 797: 724:
Understanding SCA from experts Jim Marino and Michael Rowley
263: 168: 164: 70: 42: 776: 626:"community.user: Comparing SCA, Java EE and JBI | SCN" 377:
2007. The chosen Standards Development Organization is the
65:
The original partners announced on November 30, 2005 were:
318:, which is the unit of deployment for SCA and which holds 258:
less technology dependence – does not have to rely on the
494:
Daniel Sholler; David Mitchell Smith (December 5, 2005).
729:
SOA for the Business Developer: Concepts, BPEL, and SCA—
496:"New SOA Specification Will Fill Niche Among Java Users" 215:
The ability to declare (outside of business logic) the
229:
SCA, therefore, was promoted to offer flexibility for
151:
Target services in a multitude of languages including
857:
Microservice architecture patterns and best practices
821:
Newton open source distributed SCA & OSGi runtime
93:. Additional members announced on July 26, 2006 were 311:the portable representation of the SCA artifacts. 777:NetBeans SOA Composite Application Project Home 552:"Service Component Architecture Specifications" 867:Smart endpoints and dumb pipes – martinfowler 489: 487: 271:is a technology specification for data access 8: 862:martinfowler microservice architecture site 628:. Sdn.sap.com. 2005-12-12. Archived from 680:"OASIS Open CSA Member Section for SCA" 463: 461: 457: 298:, as explained by an architect at SAP. 836:Current SCA Resources & Collateral 434:Semantic service-oriented architecture 887:Service-oriented (business computing) 341:A component consists of a configured 7: 652:"Service-Oriented Conceptualization" 792:Introduction to programming for SCA 402:Business Process Model and Notation 882:Enterprise application integration 413:Enterprise application integration 352:Composites are deployed within an 25: 294:) or "Invocation" method used in 470:"Service Component Architecture" 445:Windows Communication Foundation 831:SCA Home Page at OASIS web site 787:Running Apache Camel in OpenESB 658:. Wiley & Sons. p. 3. 556:Open SOA Collaboration web site 589:SCA & SDO, the next Corba? 372:Transition to a standards body 31:Service Component Architecture 18:Service component architecture 1: 222:Data could be represented in 39:service-oriented architecture 851:Eclipse STP/SCA sub project 538:OSOA Technology Supporters 903: 808:PocoCapsule for WS and SCA 739:Apache Tuscany in Action, 615:The rise and fall of CORBA 314:The basic artifact is the 841:Latest SCA & SDO News 440:Service-oriented modeling 260:Java programming language 244:(SDO) in December 2005 . 251:caters for all existing 650:Bell, Michael (2008). 231:composite applications 55:enterprise service bus 103:Primeton Technologies 429:Reactive programming 269:Service Data Objects 255:technologies and C++ 242:Service Data Objects 224:Service Data Objects 562:on October 12, 2007 115:Rogue Wave Software 27:Software technology 813:2007-11-19 at the 585:2008-07-05 at the 526:2011-07-12 at the 379:OASIS organization 308:SCA Assembly Model 217:quality of service 79:Oracle Corporation 47:Oracle Corporation 749:Open Source SOA, 745:978-1-933988-89-4 665:978-0-470-14111-3 408:Docker (software) 398:Apache ServiceMix 107:Progress Software 91:Zend Technologies 75:IONA Technologies 16:(Redirected from 894: 735:978-158347-065-7 712: 711: 704: 698: 697: 690: 684: 683: 676: 670: 669: 647: 641: 640: 638: 637: 622: 616: 614: 612: 611: 602:. Archived from 596: 590: 578: 572: 571: 569: 567: 558:. Archived from 548: 542: 536: 530: 517: 511: 510: 508: 506: 500: 491: 482: 481: 479: 477: 465: 366:Policy Framework 123:Sun Microsystems 21: 902: 901: 897: 896: 895: 893: 892: 891: 872: 871: 815:Wayback Machine 763: 721: 719:Further reading 716: 715: 706: 705: 701: 692: 691: 687: 678: 677: 673: 666: 649: 648: 644: 635: 633: 624: 623: 619: 609: 607: 598: 597: 593: 587:Wayback Machine 579: 575: 565: 563: 550: 549: 545: 537: 533: 528:Wayback Machine 518: 514: 504: 502: 501:. Gartner Group 498: 493: 492: 485: 475: 473: 468:Edwards, Mike. 467: 466: 459: 454: 419:Mule (software) 395: 374: 304: 275:Disadvantages: 236:Marketing firm 142: 63: 28: 23: 22: 15: 12: 11: 5: 900: 898: 890: 889: 884: 874: 873: 870: 869: 864: 859: 854: 848: 843: 838: 833: 828: 823: 818: 805: 800: 795: 789: 784: 779: 774: 769: 762: 761:External links 759: 758: 757: 747: 737: 727: 720: 717: 714: 713: 699: 685: 671: 664: 642: 617: 591: 573: 543: 531: 512: 483: 456: 455: 453: 450: 449: 448: 442: 437: 431: 426: 421: 416: 410: 405: 399: 394: 391: 373: 370: 343:implementation 303: 300: 288: 287: 280: 273: 272: 266: 256: 227: 226: 220: 213: 182: 179: 149: 141: 138: 127:TIBCO Software 62: 59: 51:TIBCO Software 26: 24: 14: 13: 10: 9: 6: 4: 3: 2: 899: 888: 885: 883: 880: 879: 877: 868: 865: 863: 860: 858: 855: 852: 849: 847: 844: 842: 839: 837: 834: 832: 829: 827: 824: 822: 819: 816: 812: 809: 806: 804: 801: 799: 796: 793: 790: 788: 785: 783: 780: 778: 775: 773: 770: 768: 765: 764: 760: 756: 755:1-933988-54-1 752: 748: 746: 742: 738: 736: 732: 728: 726: 723: 722: 718: 709: 703: 700: 695: 689: 686: 681: 675: 672: 667: 661: 657: 653: 646: 643: 632:on 2012-12-17 631: 627: 621: 618: 606:on 2008-12-02 605: 601: 595: 592: 588: 584: 581: 577: 574: 561: 557: 553: 547: 544: 541: 535: 532: 529: 525: 522: 516: 513: 497: 490: 488: 484: 471: 464: 462: 458: 451: 446: 443: 441: 438: 435: 432: 430: 427: 425: 422: 420: 417: 414: 411: 409: 406: 403: 400: 397: 396: 392: 390: 387: 384: 380: 371: 369: 367: 361: 359: 355: 350: 348: 344: 339: 337: 333: 329: 325: 321: 317: 312: 309: 301: 299: 297: 293: 285: 281: 278: 277: 276: 270: 267: 265: 261: 257: 254: 253:Java platform 250: 249: 248: 245: 243: 239: 238:Gartner Group 234: 232: 225: 221: 218: 214: 211: 207: 203: 199: 195: 191: 187: 183: 180: 178: 174: 170: 166: 162: 158: 154: 150: 147: 146: 145: 139: 137: 134: 132: 128: 124: 120: 116: 112: 108: 104: 100: 96: 92: 89:, Xcalia and 88: 84: 80: 76: 72: 68: 60: 58: 56: 52: 48: 44: 40: 36: 32: 19: 702: 688: 674: 655: 645: 634:. Retrieved 630:the original 620: 608:. Retrieved 604:the original 594: 576: 564:. Retrieved 560:the original 555: 546: 534: 515: 503:. Retrieved 474:. Retrieved 381:, and a new 375: 365: 362: 353: 351: 346: 342: 340: 335: 331: 328:Entry Points 327: 323: 319: 315: 313: 307: 305: 289: 286:'s mistakes. 274: 247:Advantages: 246: 235: 228: 186:Web Services 143: 135: 64: 34: 30: 29: 167:as well as 119:Software AG 99:Interface21 67:BEA Systems 876:Categories 794:Dr. Dobb's 636:2013-06-16 610:2011-04-08 452:References 354:SCA System 347:properties 332:references 324:components 212:and others 140:Definition 131:Siemens AG 95:Cape Clear 566:April 29, 505:April 29, 316:composite 302:Artifacts 811:Archived 583:Archived 524:Archived 424:Open ESB 393:See also 386:Open CSA 320:services 782:camelse 476:7 April 472:. OASIS 111:Red Hat 61:History 57:(ESB). 753:  743:  733:  662:  436:(SSOA) 404:(BPMN) 175:, and 163:, and 87:Sybase 83:SAP AG 499:(PDF) 447:(WCF) 415:(EAI) 383:OASIS 336:wires 284:CORBA 210:CORBA 161:COBOL 751:ISBN 741:ISBN 731:ISBN 660:ISBN 568:2017 507:2017 478:2011 358:BPEL 306:The 177:XSLT 173:BPEL 157:Java 125:and 49:and 296:JCA 292:JBI 264:XML 262:or 206:RPC 202:RMI 198:JCA 194:JMS 190:EJB 169:XML 165:PHP 153:C++ 71:IBM 43:IBM 35:SCA 878:: 654:. 554:. 486:^ 460:^ 338:. 208:, 204:, 200:, 196:, 192:, 188:, 171:, 159:, 155:, 129:. 121:, 117:, 113:, 109:, 105:, 101:, 97:, 85:, 81:, 77:, 73:, 69:, 45:, 710:. 696:. 682:. 668:. 639:. 613:. 570:. 509:. 480:. 33:( 20:)

Index

Service component architecture
service-oriented architecture
IBM
Oracle Corporation
TIBCO Software
enterprise service bus
BEA Systems
IBM
IONA Technologies
Oracle Corporation
SAP AG
Sybase
Zend Technologies
Cape Clear
Interface21
Primeton Technologies
Progress Software
Red Hat
Rogue Wave Software
Software AG
Sun Microsystems
TIBCO Software
Siemens AG
C++
Java
COBOL
PHP
XML
BPEL
XSLT

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.