October 2008 - Posts

"Oslo"==SOA++?
30 October 08 05:34 PM | wmmihaa | 1 comment(s)

In my last post I wrote "Oslo" == Windows Registry++, to describe the simplicity of "Oslo". I also said "the simplicity of "Oslo" is what makes up its complexity".

SOA has different impact upon different roles within an organization. But if you would be a "Process Developer", you would have this "toolbox of services", which you could reuse when creating your processes. One could imagine such a tool being Visio (or Surface), and where you'd find the publicly exposed service in some toolbox window, and you could drag these services to the process surface to compose the content of the process. So far these services has been more or less the endpoints of those services.

-Now, imagine the Repository of "Oslo" being the source of that toolbox window. -But hey, the repository stores much more then endpoints, right...It stores models of endpoints, services, workflow's or your custom processes etc. These could all be reused across your organization.

Does this mean Models == Service or perhaps SOA has grown to MO or MOA? And another thing that will blow your mind, put your Repository in Windows Azure, and share your models across organization boundaries ...

BTW...The slogan for PDC 2008 was "Think WAY out side the box"

Filed under: , , ,
"Oslo"==Windows Registry(++)?
30 October 08 05:30 AM | wmmihaa | 2 comment(s)

So finally, Microsoft revealed "Oslo". There has been so much rumors about what it is. Starting of at the SOA & BPM conference last year, "Oslo" was to be the next generation of BizTalk. For some time now, it's been clear that this was not to be the case. But what is it then?

This question was the main reason why I attended the PDC this year. However, I left the first "Oslo" session even more confused then was before attending it. The main reason for this was probably that I created my own expectations about what it would be.

I've now attended five "Oslo" sessions, along with several discussions with the team members, and I believe I finally understand the concept. You see, the simplicity of "Oslo" is what makes up its complexity. Once you understand it, you'll find endless possibilities where to use it, or at least where Microsoft will be using  it.

So "Oslo" is three things:

  1. "Repository" the store
  2. "Quadrant" the tool
  3. "M" the language

To explain this in a (much) simplified way, think of it as:

  1. A Registry like we have today, but to which you can store user defined types and models (not only string, binary, DWORD and QWORD)
  2. Regedit(++), from which you can view and edit the types and models from the Registry
  3. A language which describes the models, in the same way as xaml describes a workflow.

WHAT! THAT'S IT????

-Well, add to that; "Oslo" ships with lots of models, such as System.Workflow, System.ServiceModel and many more. This will give you ONE store (SQL db) from which you can find all your workflows and WCF endpoint configuration!!

And you can of course create your own models, say a Process model, which would have a number of workflows, with any number of endpoints... You really need to poke "Oslo" with your own ideas to grasp its magnitude.

In the current bits, you can create your workflow from within Quadrant and export it to Dublin. I'm willing to bet that, in the future, we'll see it the other way around. That we will from Dublin, point to the Repository, to get the xaml and endpoint configuration. No more .config files!

Next post: Oslo == SOA++? 

 

Filed under:
Blogical Sftp Adapter - New release
27 October 08 01:17 AM | wmmihaa

Johan Hedberg has updated the Sftp adapter with various features such as:

  • Supports file Rename on top of the default Delete behavior for Receive, with macro support - you can specify eg. %SourceFileName%.old for rename name.
  • Support for a temporary filename on Send, with macro support, as well as a temporary folder.
  • Added VerifyFileSize property to Send Adapter - for situations where you have the need to perform an extra check of the file sent, that it is in fact the size you expected.

Download from Codeplex

Filed under: , ,
Updated tool for undeploying BizTalk assemblies
23 October 08 11:02 PM | wmmihaa

I previously wrote an article about a tool that could help you undeploy BizTalk assemblies with its references, without going through the pain of keeping track of all assembly references.

FailedToRemove

 

The tool has now been updated for better support of dependency tracking along with some other minor UI changes.

The application requires .Net 3.5, which, if you haven't got it installed, can be found here. If you choose not to run the application on the server, make sure the assemblies you're about to uninstall are deployed to the computer from which you're running the application. This is because the application needs to access the assemblies to get its dependencies.

Download

HTH

Filed under: ,
Samples from BizTalk User Group meeting
21 October 08 11:17 PM | wmmihaa | 1 comment(s)

Here are the samples from the BizTalk User Group meeting last Monday.

Tool for undeploying BizTalk assemblies
02 October 08 11:15 PM | wmmihaa | 2 comment(s)

Ever found it challenging to uninstall a schema or an orchestration? This tool was designed to find all referencing assemblies and related BizTalk artifacts such as Ports, Locations and Orchestrations.

Installing the tool:

The zip-file includes both source code and binaries.

Using the tool:

Important! For the tool to be able to find assembly references, those BizTalk assemblies need to be installed on the same machine as the one you are running the tool on.

BizTalkUndeployHelper_pic1 

By selecting one assembly, the tool marks all assemblies that is referencing the one you selected. If the selected assembly includes orchestrations, the tool will look through all orchestration ports for referencing pipeline and transformation assemblies.

 

BizTalkUndeployHelper_pic2

Before you choose to undeploy, you'll be given a list of all assemblies and BizTalk artifacts related to those assemblies. You'll be given an option to leave the ports, in case the ports will be reconfigured to use passthrough pipelines and no in- or outbound transformations.

Downloads 

Please provide me with feed-back if you find any problems or bugs.

//Mikael

Filed under: ,

This Blog

News

    MVP - Microsoft Most Valuable Professional BizTalk User Group Sweden BizTalk blogdoc

    Follow me on Twitter Meet me at TechEd

    Visitors

    Locations of visitors to this page

    Disclaimer

    The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.

Syndication