Forum Replies Created
-
Posts
-
Hi 😀
I’m having some issues getting started with what seems to be basic BizTalk 2006. BizTalk doesn’t seem to like the XSD’s I’ve been supplied with so I’m hoping to type message objects within orchestrations using .net classes.
I’ve generated classes from an xsd, then created a class library with the classes and used this within an orchestration to receive a message typed as one of these classes. If I send an xml message (which conforms to the xsd used to generate the classes) to the web service around the orchestration, should this be deserialized into the Message object received using a receive shape?
or do I need to write a custom pipeline component to deserialize the incoming xml message and replace it with the deserialized .net object? 🙁
Regards,
Lee.Hi Tim,
I was wondering if you ever worked out how to do a dynamic orchestration call? I Realise that you can submit the msg to the MsgBox with a specific promoted property and have a particular orchestration subscribe to a specific value of the promoted property. However I was after something similar to the dynamic transform calls, which seems to be what you were after originally. How did you go?Guy
Let’s go back to basics. I don’t want to re-read all the prior messages, but these two items are important:
1) You should have an error in your Application EventLog
(on the machine that is running Biztalk Server).2) Is the receive file on the same machine as Biztalk Server – maybe that’s the whole problem? If you have the same folder on two machines, Biztalk is only monitoring the folder on its machine – and thus there might be no errors. If you want Biztalk to read a file from another machine, then you need to use an UNC name in the Receive Location definition.
Neal
When I save my file into the receive location, I then go to BizTalk explorer and refresh the configuration database. On expanding the receive location it has been disabled. I was definately enabled before I save the file.
The account being used by the BizTalk Host service has full control on the receive folder and the file.
I have set the shared permissions to full control. Still no joy. Receive location still disabling.
Could it be a permissions issue with the BizTalk configuration database, which is on a different server to where my file drop locations are (my local machine)?
the called orc. has type modifier public,but still cannot select from the list in the master orc.
All the time im getting that orchestration to be called shoulnt have \”out\” or \”ref\” params…i have only 1 \”in\” param…My best guess is that it’s a security issue. The id that your Biztalk Host Service is running under doesn’t have full access to the directory – OR – if you are using a UNC name or a SAN there might be other considerations (check the sharing permissions tab and set Shared Permissions to Full Control).
Is your receive directory a local name?
Neal
Which and how many exception blocks should I done “by the book”?
Is there any type that covers all exceptions?10x
Have you tried
[code:1:2d4a211598]throw new System.Exception(\"null value not allowed!\"); [/code:1:2d4a211598]You can specify your own customised data types in the schema.
[code:1:d13011601c]<xs:simpleType name=\"MyDataType\">
<xs:restriction base=\"xs:string\">
<xs:pattern value=\"regular expression\"/>
</xs:restriction>
</xs:simpleType>
<xs:element name=\"MyData\" type=\"MyDataType\"/>
[/code:1:d13011601c]You can then use the XmlValidator component in the receive pipeline.
You can also use a map, but this is a bit more complicated.
To format the output file name you can do the following:
On the send port set the output file name to %SourceFileName%
In an orchestration set the output message FILE.ReceivedFileName property to your desired file name
When your construct the output message add this code to a message assignment shape
[code:1:d13011601c]OutputMessage(FILE.ReceivedFileName) = \"MyFileName.txt\";[/code:1:d13011601c]The problem is in the receive side.
The File adapter will delete the file after it is written to the messagebox, if it cannot delete the file it will rollback the the messagebox update.If this fails 3 times the receive location will be disabled.
Is the receive location still being disabled?
Nope. The file i’m saving into the recieve location (an XML file using infopath) is not being deleted.
