The vendor solutions in the Web Services marketplace can be described as follows:
Infrastructure
Application server
Middleware, such as JMS-enabled middleware
Edge server, such as cache (using XML database)
Registries, such as the UDDI or ebXML registry
Development Tools
Developer workbench that can wrap apps logic into a SOAP proxy, and publish it to UDDI
Automated testing tools, such as jTest
Web Services Tools
JMS-SOAP bindings, such as the JMS bridge
SDK, such as WSTK
Web Services Standards
Java, such as JAX, Web Services Developer Pack
C#
XML standards, such as SOAP, SOAP-SEC, XAML, SAML
Specialized Market
Porting .NET to Unix
Porting Java to Windows platform
Web Services Management
Metering Web Services calls performance and service level. This can also send alerts to administrators or system management tools based on user-defined business rules.
Security appliance, such as XML firewall for SOAP messages; appliance for SOAP message encryption and decryption.
Service versioning, such as mapping to different service end-point URLs based on the incoming SOAP request and user profile. This addresses many legacy systems or customized services that provide the same business functionality but exist in multiple versions and perhaps operate in different platforms.
Table 3-4 offers a sampler of the vendor products in the marketplace.
Table 3-5 shows some examples of vendor solutions that are available to meet different needs of the development life cycle.
Development Life Cycle | Types of Development Tools | Examples of Vendors |
---|---|---|
Discovery | UDDI ebXML | Sun ONE™, IBM, BEA, The Mind Electric, Systinet, Novell (Silverstream), MicrosoftSun ONE™, XMLGlobal |
Creation | Developer Workbench (IDE) | Sun ONE™ Studio, IBM, IONA, CapeClear, Bowstreet, Avinon, Microsoft |
Transforming | JAX, XML, SQL Mapping | Sun (JAX), IBM (Xerces), XMLGlobal, Microsoft |
Building | SOAP, WSDL | OSF (Apache), Sun ONE™ Studio, IBM, CapeClear, Bindsystems, The Mind Electric, Killdara, Microsoft |
Deploying | Deploying tools | OSF (Apache ANT) |
Testing | Local/remote testing | Jtest |
Publishing | Publish to registries | Sun (JAXR), IBM (UDDI4J) |
Here are some development or productivity tools that can be downloaded as a free trial:
XMLSpy. For developing XML Schema, DTD, and validating XML well-formedness. The new version 4.2 also provides SOAP debugging. See Figure 3-29.
Figure 3-29. XMLSpy 4.2
Java Web Services Developer Pack. A freeware for developers to build Web Services using JAX. See Figure 3-30.
Figure 3-30. Java Web Services Developer Pack
The Java Web Services Developer Pack (JWSDP) from Sun Microsystems is a vendor-neutral Web Services Development Kit that avoids the need to purchase expensive Web Services packages. It provides basic tools but is not sufficient for serious or large-scale development. JWSDP provides:
Tomcat engine with ANT deployment tool
All-in-one JAR files—javamail, smtp, and so forth
JAX pack—JAXP, JAXM, JAXR, JAXB
UDDI browser and registry
Application deployment tool
Excellent tutorial book
JWSDP can be used for proof of concept/prototyping, as a rudimentary development platform for road warriors, and for coding simple SOAP messages for integration testing. To best utilize JWSDP, you can run JWSDP on Linux, Solaris OE™, or Windows NT. You can run it with a SOAP server administration, or run it with Apache Cocoon for any-to-any delivery.
Something to Note. JWSDP has applied some special patches for JAR. There is also a version that is compatible with other stand-alone downloads of JAX Pack, Tomcat, or SOAP.
Here are some suggestions for selecting an appropriate Web Services tool for your IT shop:
General
Total cost of ownership
Reliability and support service of vendor (for example, financial stability, local support)
Standards compliance (for example, J2EE™, EJB™ 1.2, SOAP 1.2, WSDL 1.1)
Availability of technical documentation, such as examples, tutorial
Application Server Platform
Clustering features benchmarking—failover recovery time, any manual intervention
Logs—logging availability at different levels (for example, can it trace back different callers and intermediaries?)
Automated testing and deployment platform
Availability, of or integration with, other apps server analyzer tools (for example, thread performance analysis)
Web Services Development Platform
Automatic WSDL generation from IDE
IDE integration with other tools
Among these criteria, you may also look for:
SOAP 1.1/1.2 support; SOAP 1.2 has some considerable changes
Integration with J2EE™ application servers, and their positioning
Compatibility with other Web Services products, such as JMS bridge
Any proprietary features, such as Electric Server Page
There are three major Web Services development technologies in the industry:
ebXML. ebXML is a key technology supporting Web Services. It is backed by OASIS, CE/FACT, DISA, and many public communities. One motive driving these public communities is to use ebXML as an alternative for EDI-type transactions. ebXML uses SOAP 1.1 with Attachment as the transport and routing layer. It has much richer functionality and contents and is supported by business processes (such as BPSS) and better security.
SOAP. SOAP 1.0 used to be Microsoft NT-centric technology. IBM and other vendors have modified it to turn SOAP 1.1 into an open platform and submitted it to Apache Open Sources Foundation. SOAP 1.1 with Attachment is an extension to support object embedding with S/MIME, developed by HP and other vendors.
UDDI. UDDI is a business Service Registry that allows users to create, discover, and bind business services. IBM, Microsoft, and Ariba initially set up three different test UDDI sites. Recently, Ariba withdrew, but there is some discussion that HP will provide the UDDI test site on behalf of Ariba. SAP also now provides a public UDDI node.
Leading technology vendors such as IBM and Microsoft have large-scale initiatives in developing Web Services toolkits and White Papers. There are many Application Server and Middleware vendors developing components that support Web Services, including BEA Weblogic, webMethods, and TIBCO.
Many Web Services standard bodies have emerged since 2000. Among them, there are a few standard bodies (or related associations) that have large industry involvement:
OSF Apache. Open Source Foundation coordinates and distributes Web Services technology as public domain (http://www.apache.org)
UDDI.org. (now under OASIS) Standard body for promoting UDDI registry. It has recently transitioned to OASIS's management (http://www.uddi.org or http://www.oasis.open.org)
W3C. Worldwide Web Consortium that publishes and approves Internet-related standards (http://w3c.org)
Some examples of the supporting communities include:
OASIS. A community that supports ebXML standards and implementation (http://www.oasis-open.org/)
UN/CEFACT. Previously UN/EDIFACT, UN/CEFACT promotes EDI and also supports ebXML as the successor to EDI in collaboration with OASIS (http://www.ebxml.org/)
Open Application Group. A standards body that adopts the ebXML implementation (http://www.openapplications.org/)
DISA. A U.S. ANSI standard body that also adopts the ebXML implementation (http://www.disa.org/)
Web Services technology is intended to be platform- and vendor-neutral. It is expected that this technology be highly flexible for interoperability and integration. SOAP and ebXML standards are used for different reasons. This can be understood in the context of their underlying design principles and value proposition.
The initial design of SOAP does not cater to non-XML contents such as EDI transactions. SOAP 1.1 with Attachment is a major breakthrough; it uses MIME to embed binary objects. The original design principles behind SOAP also support non-HTTP transport, though it has not been implemented at all. The security design of SOAP is highly volatile and weak at this stage.
ebXML can be used to exchange XML contents (incorporating any XML document in the SOAP Body) and non-XML contents (embedding ANSI X12 transactions as attachments). The latter is the mechanism by which ebXML supports EDI documents. It now uses SOAP as the transport layer. ebXML differentiates from SOAP/UDDI by introducing business processes and JMS binding. It uses UML to model business processes. The business process and information models will help integrate with the business entities' back office applications. JMS binding provides a secure and reliable transport mechanism over HTTP.
Table 3-6 summarizes some facts about different Web Services technology thought leaders.
Sun | Microsoft | IBM | |
---|---|---|---|
Framework | Sun ONE™ | .NET | IBM Web Services |
Infrastructure | Open standards technology, e.g., J2EE™—Java™ and XML LDAP | .NET framework, including C#, VB, C++, VBScript, and JScript | WebSphere suite |
Developer tools | Sun ONE™ Studio Sun ONE Integration Manager | Visual Studio.NET
.NET framework SDK .NET enterprise servers | Web Services Toolkit Application Developer Studio Visual Age |
Web Services dialects | Sun ONE™—Smart Web Services | Hailstorm (not available yet) | N/A |
Discovery | UDDI ebXML | UDDI UpnP | UDDI |
Security | WS-Security
Liberty SAML | WS-Security | WS-Security |
Business logic | J2EE™
ebXML WSCI | Biztalk BPEL4WS | J2EE™
ebXML BPEL4WS |
http://www.webservices.org/framework.php
91Web Services Technology Overview Table 3 6 Comparing Sun Microsoft and IBM Approaches Sun Framework Infrastructure Sun ONETM Open standards technology e g J2EETM--JavaTM and XML LDAP Sun ONETM Studio Sun ONE Integration Manager Web Services dia lects Discovery Security Sun ONETM--Smart Web Serv ices UDDI ebXML WS Security Liberty SAML Business logic J2EETM ebXML WSCI Biztalk BPEL4WS J2EETM ebXML BPEL4WS Microsoft NET NET framework including C# VB C++ VBScript and JScript Visual Studio NET NET framework SDK NET enterprise servers Hailstorm not available yet UDDI UpnP WS Security WS Security N/A UDDI IBM IBM Web Services WebSphere suite 91 Developer tools Web Services Toolkit Appli cation Developer Studio Vis ual Age References Bibliography Comparison of Web Services architecture [ch03biblio03div01entry01] http //www webservices org/framework php
http://wwws.sun.com/software/xml/developers/wsci/wsci-spec-10.pdf
http://www-106.ibm.com/developerworks/webservices/library/ws-bpel/
18.118.141.27