Fixed Field Settings on Map

On a map, you can set the value of a destination node to a fixed value, from within the mapper, simply by setting the value property when clicking the destination node on the right hand side schema. I’ve see people use the string functiods to pre-set a value, however you do not need to do this.

There is a catch I found in BizTalk 2009. If you set the fixed value on a map page other than the first page, it does not set, worse yet, if that field on the destination schema happens to be a promoted property, it does not promote the value, and will fail when you try and use the value inside your orchestration as desired.

You will not know why, the shape will just fail, with some weird exception.

Always use the first page.

Proef Ordina! Aangenaam kennis te maken

Proef Ordina! Aangenaam kennis te maken

Proef Ordina! Zomer editie geeft je donderdagavond 22 september een kijkje in de keuken van Ordina.
Je bent bij Ordina thuis uitgenodigd! In een ongedwongen sfeer kun je kennismaken met Ordina als werkgever en ontdekken wat ’jouw toekomst bij Ordina’ is.

Want bij Ordina is de zomer nog niet voorbij! Samen maken we deze avond tot een groot succes: barbecue, inhoud en een spetterend optreden van talenten van de Voice of Holland Pearl, Rafaella en Bart.

Tijdens de avond krijg je onder andere een kijkje in de keuken van de Excellence Centers van Ordina. Zowel professionals als leden van het management zijn aanwezig om je te informeren over de diensten en producten die wij aan onze klanten leveren. Via demo’s, presentaties en gesprekken hoor en zie je wat voor moois er allemaal gebakken wordt in de keuken van Ordina.

Kijk voor meer info op http://www.proefordina.nl/

BizTalk 2010: BizTalk and Adapter Pack gets a facelift with CU2

In recent days the Cumulative Update #2 has been released with several improvements
and fixes.
(The team have done an amazing job addressing previous issues/fixes with currently
*no* open issues!!! WELL DONE GUYS)

As you may well know by know – BizTalk is made by people who care for Integrators
(us) who care. BizTalk has always been a quality product in the past and in my opinion
will be in the future.

Here’s some details if CU2 that was passed onto me

——————————————-

Hi,

It is a pleasure to announce the release of CU2 for BizTalk Server 2010 on
behalf of the BPD Sustained Engineering group.  With this CU, we have addressed
all known customer issues from all branches of BizTalk (i.e. applicable to BizTalk
2010) and also available in multiple locales.

 

This CU includes few serviceability improvements along with product updates based
on customer requests.  Some of the notable updates in this CU are:

 

  • Transparent CU Setup: Provides info on number of fixes applicable
    to feature during installation
  • Enhanced EPM debug Tracing: Helps the support team isolate specific
    failures in a large volume scenario
  • BizTalk Host Instances not coming back-on-line after SQL being off-line:
    Allows to restart the BizTalk service automatically when SQL connectivity is restored
  • BAM Archive checks & Logging before dropping tables from BAMPI: Prevents
    possible data loss scenarios when archiving fails unexpectedly and also allows for
    a user configurable setting on the rate of archiving.
  • Applications stop responding or crash when System Center Operations Manager
    monitors BizTalk Server applications:
    Issue was caused by a race condition
    in one of our internal class and has been fixed in this release.
 
 

Fixes Per Feature Area

 
 
 

Blog Post by: Mick Badran

BizTalk 2010: BizTalk Server Application Service (BTSNTSvc.exe) fails to start automatically after a system restart

BizTalk 2010: BizTalk Server Application Service (BTSNTSvc.exe) fails to start automatically after a system restart

After rebooting the operating system BizTalk Server 2010 services, in my case: “BizTalk Service BizTalk Group: BizTalkServerApplication” fails to start automatically, despite being configured to do so. This is a Microsoft known Issues with BizTalk Runtime forcing us to manually start the services. I was hoping that BizTalk 2010 CU2 released in August 31, 2011 […]
Blog Post by: Sandro Pereira

ESB Toolkit 2.1 mess up Enterprise Library 5.0 big time

I spend nearly 5 hours so far today trying to configure Enterprise Library 5.0 for one of our projects. The machine I’m working on got ESB 2.1 installed previously.

ESB Toolkit 2.1 utilises Enterprise Library 4.1. Among the various application blocks, it takes advantage of ConfigurationSource to point to ESB specific configuration information (esb.config and SSOConfigurationSource) from machine.config file.

When you open the machine.config file after ESB Toolkit 2.1 installation you will see the following information.

<configuration>
  <configSections>
    <section name="enterpriseLibrary.ConfigurationSource" 
type="Microsoft.Practices.EnterpriseLibrary.Common.Configuration.ConfigurationSourceSection, Microsoft.Practices.EnterpriseLibrary.Common, Version=4.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />

<enterpriseLibrary.ConfigurationSource selectedSource="ESB File Configuration Source">
    <sources>
      <add name="ESB File Configuration Source" type="Microsoft.Practices.EnterpriseLibrary.Common.Configuration.FileConfigurationSource, Microsoft.Practices.EnterpriseLibrary.Common, Version=4.1.0.0,Culture=neutral, PublicKeyToken=31bf3856ad364e35" filePath="C:\Program Files (x86)\Microsoft BizTalk ESB Toolkit 2.1\esb.config" />
      <add name="ESB SSO Configuration Source" type="Microsoft.Practices.ESB.SSOConfigurationProvider.SSOConfigurationSource, Microsoft.Practices.ESB.SSOConfigurationProvider, Version=2.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" applicationName="" description="Configuration Data" contactInfo="" userGroupName="" adminGroupName="" />
    </sources>
</enterpriseLibrary.ConfigurationSource>

This will break all the applications that uses Enterprise Library 5.0, when you try to initialize the Enterprise Library objects you will encounter errors as shown below.

[A]Microsoft.Practices.EnterpriseLibrary.Common.Configuration.ConfigurationSourceSection cannot be cast to [B]Microsoft.Practices.EnterpriseLibrary.Common.Configuration.ConfigurationSourceSection. Type A originates from ‘Microsoft.Practices.EnterpriseLibrary.Common, Version=4.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ in the context ‘Default’ at location ‘C:\Windows\assembly\GAC_MSIL\Microsoft.Practices.EnterpriseLibrary.Common\4.1.0.0__31bf3856ad364e35\Microsoft.Practices.EnterpriseLibrary.Common.dll’. Type B originates from ‘Microsoft.Practices.EnterpriseLibrary.Common, Version=5.0.505.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ in the context ‘Default’ at location ‘C:\Windows\assembly\GAC_MSIL\Microsoft.Practices.EnterpriseLibrary.Common\5.0.505.0__31bf3856ad364e35\Microsoft.Practices.EnterpriseLibrary.Common.dll’

There is a suggestion on the BizTalk forum for this issue

http://social.msdn.microsoft.com/Forums/en-CA/biztalkesb/thread/8dc6ecda-862c-415a-912c-8215caa67a85

but that doesn’t seem to work. When you try to use <enterpriseLibrary.ConfigurationSource selectedSource="Local Application Configuration Source"> in your configuration file, you will receive the following error "Configuration system failed to initialize, Section or group name ‘enterpriseLibrary.ConfigurationSource’ is already defined. Updates to this may only occur at the configuration level where it is defined.". That’s because the section is already added to the machine.config file by EST Toolkit 2.1 installation.

I couldn’t find a solution to the problem. I’m just posting this so people are aware of the consequences, before installing ESB Toolkit 2.1.

Nandri!

Saravana

New Job, Same Place

New Job, Same Place

I’m a bit of a restless employee who is always looking for new things to work on and new challenges to tackle. So, this recent change should hold me for a while. I’ve accepted a role as the lead functional architect for the Research and Development division of my biotechnology employer. What this means is […]
Blog Post by: Richard Seroter