Building Service Oriented Architectures with Java and Web Services NY Java SIG Meeting Feb 1st, 2005

1
Building Service Oriented Architectures with
Java and Web ServicesNY Java SIG Meeting Feb
1st, 2005

• Ashutosh Kulkarni, Group Mktg Manager

2
SOA v/s Web services
3
The Solution is SOA

• Service Oriented Architecture (SOA) is an
  integrated software infrastructure and design
  approach, leveraging Web computing standards, for
  delivering business functions as shared services.

4
SOA vs. Web Services

• Web Services
• Business logic exposed as self-describing,
  loosely coupled, reusable services
• Uses low level protocols and infrastructure
• Service Oriented Architecture
• Integrates web services architecture with legacy
  systems in a loosely coupled way.
• Enables higher level IT functionality, such as
  Identity, Security, Management, BP modeling

5
Before SOA
Traditional EAI Middleware MOM Integration Broker
Suites
S2
S1
6
SOA Architecture
Web Computing Standards (Internet)
S1
S2
Computing Approach
SOA Middleware
SOA Middleware
7
Service Integration
8
A Service as a Component
9
A Composite Application
10
Service Integration many Technologies and
artifacts
11
JSR 208 New Container for Service Integration
12
JSR 208 Java Business Integration
13
JSR 208 Architecture
14
Composite Application Descriptor
SOA Composite App Descriptor
15
Deploying a Composite Application
JBI Core Services
Installation Deployment Management Component
Registry
J2SE/J2EE
SOAP
SOAP
JMS
WSDL
WSDL
WSDL
Service 1
Service 2
Service 3
16
Optimizing Service Integration
17
Why XML? And why not?
Advantages and disadvantages

• Advantages
• Ubiquity and momentum
• Transparency
• One syntax (unicode with ltgt)
• Human readable
• Enables loosely coupled robust (infoset) systems
• Disadvantages
• Verbose
• Redundancy
• Data as characters
• More processing
• Parsing and binding

18
Why Who Binary XML?

• Expand range of use of WS
• Limited bandwidth
• Large docs/images
• Fast response
• Many requests, ...
• With the cost-benefits of XML tools!
• Standarization Is Critical!
• W3C Workshop _at_ Sun
• ISO/ITU-T Effort
• Fast Infoset, Fast Schema, Fast WebServices
• W3C XML Binary Characterization WG
• Sun is co-editor, 41 participants, 25
  organizations

19
Standards for Interoperability
Joint ITU-T ISO/IEC standards
X.fws
Fast Web Services
X.finf
X.694
FastInfoset
FastSchema
FastSOAP
Self-describingor structuredcontent
Schema-based content
SOAPmessage with content
20
The Set of Technologies

• Fast Infoset
• For efficient XML Infoset processing
• Binary encoding of XML Infosets
• Substantial improvements (x3-x4 for JAX-RPC)
• Fast Schema
• For efficient schema-based processing
• Binary encoding utilizing schema
• Even better improvement than FI (another x2)
• Fast Web Services
• Combines Fast Infoset and Fast Schema
• Fast SOAP - Binary encoding of SOAP 1.2
• Use of protocol negotiation to adjust encoding

21
Fast and APIs

• Fast Infoset
• Easy under JAX-RPC 1.x, StAX, SAX, DOM
• Easy to use with intermediaries
• Available as Open Source at Java.Net
• FWS
• Limited under 172
• New APIs being refined
• JAX-RPC 2.0 (JSR-224)
• JAXB 2.0 (JSR-222)
• New integrated stack implementation

22
In a Nutshell

• There is a need today for optimized Service
  Integration
• Sun leads in Interop Standards
• WS-I BP, WSS, Liberty, ebRegistry, WSRP
• Sun leads Java specifications and specifications
• JSR 208, Binary XML (Fast Infoset, etc.)
• Sun will continue to lead the industry in helping
  developers build and deploy Service Oriented
  Architectures on the Java platform

23
For More Information

• JSR 208 EG Page
• http//www.jcp.org/en/jsr/detail?id208
• WSDL 2.0
• http//www.w3.org/TR/wsdl20/
• Fast Web Services
• http//jwsdp.dev.java.net
• http//fi.dev.java.net (Open Source)
• W3C XML Binary Characterization WG
• http//www.w3c.org/XML/Binary
• Oasis BPEL TC
• http//www.oasis-open.org/committees/tc_home.php?w
  g_abbrevwsbpel

23
24
THANK YOU

• Ashutosh.Kulkarni_at_sun.com