Forum Replies Created
-
Posts
-
Today I talked to one person. It seems they are not giving trainng in Biztalk server 2006. But they are providing training in other EI tools and only for corporate.
I’ve heard of people doing this. I guess it all depends on what you want to accomplish… BizTalk is not “officially” supported on non-Microsoft VW’s. You’d need to check the KB for the exact details. And performance would take a hit.
So, if you didn’t need a high performing and mission critical solution, it would be fine.
It’s not something I’d really go and suggest or even be too thrilled about having to work with. I don’t even do Dev work on VM unless the client absolutely demands it.
I guess this is the obvious question… What message are you sending out of your Send Shape? Make sure this is the Message Variable that corresponds to Schema F.
Sorry, you lost me a bit. Are you calling the pipeline inside your Orchestration? If so, I don’t think that will work since Message Type is demoted when you send out the message from the Orchestration.
You can always cast the message from an Xml Doc to a typed message… I did that in one of my BizTalk 2004 untyped message samples. I think it was this one: http://www.biztalkgurus.com/Samples/Untyped-Documents-Promoted-Orchestration.html
Have you tried the Xml Receive Pipeline but set the Allowed Unrecognized Message = True? I think that still promotes Message Type.
Not really sure how to do what you want… but typically correlation properties need to exist inside the message. Then, on the Send you initialize the correlation and on the Receive you would follow it.
Might want to check this out as well: http://geekswithblogs.net/cyoung/articles/17364.aspx
Not really any easy way to do it… What I would do is create a custom pipeline component and resided after the Xml Disassembler. I’d read the email subject property and then either edit it or set the text to another property. It could be as simple as having .net code to check if your Routine XXX exists and set a custom property isRoutine and then all you have to do is filter on isRoutine. Make sense?
All in all, this should only be a few lines of code. Guessing 10 to 20 total.
Make sure you sue the BizTalk Pipeline Wizard. It’s a huge time saver.
Oh, guess you could also do the sample type of thing in a Orchestration. Easer to code, but not the right place to do this I’d say.
Take a look at this: http://biztalkblogs.com/carlosmedina/archive/2006/04/21/509.aspx
Not real sure. But you might want to look up in the help guide what the exact input and outputs requirements are for those functoids. They will not let you link if the expected parameter is not of the correct type. Example: if the input parms were bool, string you could only link functoid with output type bool to this first. Then, type string. Make sense?
Yep, not something the mapper can do. Unless you have a max number of nodes to count up to.
You’ll need to look at using some .net code or something like that to build your message.
Maybe it’s a problem with changing the file in Notepad. Can you see the changes in the map?
Your steps sound correct to me. If all else fails, try removing the Application and DLL and try a full redeploy.
Not real sure, but I think there has been some patches and updates to the Adapter. Might want to make sure you are running BT04 with SP2.
Hello again,
I thought this problem had been resolved but unfortunately I am still getting what appears to be a caching problem. Below is a description of the steps taken and problem:
Solution in Visual Studio comprises of 2 projects, 1 for Schemas, maps and pipeline and the other for an orchestration.
Made a change to custom Xslt via notepad and saved file.
Both projects have properties set as follows:
Redeploy = true
Install to Global Assembly Cache = true
Restart Host instance = true
Refreshed, built and deployed both project.
Deployed solution.
In BizTalk refreshed the BizTalk Group, stopped & restarted the host instance.
Stopped and started the application.
The test produces data that does not reflect the change made in Xslt file.
Have I missed a stepped somewhere?
We are running BizTalk 2006 on MS virtual machine windows 2003 server with SQL 2005 – this shouldn’t cause any problems should it?
Could it be a BizTalk configuration / setting?
Cheers
Stable
