Software Components Interaction Standards: - Java 2 Enterprise Edition (J2EE) - Windows Communication Foundation (WCF)
Software Components Interaction Standards: - Java 2 Enterprise Edition (J2EE) - Windows Communication Foundation (WCF)
Standards
Application Client
Typicallyhave GUI.
Abstract windows toolkit
May be., command line interface.
•
•
Java Server Communication
Web Tier and j2ee application
J2ee and ESI tier
Data
J2EE Architect JDBC
RDBMS
Server IIOP
JNDI
JDBC
JTA
JMS
JAF
Applet
EJB Container CORBA
Session Beans Entity Beans
JNDI
Client
Applica-
tion
Directory Services
JavaMail
RMI/IIOP
JMS
JNDI
JDBC
JTA
JMS
JAF
J2ee API
RMI : RMI is an API which allows Java
objects to communicate remotely with
other objects. This API has the same
purpose of CORBA from OMG.
JNDI : provide naming and directory
functionality.
JDBC : Let you invoke SQL command from
java program.
JMS : Messaging standard tat allow to
crate, send, receive and read messages.
JavaMail : to create e-mail.
Windows communication foundation
Introduction
WCF is an extension of the .NET
framework to build and run connected
systems.
WCF provides a unified framework for
building secure and reliable transacted
Web services.
The WCF framework builds loosely-
coupled applications on a service
oriented architecture that
interoperates more securely and
The architectures
The WCF Framework Model
Architecture
T h e fo llo w in g
g ra p h ic illu stra te s
th e m a jo r la ye rs o f
th e W in d o w s
C o m m u n ica tio n
Fo u n d a tio n
a rch ite ctu re .
Contracts and Descriptions
v C o n tra ct d e fin e va rio u s a sp e cts o f th e m e ssa g e syste m .
v T h e d a ta co n tra ct d e scrib e s e ve ry p a ra m e te r th a t m a ke s
u p e ve ry m e ssa g e th a t a se rvice ca n cre a te o r co n su m e .
( The message parameters are defined by XML Schema
d e fin itio n la n g u a g e d o cu m e n ts.)
v T h e m e ssa g e co n tra ct d e fin e s sp e cific m e ssa g e p a rts
u sin g S O A P p ro to co ls, a n d a llo w s fin e r-g ra in e d co n tro l
o ve r p a rts o f th e m e ssa g e , w h e n in te ro p e ra b ility
d e m a n d s su ch p re cisio n .
v T h e se rvice co n tra ct sp e cifie s th e a ctu a lm e th o d
sig n a tu re s o f th e se rvice , a n d is d istrib u te d a s a n
in te rfa ce in o n e o f th e su p p o rte d p ro g ra m m in g
la n g u a g e s, su ch a s V isu a lB a sic o r V isu a lC # .
v Policies and bindings stipulate the conditions required to
communicate with a service.
v
Service Runtime
vThe service runtime layer contains the
behaviors that occur only during the
actual operation of the service, that is,
the runtime behaviors of the service.
vThrottling controls how many messages
are processed, which can be varied if
the demand for the service grows to a
preset limit.
vAn error behavior specifies what occurs
when an internal error occurs on the
service
Messaging
v The messaging layer is composed of channels. A channel
is a component that processes a message in some way.
v A set of channels is also known as a channel stack.
Channels operate on messages and message headers.
v There are two types of channels: transport channels and
protocol channels.
v Transport channels read and write messages from the
network (or some other communication point with the
outside world). Examples of transports are HTTP,
named pipes, TCP, and MSMQ. Examples of encodings
are XML and optimized binary.
v Protocol channels implement message processing
protocols, often by reading or writing additional headers
to the message. Examples of such
Hosting and Activation