by community-syndication | Jun 12, 2014 | BizTalk Community Blogs via Syndication
Basically there are two properties inside the schema element decides whether an element can be absent from the document: Min Occurs and Nillable. If Min Occurs property is set 0 then that element can be absent from the XML message but if it is set to 1 it has to be present though its value […]
Blog Post by: Sandro Pereira
by community-syndication | Jun 11, 2014 | BizTalk Community Blogs via Syndication
One of our customers removed their ISA proxy and had removed all the proxy settings from all the send ports but one set of WCF-Custom send adapters showed an erratic behaviour. For short periods of time the request returned successful responses but at other times we received this response System.ServiceModel.EndpointNotFoundException: There was no endpoint listening […]
Blog Post by: mbrimble
by community-syndication | Jun 6, 2014 | BizTalk Community Blogs via Syndication
In the previous post I have demonstrated how I can secure my internal BizTalk services application with X.509 certificates security (that might represent a hypothetical B2B application-to-application scenario). For that, I did not have to change anything in the way my internal BizTalk application is deployed or configured. I accomplished that by simply virtualizing the BizTalk service through a
by community-syndication | Jun 6, 2014 | BizTalk Community Blogs via Syndication
In classic BizTalk are Business Rules not often used in solutions because they are a bit undervalued and also out of the box you can only use them in Orchestrations. With the ESB Toolkit it’s almost the other way around. The ESB Toolkit is all about creating reusable components and making your solution dynamic so at runtime is decided what to do for a specific message type. To accomplish this you use a Resolver to resolve the itinerary, map or endpoint and Resolvers that use Business Rules make it really dynamic! Business Rules also make your components reusable because in your component you don’t need to implement logic anymore that’s specific for a particular message type.
The BizTalk ESB Toolkit includes several resolvers but only the BRE and BRI Resolver use Business Rules. They can be used in the following scenarios:
Specifying Itineraries
With the BRI Resolver you can select an itinerary based on the content or properties of the received message in BizTalk. This is very useful if you want to receive multiple message types in the same location and handle them by different itineraries. This can be for example a folder but also a table in a database or a web service with multiple actions.
Dynamic Routing
With the BRE Resolver you can dynamically route a message, based on the content or properties of the message. In this case you don’t create an itinerary for each message type but you create a generic itinerary that can handle multiple message types. With Business Rules you can decide to which location or endpoint a particular message has to be sent. Note that using the BRE Resolver for Dynamic Routing is not really suited for larger projects because in an OTAP street you have to call probably other web services in your development environment then in the production environment. In that case you have to create Business Rules Policies for each environment. For larger environments is the Sentinet Resolver more suited.
Dynamic Transformation
With the BRE Resolver you can also dynamically get a map based on the content or properties of the message . This is also very convenient when you want to create a generic itinerary for multiple message types.
Custom Solutions
There are also other scenarios where Business Rules can be quite useful like for example message validation. It’s not possible out of the box but you can modify and/or extend %u200bthe ESB Toolkit services and components to suit your specific requirements.
In the following example is the Itinerary Designer extended and an Orchestration Extender created which contains a Policy and a DocumentType property. These properties are used in a Validation Orchestration Service which validates the message by using the Business Rule Engine.
See Also
For more information on how to use Business Rules in the ESB Toolkit see:
by community-syndication | Jun 4, 2014 | BizTalk Community Blogs via Syndication
As the TFS courseware author and lead ALM trainer for QuickLearn, I work hard to try to make sure our eight TFS 2013 courses are best of breed. Students who attend our training are often doing so not only for the skills and knowledge to help them do their job more efficiently, but quite a […]
Blog Post by: Anthony Borton (TFS Instructor)
by community-syndication | Jun 4, 2014 | BizTalk Community Blogs via Syndication
I recently had the pleasure of speaking at Microsoft TechEd in Houston, TX, and the videos of those sessions are now online. A few thousand people have already watched them, but I thought it’d be good to share it here as well. The first one– Architecting Resilient (Cloud) Applications – went through a series of […]
Blog Post by: Richard Seroter
by community-syndication | Jun 3, 2014 | BizTalk Community Blogs via Syndication
I public announce for the first time that I was working in an eBook about BizTalk Mapping Patterns and Best Practices, and that I was published for free, this March during BizTalk Summit 2014 London At the time I said it would be published in mid-April or May but since then I’ve been slightly […]
Blog Post by: Sandro Pereira
by community-syndication | Jun 3, 2014 | BizTalk Community Blogs via Syndication
Blog Post by: AxonOlympus
by community-syndication | Jun 2, 2014 | BizTalk Community Blogs via Syndication
A release for the next version of the BRE Pipeline Framework is now weeks away, with the framework in the latter stages of unit testing (speaking of which the framework has had a massive shift from about 30% test coverage to approximately 80% at the time of writing, so expect a much more reliable product). […]
Blog Post by: Johann
by community-syndication | Jun 2, 2014 | BizTalk Community Blogs via Syndication
Sentinet is a lightweight and scalable SOA and API management platform that helps to define, secure and evolve your API program.