Progress / Actional/Resources/White Papers/Getting Started With Web Services
Web Services VersioningWeb services versioning is the ability to provide consumers with uninterrupted service while upgrading a Web service or sets of shared services. Service upgrades occur regularly – server hardware is upgraded, application server platforms are revised, and services change over time to accommodate new functional requirements or to fix bugs. In a 24x7 service network, where consumers of shared services are often unrelated, it is imperative to avoid any dependencies between service consumers and service providers. In a production environment of shared services it is important that:
SOAPstation DeploymentThe minimum requirement for the approach outlined above involves one SOAPstation instance, however we recommend a cluster of two SOAPstations for resiliency. SOAPstations can be clustered so that if one system fails, the other carries the total load without any service interruption at all. Implementation could take the form of the following:
Running an unmanaged enterprise service network is fraught with escalating difficulty and expense. Web services versioning with Actional SOAPstation can dramatically ease migrations to enterprise-wide Web services. SummaryBoth provisioning and versioning capabilities often come into play after initial service deployments. Having SOAPstation in place early will enable development and operations to react more quickly and effectively to change than they would otherwise. For More InformationDiscover the details of Web services versioning – and other topics concerning network change: download the free white paper, SOA Primer: Comprehensive Runtime Governance from Actional |
Learn more about Web Services VersioningDownload the free white paper, "Getting Started With Web Services — Breaking Through the Complexity," now. |



