Building Service-Oriented Architectures with Java and Web ...
24
Building Service Oriented Architectures with Java and Web Services NY Java SIG Meeting – Feb 1st, 2005 Ashutosh Kulkarni, Group Mktg Manager
description
Transcript of Building Service-Oriented Architectures with Java and Web ...
Building Service Oriented Architectures with Java and Web ServicesNY Java SIG Meeting – Feb 1st, 2005
Ashutosh Kulkarni, Group Mktg Manager
SOA v/s
Web services
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.
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
Before SOA
S1
S2Traditional EAI MiddlewareMOMIntegration Broker Suites
SOA Architecture
Computing Approach
SOA Middleware
S1
SOA Middleware
S2Web ComputingStandards(Internet)
Service Integration
A Service as a Component
A Composite Application
Service Integration – many Technologies and artifacts
JSR 208: New Container for Service Integration
JSR 208: Java Business Integration
JSR 208 Architecture
JBI CoreServices
Normalized Message Service InstallationDeploymentManagement
Component Registry
Syst
em
M
an
ag
em
en
tA
dm
in.
Con
sole
Log
ger
Dis
covery
&
Dep
loym
en
t
Orchestration
(BPEL)WSD
L
Transformation
(XSLT)WSD
L
J2EE
WSDL
Filesystem
WSDL
JMS
WSDLWS-I Basic
+Basic
Security
WSDL
Other Bindings
WSDL
Other Service Engines
WSDL
Service1
Service2
Service3
SOAP SOAP JMS
WSDL WSDL WSDL
J2SE/J2EE
Composite Application Descriptor
JBI CoreServices
Normalized Message Service InstallationDeploymentManagementComponent
Registry
Syst
em
M
anagem
ent
Adm
in.
Conso
leLo
gg
er
Dis
covery
&
Deplo
ym
ent
Orchestration
(BPEL)WSD
L
Transformation
(XSLT)WSD
L
J2EE
WSDL
Filesystem
WSDL
JMS
WSDLWS-I Basic +
Basic Security
WSDL
Other Bindings
WSDL
Other Service Engines
WSDL
Service1
Service2
Service3
SOAP SOAP JMS
WSDL WSDL WSDL
J2SE/J2EE
Application Element Artifact
Service Orchestration BPEL
Data Transformation XSLT
Service 1 WSDL
Service 2 WSDL
Service 3 WSDL
SOA Composite App Descriptor
Deploying a Composite Application
JBI CoreServices
InstallationDeploymentManagementComponent
Registry
Syst
em
M
anagem
ent
Adm
in.
Conso
leLo
gg
er
Dis
covery
&
Deplo
ym
ent
Orchestration
(BPEL)WSD
L
Transformation
(XSLT)WSD
L
J2EE
WSDL
Filesystem
WSDL
JMS
WSDLWS-I Basic +
Basic Security
WSDL
Other Bindings
WSDL
Other Service Engines
WSDL
Service1
Service2
Service3
SOAP SOAP JMS
WSDL WSDL WSDL
J2SE/J2EE
Application Element Artifact
Service Orchestration BPEL
Data Transformation XSLT
Service 1 WSDL
Service 2 WSDL
Service 3 WSDL
Optimizing Service Integration
Why XML? And why not?
● Advantages– Ubiquity and momentum– Transparency
● One syntax (unicode with <>)● Human readable
– Enables loosely coupled robust (infoset) systems● Disadvantages
– Verbose● Redundancy● Data as characters
– More processing● Parsing and binding
Advantages and disadvantages
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 @ Sun– ISO/ITU-T Effort
● Fast Infoset, Fast Schema, Fast WebServices
– W3C XML Binary Characterization WG● Sun is co-editor, 41 participants, 25 organizations
Standards for InteroperabilityJoint ITU-T | ISO/IEC standards
Fast Web ServicesFastInfoset
FastSchemaFast
SOAP
X.finf X.694
X.fws
Self-describingor structured
content SOAPmessage
with content
Schema-basedcontent
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
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
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?id=208● 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?
wg_abbrev=wsbpel
