Written by: Preetham Reddy 8/12/2009 12:45 AM
Microsoft has shipped a new Itinerary Designer with ESB Toolkit 2.0 to assist the developers in creating the Itineraries visually... Creating Itineraries in ESB Guidance 1.0 was a real pain.... You would have to create that XML manually or using a .NET library and there was very little validation support.. Itinerary Designer in Version 2.0 comes with lot of cool features that not only simplifies the tasks but also has features for security and validation... Every time you export the data either to an Itinerary store or to a file location on your local drive, the designer validates the XML and makes sure it conforms to the Itinerary Schema. It also has a way to protect the sensitive information in the Itineraries using X.509 Ceritificates. While these security features are a welcome addition, sometimes it gets annoying during the development time. Most programmers, myself included, would want to concentrate on the task on hand rather than concentrate on trivial security features that doesn't really matter at the development time. So, If you are like me, and would like to disable Encryption while developing your Itineraries, then you've got plenty of options!!! In the Registry Editor, navigate to the subkey HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\BizTalk ESB Toolkit\2.0\Designer, and then set the RequireX509Certificate property value to false. If you installed the BizTalk ESB Toolkit on an operating system that has 64-bit support, the subkey is HKEY_LOCAL_MACHINE\SOFTWARE\SysWOW64\Microsoft\BizTalk ESB Toolkit\2.0\Designer. While, this is a recommended way to disable encryption certificates, I am not a great fan of interfering with System Registries. The way I've disabled in my system is by commenting out the lines in the Itinerary Configuration File which insist on throwing errors and warning for having an Invalid Certificate. Open up the file at C:\Program Files\Microsoft BizTalk ESB Toolkit 2.0\Tools\Itinerary Designer\ruleset.config and look for a property node that has a value of 'EncryptionCertificate' for it's 'name' attribute and comment out those following lines. If you'd just like to disable the error, just disable for first 'Validator' node. If you'd like to get rid of warning too, then go ahead and comment out the next 'Validator' node... That should keep the designer's mouth shut!!!!
0 comment(s) so far...