SOAP, Web Services,

and E-Commerce
K.Saranya
KCT
  SOAP opens up new options for distributed computing.
 SOAP as a distributed protocol for communicating across the Web

OAP, Web
ervices, and
Commerce
  Web-based e-commerce needs transaction capability
 Transactions, security, and identity are critical to the success of
the new Web environment (SOAP+Web Service)
 Transactions
 A transaction is a set of software operations that share what is
known as the ACID properties of transactions: atomicity,
OAP, Web consistency, isolation, and durability.

ervices, and  Security

 The Secure Sockets Layer and Transport Layer Security protocols
Commerce have been successful in verifying the authentication of Web sites,
encrypting the transfer of data, and ensuring the integrity of
information exchange.

 Identity
 Web-based networks need a way to validate users.
 Microsoft's Passport technology and the Sun-backed Liberty
Alliance
  .NET and J2EE are frameworks for enterprise computing.

NET, J2EE
  Microsoft's .NET represents the implementation of a complete
enterprise architecture tuned to the Windows platform

 J2EE, on the other hand, is a specification of architectural

.NET, J2EE components designed to work together to define a complete
enterprise architecture.

 J2EE is a specification, it requires implementation from vendors

such as Sun, IBM, BEA, Oracle, and HP
  .NET: a Microsoft framework.
 Microsoft's .NET is an umbrella term that describes Microsoft's
strategy for delivering software as services across the Web
 .NET is based on earlier Microsoft technology
 The .NET initiative represents a development framework that
integrates earlier Microsoft technologies with newer technologies
.NET built around XML
 The result is an integrated framework focused on the Internet that
packages the component services of the earlier extension to the
Component Object Model known as COM+ and the Active Server
Pages (ASP) Web development framework with XML and support
for XML protocols such as SOAP, WSDL, and UDDI.
 .NET architecture includes several technology components:
 Development tools: A set of languages, including C# and VB.NET; a
set of development tools, including VisualStudio.NET
 Specialized servers: A set of .NET Enterprise Servers that provide
specialized functionality for relational data storage, email, and B2B
commerce
.NET  Web services: Support services such as Passport and .NET My Services
that let developers build applications that require knowledge of user
identity
 Devices: New .NET-enabled non-PC devices, from cell phones to game
boxes. Microsoft is devoting considerable resources to the
development and success of .NET and related technologies; their bets
are on .NET as the next big thing in computing.
.NET
  A Common Language Runtime supports different languages for
.NET development.
 Key ingredients of the .NET Framework are CLR and a common
framework of classes that can be used by all
he .NET  With .NET all languages translate into a CLR.

amework  MTS is the Microsoft transaction engine.

 Their transaction software was based on a Object Transaction
Monitor, integrating the capabilities of a Transaction-Processing
Monitor with distributed object services
  J2EE is the Java-centric enterprise platform specification.
 J2EE is a standard for building robust enterprise applications
based on an evolving vision of application-server technology
centered around the Java programming language.
 It has historically been used to build Web sites and applications
around Enterprise JavaBeans (EJB). Recently it has been extended
J2EE to include support for XML and Web services.
 J2EE is now part of a collaborative process.
 While J2EE originated with Sun, changes to the J2EE specification
are under the collaborative umbrella of the Java Community
Process with input from vendors who have J2EE-compliant server
products.
  The Web Services Pack includes the following APIs:
 Java API for XML Processing (JAXP): JAXP gives developers flexibility b
letting them easily swap out XML parsers, Without JAXP, it's easy to get locke
into one vendor's XML parser.
 Java Architecture for XML Binding (JAXB): JAXB is a Java API and toolset f
creating two-way mapping between XML documents and Java objects. JAX
simplifies the task of going from an XML document type definition or schem
and creating a program to process a conformant XML document. JAXB enabl
J2EE the creation of Java classes from the schema. JAXB greatly simplifies th
process, which was complex, error prone, and often not portable.
 Java API for XML Messaging (JAXM): JAXM is designed to allow access
emerging XML messaging standards such as Electronic Business XML (ebXM
Transport/Packaging and Routing
 Java API for XML Remote Procedure Calls (JAX-RPC): JAX-RPC is the API f
doing XML-based procedure calls via XML-RPC in Java. XML-RPC allows on
network node to execute code on another node by transferring XML data.
 Java API for XML Registries (JAXR): JAXR provides a uniform standa
interface to registries of XML business data such as the UDDI protocol.
J2EE