Forum Replies Created
-
AuthorPosts
-
December 17, 2006 at 5:42 PM in reply to: Reuse of orchestration that start with active receive shap #16970
You could make your reusable orchestration callable by removing the activate receive and then creating a replacement orchestration that is activatable that calls the reuseable orchestration.
Alternatively you could investigate direct ports rather than calling the orchestration.
December 17, 2006 at 11:27 AM in reply to: BizTalk does not appear to use latest Custom Xslt version #16969Thanks Stephen and Greg.
I had 2 projects set up – one for schemas and the other for orchestration. Only one of these had these had the restart host instance set to true!
Thanks again for the help
Stable
Have you looked at the schema property to Ignore Trailing Delimiters?
It’s on the <Schema> node if I remember correctly.
December 17, 2006 at 11:10 AM in reply to: Inserting / Reading binary data with the SQL adapter? #16967I’d probably go about this using .net code inside an Orchestration – for insertion at least.
Otherwise, have you taken a look at: http://www.biztalkgurus.com/samples/SQL-XML-Data-BizTalk-2006.html This should be able to process any type of data, just make sure you use the pass though pipeline.
December 17, 2006 at 8:49 AM in reply to: Unable to obtain service organization from the adapter (Oracle adapter) #16965Have you checked the DNS name and make sure that connection works?
Thank you, I shall try that, I shall create a send pipeline with a flat file assembler. Under the document schema specifications I shall select the per instance config and in my expression shape I shall create the new message as stated above before sending it.
I guess I need to use a flat file dis assembler when I receive the message initially otherwise I dont think this would not work with a pass thru pipeline.
Thanks,
Jess
Well, your two message schema need to be the same to create a new message from it. It looks like you have two different schema. If that’s the case, you’ll need a map.
If the document schema property on the Flat File Assembler is blank, the assembler will try to use the schema that matches the message type of the message.
I have built a small project that contains a Flat File receive pipeline (FF Disassembler + Party Validation) and a Flat File send pipeline (Flat File Assembler). This project is deployed into a Biztalk application, I call Common. I can then reference this application from my other Biztalk applications. When I need to send or receive a flat file I use one of these pipelines. I use the per instance pipeline configuration feature of BTS2006 to specify the document schema on the receive pipeline, and almost never specify the document schema on the send pipeline.
December 16, 2006 at 6:41 PM in reply to: how to make an orchestration activate on 2 different queues #16960It’s not possible to have 2 Activates inside an Orchestration.
You need to either have 2 separate Orchestration or you need to tell the 2nd message what instance of an already running Orchestration it needs to get routed back to. Make sense?
It almost sounds like you have 2 separate processes.
Hi Greg, Thanks for that explanation. I shall copy the above in my expression shape, But i am not sure how to use a Flat file assembler without specifying the properties for document schema in my flat file assembler.
Thanks,
Jess
You can grab an evaluation copy of the latest version of BizTalk here .. http://www.microsoft.com/biztalk/evaluation/trial/default.mspx.
Saravanan,
Did you get any contact for Training on BizTalk. Pls let me know. I have got a number in chennai. 044 64535600 try this out.
Pls contact me at [email protected] if you get any biztalk training center in chennai or bangalore.
You could put the config settings in C:\Program Files\Microsoft BizTalk Server 2006\BTSNTSvc.exe.config instead.
The messages passed thru Biztalk are a serializable .Net class that contain a message context (dictionary of name/value pairs) and a stream of bytes.
In an orchestration you can receive a message of type XmlDocument. This does not mean the message has to be Xml. It means there is no MessageType on the messagebox subscription, so it will accept any type of message, even an image file. You will still have access to all the message context properties promoted by the adapter and pipeline components, including the FILE.ReceivedFileName if the message came from a file adapter.
So your mechanism of sending an Xml file with the file name, which then uses a .Net component to read the file is not needed. You can simply have a single receive location with a file mask of *.* , a pass-thru pipeline and an orchestration accepting untyped messages, you will have achieved the same result.
You could still use other receive locations on this receive port to accept xml files for example. Have a single receive location with the XmlReceive pipeline, which would determine the message type for you. In the orchestration you could check to see if BTS.MessageType property is set this would save you calling a receive pipeline first. Otherwise you can use your custom logic inside your orchestration to determine the pipeline to call to process the input file, perform some logic and and call the output pipeline and send the output. You still need to have a lot of configuration, that will enable you to determine which pipelines to call.Personally I would use as much of the functionality in the product as possible. The configuration setup is a one-off task that will probably be less effort than writing, testing and maintaining your own version of message routing.
December 15, 2006 at 2:14 PM in reply to: how to catch exception in biztalk server 2004 for request-response type port #16954There is a limit of 256 chars on the Promoted Properties.
If you make it a Distinguished field you shouldn’t have a problem.
I'd guess you are probably not using it for Routing anyway.
-
AuthorPosts