Forum Replies Created
-
AuthorPosts
-
I don’t really understand your question. Installing .NET 3.0 is fine, and it will work with VS2005. However, you still won’t be able to use VS2008 with BizTalk 2006 R2.
February 4, 2009 at 7:00 AM in reply to: Custom Pipeline Component Adding Rootnode and NameSpace #21641But the problem is If I use generic Xml.XmlDocument for the incomming message then there is a potential risk that biztalk can receive any type of message and my Xpaths and custom logic will fail there.
Hay Guys, Please suggest any better approach for this..
<wsdl:part name=”parameters“ element=”tns:PearsonXMLOrder“ /></wsdl:message><wsdl:part name=”parameters“ element=”tns:PearsonXMLOrderResponse“ /></wsdl:message>I think what I sent as my web service got screwed up, lets see if this looks better.If I’ll choose .net 3.0 framework in visual studio, then also, will it not work????
Hi Neeraj,
If I’m not mistaken, BizTalk 2006 does not work with VS2008. You have to use VS2005 or wait for BT2009.
Here are the system requirements for BizTalk 2006 R2: http://www.microsoft.com/biztalk/en/us/system-requirements.aspx
Thanks for your reply greg, I forgot to mention one thing element1,element2,element3 contains integer values which I have to Map those values in Descending order Like
element1 — contains 300
element2 — contains 200
element3 — contains 500
then my output should be
element – 500
element – 300
element – 200
Again Thanks for your prompt reply..
a) For dynamic mapping check out Issue 4 of Biztalk Hotrod in the section Smart Use of XSLT
b) For predefined configurable FTP destinations a Send port using the FTP adatpter is best.
If you wish the ability to change the destination at runtime then a dynamic send port from an orchestration is one option, or possibly a rolelink?You should just connect input elements (element1, element2. element3) to the output element (element) without functoids.
sorry i did not get the question ..what i understood is like .you mean to say that you want to overwrite the default properties which BTS provide us…if you want to do that you have to create custom pipe component for Send with you custom needs..
Cool Akash
Element Datatype must be same with webservice papameter…BizTalk Server won’t be convert the datatype…by defalut webservice parameters promoted…no need to do the properties pomotion … Create XSD element with same datatype with Webservice Parameter, then do the pomotion …before call use the MessageAssignment Shape to Align the elemets(XSD) and Parameters(Webservice)
Akash KB ([email protected])
It ges even weirder …. once the file is taken by BTS the first process continues writing it so we end up with the bottom half of an XML file getting created.
The easiest way is to use a filename filter on the receive location (like *.txt) and change the system to write the file with a temporary extension and then rename the file after finishing.
If you have deployed any activities or views to BAM in the past it might not have been removed correctly. Try running:
bttdeploy.exe /remove yourdefinitionfile.xml
Where yourdefinitionfile.xml is the xml file you get from Excel after defining the activities and views.
You cannot host your current web service on a non-Biztalk server. This web service is responsible for receiving the message, executing the pipeline and publishing to the message box. All this happens in the IIS Process (the isolated host). You need to have the Biztalk software installed to be able to do this.
You can however write your own web service that runs on another server that will call the Biztalk web service.
Or you could use a reverse proxy server. -
AuthorPosts