I haven’t had the chance to spread it across. Pasting it from the MSDN site..
Info:
During the recent months a group of world wide MVPs and Field Experts answered to create this series.
We call this series BizTalk 2009 Light and Easy Webcast Series and we cover 16 different topics all listed under the downloads page.
Contents:
Download page: [...]
Read Full Post »
Refer: Click here
Read Full Post »
After the release of BizTalk 2009 – finding the BizTalk 2006 R2 edition comparion chart has become more than important (just because I couldn’t find it ). Hope it saves you the pain of searching around !
Comparison Matrix
Capability Poster
Capability Doc
(Click icon to download)
Happy choosing
Read Full Post »
Here is a small code snippet to extract the strong name value from a BizTalk message stream.
//messageStream is the stream extracted from the BizTalk pipeline context
XmlDocument xmlDoc = new XmlDocument();
xmlDoc.Load(messageStream);
string documentMessageType = xmlDoc.DocumentElement.NamespaceURI + “#” + xmlDoc.DocumentElement.LocalName;
IDocumentSpec documentSpec = pContext.GetDocumentSpecByType(documentMessageType);
string documentStrongName = documentSpec.DocSpecStrongName;
Happy coding J
Read Full Post »
Consulting with one of my colleague on a BizTalk assignment, we came across a performance question while calling web-services from a BizTalk application. The application was quite simple in BizTalk terms doing the following:
1) Input is an xml file (around 1KB in size)
2) BizTalk consumes the file and sends it to a web-service (SOAP Adapter)
3) The [...]
Read Full Post »
Error:
The transaction log for database ‘BizTalkMsgBoxDb’ is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases (.Net SqlClient Data Provider)
Solution:
sp_helpdb ‘BizTalkMsgBoxDb’
ALTER DATABASE BiztalkMsgBoxDb
SET RECOVERY SIMPLE;
GO
DBCC SHRINKFILE (BiztalkMsgBoxDb_log, 1);
GO
sp_helpdb ‘BizTalkMsgBoxDb’
Hope that helps..
Happy coding
Read Full Post »
With the ESB Guidance 2.0, I grabbed the Archive pipeline component in one of my projects. However, this component appears to be failing while archiving a flat file message in a send pipeline (Encode stage).
Error:
ForwardOnlyEventingReadStream does not support Seek()
This is original source code in the Archive component
public IBaseMessage Execute(IPipelineContext pContext, IBaseMessage message)
{
….
finally
{
[...]
Read Full Post »
Error:
C0C01301: Finding the document specification by name failed. Verify the schema deployed properly
The DocumentSpecName value was incorrectly filled in this case. The value should be the strong name key. In this case, it is:
Incorrect Value:
MyProject.Schemas.RootNode_FF
Correct Value:
MyProject.Schemas.RootNode_FF, MyProject.Schemas, Version=1.0.0.0, Culture=neutral, PublicKeyToken=74b2ad3c4ce407d8
I was in correctly setting this property and using it in my (dynamic) Assembler [...]
Read Full Post »
Here is the error that appears in the event viewer.
There was a failure executing the send pipeline: “<PipelineStrongName>” Source: “<PipelineComponentName>” Send Port: “<PortName ” URI: “<FullPathName>” Reason: Root element is missing.
On tracing it down, this is the code that was causing it:
public static Stream DoTransformation(IPipelineContext pContext, IBaseMessage message)
{
//….
Stream transformerdStream = TransformHelper.XsltTransform(message);
[...]
Read Full Post »
There have been a few updates on the BizTalk front – especially with 2009 beta being released recently. With that, here are a few whitepapers/downloads that got me interested…
1) Using the WCF adapters in BizTalk 2006 R2
Link: Click here
2) WCF, WF and .NET 3.5 Whitepapers
Link: Click here
3) Modifying Messages with the WCF Adapters
Link: Click here
4) Using [...]
Read Full Post »