Forum Replies Created
-
Posts
-
You have specified this [b:95bdcde71c]owc10.dll [/b:95bdcde71c] but it present on Windows XP OS but on our virtual server Windows server 2003 is present so we are not able to get that DLL.
For [b:95bdcde71c]Windows server 2003[/b:95bdcde71c] any other DLL is required?
Thanks in advance
Hi,
HWS is not one of the best features of BizTalk, it will be present in 2006, but maybe not after that. There’s a few other options for building human workflow solutions with Microsoft Technology:
BizTalk + SharePoint + Office (InfoPath)
You can build a human workflow application very easily with these technologies, you don’t get the full featureset of a human workflow product unless you implement it yourself, but for simple scenarios, it’s a good option.Windows Workflow Foundation (WF)
WF is worth looking at, you don’t have the enterprie hosting that BizTalk povides, but if you don’t need that (messaging, adapters, BAM etc.) it’s an option. The disadvantage is it’s only in beta at the moment.Third Party Products.
K2 (http://www.k2workflow.com) has a workflow solution that allows you to build an advanced workflow solution on top of the Microsoft products (BizTalk, SharePoint, Office etc.). Worth looking at if you need a powerful solution.Regards,
Alan
The only lab I know is: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odc_ip2003_tr/html/odc_INF_Lab_12.asp
You might also want to look at Window Workflow Foundation for your Human Workflow scenarios.
I don’t think this can easily be done using the existing adapters.
The only think I can think of is to have the first message start an Orchestration. Then, either use some type of Convoy to collect the other messages or just use System.IO to read the messages by-passing the file adapter.
Using a Convoy gets difficult if you do not get the message that lists the other file first before any of the other messages.
Best of luck.
Other then the actual install package I don’t know of any other temp files that can be deleted.
Sorry.
I think it would be possible.
See if this helps:
http://martijnh.blogspot.com/2004/08/decompression-pipeline-component-zip.htmlBest of luck.
Don’t know for sure that the problem is. It sounds like a reference problem.
Are you versioning your assembly or just redeploying? If you change the version number each time, you would have to update your map on your receive port.
Also, make sure your pipelines is the Xml Disassembler or the document will not get mapped.
As far as I know, BizTalk 2006 will HWS just like BizTalk 2004.
With that said, I think it will have all the same features as BizTalk 2004. I do not think Microsoft has made any improvements on that side of things.
For a HWS solution, you might want to look at Windows Workflow Foundation.
You could probably just use your schema to break up the record. Just make the schema 1 to 1 and the pipeline should debatch it for you.
Did you take a look at this 10 minute video:
http://www.biztalkgurus.com/Video/Flat-File-Disassembler-Video.htmlQueues – yep I was talking about MSMQ Queues. You might be able to have a trigger in SQL collect the data and then send it to a MSMQ that biztalk will monitor. We did something like that with an integration project into Great Plains.
As far as web services go, in Biztalk 2004 if you want to call them without an Orchestration you need to use the WSE Adapter. Other then that, I have not worked with web service calls too much so you best bet would be to test it out.
There are two methods that I know of.
1. Microsoft’s MSI (can get info on this in the help guide)
2. NAnt (visit [url]http://www.traceofthought.net/[/url])I have always used the MSI approach since that is rather straight forward. It gets more complex if you have Parties and Role Links.
Another great resource is Todd Uhl’s blog:
[url]http://geekswithblogs.net/toddu[/url]
