Forum Replies Created
-
AuthorPosts
-
Thanks Mr Stephen W. Thomas!
I solved my problem with your guides.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.
Ooooops …Spelling mistake…Its Nant tool
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]Hello,
You can use NAND.exe for deplyoment as well as Deplyoment wizard of VS.NET is there … 🙂
Worked a treat. Thanks very much! 😀
hai caroline,
You don’t need to re-create your send and receive ports.Step 1:
When you want to undeploy a assembly, you just supprime the name of maps in send and receive ports .Step 2:
Undeploy the assembly(Now it will undeploy the assembly successfully)Step 3:
If you want to redeploy it,Change the version of your biztalk project as 1.0.0.1 and deploy.Step 4:
Add the name of map in the already existing send and receive ports and test.I hope this helps you.If want further details write me again
I am having what I think to be the same problem. When I try to redeploy a project it will not let me as it gives me the error message
\”Some items in the removed assembly are still being used…\”. To get past this I have to then delete my receive port and location, deploy and then add the receive location and port again. I have checked my assembly version and it is 1.0.0.0. Is there anyway around this problem or do I have to continue recreating my receive port every time? -
AuthorPosts