This glossary supports the following titles:
SOA Design Patterns
Web Service Contract Design & Versioning for SOA
SOA Principles of Service Design
Service-Oriented Architecture: Concepts, Technology, and Design
Modern SOA Infrastructure: Technology, Design, and Governance
SOA with REST
Next Generation SOA: A Real-World Guide to Modern Service-Oriented Computing
SOA with .NET & Azure
SOA with Java
SOA Governance
SOA Security: Practices, Patterns, and Technologies for Securing Services
SOA and Cloud Computing: Practices, Patterns, Technologies
This glossary also supports the SOA Certified Professional (SOACP) program.
For more information, visit: www.soacp.com
and
www.soaschool.com
|
|
|
context rules (context data type)
|
The protocols and constraints applied to the execution of a specific service activity are collectively referred to as context rules. These rules may be predetermined during the service composition design; however, there may also be context rules that are dynamically determined at runtime in response to certain scenarios and conditions.
Examples of context rules include:
• the allowable duration of the service activity
• the allowable quantity of service activity instances
• the allowable quantity of participating services
Another common form of context rules governs the transaction management of a service activity, such as whether the service activity is wrapped in an ACID-like transaction (that supports abort, commit, or rollback) or whether the activity is long-running (and relies on a compensation process to deal with exception conditions).
The WS-Coordination context framework is supplemented by two additional specifications that introduce context rules expressed via industry-standard SOAP headers. The WS-AtomicTransaction specification provides ACID-style protocols and the WS-BusinessActivity specifications provides context rules for long-running service activities.
Context rules represent one of two context data types, the other being context data. Context data types are of relevance to the application of the Service Statelessness design principle.
See also:
- Service Statelessness
- active (primary state)
- context (state information type)
- context data (context data type)
- passive (primary state)
- session (state information type)
- stateful (primary state condition)
- stateless (primary state condition)
|
|
