Introduction to Oracle SOA Suite

Introduction to Building Applications with Oracle SOA Suite 1-3 Consequently, you can use static or dynamic programming styles and obtain connected and disconnected access. ■ Business Process Execution Language BPEL Provides enterprises with an industry standard for business-process orchestration and execution. Using BPEL, you design a business process that integrates a series of discrete services into an end-to-end process flow. This integration reduces process cost and complexity. BPEL versions 1.1 and 2.0 are supported. ■ XSL Transformations XSLT Processes XML documents and transforms document data from one XML schema to another. ■ Java Connector Architecture JCA Provides a Java technology solution to the problem of connectivity between the many application servers in Enterprise Information Systems EIS. ■ Java Messaging Service JMS Provides a messaging standard that allows application components based on the Java 2 Platform, Enterprise Edition Java EE to access business logic distributed among heterogeneous systems. ■ Web Services Description Language WSDL file Provides the entry points into a SOA composite application. The WSDL file provides a standard contract language and is central for understanding the capabilities of a service. ■ Simple Object Access Protocol SOAP Provides the default network protocol for message delivery.

1.5 Service Component Architecture within SOA Composite Applications

Oracle SOA Suite uses the SCA standard as a way to assemble service components into a SOA composite application. SCA provides a programming model for the following: ■ Creating service components written with a wide range of technologies, including programming languages such as Java, BPEL, C++, and declarative languages such as XSLT. The use of specific programming languages and technologies including web services is not required with SCA. ■ Assembling the service components into a SOA composite application. In the SCA environment, service components are the building blocks of applications. SCA provides a model for assembling distributed groups of service components into an application, enabling you to describe the details of a service and how services and service components interact. Composites are used to group service components and wires are used to connect service components. SCA helps to remove middleware concerns from the programming code by applying infrastructure declaratively to composites, including security and transactions. The key benefits of SCA include the following: ■ Loose coupling Service components integrate with other service components without needing to know how other service components are implemented.