- Business Rule Engine

BizTalk 2006: Deploy the Policies with command line (BTSTask)

It is not so strightforward as it suppose to be. Below are the bat files with comments: @rem ----------- Deploy.Policies.bat ---------------------------... @call Settings.bat @ECHO. @ECHO. Deploy Policies: @ECHO. ===========================... @ECHO. @Time /T @ECHO 1) Create the ResourceSpec.xml file. @rem BTSTask ListApp /ApplicationName:%Applicati... /Server:%BizTalkDataBasesSe... /Database:%BizTalkConfigura... /ResourceSpec:"%CurrentBuil... ......

BizTalk: Anti-Patterns: Business Rule Engine

Let's see one of the projects I've made with the Business Rule Engine from the Microsoft BizTalk tool set. There are the EDI data in"very flexible format". The source partners fill up the fields of these documents by different applications and peoples. As a result the data are usually spread through the several fields if they filling application has a limit to the field size. For example: Good data: N1*CN*YOUNG BAY INTERNATIONAL INC N3*2655 ST-JACQUES#101*MONTREAL QC H3J 1H8 CANADA N3*TEL:514-8121887 ......

BizTalk: Business Rule Engine: Don't use vocabulary in development

BizTalk: Business Rule Engine:Don't use vocabulary in development! Why? Because it gives you big headache and so little instead of. Our typical work with the facts in the rules is compounded from the steps: * Changing/Add fact in/to a rule (if fact is in the one of the tabs of Fact Explorer): Without vocabulary we change/add fact in a rule by drag-and-drop it from the Fact Explorer. With vocabulary we drag-and-drop a definition from the Fact Explorer. No difference. * Changing/Add fact in/to a rule ......