Overview - SCA feature pack release contents Overview – SCA feature pack release contents IBM® WebSphere® Application Server V7 Feature Pack for Service Component Architecture This presentation will cover an overview of the WebSphere Application Server V7.0 Feature Pack for SCA release specifically the contents of the SCA feature pack. Agenda Agenda SCA FP release contents Summary and references This presentation will look at what’s in the SCA feature pack at high level and finally summarize. SCA Feature pack : Delivery overview SCA Feature pack : Delivery overview Uses Apache Tuscany open source SCA V1.0 to provide support for SCA and provide deep integration with WebSphere Application Server Simple SCA POJO application management through extension of the new WebSphere application management framework : business level application Enhanced quality of service through integration with WebSphere security management , transaction management and Web services policy management IBM WebSphere Application Server V7 Feature Pack for SCA delivers critical technology that enables adoption of Service-Oriented Architecture (SOA) principles. As part of the larger SOA Foundation, which straddles all of IBM software brands, this feature pack delivers an integrated, open implementation of Service Component Architecture (SCA). SCA is a technology specified by IBM and other industry leaders through the Open SOA Collaboration (www.osoa.org). WebSphere has taken the open source SCA v1.0 implementation from Tuscany, an Apache project, and integrated it with WebSphere Application Server. This integration ensures that all of WebSphere’s capabilities work together with SCA applications to provide a natural environment for both the SCA and existing applications. IBM WebSphere Application Server V7 Feature Pack for SCA and the underlying Tuscany framework, is a "proof-point" delivery of SCA built using a plug-in concept. IBM plans to augment and enhance this initial support in subsequent releases by providing additional plug-in capabilities. In this release there has also been additions in the application management with simple SCA POJO applications being extended into business level applications in WebSphere Application Server. Quality service has also been enhanced through the integration with WebSphere security management, transaction management and Web services policy management. The primary objective of this initial release is to highlight usage of SCA. SCA enables users to create composite applications using new or existing assets. The key principle of SOA demonstrated by this support could be described as "Use what you have got and run it where it lives," or "Use your existing services to create new ones." Another key objective of this initial delivery of SCA is to highlight the ease-of-use characteristics of SCA service development in Java™. This is accomplished by demonstrating annotated plain-old java-object (POJO) components deployed using simple JAR packaging schemes, an easy to use assembly model, and powerful wiring abstractions that enable service definition over different transports and protocols. It makes development and maintenance easier by moving protocols out of business logic. The key principle of SOA demonstrated by this support might be described as “Know only what you need to know to get your job done,” or “Maintain proper separation of concerns.” Feature Pack for SCA highlights SCA Feature Pack for SCA highlights Foundation for Open SCA Trans. Security QoS WebSphere Application Server Web service (SOAP) Service Composition Programming model support for building composite applications to leverage services that reside within a Services Oriented Architecture Service Assembly/development Programming model for building and deploying services that can be used within a Services Oriented Architecture EJB 2.1, 3.0 Service Oriented Architecture (SOA) Existing Enterprise Services Composite Applications / Services SCA SCA WebSphere Application Server 6.1 Other Platforms Composite Applications Business Services Supported Bindings: WS, EJB2-3, SCA Supported Bindings: WS, EJB2-3, SCA WebSphere has chosen to embrace the open source Apache project Tuscany to provide the core of the SCA runtime and then support with the world-class enterprise application server functions inherent in the WebSphere Application Server V7 were integrated. This picture shows the specific highlights of the SCA feature pack. What is contained in the feature pack can be classified into three groups: (1) Features under service composition on the application server. (2) Features under Simple Service development (3) and features under WebSphere application server SCA foundation – agility and flexibility Service Composition Businesses today are challenged not only by competitors, but by social and economic pressures that directly affect their information technology systems. As businesses adopt SOA and build a growing inventory of business services, there is a real need to be able to compose, reuse, and otherwise assemble new services from those existing business services. SCA offers a metadata assembly and composition model for assembling and constructing coarse-grained services out of software components and other services. In a sense, SCA applies the hardware circuit-board paradigm to software programming. While service implementations are vital to the functioning of the overall application, they can also be viewed as “chips” because details of their inner workings are hidden from the assembler. SCA assemblies provide the metadata language to describe the chips, hide certain details, and provide wiring and binding semantics to the workings inside the chips, and to those exposed outside the chip. This metadata assembly language is called Service Component Definition Language (SCDL). In the hardware realm, wires have physical constraints, such a certain voltage range or frequency of operation. Software “wires” have similar constraints which are expressed as SCA policy. Service Development SCA has a language-neutral programming model for which there are multiple language-specific specifications defined at OSOA. The language-specific component models include Java, Spring, and C++. Being a Java runtime, WebSphere supports SCA in Java in a first-class and natural way. The concepts of SCA apply broadly across both Java and non-Java application environments. The SCA component model has at its heart a strong focus on a proper separation of concerns. The service consumer business logic author should not need to know the details of the service implementation. For instance, a Java service consumer should not be burdened with having to know that a target service is implemented using C++ or COBOL. A logical name can be used to identify a service, for example, “MyStockQuoteService,” and that name can be used in SCA wires to delegate the specific details of service connectivity to the SCA runtime. Essentially, the application programmer is telling SCA to use the best connectivity alternatives available to wire the service consumer to the service providing “MyStockQuoteService.” Service Agility and Flexibility One of the key reasons for SOA is to provide a set of patterns and best practices–formalized through infrastructural concepts and products--that allows businesses to realign and remission multiple aspects of information technology. In short, IT professionals need to be able to rewire, recast, and reuse applications in very flexible ways to keep up with business needs in the tumultuous and dynamic business climates faced today. IBM's initial delivery of SCA in this feature pack highlights the flexibility and agility of metadata bindings, and the appropriate separation of concerns. The ability to rewire, compose, and assemble business logic without impacting the business logic itself is key. Functional description – Highlights (1) Functional description – Highlights (1) Based on Tuscany SCA Java implementation POJO service component implementations Tuscany component container Bindings for Web services (WS feature pack), and EJB2 and EJB3 Admin Extensions – panels, commands, application install (based on BLA), MBeans Native SCA2 packaging model (jars) The SCA feature pack is consuming a subset of Tuscany that implements SCA V1.0. In particular it includes assembly and Java support and bindings such as: POJO Service component implementations. Bindings which include Web services, EJB2 and EJB3. The protocol used internally for default binding is currently is IIOP (for cross-JVM) Admin Extensions – application management piece on business level applications Native SCA2 packaging model which include jars. Functional description – Highlights (2) Functional description – Highlights (2) Policy framework – interaction, implementation policy Qos Extensions (security, transactions, reliability) Web service profile integration JAXB data bindings RAS (log/trace), FFDC, ARM Technology samples In the area of policy framework, security policies, transaction policies, and reliability. In databindings, JAXB databinding is implemented. Technology samples such as multiservice, candystore, jobbank and others showing different bindings have been implemented and are also included. ** ARM is an Open Group standard to measure the performance and availability of applications or business services. It's instrumented by the applications in development phase, and used at run time to analyze the transactions that are involved. Security Security Based on SCA V1.0 Policy Framework Abstract intents mapped to WebSphere Application Server PolicySets Authentication, authorization, Runas, WS Policy Interaction policy Transport security, authentication, message protection WS-Security, WS-I BSP Implementation policy Role assignment, authorization rules, runas role For security, intents, policy sets, authorization policies are all implemented. Benefits of SCA feature pack Benefits of SCA feature pack Perform basic service composition in new POJO-based SCA applications. (Reuse) Develop and deploy services that leverage SCA natively to simplify access from different application types. (Reuse, Connectivity) Key technology components supported Java (POJO) language support Wiring support: SCA, Web services (SOAP), EJB2-3 SCA data support: JAXB data bindings Quality of Service (QoS) and full WebSphere Application Server platform support The benefits of SCA Feature pack include the ability to perform basic service composition in new POJO-based SCA applications. (Reuse). Another benefit is to develop and deploy services that leverage SCA natively to simplify access from different application types. (Reuse, Connectivity) Key technology components supported: Java (POJO) language support Wiring Support: SCA, Web services (SOAP), EJB2 and EJB3.0 SCA Data Support: JAXB static data bindings Quality of Service (QoS) and full WebSphere Application Server platform support Summary and references Summary and references Section Summary Summary IBM WebSphere Application Server V7 feature pack for SCA makes service oriented architecture simpler for developers preserves and enhances the value of existing assets provides a consistent system-wide abstraction service abstraction can apply QoS policies (security, reliability, …) at the service abstraction Simplicity, Consistency, Abstraction SCA Feature pack makes SOA simpler for developers in that application is structured as services and components. Business logic is not coupled to deployment infrastructure and there is wide choice of component kinds (use the right tool for the job). As a result, this makes developers stay focused on solving business problems, rather than getting bogged down in the individual complexities of the technologies that connect service consumers and service providers. SCA feature pack preserves and enhances the value of existing assets which can be exposed as SCA services. SCA feature pack can model and integrate assets from a heterogeneous mix of new and existing runtime environments and provide a consistent system-wide abstraction. Service abstraction captures the SOA design and its mapping to underlying implementations. SCA feature pack can apply QoS policies (security, reliability, and others) at the service abstraction level across different runtime implementations. References References Open Service Oriented Architecture Web site http://www.osoa.org/ Apache Tuscany Web site http://incubator.apache.org/tuscany/ developerWorks® http://www.ibm.com/developerworks/websphere SCA white papers – open SCA FP beta site: https://www14.software.ibm.com/iwm/web/cc/earlyprograms/websphere/soawas61/ Feedback Feedback Your feedback is valuable You can help improve the quality of IBM Education Assistant content to better meet your needs by providing feedback. Did you find this module useful? Did it help you solve a problem or answer a question? Do you have suggestions for improvements? Click to send e-mail feedback: mailto:iea@us.ibm.com?subject=Feedback_about_WASv7SCA_Overview_SCAfp_Releasecontents.ppt This module is also available in PDF format at: ../WASv7SCA_Overview_SCAfp_Releasecontents.pdf You can help improve the quality of IBM Education Assistant content by providing feedback. Trademarks