Forum Replies Created
-
Posts
-
Anon,
one quick way is to create a map. In the map, *do not map* the element you dont want if it is empty (use the conditional mapping functoid).
I don't see what this has to do with the flat file input by the way – in the orchestration you are treating an XML message.
John D.
Anon,
Create a thin .NET wrapper which just calls out to the C++ component. This will give you testability and flexibility.
John D.
You can use SSODB.
You can refer my link below where I discussed about SSODB.
I would first modify the target namespaces on the schemas so there are no conflicts with having multiple schemas with the same root node. Then i would use a listen shape with multiple recieve shapes. The listen shape would allow for the orchestration to listen for different messages matching a schema for any of the recieve shapes in the listen shape. However, you need to change the namespaces for the schemas…
1. Open a project that has the schema
2. Double-click the schema to open it
3. Select the schema node.
4. Right-click and select properties
5. Modify the target namespace property.
Hi John,Thanks for the reply. We are considering of the issue about opening & closing of xml files each time when an orchestration fires up. Will it be a problem? Not sure about the performance hit that happens. If i implement the lookup file to database table also then it would be again opening/closing connection each time for an orchestration. The DB people wont be happy to make hundreds of connection opening & closing.The xml file content would be changed often.The best thing to do is spend a little time looking for the BizTalk content on the Microsoft site. It shows at a high level what BizTalk is and what it is used for.
You need to enable Suspended Message Routing. And then build a process (Orchestration probably) to subscribe to the message and send an email.
Check out the sample here: http://www.biztalkgurus.com/Samples/Suspended-Message-Routing-Biztalk-2006.html
It should get you started.
You’ll need some type of schema resolver pipeline component. There is a sample in the SDK in the Pipeline folder I think. It based on Flat Files so it should be easy to modify.
The sample was written for BizTalk 2004 – before .net 2.0 was available. You might be able to run the solutions through the VS 2005 upgrade wizard. That would work.
Not sure if all the .net components and samples will work though. Sorry.
Anon,
are you really worried about the performance hit of reading a small file for each instance of an orchestration which starts? I wouldn't worry, I think, because it will only be a small element against all the other things which one orchestration instance incurs.
But you could try to make the retrieval of the info faster – for example, by COM+ singleton (System.Enterprises) or by a database table.
John D.
Hi Stephen.
I tried to install your example on my computer but it says that I need to install .Net framework version 1.1.4322. At the moment i have .Net framework 2.0 installed on my windows vista system.
Best regards
Kim
Anon,
if the contents of the 'lookup file' aren't changing very often, then perhaps you could use the BizTalk config file?
But, I agree that this is not really an answer to your question about a 'global' variable.
John D.
