- This topic has 2 replies, 1 voice, and was last updated 9 years, 5 months ago by
.
-
Posts
-
-
What do you mean by dynamic policy update? Where are you looking?
With regards to the policy version used, the orchestration engine will always grab the LATEST version of a rule policy. So, you can have 3 deployed, but the most recent is used. That’s pretty much because the engine is calling the Rules API without passing in a version, which returns the most recent. If you wanted to call a specific rule policy version, you can use the Rules API instead of the \”Call Rules\” shape.
-
I see what you were looking at. This behavior’s been around. Dynamic Policy Update is explained in the Help docs as \”Dynamic policy updates allow you to modify policies independently of a running business process. You can create and deploy an updated version of the policy, and the hosting application can incorporate the update in near real time. This update does not require you to change any code, and thus you can avoid the overhead of redeveloping and redeploying the application.\” This is because the Rules Engine Update Service polls the rules repository for changes (60 seconds, but you can change that in the registry) which means you can modify your business logic without updating any other components.
-
I found that there is dynamic policy updates feature in biztalk 2006. Can anyone explain it to me?
Also, I have another question.. I have a policy and the policy is being used by an orchestration. now I have created a new version of the policy and deployed it without undeploying the previous version. Which version will execute when the orchestration execute next time..?
Thanks for your time..
Shane.
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.