Forum Replies Created
-
AuthorPosts
-
June 19, 2008 at 1:14 AM in reply to: Error2 The number of applications in this group has reached the maximum number allowed in this BizTalk edition. #19954
how to over coem this issue !!!
June 19, 2008 at 12:50 AM in reply to: Error2 The number of applications in this group has reached the maximum number allowed in this BizTalk edition. #19953There is a limit on the number of applications between the various editions of Biztalk:
Enterprise = unlimited
Standard = 5
Branch = 2
Dev=unlimited (but constrained in other ways)The inline Xslt might not be necessary, but there is no input nodeset to iterate over with the for-each.
The input data comes from disparate nodes in the source and these nodes map to the same output field. This would normally be accomplished by connecting each input node to the output node, however the output is a structure requiring additional fields that are dependent on the input node context.
There is probably a way of doing this with lots of conditional and value mapping functoids, but the Xslt Call Template seemed like the easiest option
looking at techsavvygal’s example…
//this functoid accepts exactly two parameters.
this.SetMinParams(2);
this.SetMaxParams(2);
AddInputConnectionType(ConnectionType.AllExceptRecord);
}It looks like she is covering both inputs with the single connection type statement.
I think there is a natural inclination to define what type is allowed for each parameter position, but it looks more like a single blanket definition for the whole functoid – case in point the conditional mapping functoid. Here you have a string and a logical and, as you know, these can be out of order and the mapper will not warn you, it will just simply fail to map the field. So that suggests that there is no 1:1 enforcement of input types.
Hi Greg:
I have downloaded and installed the ScheduledTask Adapter in Biztalk Server Administration, deployed the assembly Biztalk.Adapter.ScheduledTaskProperties.dll to the GAC using Biztalk Deployment Wizard. I have created a receive port in Biztalk explorer with a Receive Location using this adapter to use the Xml String component from the ScheduledTask.TaskComponents library. I set a weekly schedule starting today at a specified later time to trigger the orchestration.
However, then the time came, the adapter did not trigger the orchestration to run, there was no activity in HAT and no events were captured in Event Viewer.
Can you tell me why the adapter did not run?
Thanks,
Daniel.
Greg – is the inline XSLT really necessary?
I think the key was adding the looping functoid which creates the “for each” in the underlying xslt. This is what sets the context to allow him to get the subordinate data for each node, instead of getting the first nodes data each time.
The problem there is restarts of the host. Everytime you restart the host, the adapter will fire again.
There is a solution that uses the SQL Adapter to call a stored proc that decides whether it is the correct time based on config stored in a table. If the time is right it returns the correct message otherwise nothing, Not sure what happened to this example.
I can’t do much about the stored procedure. Even if I somehow get my hands on it I’m bound to run into this problem again sooner or later.
My messages are small (1 kb) and not complicated. I’m glad to hear there’s a way to do this in Xslt (sort), although I’m no expert at that. How can I build and scatter the mentioned batch-message in Biztalk ? The rest is already done or easily googled I guess.
If you are using a polling adapter, setting the polling interval to once a week might be the solution. The FILE and SQL adapters have decent control over the polling interval.
How much control do you have over the database? Is it possible to modify the stored proc? How complicated are the messages and how big are they?
One possibility is to create an insert table and add the incoming messages to this table, as you receive them, after the delay timeout, call a stored proc that will process the insert table adding records to the real tables. You can control the order of processing the messages within this stored proc.
Another possibility is to create a .NET class (it will need to be serializable) that can accumulate these messages and return them in the correct order. As each message arrives have an Add method on this class to save each instance. At delay timeout have a GetNext method that that you can loop on that returns the messages in the correct order.
Another possibility would be to aggregate the messages into a single message, at delay timeout use a custom Xslt map using <xsl:sort> to order the messages and then loop extracting each indivdual message and sending to the DB
Your orchestration will be like an aggregating sequential convoy, you can have a single orchestration by correlating on message type or you could have one orchestration for each ID by correlating on the ID field.
You could try Haley Office Rules (formally RuleBurst)
Allows you to manage your rules and export them to the BRE
Hi Greg:
Thanks for quick reply and the feedback! I will check the adapter out…
Cheers,
Daniel.
The BTSServiceWindow utility was lost when GotDotNet went away.
You could try contacting him via his blog http://geekswithblogs.net/bloesgen/archive/2004/09/30/11983.aspx
Alternatively there is this adapter http://www.codeplex.com/BizTalkScheduledTask
This adapter has a flaw, (sometimes fires twice due to a race condition in the TaskScheduler) but look for a revised version in about 1 week, hopefully with documentation (http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=3306448&SiteID=1)
Hi,
if you have no prior knowledge about BizTalk I highly recommend that you start with BizTalk alone for the beginning. Knowing the basics will save yourself a lot of trouble (note that knowing the basics for BizTalk is already quite a lot).
Once you understand BizTalk, stick to the Installation Instructions shipping with the Accelerator, be sure that you pay a lot of attention to the needed prerequisites.
HTH
Dominik
Dominik
-
AuthorPosts