A Sad day – I’ve lost a great friend and Mentor, Steve Ross passes away

Hi folks,

I got some sad news over this holiday period that Steve Ross suddenly passed away
while on holidays with his family. What a shock!!! just never a thought that crosses
your mind.

‘Chipper’ as he was better known to all and sundry was a reminder to me on how to
love life to its fullest.
Even though he was the GM of DDLS his door was always
open and always up for a chat and to lend an ear.

Family was one of his most treasured aspects – having a good one and being all that
you can to them. They’re the most important.

Chipper has done so much for me personally and for Breeze over the years, along with
the priceless mentoring that goes without asking.

He leaves a huge hole and some very big shoes to fill – I’ll miss you Chipper
and thanks for every second!

Life is short my friends – make the most of every ounce of it!

Funeral Details:



Chipper’s funeral is on Friday 11th January at 2pm at St Matthew’s Anglican Church,
The Corso, Manly.

St Matthew’s is on the corner of The Corso and Darley Road, halfway between the Manly
wharf and the beach.

A bus will leave the DDLS Sydney office at 1pm (to be confirmed) on Friday to travel
to the funeral.

The DDLS Sydney office will be closed on Friday.

The family has asked for donations to be made to the Cancer Council of NSW in lieu
of flowers.

Dale, Joel and Chanel invite you to join them afterwards at the The Manly Wharf Hotel
at Manly Wharf.

If you would like send a card: Dale, Joel and Chanel Ross 19 Blamey Road, Allambie
Heights 2100. John (Dale’s brother) is happy to take calls 99382742 or 99392172.

Back on "track"

Hi

Well, the time has come for me to start running again.

11 years ago (when I was a soldier), I was quite the runner. My best times are 5 km
in 17:30 and half a marathon (21,0975 km) in 1:32:46.

Since then, the weight has come up, as the amount of exercise went down :-).

Anyway, I have lost about 7kg in the last 3-4 months, and now was the time to start
running again… and today was the first time.

A local fitness center had an offer for new members, that I have taken, so not only
did I run today for the first time in a very long time, I also did it on a running
machine. That took some getting used to! 🙂 I managed to get the damn machine running,
but then it stopped… then I started it again… and then it stopped. Probably next
time I will get some help figuring out how to set the machine appropriately. The run
itself went fairly well… around 7km. I will have to bring some music the next time,
though.

It felt pretty weird, that I did some interval training, where the maximum speed (16
km/h) was just about the same speed as I ran for an hour without breaks in my earlier
years (15 km/h) 🙂

So, any goals, Jan? Yes, off course. I have a couple;

  1. I would like my average time to run 1 km to be about 4 minutes.
  2. At “Limfjordsl%u00f8bet” (14 km) at the end of May (2008 🙂 ), I want to run faster than
    a friend of mine called Tom. Also, running faster than my old boss Anne would be nice
    :-). 4 minutes per kilometer would take care of both 🙂
  3. At some point, I want to run a marathon. I will wait a couple of months to set any
    specific dates, times, etc. for this one, since I am really in no shape to guess right
    now 🙂

My legs are fine, I believe.. but perhaps tomorrow I will edit that part out of this
blog post 🙂

The plan now is to run every Tuesday, Thursday and Sunday on average.. sometimes it
will be Wednesday instead of Tuesday and so on.

Wish me luck…



eliasen

ESB Guidance…part 4

Extending the ESB Guidance

If what you get from ESB Guidance is not enough, there are three areas you should look in to:

%u00b7         Adapter Providers

%u00b7         Resolvers

%u00b7         Services

Building your own Adapter Provider

When the message has been processed, it is going to be sent to its destination through a dynamic send port, (a.k.a off-ramp). Usually, when using a dynamic port, we’d set the port properties such as transport type and location programmatically in an expression shape (orchestration) or in a custom pipeline component.

In the case of ESB Guidance this is all done using an Adapter Provider. In other words, the Adapter Provider serves to write and promote context properties for specific adapters.

ESB Guidance comes with support for the most common adapters such as WCF-BasicHttp, WCF-WSHttp, MQSeries, FILE and FTP. But for the purpose of this article, we’ll create a SMTP provider.

 

1.       Start of by creating a new Class Library project. And rename the default class to AdapterProvider.

2.       Let the AdapterProvider inherit from the Microsoft.Practices.ESB.Adapter .IAdapterProvider interface and implement the two SetEndpoint methods. (I’m aware the code sample does not fit the size of the frame, but it works if you want to copy the text)

        public void SetEndpoint(Dictionary<string, string> ResolverDictionary, IBaseMessageContext pipelineContext)
        {
            if (null == ResolverDictionary)
                throw new ArgumentNullException("ResolverDictionary");
            if (null == pipelineContext)
                throw new ArgumentNullException("pipelineContext");

            try
            {
                string transportLocation = ResolverDictionary["Resolver.TransportLocation"];
                string endpointConfig = ResolverDictionary["Resolver.EndpointConfig"];

                string to = transportLocation.Replace("SMTP://", "");
                string from = string.Empty;
                string subject = string.Empty;
                string host = string.Empty;
                
                string[] endpointConfigs = endpointConfig.Split(':');

                foreach (string config in endpointConfigs)
                {
                    string[] configs = config.Split('=');
                    switch (configs[0].ToUpper())
                    {
                        case "SMTPHOST":
                            host = configs[1];
                            break;
                        case "FROM":
                            from = configs[1];
                            break;
                        case "SUBJECT":
                            subject = configs[1];
                            break;
                        default:
                            throw new ArgumentNullException("Invalid SMTP Adapter Provider Configuration");
                    } 
                }
                
                //First, set the outboundtransportlocation, transporttype and SMTP specific attributes
                pipelineContext.Write(BtsProperties.OutboundTransportLocation.Name, BtsProperties.OutboundTransportLocation.Namespace, transportLocation);
                pipelineContext.Write(BtsProperties.OutboundTransportType.Name, BtsProperties.OutboundTransportType.Namespace, "SMTP");
                pipelineContext.Write("From", "http://schemas.microsoft.com/BizTalk/2003/smtp-properties", from);
                pipelineContext.Write("OutboundTransportLocation", "http://schemas.microsoft.com/BizTalk/2003/system-properties", "mailto:" + to);
                pipelineContext.Write("Subject", "http://schemas.microsoft.com/BizTalk/2003/smtp-properties", subject);
                pipelineContext.Write("SMTPHost", "http://schemas.microsoft.com/BizTalk/2003/smtp-properties", host);

                // Second, loop through the endpointconfig, this should be ; seperated and set properties
                // by namespace of specific adapter
                if (!string.IsNullOrEmpty(endpointConfig))
                    AdapterMgr.SetContextProperties(pipelineContext, ResolverDictionary);

            }
            catch (System.Exception ex)
            {
                EventLogger.Write(MethodInfo.GetCurrentMethod(), ex);
                throw;
            }
        }

3.       Build and GAC the project. 

4.       Add the new AdapterProvider to the <AdapterProvider> section of your machine.config.

Eg:

<add key="SMTP"
         value="Blogical.Adapter.SMTP,
                Version=1.0.0.0, Culture=neutral,
                PublicKeyToken=c2c8b2b87f54180a" />

5.       Restart IIS and BizTalk.

6.       Create an Itinerary and attach a STATIC resolver to your service (“DynamicTest” in this sample)

E.g:

<Resolvers serviceId="DynamicTest0">&lt;![CDATA[
STATIC:\\TransportLocation=SMTP://[email protected];
EndpointConfig=SMTPHOST=labs:[email protected]:SUBJECT=This is a test mail;]]&gt;</Resolvers>

 ESB Guidance…part 5

TechEd U.S. 2008 Call for BizTalk Content – SOA and Web Infrastructure Track

Although TechEd doesn’t happen until June, there is an extensive timeline that requires us to have sessions submitted in January in order to drive demand generation for the event. Thank you in advance for making TechEd, our largest customer event – a priority.



This year TechEd will feature two separate back-to-back conferences: Tech%u00b7Ed U.S. 2008 Developers, June 3-6, and Tech%u00b7Ed U.S. 2008 IT Professionals, June 10-13, in Orlando, FL.


 


Currently we need more BizTalk session proposals especially for the IT Pro conference.


 


This year we would like to emphasize the following topics:


%u00b7         BizTalk Server 2006 R2 new features in action (EDI/AS2, RFID, WCF Adapters, WCF LOB Adapters, WF/WCF BAM Interceptors)
Demonstrating how the new BizTalk capabilities have been implemented and are already creating value for customers.


%u00b7         ALM of BizTalk implementations
Providing best practices and the details of what it takes to design, build, deploy and maintain BizTalk Applications. Especially for enterprise scale/mission critical implementations.


 


ACTION:



  1. Go to: https://2008.msteched.com/cft

  2. Enter Access Code: TEUS-MSFT

  3. Complete all fields, and submit

NOTE: You will be asked to create a password, which allows you to revisit your submission to make changes or additions, or to enter another session idea


 


Deadline:  Jan 11, 2008.


 


Tips for Successful Submissions:



  • Write a descriptive, fun and enticing title

  • Target 300-400 level technical content; 200 level content is in low demand

  • Make sure your proposal is new, unique and/or refreshed content

  • Take a solution oriented approach

  • Align your topic to the technologies listed for the track

  • Ensure there is no marketing in your content

  • Showcase your speaking experience

  • Focus on current technologies, which are those in beta and will be released to market prior to the next Tech%u00b7Ed

  • High scoring sessions include one or more live demos

Types of Sessions


There are three types of sessions for which you are welcome to submit ideas.


 


Breakout Sessions: 75 minutes


Track Breakout session allocations are limited, so please prioritize your submissions and collaborate with other teams and technologies where possible.   


%u00b7    The session level requirement for Tech%u00b7Ed is 300 or above. 


%u00de      200 Level: Technology overview, technical introduction, some code


%u00de      300 Level: Intermediate architecture, development and more code


%u00de      400 Level: Advanced code, deep architecture, drilldowns


%u00b7    Internal speakers must cover their own T&E out of their team budgets 


%u00b7    30% of our track speakers are required to be external – influencers (MVPs, RDs) or partners.  If you have external speakers who can represent your content, please let me know and we will send them the Call for Content message for externals.


 


TLC Interactive Theater presentations (not sessions): 75 minutes



  • Small group interactions that allow for discussion around a specific topic area 

  • Include white boarding, demos, and/or drill downs, but no PPT

  • Typically are created to compliment a Breakout session

  • T&E is not provided for TLC presenters

 


Hands on Labs (HOLs) – 45 to 60 minutes of content


HOLs materials are provide before the event and available to attendees on computer stations.  These are drilldown technical learning opportunities in a self-paced teaching environment.  There are more than 200 featured Hands-on Lab topics-each focused on a specific task or feature of a product or technology already presented in the Breakout sessions.  When proposing Hands-on Labs, you also can propose modules (more than one lab) that an attendees would do throughout the week.


 


 


Next steps


%u00fc  Session submissions are reviewed to determine which best meet the needs of the Tech%u00b7Ed audience, as well as fulfill the messaging requirements of the PG. 


%u00fc  Tech%u00b7Ed will notify you if your submission status has changed.  By returning to the Call for Content tool, logging in using your Username and Password, and clicking on “My Topics” you will be able to see the status of your submission.


Thanks,


 


Ofer Ashkenazi 

Off Topic: Quiet Time

I'd like to apologize to everyone that regularly reads my blog and has been awaiting something (anything) new. I've been having some health issues over the past nine months that culminated in several hosptial stays including emergency surgery on Christmas eve. The bad news is that not all of my conditions have been fully diagnosed so the doctors are treating the symptoms rather than working on a cure. The good news is that my emergency surgery went just fine and I've returned to work this week. I plan to continue blogging as time and energy permits but my posts may be a little more sporatic than usual.

I'd really like to thank everyone that reads my blog and send in comments. Your continued readership and support really means a lot to me!

Jeff Lynch

Monitoring BizTalk 2006 R2 with SCOM 2007…

I believe there is a problem with the “pre-converted” (from MOM 2005) management
pack that is offered for BizTalk 2006 on the SCOM 2007 management pack download
page
.

I believe the conversion started with the BizTalk 2006 (flat) MOM 2005 management
pack, rather than the BizTalk 2006 R2 version.  The latter is available here.

Assuming you have already installed the MOM
2005 Backward Compatibility Management Pack
, version 6.0.5000.12, you should
be able to import the 2006 R2 version (via the Operations Manager Migration Wizard.)

The reason this is important is because the computer attribute that the (older) management
pack is looking for includes:

MatchWildcard(AttributeValue(BizTalkServer2006Attribute), "3.5.*")

BizTalk 2006 R2 has a version stamp of 3.6.1404.0.

(I believe other
folks have run into this issue as well.)