Forum Replies Created
-
Posts
-
What is the purpose of the loop? You receive one message, why do you need to call the webservice multiple times?
Neal Walters
http://Biztalk-Training.comMy first question would be why do you want to write to a database from a map. It would have to be a very compelling reason – using the SQL adapter would be the preferred method.
But if you really have to…
Anything you can do in .Net code can be executed in a map.
You can write code in an external assembly, inline C#/VB, Javascript even, to write to a SQL database.
You code can be called using the scripting functoid.Hi,guys!
In my orchestration,I try to continue reading a web service using a loop.The condition of the loop is set as true.But when I run this instance, the steps in the loop are executed just one time.
Can anyone help me tell me why?I paste the picture of the orchestration as following:
[img]http://temperary.bokee.com/inc/1.bmp [/img]Can you post the following:
The XSLT output from the map: Validate Map and copy and paste XSLT output.The output from Test Map (set Output Validation = false on map file properties)
The error you are getting from Test Map with Output Validation = true
When you add a send port within an orchestration you specify its type as Dynamic.
You need to set the address within an expression shape:
DynamicSendPort(Microsoft.XLANGs.BaseTypes.Address) = \”mailto:[email protected]\”A document schema is used to define a message. It is a definition on an Xml message with optional extensions for flat files, EDI file, etc that enable the parsers to convert the native format into Xml.
A property schema is used to define message context properties. These can be of type MessageDataPropertyBase (the property value is promoted or demoted from/to the message itself) or MessageContextPropertyBase(property value only exists within the message context and can be set by adapters, pipelines or within orchestrations).
If you wish to promote a field from a message into the message context the you need to define a document schema and property schema. In the document schema you promote the required field using the property schema to define the property type that will be used in the message context.
Message context properties are used for content based routing, correlation, modifying message content within orchestrations, etc.
Biztalk will only install the tools and SDK components if Visual Studio is already installed, so the order of installation is important.
If you installed Visual Studio after Biztalk, then you can modify Biztalk via Add/Remove programs at add the missing pieces.
Thanks for quick reply.
How to create dynamic ports?
Regards,
Rax[quote:aa4a5b1dd8=\”greg.forsythe\”]Binding is connecting the orchestration ports to the messaging ports you have configured using the Biztalk Explorer or Biztalk Admin Console.
This effectively sets up subscriptions on the messagebox for the relevant entities.
These can be:
1. Specify Now (messaging ports configs and bindings are built into the Biztalk assembly)
2. Specify Later (you must configure and bind messaging ports yourself)
3. Direct [list:aa4a5b1dd8]For a send port justs publishes the message to the message box assuming you have manually created a matching subcription on a send port or orchestration
For a receive port you must specify your own subscription using the receive shape filters[/list:u:aa4a5b1dd8]
4. Dynamic [list:aa4a5b1dd8]Only for send ports
Allows you to set the sending Url dynamically rather than hardcoded in configuration
e.g you can dynamically specify a email address within an orchestration rather than hardcoding the email address on a SMTP Send Port
[/list:u:aa4a5b1dd8][/quote:aa4a5b1dd8]Binding is connecting the orchestration ports to the messaging ports you have configured using the Biztalk Explorer or Biztalk Admin Console.
This effectively sets up subscriptions on the messagebox for the relevant entities.
These can be:
1. Specify Now (messaging ports configs and bindings are built into the Biztalk assembly)
2. Specify Later (you must configure and bind messaging ports yourself)
3. Direct [list:628026af29]For a send port justs publishes the message to the message box assuming you have manually created a matching subcription on a send port or orchestration
For a receive port you must specify your own subscription using the receive shape filters[/list:u:628026af29]
4. Dynamic [list:628026af29]Only for send ports
Allows you to set the sending Url dynamically rather than hardcoded in configuration
e.g you can dynamically specify a email address within an orchestration rather than hardcoding the email address on a SMTP Send Port
[/list:u:628026af29][b:9028ed6bab]Promoted properties[/b:9028ed6bab] are visible outside of an orchestration and can be used for routing i.e. subscription filters, and by pipeline components and adapters. They are also limited in size – less than 255 characters. There are two types MessageDataPropertyBase (references a message node) and MessageContextPropertyBase (only exists in Message Context)
In an orchestration they are accessed using this syntax:
Message_1(PropertyNamespace.PropertyName) = 27;[b:9028ed6bab]Distinguished fields[/b:9028ed6bab] can only be used within an orchestration and are accessed using dot notation:
Message_1.distinguishedfield = 27;
There is no size limitation on distinguished fieldsStephen,
Can you email me your source and destination schemas and sample Xml file and possibly the corresponding output flat file.The Biztalk Base EDI Adapter is limited by the number of X12 and EDIFACT document versions it supports.
This KB article is written for Biztalk 2004 but applies to Biztalk 2006 as well.
[url]http://support.microsoft.com/?id=840113[/url]You can create your own EDI schemas for messages not supported by the base adapter. Apparently this is not a simple task.
[url]http://msdn.microsoft.com/library/default.asp?url=/library/en-us/BTS06Operations/html/35226250-c497-467c-a9d0-64efc040e227.asp[/url]The MS recommended approach is to buy the Covast EDI Acccelerator if Base EDI Adapter does not support the message formats you need.
Thanks !
I have used the first method using functoid b4. But the problem is the source is a loop structure where as the destination is a flat structure(my case is a tab delimited FF). I would need the source to loop for n times to get the value and put them in seperate places in dest. there is no destination to link the looping functoid.
I am currently trying the xslt method you have suggested.
It can do what is wanted. However, I ran into these 🙁because xslt run in sequential manner, the position of the element produced in destination is according to the order of the source.
SOURCE(A) <source>
<RepeatingParent>
<code>A</code>
<value>123</value>
</RepeatingParent>
<RepeatingParent>
<code>B</code>
<value>456</value>
</RepeatingParent>
</source>
PRODUCE:
<destination>
<codeA>123</codeA>
<codeB>456</codeB>
</destination>
BUT IF SOURCE(B)IS:
<source>
<RepeatingParent>
<code>B</code>
<value>456</value>
</RepeatingParent>
<RepeatingParent>
<code>A</code>
<value>123</value>
</RepeatingParent>
</source>
PRODUCE:
<destination>
<codeB>456</codeB>
<codeA>123</codeA>
</destination>
—-
so source(B) produced invalid destination structure(codeB b4 codeA).what Iam trying now is in the xslt:
a. go through all loop in source to get the value into many parameter
b. then, after that create destination accordingly using the parameter.this should work, but I foresee another problem.
because if I have a another sibling children element (e.g <destination><dummy>) which was created prior to the xslt running , then this element will be overwritten after the running of xslt?really appreciate and hope to hear your advice.
Thanks
-stephen chai-
