by community-syndication | Mar 29, 2007 | BizTalk Community Blogs via Syndication
Some of us when new to building custom pipeline components would have faced this problem, especially with long messages.
You have a custom pipeline component placed downstream after the disassembler component and expect that the disassembler component would have promoted / written the required schema fields into the context, so that your component can reach out to the context and access them, but you find that it fetches a null even when the message has a value.
This is because the pipeline works in a streaming fashion, which means, all components in the pipeline gets started as the message flows through them. For example, before the disassembler has finished its work, your custom component kicks-in and tries to access the context. Now if the value that you are looking for is somewhere at the end of a lengthy message, it would not yet have got read by the disassembler to be able to promote it into the context, but your custom component already tried fetching it and failed.
One easy solution to this is to read the entire stream from your custom component before accessing the context, this will make sure that all previous components have finished its job and have promoted / written the value into the context. However this is not a good approach as you will end up reading the whole message into memory and may cause an Out-Of-Memory error. You will also anyway need to convert it back to a stream and reset the stream pointers before you can pass it on further since the whole BizTalk architecture is stream based.
Another option (the correct way, but a bit more complex) is to wrap the stream in your own stream and hook to its events to notify when it had finished the reading fully, so that you can go ahead and access the context.
If you are building a custom pipeline component, maybe its worth checking out an undocumented class called XpathMutatorStream, defined within the Microsoft.BizTalk.Streaming namespace (available only in the GAC, Microsoft.BizTalk.Streaming.dll)
Check out the following article by Martijn Hoogendoorn for more on this:
http://martijnh.blogspot.com/2006/03/xpathmutatorstream.html
Thanks & Regards
Benny Mathew
Seamless Integration Solutions
BizTalk Consulting, Development, Training
Bangalore, India
Website: http://www.seamless.in
Blog: http://GeeksWithBlogs.net/benny
BizTalk Usergroup: http://groups.google.co.in/group/b-bug
by community-syndication | Mar 28, 2007 | BizTalk Community Blogs via Syndication
Eric (MS) has been working hard in providing us (loving your work Eric!) with updated
BizTalk documentation.
The folks are doing a great job over all of this. This is a massive PDF – a single
one which encompasses a great deal of things within it.
Here’s the email I got earlier.
——
Hello,
We have provided a new, updated Monster
PDF of the BizTalk Server 2006 documentation set. It is also available off
of a link on the BizTalk Server 2006 Developer Center at http://msdn.microsoft.com/biztalk.
Highlights include:
%u00b7 The
PDF is in a self-extracting zip file that is approximately 57megs.
%u00b7 The
PDF tips the scales at 117 megabytes and includes almost 20,000 pages.
%u00b7 Links
are rendered in blue with underlines but do not work. This may be addressed
in a future enhancement.
%u00b7 Searching
may be slow due to the size of the document.
%u00b7 Feedback,
banners, and other content items have been removed to improve the PDF experience.
If you have any comments including ideas for PDF subset collections or for other content,
please send them along.
Thanks,
Eric
by community-syndication | Mar 28, 2007 | BizTalk Community Blogs via Syndication
If you haven’t already download and install the Service Factory it really reduces the time taken to build and publish your WCF services to IIS letting you concentrate on implementing business logic. Unfortunately it doesn’t come with any refactoring functionality.
by community-syndication | Mar 28, 2007 | BizTalk Community Blogs via Syndication
I have Visual Studio 2005 with Service Pack 1 installed and I cannot debug any web service or web application. This worked for a while and then it stopped working. I researched this on a couple of sites and the suggested solutions were
– Debug with F5
– Run with CTRL + F5
– copy WebDev.WebServer.exe from another machine if not present in .Net Framework folder
– From .Net Framework folder run WebDev.WebServer.exe /PORT:8081 /PATH:”path to web app”
– disable or open firewall port
I tried all of these and it still failed with several errors
Configuration system failed to initialize
Unable to launch Visual Studio’s Localhost Web Server.
ASP.NET Development Server failed to start listening on port 8081.
Error message:
Configuration system failed to initialize
In my case, this error was caused by system.net\machineKey element in machine.config. Removing this element fixed the problem. Of course on a production system you don’t want to this but you would not run WebDev.WebServer.exe either so that’s not actually a problem.
I hope this helps other people facing the same problem!
by community-syndication | Mar 28, 2007 | BizTalk Community Blogs via Syndication
I have Visual Studio 2005 with Service Pack 1 installed and I cannot debug any web service or web application. This worked for a while and then it stopped working. I researched this on a couple of sites and the suggested solutions were
– Debug with F5
– Run with CTRL + F5
– copy WebDev.WebServer.exe from another machine if not present in .Net Framework folder
– From .Net Framework folder run WebDev.WebServer.exe /PORT:8081 /PATH:”path to web app”
– disable or open firewall port
I tried all of these and it still failed with several errors
Configuration system failed to initialize
Unable to launch Visual Studio’s Localhost Web Server.
ASP.NET Development Server failed to start listening on port 8081.
Error message:
Configuration system failed to initialize
In my case, this error was caused by system.net\machineKey element in machine.config. Removing this element fixed the problem. Of course on a production system you don’t want to this but you would not run WebDev.WebServer.exe either so that’s not actually a problem.
I hope this helps other people facing the same problem!
by community-syndication | Mar 28, 2007 | BizTalk Community Blogs via Syndication
Here are a few scripts / stored procedures that most of the BizTalk newbies would love to know.
These scripts are very useful in a development environment to clean up your MessageBox and Tracking databases.
To clean up the MessageBox
- First create the stored procedure bts_CleanupMsgBox by running the sql script found in <BizTalk Installation Folder>\Schema\msgbox_cleanup_logic.sql against your MessageBox database(BizTalkMsgBoxDb).
- Note that your BizTalkMsgBoxDb database will already have a dummy stored procedure by the same name which does nothing, so it is important that you run the above script if this is your first time.
- Stop all BizTalk services.
- Reset IIS server (run iisreset from start/run) if you are running any webservices
- Execute stored procedure bts_CleanupMsgbox on your message box database
- Execute stored procedure bts_PurgeSubscriptions on your message box database
- Restart all BizTalk services
To clean up the Tracking data
- Stop all BizTalk services.
- Execute stored procedure dtasp_CleanHMData on your tracking database (BizTalkDTADb)
- Restart all BizTalk services
Regards
Benny Mathew
Seamless Integration Solutions
BizTalk Consulting, Development, Training
Bangalore, India
Website: http://www.seamless.in/
Blog: http://GeeksWithBlogs.net/benny
BizTalk Usergroup: http://groups.google.co.in/group/b-bug
by community-syndication | Mar 28, 2007 | BizTalk Community Blogs via Syndication
The Architecture Strategy Team has just released an Office Business Applications Reference Application Pack for Loan Origination Systems (OR-LOS) that leverages SharePoint, BizTalk Orchestrations, BizTalk Business Rules Engine, WF Workflows, and Office Clients to automate a Loan Origination process spanning multiple human and system participants. Mike Walker has posted all the details including whitepapers, an introductory video, and the sample bits (including a new MISMO accelerator) on his blog. Attached is a pic from one of the whitepapers that shows the high level view of the process.
Also, Mike and the Financial Services team have some more great content on building OBAs on top of an ESB here. Be sure to check out this paper. It has tons of BizTalk (even though it’s not in the title ;).
-Kris
by community-syndication | Mar 28, 2007 | BizTalk Community Blogs via Syndication
Any day now…..it’ll be making it’s way to the download area and then refreshed by
the web front end servers and then…..viola!!! It will appear as a download.
Some great improvements around EDI (6000+ schemas out of the box)
– WCF + WCF adapters.
– there’s a new LOB Adapter SDK that allows us to develop Adapters WITHOUT the need
for BizTalk. So your one adapter has legs in many different apps.
– lots more…..
Stay tuned……there’s some great WCF channel examples being called by BizTalk in
the pipelines.
Should see it under http://www.microsoft.com/technet/prodtechnol/biztalk/2006/default.mspx I
guess sometime in the *very* near future.
We’re supporting some clients through the R2 TAP program which is always an adventure
🙂
by community-syndication | Mar 28, 2007 | BizTalk Community Blogs via Syndication
Clayton has posted a link to fix this problem:
http://claytonj.wordpress.com/2007/03/26/moss-2007-records-center-fails-when-using-a-required-field/
by community-syndication | Mar 28, 2007 | BizTalk Community Blogs via Syndication
Sezai has written a whitepaper detailing the process involved in migrating a Microsoft Content Management Server 2002 Website to a Microsoft Office SharePoint Server 2007 Publishing Internet Site. Have a look at it here:
http://sharepointblogs.com/sezai/archive/2007/03/27/white-paper-released-migrating-a-microsoft-content-management-server-mcms-2002-website-to-microsoft-office-sharepoint-server-2007-moss-2007.aspx
