Forum Replies Created
-
Posts
-
I am looking at options for integrating BTS into our product line with minimal additional configuration issue.
It woudl be handy to be able to use a connection string similar to that for SQL to be the target of a message. Yes, very similar to a SOAP adapter but less setup on the BTS server. There are lots of ways to do this and I am still trying to figure out the impact of each.
Doug
One solution I see is to have a singleton orchestration that check your table column at desired intervals and then perform action according to Y or N flag…
Or maybe you could have an SQL jobb that sends a XML message to a folder if the flag is N, this will trigger the orch. and you could monitor the table column flag and terminate the orch if it's Y…
just some rapid ideas…
The ExplorerOM classes are used for admin only.
Using IBTTransportProxy remotely would defeat the loosely coupled nature of Biztalk.
How about using the SOAP adapter or soon the WCF adapter
What is that you are trying to do?.
Correlation is the method used to match an incoming message with a running instance of an orchestration. Biztalk uses subscriptions to do this.
Subscriptions are used to route incoming messages to send ports and orchestrations. Some subscriptions will activate the send port or orchestration and some are used for active orchestrations e.g correlations and convoys
There is a blog post from Matt Meleski:
http://objectsharp.com/blogs/matt/archive/2006/01/29/3778.aspxThere are also some commercial offerings in this space:
http://www.fpoint.com/biztalk/default.aspxI wrote a sample pipeline component for doing that, there is a sample that turns a UBL invoice into a PDF.
You map your Xml file into XSL-FO and then use the pipeline component to convert into PDF. It uses a third party XSL-FO to PDF converter. This sample uses a product from Visual Programming (http://www.xmlpdf.com) but there are a number of other products that could just as easily be used.
They are very different things in truth, while both dealing with routing of a message:
Subscription is the process of routing a message based upon metadata and structure to a particular process.
Correlation is the process of routing a message based upon metadata and structure to a particular instance of a process that already exists.
Lets say that you have a process which receives MsgA, sends MsgB to another system which could take a long time to return, when it does return MsgC comes back with given data and finally you produce MsgD as final output which contains data from MsgC and MsgA.
Every message above has a subscription, you have to know how to receive or send that message. Only the MsgC return subscription requires correlation, because you need to be able to return to a specific orchestration process, the one with your matching MsgA, so that MsgD can be properly produced.
Put in a much more simple way, it is the difference between going to a High School football game, and an NFL football game. At the High School game, you come in, can sit anywhere you like and watch the game. At the NFL game, you come in and are issued a particular seat. The process of matching you and that seat is correlation. Going to a game is subscription.
Prasanth,
Yes MQSeries adapter comes out-of-the box with biztalk server 2006. You might be looking for it when you are desigining the orchestration and binding the Receive port at design time, there we can see only four adapters which doesn't contain MQSeries (I dont know why is this). Leave your binding to Specify Later and after deploying the project make a new Receive port in the Biztalk Administration Console, there you'll be able to see all the adapters that come with Biztalk server 2006, including MQSeries. If you still cant find it there, Go into the Platform Settings (Within Biztalk Administration Console) –> Adapters, right click and add a new adapter for MQSeries.
I've tried to use it with MQSeries queues running on Windows and it works fine, but I am not too sure about Unix AIX.
Hope this helps
Regards,
Sajid.
Found "The Bloggers Guide to BizTalk".
Helps to Google once in awhile.
Yeah Orchestration is the right way, its pretty easy when you start, just grasp basic concepts on how Biztalk works and then go straight into developing simple solutions into it. Biztalk provides different adapters out of the box, which includes, the File and SMTP adapters, so you can easily recieve messages using emails or Files of file system.
Here is a link to some useful Getting started material:
Regards,
Sajid.
I found the issue, the orchestration properties in the assembly had private modifier (silly me) . I changed it to public and everything was smooth after that.
I got a solution.. to create the interop dll manually with a key.. but not sure it is perfect solution in Biz2006
Yes, BOM ( byte order mark) was creating the problem. I was modifying the input instance xml file in textpad and interestingly enough when I save the file, textpad removes preceding BOM (0xff, 0xfe) from the file and Biztalk was throwing exception because of missing BOM. Though there is a work around in textpad to fix this, I would recommend using notepad for modifying the input instance xml.
Thanks a lot for the help guys.
Can you copy the suspended message out to the filesystem and run the flat file disassembler on it? If the encoding specified in the xml doesn't match the encoding of the file that can cause problems.
Looks like if that's your problem and you need to handle unicode here's a few pointers:
http://blogs.msdn.com/csdcustomerexperience/archive/2006/01/24/517228.aspx
