Patterns: Extended Enterprise SOA and Web Services

150 Patterns: Extended Enterprise SOA and Web Services

򐂰 The role of private UDDI nodes in Web services, Part 1: Six species of UDDI

http://www.ibm.com/developerworks/webservices/library/ws-rpu1.html

򐂰 The role of private UDDI nodes, Part 2: Private nodes and operator nodes

http://www.ibm.com/developerworks/webservices/library/ws-rpu2.html

9.1.5 WS-BPEL

Business Process Execution Language for Web Services (WS-BPEL) provides a

means to formally specify business processes and interaction protocols.

WS-BPEL (formerly BPEL4WS) provides a language for the formal specification

of business processes and business interaction protocols. By doing so, it extends

the Web services interaction model and enables it to support business

transactions. WS-BPEL defines an interoperable integration model that should

facilitate the expansion of automated process integration in both the

intra-corporate and the business-to-business spaces.

9.1.6 WS-Security

The security protocols for Web services begin with the WS-Security specification

that defines a token-based architecture for secure communications. There are six

major component specifications built on this base:

򐂰 WS-Policy and its related specifications define the policy rules on how

services interact.

򐂰 WS-Trust defines the trust model for secure exchange.

򐂰 WS-Privacy defines how privacy of information is maintained.

򐂰 WS-SecureConversation defines how to establish a secured session between

services for exchanging data using the rules defined in WS-Policy, WS-Trust,

and WS-Privacy.

򐂰 WS-Federation defines the rules of distributed identity and how it is managed.

򐂰 WS-Authorization handles the processing for authorization to access and

exchange data.

9.2 J2EE

Java technology is both an object-oriented programming language and a platform

originally developed by Sun Microsystems. The Java platform consists of the

Java Application Programming Interface (API) and the Java Virtual Machine

(JVM), an interpreter between the programming language and the underlying

Chapter 9. Technology options 151

software and hardware architectures. The Java API is a large collection of

ready-made software components to ease the development and deployment of

applets and applications, including robust, secure and interoperable enterprise

applications.

J2EE (Java 2 Enterprise Edition) is the enterprise version of Java that simplifies

the construction and deployment of multitier enterprise applications by basing

them on standardized modular components. It provides a complete set of

services to those components, and by handling many details of application

behavior automatically without complex programming.

Java technology is critical to the IBM On Demand Business initiative. Java was

one of the first technologies to support open standards in the enterprise,

enabling customers to adopt XML and Web services in seamless information and

application integration. Additionally, Java serves as the cornerstone of many IBM

products and technology consulting services.

9.2.1 JMS

Java Message Service (JMS) is an API that adds a provider framework that

enables the development of portable, message-based applications for the Java

platform by defining a common set of messaging concepts and programming

strategies that will be supported by all JMS technology-compliant messaging

systems.

9.2.2 Web services for J2EE

Web services for J2EE (WSEE) leverages J2EE technologies, defining the

needed mechanism to standardize a deployment model for Web services. This

standardization aims to achieve interoperability across different, compliant J2EE

platforms, transforming the migration among them into a routine process and

ensuring that vendors interoperate.

WSEE defines the concepts, interfaces, file formats, and responsibilities to

support the development and runtime models for Web services.

Note: A large community of developers, testers and technology experts

contribute to the Java APIs through a community process known as the Java

Community Process (JCP). IBM has contributed significantly to the JCP since

the birth of J2EE and continues to do so. You can track the JCP at:

http://www.jcp.org/en/home/index/