Forum Replies Created
-
AuthorPosts
-
January 24, 2010 at 3:13 PM in reply to: Error calling edi pipeline inside the orchestration in BizTalk Server 2009 #24125
Hi,
Read the following threads from the MSDN forums:
Basically, EdiSend and EdiReceive pipelines are NOT supported for use inside an Orchestration.
What is the reason why you want to develop such a scenario? Is manipulating the EDI data in XML format not adequate for your needs?
Daniel.
Thanks for you reply I have one more question, I am able to get the desired output now but I am using .xsl to get the output because I have used xsi:type in my scripting functoid and its throwing error coz I have not declare xsi so when I am trying to declare xsi in the template its not accepting so I am using .xsl in my map, but I want to know whether its possible to declare xsi:type in template and not using any .xsl in my map?
Thanks
January 23, 2010 at 8:25 AM in reply to: BizTalk 2009 WebSphere MQ communication on Windows Server 2008 64 bit #24123There are 2 different Microsoft – WebSphere MQ adapters. The one that comes on the BizTalk 2006/9 cd has a COM+ based component that needs to be installed. The other one which is referred to as MQSC is on a different installation disk. You will find it on the BizTalk Adapters for Host Systems installation disk.
If you have a BizTalk license you are also licensed for this adapter even if it is on a different disk. We are using it in a similar situation as you Windows 2008 – MQ v 7 with fix pack 7.0.1
Brunchey is on the right path….
To ensure your send port instance is successful you will want to use delivery notification (http://kentweare.blogspot.com/2007/11/biztalk-delivery-notification.html). You don’t want to mark you file as done if you send port is going through retries due to connectivity or disk issues.
You can use some .Net code to either delete the .flag file or simpley rename it. You will need to write this code in an expression shape or reach out to a .net library to do this work.
You will be able to get the location of the inbound file via the file adapter’s context property in an expression shape i.e
FilePath = MsgIn(FILE.ReceivedFileName)
I have the similar problem on IIS7. However, your code should work on self hosting WCF.
Typically derived types are represented as
<BaseType xsi:type=”DerivedType”>
In your Xslt you need to use a predicate e.g
<xsl:for-each select=”/root/BaseType[xsi:type=’DerivedType’]”>
or
<xsl:value-of select=”/root/BaseType[xsi:type=’DerivedType’]/field”/>I would suggest using a custom xslt file rather than a scripting functoid. You will get to use an Xml editor rather than a text window.
http://msdn.microsoft.com/en-us/library/aa560154(BTS.20).aspxi’ll try this next week, i’ll tell you how it works.
I’ll put this code in a message assignment before sending it to the soap port.
A little problem is how to access secondXml ? by xpath ? and to pass this parameter in the convert method ? I’ll try this, but the call of this method doesn’t work, impossible to cast this xpathdocument to an xmldocument.
Thank you again, you’re of great help.
From the documentation:
The Backup BizTalk Server Job creates synchronized backups of all BizTalk Server databases by using full database backups and transaction log backups, in conjunction with a type of transaction known as a marked transaction. Marked transactions are transactions that place a mark into the transaction log of all databases participating in the transaction. The marked transaction blocks new distributed transactions from starting, waits for the distributed transactions that are currently running to complete, and then executes to place the mark. For more information about marked transactions in SQL Server, see http://go.microsoft.com/fwlink/?LinkID=137859.
The mark represents a transaction point that is consistent across all databases; you can use the mark with subsequent log backups to restore your databases to that point.
For each BizTalk Server database, the Backup BizTalk Server job creates a marked transaction log backup every time it runs, and it creates a full backup based on a time period that you specify.Without using this Biztalk backup job you risk having backups that restore from a SQL point of view but are useless to Biztalk because the databases are in an inconsistent state.
You can use the xpath function to assign a value to a node:
xpath(Message, “/*[local-name()=’Message’]/*[local-name()=’message’]”) = ConvertXmltoBase64(XmlDocument secondXml);
A quick though on this…
You could move this logic into an orchestration.
Using the context properties of the message you could identify where the source file arrived from and write out your .flag file to this location. For this, I believe that you could use the File Adapter in a send port.
Do your processing…
Once complete you would then write out the .done file. This could as well be done using the File Adapter in a send port.
I believe that to delete your .flag file you will need to do this using an expression shape that deletes the file. There are other ways to do this last one, but i am not currently aware of anyway to rename a file in a directory using the native biztalk adapters.
it doesn’t seem to work :
making the message element a distinguished field
the base64 element cannot be distinguished
Message.message = ConvertXmlToBase64(XMlDocument secondXml);
How and where to do that, in an orchestration (assignment), mapping, …
Regards
Any other help ?
Regards
Thanks a lot Greg,
I got some userful information…..
January 21, 2010 at 10:49 AM in reply to: Dynamic MSMQ port error – ‘outbound transport could not be resolved ‘ #24109Thanks
Within 10 min of posting the question i figured it out.
January 21, 2010 at 10:26 AM in reply to: Dynamic MSMQ port error – ‘outbound transport could not be resolved ‘ #24108The MSMQ adapter uses the MSMQ:// scheme for its URLs, not queue://. Might that be what’s causing you trouble?
-
AuthorPosts