by community-syndication | Feb 21, 2007 | BizTalk Community Blogs via Syndication
UPDATE!
Gert Drapers [MSFT] has posted a much more thorough explanation of refreshing and resyncing the schema view. Take a look!
To Synchronize or To Refresh?
Here's a quick tip for those of us using VSTEDP (DataDude) for database development and TFS (Team Foundation Server) for source control.
You may occasionally see a yellow message stating "External file change, resynchronization required…" when you open a large solution, perform a "get latest version (recursive)" and switch to the schema view. I'm assuming this is a normal behavior since the local schema database may be out of sync with the object scripts just downloaded from the TFS server. If I remember correctly, the DataDude team decided not to "resync" automatically since it may take some time to accomplish on a large scale project. Unfortunately, it's not immediately obvious how to do this unless you mouse over the "Synchronize" icon as shown below:
No, this is not a "Refresh" button as the icon suggests, it's a "Synchronize" button and will bring your Solution Explorer view and Schema View into sync! Keeping these two views in sync is critical since the Schema Compare and Data Compare functions use the local schema database and not the SQL script files.
I know the DataDude team talk about the "one version of the truth" in database development but in reality there are two versions, one in the script files and the other in the local schema database. It's important to keep these two versions of the truth in sync!
Technorati Tags: Visual Studio, DataDude, Team Foundation Server
by community-syndication | Feb 21, 2007 | BizTalk Community Blogs via Syndication
Mike Ammerlaan (PM for WSS) stepped up and posted a detailed article about the integration of ASP.NET AJAX and SharePoint.
Here’s an interesting section:
Here are some common scenarios in SharePoint you should be able to achieve with Microsoft ASP.NET AJAX 1.0:
- Building a more powerful, re-usable JavaScript libraries you can use in your web controls and parts
- Enabling your web services to render via JSON, resulting in easier usage in JavaScript/Ajax Applications
- Building a web part that takes advantage of Extender technology to provide richer interaction styles, such as autocomplete on a textbox.
- Using an UpdatePanel in your web part or control for more fluid, no postback interaction. (this will require some workarounds, however.)
Recommended reading: the full article.
Technorati tags: sharepoint, ajax, web parts, wss, moss
by community-syndication | Feb 20, 2007 | BizTalk Community Blogs via Syndication
I was having lunch this week with a bunch of Auckland based MVP’s.
Amongst them Lukas Svoboda
Lukas mentioned that off the back of Ron Jacobs world tour of New Zealand last December (organised by Mark Carroll) he would be setting up a New Zealand version of Ron’s famous ARCast Channel.
The New Zealand ARCast Site is now LIVE go check it out – http://www.arcast.co.nz
Some of you might remember these ARCast episodes from last year…
ARCast – Web V.Next Panel with Scott Guthrie, George Moore and Rowan Simpson
ARCast – Web V.Next Panel with Scott Guthrie, George Moore and Rowan Simpson (Part 2 of 2)
by community-syndication | Feb 20, 2007 | BizTalk Community Blogs via Syndication
Always handy info to keep at an arms length, especially when doing upgrades of BizTalk
2004 to 2006 or building/migrating Sharepoint webparts from v2.0 to v3.0.
Msdn article found here: Breaking
Changes
Enjoy – Mick.
by community-syndication | Feb 20, 2007 | BizTalk Community Blogs via Syndication
Most of you might have come across situations where you have to map a huge number of elements from the source schema to the target schema using the BizTalk Mapper.
There is an easy way to do this depending on your source and target schema structures.
Actually there are two scenarios where you can make use of this:
1. If your source and target schemas have an identical structure, or even if a part of your source schema and target schema have an identical structure.
2. If your source and target schemas have an identical node names, or even if a part of your source schema and target schema have an identical node names.
Here’s how to do it:
1. Bring up your BizTalk mapping editor and load the source and target schemas
To Auto Map by Structure
2. Click on the grid surface of the map and in the properties window and set the “AutoLink By” property to “Structure” (which is actually the default value)
To Auto Map by Node Name
2. Click on the grid surface of the map and in the properties window and set the “AutoLink By” property to “Node Name”
3. Map the nodes by holding down the SHIFT key and drawing a line from the parent node of the source schema to the parent node in the target schema as shown in the figure below:
Note that in our figure above, the node names as well as the structure is the same, so you could set the “AutoLink By” property to either “Structure” or “Node Names” in this case.
Benny Mathew
Seamless Integration Solutions
BizTalk Consulting, Development, Training
Bangalore, India
http://www.seamless.in
http://GeeksWithBlogs.net/benny
![]()
by community-syndication | Feb 20, 2007 | BizTalk Community Blogs via Syndication
Why biztalk 24 * 7 ? |
Biztalk 24 * 7 is an attempt by a Microsoft Biztalk server enthusiast Saravana kumar to put pointers to all the available resources for Biztalk under one roof. The left hand side navigations shows a glance of what you can get, I hope you got the idea. By the time of first release in January 2007 there were around 350 unique external BizTalk links. The site also features a special search engine designed for searching biztalk resources (Explained in detail later) using Windows Live Search and a special aggregator for BizTalk blogs. I’m planning to update the site every 15 days once, or whenever I find a must have new resource. Updates to the site will be communicated via my blog.
About Saravana Kumar |
Saravana kumar [MCAD (Charter member), MCP (BizTalk 2004)] is an independent consultant focused solely on Microsoft based integration solutions using BizTalk Server. He is currently living and working in Birmingham, United Kingdom. Microsoft recently published his white paper Understanding Design-Time Properties for Custom Pipeline Components in BizTalk Server
Want to know more? Click Here |
|
|
|
by community-syndication | Feb 20, 2007 | BizTalk Community Blogs via Syndication
Why some BizTalk artifacts can be Enlisted and Started and others can only be Enabled?
What kind of errors depends of those actions (Enlisted, Started, Enabled)?
One of the main rule of the BizTalk message system is:
Only messages with subscription can come to the message system. System cannot “eat” messages without subscription, otherwise they would overfill it (messages without subscription would come into the message system but cannot go out, anyone want this.)
There are two places where messages come into: Orchestrations (“send port” shapes) and Receive locations. They are “Publishers“.
And two places where messages go out: Orchestrations again (“receive port” shapes) and Send ports. They are “Subscribers“.
Publishers can be Enabled/Disabled, that’s all. But Subscribers can be Enlisted/Unenlisted and Started/Stopped. Enlist/Unenlist means Start_Subscribe/Stop_Subscribe. (I don’t know why MS guys created such mess in terms. It looks like something historical. (?)) I can only propose my view of things in http://geekswithblogs.net/leonidganeline/archive/2006/12/18/101541.aspx
Subscribers should be “Enlisted”. That’s mean your message type + routing parameters (here it is your promoted element) are written to the routing table. Only after that your messages (with your message type + routing parameters) can come to the BizTalk message box. Otherwise you’ve got different kind the errors (see below).
How does the system depend of these Enlisted, and Enabled statuses?
We have four variants with messages received by adapter :
1).
After Subscriber is Enlisted and Started, the messages subscribed by this subscription can come to the Message box and then to this Subscriber .
2).
After Subscriber is Enlisted but not Started yet, those messages are waiting inside Message box in the Suspended (Resumable) state. When Subscriber is started, those messages go out from Message box to this Subscriber. [BTW We don’t need to restart the BizTalk service to get the messages gone to Subscriber! Just Start the Subscriber.]
3).
If the Subscriber is not Enlisted, and the message type in well-known by BizTalk, we’ve got 4 (!) error event: 5755, 5778, 5753, and 5752. The most clear is the second:
“
Event Type: Error
Event Source: BizTalk Server 2004
Event Category: BizTalk Server 2004
Event ID: 5778
…
Description:
The Messaging engine failed to process a message submitted by adapter:FILE Source URL:C:\Solutions\Monitor\TestData\In\*.xml. Details:Could not find a matching subscription for the message. . This error occurs if the subscribed orchestration schedule or send port has not been started, or if some of the message properties necessary for subscription evaluation have not been promoted. Please refer to Health and Activity Tracking tool for more detailed information on this failure
…“
It means the message was recognized by BizTalk, because BizTalk knows of its namespace. But there is no one subscription to this message. What BizTalk should do with such message? It was also processed by adapter, it is inside the BizTalk, but there is not any destination point to it.
In this case we’ve got those events and two (!) Suspended (not resumable) copies of the message in the MessageBox, one is with “Routing failure report” in the Service class field, and second with “Messaging” in the Service class field. Why two? Maybe because the message was passed to the second processing stage (Adapter –> Routing) and now it is stored in two places.
Bad situation: our system received the message, but it is stooped inside (and in two copies!). For FILE adapter it means the file disappears from the drop folder, but was suspended in the MessageBox. How we can restore the file and start it again? It’s a different story…
4).
If the Subscriber is not Enlisted, and if the received by adapter message has unknown namespace or has an error by promoting the promoted properties, we’ve got 4 (!) error event: 5719, 5755, 5753, and 5752. The most clear is the third:
“
Event Type: Error
Event Source: BizTalk Server 2004
Event Category: BizTalk Server 2004
Event ID: 5753
…
Description:
The “FILE” adapter is suspending a message coming from Source URL:”C:\Solutions\Monitor\TestData\In\*.xml“. Details:”Error in accessing the part data or one of its fragments. The part or fragment may not exist in the database. “.
…
“
It is similar to the previous case. One difference is we have one copy of the Suspended (not resumable) message in the MessageBox.
It is still a bad situation: our system received the message, but it is stooped inside. For FILE adapter it means the file disappears from the drop folder, but was suspended in the MessageBox. How we can restore the file and start it again? It’s a different story too…
I would realy appreciate your response!!!
by community-syndication | Feb 20, 2007 | BizTalk Community Blogs via Syndication
In development machines, BizTalk developers normally tend to enable full body tracking of messages they process inside the BizTalk server for debugging purpose. As BizTalk Server processes more and more data on your system (over a period of time), the BizTalk Tracking (BizTalkDTADb) database continues to grow in size. Unchecked growth decreases system performance and may generate errors in the Tracking Data Delivery Service (TDDS). In addition to general tracking data, tracked messages can also accumulate in the MessageBox database, causing poor disk performance.
According to this MSDN article http://msdn2.microsoft.com/en-us/library/aa560754.aspx
“By default, the DTA Archive and Purge job is not enabled. You must first configure and then enable the job.”
I haven’t enabled the job after BizTalk server installation on my development machine and recently when I visited the SQL Data folder for something else I saw this shocking file size (shown below after 6 months of usage). My BizTalk tracking data file is 3.05GB.
Purge tracking data:
BizTalk 2006 got some nice Stored Procedures and SQL Jobs to Archive and Purge the tracking database. BizTalk 2006 gives you an option to Archive and Purge the tracking data or just purge the data without archiving. In a development machine we don’t need to maintain the archived tracking data, so we will just purge it periodically.
As soon as I saw the data file size of 3.05GB, first thing I did was configured the DTA Purge and Archive SQL job to just purge the tracking data as explained in the article http://msdn2.microsoft.com/en-us/library/aa578470.aspx
Long story short:
1. Change the SQL Statement inside “DTA Purge and Achieve” SQL Job to
declare @dtLastBackup datetime set @dtLastBackup = GetUTCDate() exec dtasp_PurgeTrackingDatabase 1, 0, 1, @dtLastBackup
If your data file size is too big (like mine 3.05GB) after configuring DTA Purge and Achieve SQL job don’t go and run the SQL Job directly, due to the volume of data present in the tracking database, it will take very long time to process the backlog. Instead do a manual purge first as explained in this article
http://msdn2.microsoft.com/en-us/library/aa561918.aspx
Long story short:
1. Stop all BizTalk/IIS service (SSO, Rule,EDI,Host Instances)
2. Open SQL Management Studio and run the following stored procedure under BizTalkDTADb database as shown below:
EXEC [BizTalkDTADb].[dbo].[dtasp_PurgeAllCompletedTrackingData]
The stored procedure will be executed very quickly, mine took less than 10 seconds (remember my data file size was 3.05GB).
Shrink your BizTalkDBADb via SQL Management Studio:
Right-Click on the BizTalkDTADb database inside management studio and select
Tasks => Shrink => Database, and click “OK”
Now, look at the size of the BizTalkDTADb.mdf file, its shrinked to the absolute minimum value.
Configure the SQL Job to run periodically (every 1 minute)
After performing the steps above (once the tracking data is purged) “DTA Purge and Archive (BizTalkDTADb)” SQL Job will run instantaneously without any wait. Now, you can enable the job to run periodically.
Nandri!
Saravana
by community-syndication | Feb 20, 2007 | BizTalk Community Blogs via Syndication
Last year I had the pleasure of meeting Scott
Hanselman (who
also talked about this subject today) when he was in town to speak at the Dallas
.NET User Group and North Dallas .NET User Group.
I told him “I’m paid more today because of you, thanks.” and he quipped that perhaps
he should setup a “Hanseltax”. Well I don’t know that I’m ready to start forking over
cash to Scott just yet, he costs me enough in gadgets already, but I might just be
convinced that a “RoederTax” is necessary after the release of Reflector 5.0.
Lutz Roeder’s Reflector is a must
have for all .NET developers, period, full stop. If you don’t have this on your box
yet, stop reading this right now and go download it. The latest version includes the
ability to set a display font size, which I much appreciate given the 1400×1050 resolution
of my Toshiba M200 Tablet, and an incredible new Custom Protocol Handler registered
to code://.
Why is this so incredibly cool? Because now it becomes possible to link directly to
methods from a blog post. For instance if I’m writing about XML, as I’m like to do
from time to time, I might say you need to check out System.Xml.XmlReader and
if you’ve got Reflector 5.0 installed it will open Reflector and open that exact method
for you to examine.
There are a ton of other features in Reflector 5.0, but I doubt that many will be
affecting my life as quickly as this one. Lambda Expression, LINQ syntax, C# 3.0/.NET
3.5 support are all great, but code:// will be used today!
by community-syndication | Feb 20, 2007 | BizTalk Community Blogs via Syndication
Why some BizTalk artifacts can be Enlisted and Started and others can only be Enabled?
What kind of errors depends of those actions (Enlisted, Started, Enabled)?
One of the main rule of the BizTalk message system is:
Only messages with subscription can come to the message system. System cannot “eat” messages without subscription, otherwise they would overfill it (messages without subscription would come into the message system but cannot go out, anyone want this.)
There are two places where messages come into: Orchestrations (“send port” shapes) and Receive locations. They are “Publishers“.
And two places where messages go out: Orchestrations again (“receive port” shapes) and Send ports. They are “Subscribers“.
Publishers can be Enabled/Disabled, that’s all. But Subscribers can be Enlisted/Unenlisted and Started/Stopped. Enlist/Unenlist means Start_Subscribe/Stop_Subscribe. (I don’t know why MS guys created such mess in terms. It looks like something historical. (?)) I can only propose my view of things in http://geekswithblogs.net/leonidganeline/archive/2006/12/18/101541.aspx
Subscribers should be “Enlisted”. That’s mean your message type + routing parameters (here it is your promoted element) are written to the routing table. Only after that your messages (with your message type + routing parameters) can come to the BizTalk message box. Otherwise you’ve got different kind the errors (see below).
How does the system depend of these Enlisted, and Enabled statuses?
We have four variants with messages received by adapter :
1).
After Subscriber is Enlisted and Started, the messages subscribed by this subscription can come to the Message box and then to this Subscriber .
2).
After Subscriber is Enlisted but not Started yet, those messages are waiting inside Message box in the Suspended (Resumable) state. When Subscriber is started, those messages go out from Message box to this Subscriber. [BTW We don’t need to restart the BizTalk service to get the messages gone to Subscriber! Just Start the Subscriber.]
3).
If the Subscriber is not Enlisted, and the message type in well-known by BizTalk, we’ve got 4 (!) error event: 5755, 5778, 5753, and 5752. The most clear is the second:
“
Event Type: Error
Event Source: BizTalk Server 2004
Event Category: BizTalk Server 2004
Event ID: 5778
…
Description:
The Messaging engine failed to process a message submitted by adapter:FILE Source URL:C:\Solutions\Monitor\TestData\In\*.xml. Details:Could not find a matching subscription for the message. . This error occurs if the subscribed orchestration schedule or send port has not been started, or if some of the message properties necessary for subscription evaluation have not been promoted. Please refer to Health and Activity Tracking tool for more detailed information on this failure
…“
It means the message was recognized by BizTalk, because BizTalk knows of its namespace. But there is no one subscription to this message. What BizTalk should do with such message? It was also processed by adapter, it is inside the BizTalk, but there is not any destination point to it.
In this case we’ve got those events and two (!) Suspended (not resumable) copies of the message in the MessageBox, one is with “Routing failure report” in the Service class field, and second with “Messaging” in the Service class field. Why two? Maybe because the message was passed to the second processing stage (Adapter –> Routing) and now it is stored in two places.
Bad situation: our system received the message, but it is stooped inside (and in two copies!). For FILE adapter it means the file disappears from the drop folder, but was suspended in the MessageBox. How we can restore the file and start it again? It’s a different story…
4).
If the Subscriber is not Enlisted, and if the received by adapter message has unknown namespace or has an error by promoting the promoted properties, we’ve got 4 (!) error event: 5719, 5755, 5753, and 5752. The most clear is the third:
“
Event Type: Error
Event Source: BizTalk Server 2004
Event Category: BizTalk Server 2004
Event ID: 5753
…
Description:
The “FILE” adapter is suspending a message coming from Source URL:”C:\Solutions\Monitor\TestData\In\*.xml“. Details:”Error in accessing the part data or one of its fragments. The part or fragment may not exist in the database. “.
…
“
It is similar to the previous case. One difference is we have one copy of the Suspended (not resumable) message in the MessageBox.
It is still a bad situation: our system received the message, but it is stooped inside. For FILE adapter it means the file disappears from the drop folder, but was suspended in the MessageBox. How we can restore the file and start it again? It’s a different story too…
I would realy appreciate your response!!!
