Forum Replies Created
-
Posts
-
It happens when the table in which you are trying to insert or update is being used by some other process.You can use Sql Profiler to check which process is creating deadlock on that table.
Hope you find it useful.
Yeh Stephen….he is right
Sibling means children of same parent.
I mean
Root1
Parent1(Record)-Child1(Field Element)
Child2(Field Element)
Parent2(Record)-Child3(Field Element)
Child4(Field Element)
Now here Child1 and Child2 are sibllings and Child3 and Child4 are siblings.
Child1 and Child4 are not siblings as they are not children of same parents.
Hope you find it useful.
Seems there is some problem with the sample xml file been dropped in the folder
C:\CallOrchestration\In\*.xml
Validate the xml against the schema.Are you using any Namespace in the xml file?
Hope you find it helpful.
Thanks Greg, it spent me some time to figure it out to use the XML Schema editor…..really good feature
Thanks guys. I got that working. I changed my port to single request-response port, instead of 2 port which were one recv and one send port.
Check out the Custom Party Resolution Pipeline component in the SDK.
C:\Program Files\Microsoft BizTalk Server 2006\SDK\Samples\Pipelines\CustomPartyResolution
This uses data from within the message to establish party identity.
You should be able to modify this to use the BTS.InboundTransportLocation message context property.
You can set up am alias for each party which is their receive location Url.
I tested your Scenario.
Input Sample- Age is of type xs:int
<R1>
<Age>10abc</Age>
</R1>I got an error in EventViewer as below
Event Type: Error
Event Source: BizTalk Server 2006
Event Category: BizTalk Server 2006
Event ID: 5753
Date: 11/7/2006
Time: 7:13:13 AM
User: N/ADescription:
A message received by adapter "FILE" on receive location "Receive Location1" with URI "C:\NISHIL\Temp\TestAPP1\In\*.xml" is suspended.
Error details: There was a failure executing the receive pipeline: "TestAPP1.ReceivePipeline1, TestAPP1, Version=1.0.0.0, Culture=neutral, PublicKeyToken=f9ba375e961a272d" Source: "Pipeline " Receive Port: "ReceivePort1" URI: "C:\NISHIL\Temp\TestAPP1\In\*.xml" Reason: The 'Age' element has an invalid value according to its data type.
MessageId: {6F1D4DB9-BE37-41D7-82C8-509B0791547D}
InstanceID: {CE8DFF51-E025-416F-B821-973BDEE3218A}For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
So I think Xml validator is working fine.Seems you are missing something.Have you set the Document Schemas Property of Xml Validator.
Hope this helps you.
If you are exposing your Orchestration as webservice …you can use multipart messages and pass on the 3 parameters to the orchestration.
You need to promote the file name into the FILE.ReceivedFileName property in the message context. You can do this in the adapter after you create the IBaseMessage. Call the IBaseMessage.Context.Promote() method.
Details on the FILE.ReceivedFileName can be found in the property schema C:\Program Files\Microsoft BizTalk Server 2004\SDK\Include\bts-file-properties.xsd
To debatch this will require a 2 stage process. The first requires grouping the orders and the second will debtach them.
To group Xml records using some arbitary content, requires a custom Xslt. The best technique is Muenchian grouping (google Biztalk and Muenchian for examples).
You can then pass this thru another pipeline to debatch (the output of the first map should be a envelope/document schema) or debatch using a loop inside an orchestration.
One way to check if the mapper is adding the choice nodes with default values is to check the Xslt output from the mapper.
Use the Validate Map command, this will compile the map and present you with a link to the Xslt in the ouput window.
If the mapper is adding the default values, you have 2 options:
1. remove the default values from your schema
2. use a custom Xslt and remove the mapper generated xsl statements you do not want.
