1 / 4

Versioning Workflow Services

Versioning Workflow Services. WCF Routing Service. ServiceA. Client. Routing Service. ServiceB. Config. Filter Tables. Filters. Easy to configure routing implementation Routing and filtering based on predefined or custom heuristics Filter by action, address, header or body content

meryl
Télécharger la présentation

Versioning Workflow Services

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Versioning Workflow Services

  2. WCF Routing Service ServiceA Client Routing Service ServiceB Config Filter Tables Filters • Easy to configure routing implementation • Routing and filtering based on predefined or custom heuristics • Filter by action, address, header or body content • Useful for: • Content-based routing • Versioning • Partitioning

  3. Content Based Routing Versioning Workflow Services Challenge: No out of the box support for updating workflow definitions. Problem: Persisted instances fail on resume if correct XAMLX not present. Solution: One approach is Content Based Routing. Client v1 Client v2 Router Service XAMLX v1 XAMLX v2 Use WCF Routing Service with XPath filter on message content Configure it to route to correct version of workflow service Default is config based Requires specific message shape

  4. Versioning Activities • Versioning of Activity Types within a Workflow • Activities are versioned within assemblies • XAMLX workflow services reference these types • Publishing new activity assemblies potentially introduces problems which cause persisted workflows to fail to resume • Consider placing all versions of activity library in GAC

More Related