Welcome!

Microservices Expo Authors: Liz McMillan, Pat Romanski, Elizabeth White, Yeshim Deniz, Zakia Bouachraoui

Related Topics: Microservices Expo

Microservices Expo: Article

Introducing WS-CAF - More than just transactions

Introducing WS-CAF - More than just transactions

Web services have become the integration platform of choice for enterprise applications. Those applications by the very nature of their enterprise-scale components can be complex in structure, which is compounded by the need to share common data or context across business processes supported by those applications. Those processes may be very long lived, and may contain periods of inactivity, for example, where constituent services require user interactions.

In response to these issues, WSCAF (Web Services Composite Application Framework) was publicly released in July 2003 after almost two years of effort, and has broad industry support from companies such as Iona, Oracle, Sun, and a host of others, and is now under the care of an OASIS standardization effort through the WS-CAF Technical Committee. The WS-CAF specifications are a suite of protocols designed to provide the necessary framework for composing Web services into larger aggregate business processes. Given that WS-CAF is the first framework of its kind to make its way into standardization, it's important to understand the principles underpinning it.

This article provides a high-level view of WS-CAF starting from the bottom up, explaining the layered architecture of the trio of specifications that comprise WS-CAF, and demonstrating how each of the specifications can be used in its own right or as a whole to provide a rich framework for building reliable composite applications.

WS-Context (WS-CTX)
The ability to scope units of work (known as activities) is a requirement of a variety of aspects of distributed applications. In order to correlate the work of multiple Web services within the same activity, it's necessary to propagate additional information - the context - to each participating service. The context contains information such as a unique ID that allows a series of operations to share a common outcome, and is propagated in a SOAP header block whenever application messages are transmitted between component services. The reliable management of the contexts that provide distributed application scope is addressed by the WS-Context specification.

The purpose of a context is to allow multiple individual Web services to enter a relationship by sharing certain common attributes as an externally modeled entity. Typical reasons for Web services to share context include common security domains where multiple Web services execute within the scope of a single authorized session, or common outcome negotiation where each party within the activity needs to know whether each of the other participants successfully completed his or her work.

The structure of a context is application specific (as we shall see, WS-CoordinationFramework and WS-TransactionManagement both extend the basic WSContext context for their own purposes), but contains at a minimum a unique ID in the form of a URI. Web services are identified as participants in the activity by including the context in an application message's SOAP header block (see Listing 1).

In general terms, a context defines basic information about the activity structure. It contains information necessary for multiple Web services to be associated with the same activity, which may be dynamically updated by services as the application or process makes progress. Activities are managed by the context service, which maintains a repository of shared contexts associated with execution environments. Whenever messages are exchanged within the scope of an activity, the context service can supply the associated context, which may then be propagated with those messages. The Context Service also manages hierarchies of contexts to support nesting and concurrency.

As we have seen, the core context propagation framework provides a generic context structure that enables an activity to be uniquely identified so that work can be correlated. Additionally, it supports application- and service-specific extensions to the context, structure. To facilitate this, the context consists of:

  • A mandatory URI identifier called <context-identifier>: Guarantees global uniqueness for an individual activity
  • An optional list of child activities: The <child-contexts> element
  • A <timeout> element: Indicates how long the context information is valid

    In addition to the context service, each Web service participating in an activity may register an Activity Lifecycle Service (or ALS) with the Context Service, which allows that service to be informed about the lifetime of the context. As we shall see, the ALS is the key component in utilizing WS-Context as the base protocol for other higher-level protocols. During execution, when a context is required for the activity associated with the current execution environment, the Context Service calls each registered ALS and obtains additional content for the basic context from it; from this it eventually assembles the entire context document that can be propagated.

    The relationship between ALS and context service, application services, and applications is shown in Figure 1.

     

    WS-Context does not mandate how contexts are actually created, but the canonical route is via the Activity Lifecycle services, which "plug-in" to the Context Service. In this respect, the exact structure and semantics of an activity are defined by the combination of ALSs that have been associated with the activity. For example, a Context Service may have a transaction ALS and security ALS registered with it, so that when an activity is started, any context that is created will contain any necessary transaction and security information.

    WS-Coordination Framework (WS-CF)
    WS-CF is the middle layer in the WSCAF set of specifications and provides an extensible framework that supports a wide range of different coordination protocols (e.g., two-phase or three-phase commit).

    While WS-Coordination Framework is ostensibly similar to WS-Coordination, the main differentiator is that WS-CF defines more of the coordinator's architecture than WS-Coordination (which leaves most things up to the services that use it). For example, in WS-CF you can actually inquire as to the status of a coordinator without having to know the details of the protocol (and its implementation). In many ways, WS-CF can be considered a superset of the WS-Coordination.

    Figure 2 illustrates how individual Web services as well as composite applications can register as participants with a coordinator, which takes over responsibility for context management and notifying participants of the outcome of a series of related Web services executions. As the figure shows, a coordinator can register itself with another coordinator and become a participant, thereby improving interoperability.

     

    WS-Transaction Management (WS-TXM)
    WS-TXM builds on WS-CF to provide transactional coordination. Figure 3 illustrates the layering of WS-TXM protocols. WS-TXM defines a set of pluggable transaction protocols that can be used with the coordinator to negotiate a set of actions for all participants to execute based on the outcome of a series of related Web services executions. The executions are related through the use of shared context (scopes) that can be nested (parent-child relationships) and concurrent.

     

    WS-TXM actually embodies three separate extended transaction protocols. Like WS-Transaction and BTP, WS-TXM provides models that are designed to accommodate multiple use cases, from tightlycoupled intranet-based transactions (TXACID), to Internet-scale, long-lived transactions (TX-LRA), to business process-oriented transactions (TX-BP).

    ACID Transactions
    This model is designed to support interoperability of existing transaction processing systems via Web services, since such systems already form the backbone of enterprise class applications. Although ACID transactions may not be suitable for all Web services, they are most definitely suitable for some, and particularly highvalue interactions such as those involved in finance. As a result, the ACID transaction model defined in WS-TXM has been designed with interoperability in mind. In the ACID model, each activity is bound to the scope of a transaction, so that the end of an activity automatically triggers the termination (commit or rollback) of the associated transaction.

    Long Running Activities (LRA)
    The LRA protocol is designed for those business interactions that are long in duration. Within this model, all work performed within the scope of an application should be compensatable. Therefore, an application's work is either performed successfully or undone. How individual Web services perform their work and ensure it can be undone if compensation is required is an implementation choice. The LRA model simply defines the triggers for compensation actions and the conditions under which those triggers are executed.

    There is a caveat to this model though. Application services may not be compensatable (e.g., an application-level service that prints and mails checks), or the ability to compensate may be transient. The LRA model allows applications to combine services that can be compensated with those that cannot be compensated. Obviously, by mixing the two service types the user may end up with a business activity that will ultimately not be undone by the LRA model, but which may require outside (application-specific) compensation.

    The LRA model defines a protocol actor called a compensator that operates on behalf of a service to undo the work it performs within the scope of an LRA. How compensation is carried out will obviously be dependent upon the service; compensation work may be carried out by other LRAs which themselves have compensators.

    When a service performs work that may later have to be compensated within the scope of an LRA, it enlists a compensator participant with the LRA coordinator. The coordinator will send the compensator one of the following messages when the activity terminates:

  • Success: The activity has completed successfully. If the activity is nested, then compensators may propagate that outcome to the enclosing LRA.
  • Fail: The activity has not completed. All compensators that are registered with the LRA will be invoked to perform compensation in reverse order. The coordinator forgets about all compensators that indicated they operated correctly. Otherwise, compensation may be attempted again or a compensation violation has occurred and must be logged.

    LRAs may be used both sequentially and concurrently, where the termination of an LRA signals the start of some other unit of work within an application. However, LRAs are units of compensatable work and an application may have as many units of work operating simultaneously as it needs to accomplish its tasks. Furthermore, the outcome of work within LRAs may determine how other LRAs are terminated.

    An application can be structured so that LRAs are used to assemble units of compensatable work and then held in the active state while the application performs other work in the scope of different (concurrent or sequential) LRAs. Only when the right subset of work (LRAs) is arrived at by the application will that subset be confirmed; all other LRAs will be told to cancel (complete in a failure state).

    Business Process (BP)
    The BP protocol is significantly different from any of the other transaction models we have seen to date (and there is no directly comparable model in either WSTransaction or BTP). This model is specifically aimed at tying heterogeneous transaction domains together into a single business- to-business transaction. For example, with the BP model it's possible to have a long-running business transaction span messaging, workflow, and traditional ACID transactions, allowing enterprises to leverage their existing IT investment.

    In the business process transaction model, all parties involved in a business process reside within business domains, which may themselves use business processes to perform work. Business process transactions are responsible for managing interactions between these domains. A business process is split into business tasks and each task executes within a specific business domain. A business domain may itself be subdivided into other business domains recursively.

    Each domain may represent a different transaction model if such a federation of models is more appropriate to the activity. Each business task (which may be modelled as a scope) may provide implementation- specific countereffects in the event the enclosing scope must cancel. Furthermore, the controlling application may periodically request that all business domains checkpoint their state so that they can either be consistently rolled back to that checkpoint by the application or restarted from the checkpoint in the event of a failure.

    Figure 4 shows an online travel agent interacting with its suppliers, each of which resides in its own business domain. The work necessary to obtain each component is modelled as a separate task. In this example, the Flight Reservation task is actually composed of two subtasks - one gets the flight and the other gets the necessary travel insurance.

     

    In this example, the user may interact synchronously with the travel agent to build up the required details of the holiday. Or, the user may submit an order (possibly with a list of alternate requirements, such as destinations, dates, etc.) to the agent, who will call back when it has been filled. Likewise, the travel agent then submits orders to each supplier, requiring them to call back when each component is available (or is known to be unavailable).

    Business domains are instructed to perform work within the scope of a global business process. The business process has an overall manager that may be informed by individual tasks when they have completed their work or it may periodically communicate with each task to determine its current status. In addition, each task may make checkpoints of its progress so if a failure occurs, it may be restarted from that point rather than having to start from the beginning. A business process can either terminate in a confirmed (successful) manner, in which case all of the work requested will have been performed, or it will terminate in a cancelled (unsuccessful) manner, in which case all of the work will be undone.

    If it cannot be undone, then this fact must be logged.

    Summary
    From a distance, WS-CAF may be misinterpreted simply as the industry's third attempt at designing a transaction management solution for Web services. However, while one aspect of WS-CAF does address the kind of extended transaction models that are crucial for Web services reliability, there is actually much more to WS-CAF than just transactions. WS-CAF also provides generic context-management and service-coordination frameworks that can form the basis of composite applications, processes, and workflows. These features are exposed to Web services-based applications and can be tailored to build protocols that are specific to particular applications domains.

    References

  • Webber J., and Little M.C. (May 2003) "Introducing WS-Coordination, part 1" Web Services Journal, Vol. 3, Issue 5.
  • Little M.C. and Webber J. (June 2003) "Introducing WS-Transaction, part 2," Web Services Journal. Vol. 3, Issues 6-7.
  • Dalal, S., et al. ( January 2003). "Coordinating Business Transactions on the Web." IEEE Internet Computing Special Edition on Web Services.

    Comparison Between OASIS BTP and WS-Coordination/Transaction
    WS-CAF is not the only transactional coordination protocol for Web services. Indeed, in the past we've seen OASIS BTP and IBM/Microsoft/BEA WSCoordination and WS-Transaction. To help illustrate the features of WS-CAF, it is instructive to take a look at the factorization and features of the prior efforts.

    OASIS BTP was the first transaction protocol to gain real traction for Web services. It consists of a single API that supports two distinct transaction models, known as atom and cohesion. The atom model is a straightforward two-phase protocol where all participants in a transaction see the same outcome, although BTP does not impose any semantics on what action a particular participant takes on receipt of an outcome message (an atom may or may not be ACID). The cohesion model is more complex, and allows the set of participants to change throughout the duration of the transaction, up until the point when the confirmation protocol executes. However, unlike the atom model, BTP cohesions may deliver different outcome messages to individual participants, based on the combination of responses from participants and some business logic.

    Similarly, WS-Transaction has two transaction models: atomic transactions require ACID semantics and mandate that resources are locked for the transaction's duration. Business activities, on the other hand, are designed for use in long-running transactions. They ensure that any updates to state in a system are made immediately, significantly reducing the period during which locks must be held. WS-Transaction has no notion of a two-phase commit for a business activity because commits are made immediately on receipt of the associated messages. If a failure occurs, a business activity runs compensating actions to restore data to a consistent form.

    Underpinning WS-Transaction is WS-Coordination, which provides a generic mechanism for context creation and coordination and is extended through protocol plug-ins that provide domain-specific coordination facilities.

    Figure 5 highlights the two key differences between the specifications. The most striking feature is that each offers different transaction models at the uppermost layers, but it is important to note that the WS-Coordination layer in the WSTransaction/ WS-Coordination stack is also available for applications to build on. In the WS-CAF stack, the WS-Context layer is also exposed for use.

     
  • More Stories By Mark Little

    Mark Little was Chief Architect, Transactions for Arjuna Technologies Ltd, a UK-based company specialising in the development of reliable middleware that was recently acquired by JBoss, Inc. Before Arjuna, Mark was a Distinguished Engineer/Architect within HP Arjuna Labs in Newcastle upon Tyne, England, where he led the HP-TS and HP-WST teams, developing J2EE and Web services transactions products respectively. He is one of the primary authors of the OMG Activity Service specification and is on the expert group for the same work in J2EE (JSR 95). He is also the specification lead for JSR 156: Java API for XML Transactions. He's on the OTS Revision Task Force and the OASIS Business Transactions Protocol specification. Before joining HP he was for over 10 years a member of the Arjuna team within the University of Newcastle upon Tyne (where he continues to have a Visiting Fellowship). His research within the Arjuna team included replication and transactions support, which include the construction of an OTS/JTS compliant transaction processing system. Mark has published extensively in the Web Services Journal, Java Developer's Journal and other journals and magazines. He is also the co-author of several books including “Java and Transactions for Systems Professionals” and “The J2EE 1.4 Bible.”

    More Stories By Jim Webber

    Dr. Jim Webber is a senior researcher from the University of Newcastle
    upon Tyne, currently working in the convergence of Web Services and Grid
    technologies at the University of Sydney, Australia. Jim was previously
    Web Services architect with Arjuna Technologies where he worked on Web
    Services transactioning technology, including being one of the original
    authors of the WS-CAF specification. Prior to Arjuna, Jim was the lead
    developer with Hewlett-Packard on the industry's first Web Services
    Transaction solution. Co-author of "Developing Enterprise Web Services -
    An Architect's Guide," Jim is an active speaker and author in the Web
    Services space. Jim's home on the web is http://jim.webber.name

    Comments (1) View Comments

    Share your thoughts on this story.

    Add your comment
    You must be signed in to add a comment. Sign-in | Register

    In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


    Most Recent Comments
    melliti 12/13/03 01:46:28 PM EST

    I m a student and im interessted in your articles.
    think you

    Microservices Articles
    Lori MacVittie is a subject matter expert on emerging technology responsible for outbound evangelism across F5's entire product suite. MacVittie has extensive development and technical architecture experience in both high-tech and enterprise organizations, in addition to network and systems administration expertise. Prior to joining F5, MacVittie was an award-winning technology editor at Network Computing Magazine where she evaluated and tested application-focused technologies including app secu...
    Using new techniques of information modeling, indexing, and processing, new cloud-based systems can support cloud-based workloads previously not possible for high-throughput insurance, banking, and case-based applications. In his session at 18th Cloud Expo, John Newton, CTO, Founder and Chairman of Alfresco, described how to scale cloud-based content management repositories to store, manage, and retrieve billions of documents and related information with fast and linear scalability. He addresse...
    Adding public cloud resources to an existing application can be a daunting process. The tools that you currently use to manage the software and hardware outside the cloud aren’t always the best tools to efficiently grow into the cloud. All of the major configuration management tools have cloud orchestration plugins that can be leveraged, but there are also cloud-native tools that can dramatically improve the efficiency of managing your application lifecycle. In his session at 18th Cloud Expo, ...
    The now mainstream platform changes stemming from the first Internet boom brought many changes but didn’t really change the basic relationship between servers and the applications running on them. In fact, that was sort of the point. In his session at 18th Cloud Expo, Gordon Haff, senior cloud strategy marketing and evangelism manager at Red Hat, will discuss how today’s workloads require a new model and a new platform for development and execution. The platform must handle a wide range of rec...
    Containers and Kubernetes allow for code portability across on-premise VMs, bare metal, or multiple cloud provider environments. Yet, despite this portability promise, developers may include configuration and application definitions that constrain or even eliminate application portability. In this session we'll describe best practices for "configuration as code" in a Kubernetes environment. We will demonstrate how a properly constructed containerized app can be deployed to both Amazon and Azure ...
    SYS-CON Events announced today that DatacenterDynamics has been named “Media Sponsor” of SYS-CON's 18th International Cloud Expo, which will take place on June 7–9, 2016, at the Javits Center in New York City, NY. DatacenterDynamics is a brand of DCD Group, a global B2B media and publishing company that develops products to help senior professionals in the world's most ICT dependent organizations make risk-based infrastructure and capacity decisions.
    Discussions of cloud computing have evolved in recent years from a focus on specific types of cloud, to a world of hybrid cloud, and to a world dominated by the APIs that make today's multi-cloud environments and hybrid clouds possible. In this Power Panel at 17th Cloud Expo, moderated by Conference Chair Roger Strukhoff, panelists addressed the importance of customers being able to use the specific technologies they need, through environments and ecosystems that expose their APIs to make true ...
    In his keynote at 19th Cloud Expo, Sheng Liang, co-founder and CEO of Rancher Labs, discussed the technological advances and new business opportunities created by the rapid adoption of containers. With the success of Amazon Web Services (AWS) and various open source technologies used to build private clouds, cloud computing has become an essential component of IT strategy. However, users continue to face challenges in implementing clouds, as older technologies evolve and newer ones like Docker c...
    CloudEXPO New York 2018, colocated with DXWorldEXPO New York 2018 will be held November 11-13, 2018, in New York City and will bring together Cloud Computing, FinTech and Blockchain, Digital Transformation, Big Data, Internet of Things, DevOps, AI, Machine Learning and WebRTC to one location.
    DevOpsSummit New York 2018, colocated with CloudEXPO | DXWorldEXPO New York 2018 will be held November 11-13, 2018, in New York City. Digital Transformation (DX) is a major focus with the introduction of DXWorldEXPO within the program. Successful transformation requires a laser focus on being data-driven and on using all the tools available that enable transformation if they plan to survive over the long term.