Webinar: Web Services Versioning and SOA Versioning Made Simple

Your Web services architecture is a success: you've got employees, customers and partners consuming services of all kinds across your network. But how do you handle SOA versioning – especially in the case of mission-critical services where down-time is virtually out of the question? This webinar gives you the answers you need.

Please register for immediate access to this on-demand webcast.

Note: The items in BOLD are required fields. You must supply a valid email address to complete the registration.


First Name
Last Name
Company
Title
Job Category
Industry
Email
Telephone
Address 1
Address 2
City
Country
State/Prov
Postal Code

SOA Versioning Made Simple

Do you need to engage in SOA versioning? Read this tutorial and find out how to do it, why to do it, and what some of the challenges are that one will face along the way. More to the point, we'll lay out important best practices that will lead to successful versioning and a healthy services network.

SOA Versioning Example

But first, an example to illustrate how and why versioning -- and management of Web service versions -- is so important. This example, while not directly related to versioning practices set forth in the tutorial, indicates what happens when SOA versioning is not properly addressed on the network.

In this example, a company had rolled out a service they'd built. The service, as far as the IT Department knew, was being used by just five applications. IT told Actional representatives (during a service engagement) that they suspected there were "a few" other people who might be consuming the service. So one of the steps the Actional representatives took was to install Actional Looking Glass which automatically discovers services and consumers of services. In no time, IT was surprised to find out that Looking Glass actually discovered, not five, but 34 different applications using their service on the network!

SOA Versioning Example: what can go wrong on the network without managed versioning

SOA Versioning Example: what can go wrong on the network without managed versioning

SOA Versioning: No Downtime

The major point, however, is that the moment the network begins to feature a large number of consumers using a service -- whether those consumers are external partners or internal applications -- one must immediately focus carefully on versioning. Why? Because large networks of services can no longer enjoy the "luxury" of downtime. And the more mission-critical a service tends to be, the more likely it is that there won't be an opportunity to bring it down because there will be most likely a large range of needs for that service at any given point in time.

SOA Versioning Issues

SOA versioning is therefore essential to growing services networks and those with mission-critical services. The tutorials below will cover each stage of SOA versioning:

  • Mission Critical Software: When building a new service, what critical issues must be considered?
  • Web Services Migration: When bringing the new version of the service online, what is required to migrate service consumers to Version Two?
  • Web Services Change and Upgrade: as consumers want to upgrade and actually use the new features of Version Two, what needs to be done?
  • Web Services Life Cycle: retirement of the old Web service. How to (safely) rid Version One from the network environment.
  • SOA Tools: tools to automate and simplify versioning and SOA management

So read on -- explore these in-depth tutorials -- and learn everything you need to know about SOA versioning.

For More Information

Learn everything you ever wanted to know about SOA versioning! Register to download and watch this free webinar entitled: SOA Versioning Made Simple.