|
Sun and Web Services
The Competition Heats Up
Having missed the boat in the early stages of XML and SOAP development, Sun was shaping up to play the role of a follower, rather than a leader, in the nascent world of Web Services. However, as Java is establishing itself as the natural tool for serious server side development, and there are signs that J2EE standards are becoming more accepted, Sun may well have begun its fight back into the heart of Web Services activity.
|
|
Web Services: The Next Evolution of Application Integration
Applications are typically built to automate business processes that are part of a discrete business function. In most cases, the users of an application fall within a single functional area in a company.
|
|
Versioning of Web Services
Solving the Problem of Maintenance
Every day, we hear of vendors announcing toolkits that serve to make the building of Web Services effortless. Organizations are, however, in different stages of the Web Services implementation phase - many organizations are awaiting other organizations’ reactions; a few have already announced availability of Web Services.
|
|
Business Architecture for a Web Services Brokerage
Understanding the Business Context of Web Services
SOAP and Web Services may hold center stage of the developing Web industry, as attention focuses on toolkits and multi-platforms; however, this area of the industry is merely the tip of an iceberg, which reaches much further than merely selling utility software. Yet, rather than considering the overall architecture of a Web Services business model, the present trend seems to be for companies to produce development tools for the sake of it, in a market that is still maturing.
|
|
Internal or External Web Services?
Which One Will Dominate?
Web Services are clearly in the minds of most technical architects and developers, and as general issues about the use of uniform protocols and contracts are being settled, more specific questions arise. In this article, we will consider differences between internal and external Web Services, and attempt to suggest answers to questions, such as: What are the respective effects of implementing internal and external Web Services? And which type of Web Services will dominate in the future?
|
|
Building Smart Web Services: What Tools Will It Take?
One way to understand where Internet application development is headed is to look back--to the history of automobile assembly. It's time for software developers to follow the auto industry's lead.
Today, software is rapidly changing from static applications to collections of open, smart Web service components, assembled from applications, data and processes located across the Internet. Just as the modern assembly line orchestrates modular components from different suppliers, Internet applications must be able to source their service components from virtually anywhere and plug them into any environment.
|
|
Behind the Hype: A Pragmatic Look at Web Services
Web services have often been portrayed as a new development paradigm. In reality, they did not miraculously spring into being overnight. In fact, as SilverStream Software's Fred Holahan notes, Web services aren't that far removed from older services-based technologies such as Smalltalk, one of the original object-oriented programming languages, and Java RMI (Remote Method Invocation), which is an RPC (remote procedure call) that allows Java objects to be accessed remotely.
|
|
Web Services, Business Objects and Component Models
Web services technologies such as SOAP, UDDI and WSDL will facilitate inter-enterprise cooperation on the Internet. Using Web services, your information system will be able to communicate much more easily with your partners' information system than in the past. This leads to an important question: what technology should be used for implementing Web services themselves?
|
|
An Introduction to ebXML
Collaborative Electronic Business is here to stay
Every day we hear of businesses announcing partnerships with each other in order to provide more dynamic applications. As the number of these applications increase, electronic businesses are faced with the fundamental problems of making sure that their applications are not only dynamic but maintain a high degree of inter-operability between their applications and the businesses with which they collaborate.
|
|
Part II – ebXML and Web Services
The Way to Do Business
In part I of our series of articles on ebXML (electronic business XML), we introduced ebXML and the steps that an organization needs to take in order to start doing electronic business based on ebXML. In this article, we will look at how ebXML enables us to implement Web Services protocols, such as WSDL (Web Services Definition Language), UDDI (Universal Description, Discovery and Integration) and SOAP (Simple Object Access Protocol).
|
|
Clear Thinking on WebServices
In the previous article, I wrote about why SOAP and Web Services are important technologies and how they will impact the way in which we build applications. This article is dedicated to a deeper discussion of Web Services. A taxonomy is provided that explains how Web Services are being used, and therefore, what functionality is required by Web Services Platforms to support this functionality.
|
|
Services Brokers, the new Enterprise Middleware
Today's world is developing a level of complexity that message brokers are unable or designed to address. Today, its not about connecting application A to application B, it's about taking a set of applications, applying a business process flow to control the integration and exposing this aggregate application using a variety of middleware. Examples of services brokers are applications such as Extricity, Web Methods, IBM B2Bi and combo products such as BEA Process Integrator and Collaborator. These products are currently marketed as B2B products but are really services brokers underneath.
|
|
Web Services: Market Roundup
You've heard a lot about Web services and now, naturally enough, you'd like to go out and experiment with a few of the products available for creating them. Well, it's not quite that easy--at least, not just yet. While a slew of software vendors have announced some sort of support for Web services, that doesn't mean you can easily purchase commercial-quality Web service development products.
|
|
Web Services: The Next Generation of Distributed Computing
Move over client-server. Step aside N-tier computing. Here come Web services, the latest stage in the evolution--or devolution--of applications into smaller and smaller, ever more granular components. One by one, Hewlett-Packard, Sun Microsystems, IBM, Microsoft and even Oracle have trotted out their visions for creating, deploying, managing and sharing Web services.
|
|
The Web services (r)evolution, Part 2
This article provides a step by step explanation of how to develop a Web service, including what tools you will need, how to install them, how to write the code, and how to deploy the service. It goes on to explain how to invoke other Web services from across the Internet.
|
|
Web services architect, Part 3: Is Web services the reincarnation of CORBA?
In previous articles, I have discussed the vision of Dynamic e-business and the available technologies that enable us to achieve that vision, namely SOAP, WSDL, and UDDI. For the inquisitive reader the entire topic of Dynamic e-business is nothing more than another form of distributive computing. The justification for this new distributed computing model is cross-platform and cross-programming language interoperability. For the first time since distributive computing has been a mainstream concept, we have a solution based on open standards that can truly support interoperability.
|
|
Web services architect, Part 2: Models for dynamic e-business
Every emerging technology has to cross the chasm between innovation and acceptance. The technology adoption life cycle for Web services is no different. However, this technology does pertain to a different target audience of decision makers. Who are they? What will motivate them? Building on the vision of Dynamic e-business, this article explores the value proposition Web Service technologies offers to business entities in a variety of market segments.
|
|
Web services architect, Part 1: An introduction to dynamic e-business
Emerging technologies have played a strong role in the evolution of the Internet over the past five years. Java gave us portable code; portable data came with XML; and Pervasive Computing addressed the connectivity of any device. Now the hype surrounds Web services. In this series of articles, I will discuss the importance of this technology in developing the next generation of the Internet as well as describe the Web services strategy of IBM. Additionally, I will explore the business impact of Web services, how to identify a relevant solution opportunity, and how to evaluate the many vendor strategies building around this technology.
|
|
Insider Interview: Plan for Web Services
Web services are self-describing, modular applications that work seamlessly with other Web services to fulfill a specific task or a set of tasks. In essence, they enable just-in-time application integration. The idea behind Web services is that you'll have access components that you can not only publish, but find and invoke across the Web without prior knowledge of the application or its programming requirements.
|
|
Web Service Guided Tour: silverstream
A Web service is a component available on a remote server. Its interface is known, and you can call its methods via a standardized messaging protocol.
In the J2EE world, you make a Web service available by deploying it as a servlet in a Web application (WAR) on a J2EE application server. A client application makes a remote method call using SOAP XML messages. The SOAP dispatcher on the remote server receives the messages and directs the method call to the Web service servlet. The Web service wraps the return value as a SOAP message and sends it back to the client.
|
|
Defining Web Services
June 2001) The label "web services" is incredibly generic. Like any promising and loosely defined technology trend, the concepts it describes will be subject to a great deal of speculation and bandwagoneering in the months to come. With the aim of providing a reference benchmark—and of separating posturing from reality—we provide a technology and business definition. By Brent Sleeper and Bill Robins.
|
|
SilverStream and Web Services
|
|
Web Service Tooling for EJBs
Web Service Tooling for EJBs demostrates how a EJB pluggable provider can be used to route SOAP requests to an Enterprise JavaBean.
|
|
Integrating Apache SOAP with an EJB Server
This is part one of a 4 part series on how to use SOAP with Visual Age and WebSphere. All lot of this articles just show how to install and configure the SOAP engine with VAJ/WAS. Part 2 will be useful to anybody using SOAP regardless of which server you're using as it shows how to write the server adapter code for binding SOAP to session beans. Part 3 gets SSL working and Part 4 will get certificate based authentication working.
|
|
When is SOAP a good idea in a project.
Yet another technology to work in to your project. This article tries to provide practical information on using SOAP so that you can see through the hype and decide whether SOAP is appropriate in your project or not.
|