Web Services .NET and Java based Approaches ebXML

1
Web Services - .NET and Java based
ApproachesebXML

• P K Kanti Kiran
• 02305006
• kanti_at_cse.iitb.ac.in

2
Outline

• Web Services building - .NET
• Comparison with Java based ones and
  interoperability.
• ebXML over Web Services in business domain.
• Where is it heading?

3
Building Web Services using ASP.NET

• C and .NET
• Runtime IIS
• .asmx file

4
Simple currency converter Web Service

• using System.Web.Servicespublic class
  CurrConv   WebMethod()   public double
  DM2EUR (double DMvalue)          return sDM
  X      WebMethod()   public double EUR2DM
  (double EURvalue)          return sEUR Y  
  

5
Using these Services

• Write a SOAP aware client in any of .NETs CLR
  languages.
• Use ASP.NETs intrinsic test page.
• Web Services URL in address bar
  http//localhost/pinpub/currencyconverter.asmx

6

• Portability (across Web Platforms)
• .NET Web Services integrated with IIS.
• HTTP Runtime and the pipeline can be hosted in
  another Web Server (Apache)
• Across OS now in Linux.
• Building and deploying Web Services very
  simple.
• Code-behind model separate implementation logic
  from Web Service endpoint implementation.

7
Differences Java and .NET Platforms
8
Interoperability Apache Axis 1.1, Microsoft
.NET Framework 1.0/1.1

• Java data types - String, boolean, byte, short,
  int, long, float, and double.
• Primitive wrappers java.lang.Integer,
  java.lang.Double C object datatype.
• .NET no support for attachments WSE adds
  support for DIME (Installation of WSE on client
  machines).
• Axis supports MIME and DIME.

9
Maximum Interoperability - Avoid

• Multi-dimensional and jagged arrays.
• The Java char datatype is not supported because
  of an omission in XML Schema.
• Avoid using the same method name multiple times
  with varying parameters on a web service.

10
ebXML - auspices of UN/CEFACT and OASIS

• build an open marketplace framework any
  business can participate.
• ebXML standardizes business processes such as
  purchasing, ordering, shipping, and payment, so
  they can be performed by machines.
• allows business partners to choose quality of
  service in their message delivery.

11
Example

• ebXML registry

12
Benefits

• adoption of public standards results in lower
  costs and in improved interoperability, which is
  indispensable in inter-enterprise business
  collaboration.
• 80 of companies can expect to realize the
  biggest savings in transitioning to fully
  automated electronic business collaboration.
• REASON - majority of all business transactions
  are currently paper-based and are performed
  manually.

13

• Due to modularity of ebXML specifications,
  software vendors can focus on
• Registry and Repository
• Messaging (Transport Routing)
• Process execution and management (public and
  private processes)
• Tools (Process definition, CPP generation, CPA
  generation, Business document definition etc.)

14
ebXML over Web Services ?

• cope with potential failure conditions.
• no way to discover unavailability before service
  invocation in Web Services.
• How do service requester and service provider
  understand each other?
• WSDL and SOAP provide for technical
  interoperability but not for semantic
  interoperability common understanding of
  message content.
• Issues of non-repudiation, authorization etc.

15
ebXML

• Collaboration Protocol Agreements (CPAs)- declare
  bindings to business collaboration
  specifications, a.k.a. "public processes".
• Change in interface of business service in CPA
  renders it invalid (no effect on messaging).
• ebXML Message Service - reliable and recoverable
  message exchange. (Transport level failures)
• Business level failures BPSS (e.g. failure to
  respond reverts to previous known secure state)

16
Future

• Wireless Web Services.
• Wireless market Java technology -enabled
  devices from handset manufacturers such as Nokia,
  Ericsson, Motorola, Sharp.
• the key here is interoperability Java.

17
References

• http//www.xmlwebservices.cc
• http//www.webservices.org
• http//www.ebxml.org
• http//openebxml.sourceforge.net/index.php/article
  
• http//acmqueue.org/issue
• http//www.dotnetweblogs.com
• http//www.w3.org

18
THANK YOU