Forum Replies Created
-
Posts
-
How do you go about developing an assembly that can be referenced from a Transform Shape in an Orchestration. Is there an Interface that can be inheirited? What public methods do I need, what do those methods need to return?
Any help would be…well…helpful :p
In my experience, integration with mainframe involves cobol copybooks. These are specs for flat record structures.
You can probably get well populated instance files and define them in the schema editor with the flat file importer wizard.
What is the difference between integrating application or data?
Long time ago, but did you get any help with this issue? I have the same problem using the ffdasm.exe.
Thanx a lot for replying….
I have tried using Decision Shape also so that until and unless the condition will not satisfy it will not call the method but then also as soon as i starts the application it directly calls the .net method without executing the previous step i.e without dropping the files into the folder.
Please help me regarding…
You will see the "Delivery Notification" property on any Port ..properties window.
Yes..the DeliveryNotification = transmitted will not work with a Dynamic port. Its meant only for a statically bound port.
Delay would be the workable option.
Should be a setting on the orchestration port within the designer. Not sure if you can use it for dynamic ports, however …
Thanks for your reply.
I am using Dynamic Send Port. For which I am unable to find any option to turn on delivery notification.
Can you please elaborate this approach. Delivery Notification is property of which shape?
Thanks,
I have gone through the link. I sent mail to the given id. But i got failure delivery. The phone numbers in that site also invalid. I think the compnay is closed.
Remember that by default, the orchestration moves on (to your expression shape) after the message reaches the MessageBox, NOT the final destination (FILE adapter).
You could try turning delivery notification on, so that you don't move on until the adapter is successful, or, add a delay shape with 3 seconds in it.
Thanks guys, all this information has been great in helping me decide on the future with Biztalk. Its such a good application but unfortunately it doesn't get the amount of media coverage that it deserves
Ash
I guess it depends when you want these files to be converted. For instance if these files are to be converted at runtime, then you will want to look into custom pipelines. For instance, BizTalk can receive a flat file(csv or fixed width), as this message is received, it is "disassembled" into an xml file in the receive pipeline. So by the time the file gets to your Orchestration it is in XML format.
There is a design time component called the Flat File schema wizard(which showed up in 2006) that helps you define the structure of the flat file and how it will look in XML. The end result is that you will have a Flat File schema which you will use in your custom pipeline.
There is also a 3rd party component, called FarPoint i believe, that allows you to perform a similar function, but with Excel files. I have not used it so I can't say how well/poorly it functions.
Hope this helps…
We decided to implement BizTalk rather than writing custom solutions in order to standardize code and make it easier/quicker to bring people into the development team without having to sift through tonnes of code in order to determine how certain processes work.
We also run a SharePoint Portal so we plan on integrating BizTalk into SharePoint in order to provide information about systems to non-IT staff who are stakeholders for a particular system.
Once you get past the learning curve of BizTalk I believe its often faster to develop/deploy a BizTalk application than a custom .NET application.
I think the improvements made between 2004 and 2006 and the "quick" release of 2006 R2 is an indication that MS is behind the product and will continue to support and enhance it.
