by community-syndication | Oct 31, 2006 | BizTalk Community Blogs via Syndication
Security is important, especially when we have a B2B scenario where sensitive information has to be sent. Not too long ago, Microsoft released the Web Service Enhancement 2.0 package(WSE 2.0). Among other features like sending attachments with SOAP messages, it enables us to sent secure SOAP messages.
The amount of code to achieve this is not too much as shown with the shipped examples, but it’s the configuration of the client and server machine what is the challenge. There is good documentation what will get you a long way. But I ran into a little issue on “How to: Make X.509 Certificates Accessible to WSE”
Give the account under which WSE is running read access to the file containing the private key associated with the X.509 certificate.
- Open the WSE X.509 Certificate Tool (WseCertificate2.exe)
- Set the certificate location and store name where the certificate is located.
- Click Select the certificate from the store, choose the certificate you
want to set the permissions for, and then click OK. - Click Open Private Key File Properties, click the Security tab, add the ASPNET or Network Service account, depending on which version of IIS the Web service is running under, and then select the Read option.
The missing documentation is that if the Security tab is not showing you have to make sure the following:- You need the NTFS file format.
- Open the explorer and go to ->Folder Options, click on the View Tab, and deselect “Use simple file sharing [recommended]”
Step d. should now show the Security tab, and the Read access to the security file can
be set for the IE account (ASPNET or Network Service for IE 6.0)
by community-syndication | Oct 31, 2006 | BizTalk Community Blogs via Syndication
Another Java based XML rule engine – QuickRules, I was not aware of. They also have a DecisionTable editor. The .NET integration goes through COM, so that is just a marketing line. There is also some workflow editing provided. But not on the level as the BizTalk 2004 orchestration. Anyway have a closer look at this product if Java (J2EE) is your target application server.
by community-syndication | Oct 31, 2006 | BizTalk Community Blogs via Syndication
So who was first Idiom or Microsoft? They both use the concept of defining the datamodel by XSD schema’s and use drag-and-drop to place these elements in rule constructs. The advantage of Idiom here is that you seem to be able to show multiple rules at once. This is really missing in the Business Rule Capturing environment of MS Biztalk 2004. They also seem to be able to integrate with BPEL so that must be pretty close to Biztalk rules format. Have a look at their Decisions and Formulas demo.
What still surpise me is that also Idiom expects the Rule writer to define XSD schema’s. Why can’t we leave the technical binding to XSD, Databse, Java beans or C# components out of the Rule Definitions? Writing good business rules is already complicated enough!
by community-syndication | Oct 31, 2006 | BizTalk Community Blogs via Syndication
I feel a little guilty for omitting the following poem from my consideration of Walt Whitman as Patron Poet: I Saw Old General At Bay I saw old General at bay, (Old as he was, his gray eyes yet shone out in battle like stars,) His small force was now…(read more)
by community-syndication | Oct 31, 2006 | BizTalk Community Blogs via Syndication
There is a patch that fixes various issues, thispatch numberis 285628. If you call into supportthey will gladly give it to you.
by community-syndication | Oct 30, 2006 | BizTalk Community Blogs via Syndication
Michele Bustamente (Das Blonde, with some Indigo in her hair :)) is currently finishing her book on WCF.
This is on I will buy the moment the ink hits the paper.
Good news: we can download some chapters of her book already here !!!
Link
by community-syndication | Oct 30, 2006 | BizTalk Community Blogs via Syndication
Just a reminder that the first meeting of the Dallas
BizTalk User Group will be held on November 13th at the Microsoft Campus in Las
Colinas.
>
by community-syndication | Oct 30, 2006 | BizTalk Community Blogs via Syndication
Microsoft has this up for a couple of weeks, but I thought you might find it interesting.
“The Windows Vista Developer Story includes content for developers, and other technology experts and managers, interested in an in-depth exploration of some of the new and extended features in Windows Vista. It is released to the Windows Vista Developer Center in the form of brief articles, published approximately once every two weeks. Those articles are only a summary of the Windows Help file, which can be downloaded here. “
UAC seems to be very popular by the way, since Bart has a nice post on developing .NET apps for UAC, updating my old post on the same subject.
Link Link
by community-syndication | Oct 30, 2006 | BizTalk Community Blogs via Syndication
IBM and Microsoft have published MTOM Serialization Policy Assertion (WS-MTOMPolicy) Version 1.0.
This specification describes a domain-specific policy assertion that indicates endpoint support of the optimized MIME multipart/related serialization of SOAP messages defined in section 3 of the SOAP Message Transmission Optimization Mechanism specification. This policy assertion can be specified within a policy alternative as defined in WS-Policy Framework and attached to a WSDL description as defined in WS-PolicyAttachment.
by community-syndication | Oct 30, 2006 | BizTalk Community Blogs via Syndication
I’ve decided to start blogging in part because I feel guilty about getting great information from a lot of BizTalk blogs out there and not contributing anything myself. There are some really great bloggers out there that clearly have a very good understanding of BizTalk. Some that come to mind are: Charles Young (http://geekswithblogs.net/cyoung/), Tomas Restrepo (http://www.winterdom.com/weblog/), Scott Colestock (http://www.traceofthought.net/), and Stephen Thomas (http://www.biztalkgurus.com/blogs/biztalk/). I’ve obtained some great information from these guys and many other blogs. If it was not for blogging my work in BizTalk would have been much more painful. Hopefully I will be able to help out a few folks using BizTalk (and maybe other technologies) with this blog.