Posts

Microsoft has recently released a hotfix to enable font smoothing over remote desktop (RDP). If your addicted to font smoothing (aka ClearType) you will love this hotfix. At least Service Pack 1 is needed in order to install hotfix KB946633 on Windows Server 2003. On the client side you need at least RDC 6.0. In order for ClearType font smoothing to work it needs to be enabled per computer, on the remote desktop client and the user profile on the terminal server. ...

To provide a messaging infrastructure that will: Break the communication complexity problems associated with distributed software, such as the ability to deal with ongoing change, providing management mechanisms for the complex sea of distributed service interactions that typically take place in today’s IT environment. Provide reliable end-to-end messaging. Apply distributed software security. To provide a configurable, reusable architecture. Deal with common messaging problems generically—i.e. routing, transformation, exception handling and unification. Enforce consistency and unification. Leverage modern standards. Support legacy standards and interaction. Promote agility, through increased abstraction and loose coupling. Speed implementation turn-around, through configuration versus coding.

The goal of dynamic resolution is to avoid defining end-points anywhere statically. The responsibility of carrying and managing this knowledge, which is specific to the interaction, is frequently given to the consumer. That is, the consumer statically binds to the service endpoint/s that is consumes. If the responsibility be lifted from the consumer (or providers) itself, and given to an intermediate layer, such as the ESB, the byproduct are mechanisms for coping with change and dealing with infrastructural complexity. While the concept may appear to be trivial, its contribution toward providing a more managed distributed environment (many interacting end-points and data exchanges, etc) is significant. ...

Today I came across an interesting compile time error, given a scenario I had never exercised before. I had a vanilla orchestration that was receiving the same message type (same schema different message instance) using two different receive ports. I wanted to correlate the orchestration, so the first receive shape was set to activate with an “Initialising Correlation Set” and the second receive shape was set with a “Following Correlation Set”. This setup produced the following compile time error: ...

Lately I’ve been having heaps of fun playing with what’s known as the “ESB Guidance” (ESBG). A community/open source driven initiative as an attempt to fill the gap Microsoft currently have in the SOA/ESB space. At a high level it augments its existing messaging/integration engine, BizTalk Server, by adding extended functionality. The ESB guidance aims to: Demonstrate how to implement an ESB pattern using BizTalk Outline best practices Reduce the amount of “plumbing” clients would have to implement themselves Reduce the total cost and effort of an ESB implementation As of the November 2007 release it contains: ...

Here is a simple TSQL query for the BizTalk tracking database, to summarise the orchestration instantiation head-count for a given host. Your mileage with this query may vary depending on how frequently your tracking data archive job is scheduled for (i.e. this query might not have much data to work with if the data has just been archived and purged). SELECT [Service/Name], COUNT(*) FROM dbo.dtav_ServiceFacts sf WHERE [Service/Type] = 'Orchestration' AND [ServiceInstance/Host] = 'FooHost' GROUP BY [Service/Name] ORDER BY 2 DESC

There have been a few scenarios where the complexity of using a standard BizTalk map, have far outweighed using some custom code. This approach, prescribed in Professional BizTalk Server 2006 as the “Manual Mapping” technique, involves code generating types (xsd.exe) from the message schema and using some simple BizTalk object model to stream-in the message, craft a response and return it back to the BizTalk runtime. C# snippet: ...

Firstly, I am not a doctor or qualified in a medical profession in any way, I am just documenting my personal experiences with this particular injury. Staying physically active plays a large role in my day-to-day routine. While I love to cut code and experiment with technology, it doesnt help me towards keeping a physically healthy body. To balance this, I mainly participate in solo sports (jogging and resistance training in the gym), this way I can exercise when I want, and how I want. ...

There seems to be an intermittent deployment problem with BizTalk 2006, that has been the cause of much time wasting. When attempting to deploy BizTalk artefacts either explicitly using the BizTalk Administration Console or the Visual Studio deploy functionality results in the following: Error 26 Failed to add resource(s). Change requests failed for some resources. BizTalkAssemblyResourceManager failed to complete end type change request. Failed to update binding information. Could not enlist orchestration ‘Net.Bencode.Orchestration,Orchestration, Version=1.0.0.0, Culture=neutral’. Could not enlist orchestration ‘Orchestration.TestProcess’. All orchestration ports must be bound and the host must be set. ...

This week I got a great introduction to the subtle difficulties that are waiting to be encountered when running a 32-bit component in a 64-bit environment. In short, an orchestration that employed the standard (ships with BizTalk) MIME Decoder pipeline component was consistently failing with the following: The invocation of a pipeline component continued to raise the following exception. The pipeline “Net.Bencode.Pipeline.Decoder” could not be created for execution. Error Details: “Retrieving the COM class factory for component with CLSID {254B4004-2AA7-4C82-BB2E-18BA7F22DCD2} failed due to the following error: 80040154.” ...