Search results matching tags 'SOA' and 'BizTalk'

Dublin, Velocity and more bundled up as AppFabric

aerben — Tue, 17 Nov 2009 19:32:03 GMT

Microsoft is bundling up some functionality from previously separated product codenames, e.g. Velocity and Dublin and bundling them as AppFabric.

Download the Beta here: http://msdn.microsoft.com/en-us/windowsserver/ee695849.aspx

Interested in training on some of that new functionality? Contact me!

Cloudy messages / Send & Receive Activities in BizTalk Workflow Services

aerben — Thu, 02 Oct 2008 03:14:00 GMT

(German version may be provided at a later stage / Deutsche Version wird gegebenenfalls nachgereicht)

In previous posts, I gave an introduction to BizTalk Workflow Services, I wrote about flow control and rambled about tricks you can do in conditions.

This post will deal with the send and receive activities available now.

BizTalk Workflow Services offer the following send and receive activities:

CloudHttpReceive
CloudHttpSend
CloudServiceBusSend

CloudServiceBusSend

CloudServiceBusSend was already used in the introduction post, so I will start with this.

CloudServiceBusSend with ConnectionMode RelayedMultiCast

Please look at the provided sample typically at Program Files\Microsoft BizTalk Services SDK\Samples\Workflow\GettingStarted and find the activity "cloudServiceBusSend1".

The activity corresponds to the following Xoml-fragment:

<ns0:CloudServiceBusSend x:Name="cloudServiceBusSend1" URL="sb://connect.biztalk.net/services/ChatRooms/watchdog/MulticastService/" Response="{x:Null}" Body="&lt;Chat xmlns='http://samples.microsoft.com/ServiceModel/Relay/'&gt; &lt;nickName&gt;watchdog&lt;/nickName&gt; &lt;text&gt;The Microsoft site is responding.&lt;/text&gt;&lt;/Chat&gt;" Action="http://samples.microsoft.com/ServiceModel/Relay/MulticastContract/Chat" ConnectionMode="RelayedMulticast" />

Select cloudServiceBusSend1 and look at the properties:

ConnectionMode

There are two implemented ConnectionModes: "RelayedMultiCast" and "RelayedDuplexSession".
RelayedMultiCast requires a contract that only contains OneWay operations. "RelayedDuplexSession" in contrast will theoretically allow a response, but there seems to be a bug in the present version and the response will get lost. The posted example uses the "RelayedMultiCast" ConnectionMode. It interacts with the sample Program Files\Microsoft BizTalk Services SDK\Samples\Communication\ExploringFeatures\ConnectionModes\Multicast.

URL

sb://connect.biztalk.net/services/ChatRooms/watchdog/MulticastService/

This is the URL of the ServiceBus address you are trying to reach. A WorkflowValidator will not only check it for being not empty but also use the scheme "sb".

Action

http://samples.microsoft.com/ServiceModel/Relay/MulticastContract/Chat

Nothing really surprising. It is best understood though when looking at the contract of the corresponding sample

[ServiceContract(Name = "MulticastContract", Namespace = "http://samples.microsoft.com/ServiceModel/Relay/")]
public interface MulticastContract
{
    [OperationContract(IsOneWay=true)]
    void Hello(string nickName);
 
    [OperationContract(IsOneWay = true)]
    void Chat(string nickName, string text);
 
    [OperationContract(IsOneWay = true)]
    void Bye(string nickName);
}

So, it is basically Namespace+Name+Operation.

Body

<Chat xmlns='http://samples.microsoft.com/ServiceModel/Relay/'> <nickName>watchdog</nickName> <text>The Microsoft site is responding.</text></Chat>

What is actually being sent. A WorkflowValidator will check if it is valid XML.
In this example you see the outer element being named "Chat" like the operation that is going to be called on the interface with the namespace "http://samples.microsoft.com/ServiceModel/Relay/" of the ServiceContract. Then there are two string parameters, each represented by an XML-Tag corresponding to the parameter names of the operation: "nickName" with its value "watchdog" and "text" with its value "The Microsoft site is responding.".

Response

The response is empty, with RelayedMultiCast it will always stay empty even after the call (since it only involves OneWay operations) and unfortunately in the present CTP drop I found it impossible so far to be filled.

CloudServiceBusSend with ConnectionMode RelayedDuplexSession

Let's look at a slightly different configuration for this activity

<ns0:CloudServiceBusSend x:Name="cloudServiceBusSend1" URL="sb://connect.biztalk.net/services/andreaserben/EchoService/" Response="" Body="&lt;Echo xmlns='http://samples.microsoft.com/ServiceModel/Relay/'&gt; &lt;text&gt;Original&lt;/text&gt;&lt;/Echo&gt;" Action="http://samples.microsoft.com/ServiceModel/Relay/EchoContract/Echo" ConnectionMode="RelayedDuplexSession" />

with the properties being like

ConnectionMode

As mentioned "RelayedDuplexSession" will theoretically allow a response, but there seems to be a bug in the present version and the response will get lost. This example interacts with the sample Program Files\Microsoft BizTalk Services SDK\Samples\Communication\GettingStarted\Echo.

URL

sb://connect.biztalk.net/services/YOURWORKFLOWSERVICESUSERNAME/EchoService/

This is the URL of the ServiceBus address you are trying to reach in this case contains your username because this is how the "Echo" sample sets up its endpoint.

Action

http://samples.microsoft.com/ServiceModel/Relay/EchoContract/Echo

Again nothing really surprising. It is best understood though when looking at the contract of the corresponding sample

[ServiceContract(Name = "EchoContract", Namespace = "http://samples.microsoft.com/ServiceModel/Relay/")]
public interface EchoContract
{
    [OperationContract]
    string Echo(string text);
}
 

Again it is Namespace+Name+Operation. (Note that this is not a one-way operation now.)

Body

<Echo xmlns='http://samples.microsoft.com/ServiceModel/Relay/'> <text>Original</text></Echo>

The outer element is named "Echo" like the operation that is going to be called on the interface with the namespace "http://samples.microsoft.com/ServiceModel/Relay/" of the ServiceContract. Then there is the parameter "text" with its value "Original".

Response

The response is empty, here you would expect your value to show up that you get back from the ServiceBus as return values, however, it does not seem to work at the present time.

CloudHttpSend

Again look at the sample at Program Files\Microsoft BizTalk Services SDK\Samples\Workflow\GettingStarted and this time find the activity cloudHttpSend1.

The activity corresponds to the following Xoml-fragment:

<ns0:CloudHttpSend x:Name="cloudHttpSend1" StatusCode="0" URL="http://www.microsoft.com" Method="GET" Request="{x:Null}" RequestContentType="{x:Null}" Response="{x:Null}" />

Select the activity and look at its properties:

URL

http://www.microsoft.com

The address of the resource you want to access. The WorkflowValidator will allow the Uri-Schemes "http", "https" and "ftp". The URL has to be given in absolute format. (The actual access is done through HttpWebRequest).

Method

GET

Allowed values are "GET" and "POST".

RequestContentType

This only is being considered for the "POST"-method. An example would be "text/plain".

Request

This is only being considered for the "POST"-method. The string here will be written to the RequestStream of the HttpWebRequest by interpreting the the String as UTF8-encoded through Encoding.UTF8.GetBytes(REQUESTSTRING).

StatusCode

The StatusCode that the HTTP-Request receives will appear here after the call was being made.

Response

The "Response" property will contain the content of the ResponseStream of the HttpWebRequest interpreted as UTF8-encoded.

There is really not much more to it, I will however try to give an end-to-end example that utilizes this activity in a bit more meaningful manner.

CloudHttpReceive

CloudHttpReceive is tough to impossible to figure out with the given documentation as to date.

Let me first quote the documentation:

CloudHttpReceive: This activity receives an HTTP request at the URI http://workflow.biztalk.net/servicesHttp/<UserName>/workflows/<WorkflowTypeName>/instances/
<InstanceId>/<ActivityName> and returns a response. The HTTP listener uses Identity service access control and the operation name "Send"

Properties

Response: the HTTP content to send in response to the HTTP request

StatusCode: the HTTP status code to return in response to the HTTP request

Request: the content of the received HTTP request. This property is set by the activity when a request is received.

It sounds easier than it is.

This is the smallest possible workflow utilizing this activity:

and its corresponding Xoml-definition:

<SequentialWorkflowActivity x:Class="WorkflowProject1.Workflow1" x:Name="Workflow1" xmlns:ns0="http://schemas.microsoft.com/2007/11/CloudWorkflowActivityLibrary" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/workflow">
  <ns0:CloudHttpReceive Request="{x:Null}" x:Name="cloudHttpReceive1" StatusCode="0" Response="Hello" />
</SequentialWorkflowActivity>

A closer look of the Xoml-fragment of that very simple cloudHttpReceive:

<ns0:CloudHttpReceive Request="{x:Null}" x:Name="cloudHttpReceive1" StatusCode="0" Response="Hello" />

It corresponds to those properties:

Request

This property will contain the string you received in the Request-Stream interpreted as UTF8-encoded.

Response

What you set here will be returned to the caller.

StatusCode

This is the statuscode that you will send to the caller.

Log in to BizTalk Workflow Services and create a type named "MinimalHttpReceive" with that Xoml definition and click "save changes".

Note that you did not need to provide a rules definition.

Create an instance of that type and start it and look at your instance manager:

Note the GUID of the workflow instance: 7bf7a7c4-82f5-4935-9c03-62ba1e7991aa
This will vary for you and you will have to remember your own GUID.

Now start the workflow instance and go to this URL in your browser:

http://workflow.biztalk.net/servicesHttp/YOURUSERNAMEHERE/workflows/MinimalHttpReceive/instances/YOURGUIDHERE/cloudHttpReceive1

If your browser does not display the complete URL, here it is again as a link:
http://workflow.biztalk.net/servicesHttp/YOURUSERNAMEHERE/workflows/
MinimalHttpReceive/instances/YOURGUIDHERE/cloudHttpReceive1

You should see something like this:

Now you need to log in with the username and password (or respective Information Card) that you used to create the workflow type and instance.

Then you should see something like that:

<string xmlns="http://schemas.microsoft.com/2003/10/Serialization/">Hello</string>

Your workflow should have been changed to "Completed" state.

Now what is interesting here is that you do not receive a pure string "Hello" but actually an XML serialization representation of the object string with content "Hello".

Sending to CloudHttpReceive programmatically

Ok, but now how can you do this programmatically? As you might realize, the challenge is the need to "log in". Unfortunately you cannot just use NetworkCredentials to log in but need to make a little detour.

At first you need to retrieve a token for logging in. You can find an example how to do it in this sample: Program Files\Microsoft BizTalk Services SDK\Samples\Workflow\ExploringFeatures\CreateWorkflowAPIs in Program.cs method GetTokenGrantingToken.

I took the liberty of modifying the method slightly and to remove any dependency to the SDK:

static string GetTokenGrantingToken(string userName, string password)
{
    string tokenUrl = string.Format(
        "https://{0}/issuetoken.aspx?u={1}&p={2}",
        "identity.biztalk.net",
        userName,
        password);
 
    HttpWebRequest tokenRequest = (HttpWebRequest)WebRequest.Create(tokenUrl);
    HttpWebResponse tokenResponse = (HttpWebResponse)tokenRequest.GetResponse();
 
    using (Stream responseStream = tokenResponse.GetResponseStream())
    {
        byte[] tokenBody = new byte[500];
        int tokenBodyLength = responseStream.Read(tokenBody, 0, 500);
        return Encoding.UTF8.GetString(tokenBody, 0, tokenBodyLength);
    }
}

It is pretty straightforward. Basically it is a simple HTTPS request to this URL:

https://identity.biztalk.net/issuetoken.aspx?u=YOURUSERNAME&p=YOURPASSWORD

Now, the string that you received represents your token and you need to attach that as a header of type "X-MS-Identity-Token" to your WebHttpRequest you want to send to your workflow instance.

request.Headers.Add("X-MS-Identity-Token", token);

This is the code-snipped for a method encapsulating the whole request:

static string CallHttpReceiveActivity(
                    string requestBody, string username, string token,
                    string workflowTypeName, string activityName,
                    string instanceId)
{
 
    Uri address = new Uri(@"http://workflow.biztalk.net/servicesHttp/"
                + username + "/workflows/" + workflowTypeName +
                "/instances/" + instanceId + "/" + activityName);
    HttpWebRequest request = (HttpWebRequest)HttpWebRequest.Create(address);
    //this adds the retrieved token as a header
    request.Headers.Add("X-MS-Identity-Token", token);
    request.Method = "POST";
    request.ContentType = "text/plain";
    //send the body
    byte[] requestBodyBytes = Encoding.UTF8.GetBytes(requestBody);
    request.ContentLength = requestBodyBytes.Length;
    using (Stream requestStream = request.GetRequestStream())
    {
        requestStream.Write(requestBodyBytes, 0, requestBodyBytes.Length);
        requestStream.Flush();
    }
 
    HttpWebResponse response = (HttpWebResponse)request.GetResponse();
    using (Stream responseStream = response.GetResponseStream())
    {
 
        using (StreamReader reader = new StreamReader(responseStream,
                                                      Encoding.UTF8))
        {
            return reader.ReadToEnd();
        }
    }
}

You can combine both like this:

static string CallHttpReceiveActivityWithLogin(
                    string requestBody, string username, string password,
                    string workflowTypeName, string activityName,
                    string instanceId)
{
    string token = GetTokenGrantingToken(username, password);
    return CallHttpReceiveActivity(
                            requestBody, username, token,
                            workflowTypeName, activityName,
                            instanceId);
}

And an example call to the same workflow instance that we accessed above through the browser would be:

string userName = "YOURUSERNAME";
string password = "YOURPASSWORD";
string workflowTypeName = "MinimalHttpReceive";
string activityName = "cloudHttpReceive1";
string instanceId = "7bf7a7c4-82f5-4935-9c03-62ba1e7991aa";//YOUR GUID HERE INSTEAD
string requestBody="Text to send to cloud";
string result = CallHttpReceiveActivityWithLogin(
                        requestBody, userName, password,
                        workflowTypeName, activityName,
                        instanceId);

For the sake of completeness here the complete code together:

using System;
using System.Text;
using System.Net;
using System.IO;
 
namespace SendToHttpReceive
{
    class Program
    {
        static void Main(string[] args)
        {
 
            string userName = "YOURUSERNAME";
            string password = "YOURPASSWORD";
            string workflowTypeName = "MinimalHttpReceive";
            string activityName = "cloudHttpReceive1";
            string instanceId = "7bf7a7c4-82f5-4935-9c03-62ba1e7991aa";//YOUR GUID HERE INSTEAD
            string requestBody="Text to send to cloud";
            string result = CallHttpReceiveActivityWithLogin(
                                    requestBody, userName, password,
                                    workflowTypeName, activityName,
                                    instanceId);
            Console.WriteLine(result);
            Console.ReadLine();
        }
 
 
        static string CallHttpReceiveActivityWithLogin(
                            string requestBody, string username, string password,
                            string workflowTypeName, string activityName,
                            string instanceId)
        {
            string token = GetTokenGrantingToken(username, password);
            return CallHttpReceiveActivity(
                                    requestBody, username, token,
                                    workflowTypeName, activityName,
                                    instanceId);
        }
 
        static string GetTokenGrantingToken(string userName, string password)
        {
            string tokenUrl = string.Format(
                "https://{0}/issuetoken.aspx?u={1}&p={2}",
                "identity.biztalk.net",
                userName,
                password);
 
            HttpWebRequest tokenRequest = (HttpWebRequest)WebRequest.Create(tokenUrl);
            HttpWebResponse tokenResponse = (HttpWebResponse)tokenRequest.GetResponse();
 
            using (Stream responseStream = tokenResponse.GetResponseStream())
            {
                byte[] tokenBody = new byte[500];
                int tokenBodyLength = responseStream.Read(tokenBody, 0, 500);
                return Encoding.UTF8.GetString(tokenBody, 0, tokenBodyLength);
            }
        }
 
 
 
        static string CallHttpReceiveActivity(
                            string requestBody, string username, string token,
                            string workflowTypeName, string activityName,
                            string instanceId)
        {
 
            Uri address = new Uri(@"http://workflow.biztalk.net/servicesHttp/"
                        + username + "/workflows/" + workflowTypeName +
                        "/instances/" + instanceId + "/" + activityName);
            HttpWebRequest request = (HttpWebRequest)HttpWebRequest.Create(address);
            //this adds the retrieved token as a header
            request.Headers.Add("X-MS-Identity-Token", token);
            request.Method = "POST";
            request.ContentType = "text/plain";
            //send the body
            byte[] requestBodyBytes = Encoding.UTF8.GetBytes(requestBody);
            request.ContentLength = requestBodyBytes.Length;
            using (Stream requestStream = request.GetRequestStream())
            {
                requestStream.Write(requestBodyBytes, 0, requestBodyBytes.Length);
                requestStream.Flush();
            }
 
            HttpWebResponse response = (HttpWebResponse)request.GetResponse();
            using (Stream responseStream = response.GetResponseStream())
            {
 
                using (StreamReader reader = new StreamReader(responseStream,
                                                              Encoding.UTF8))
                {
                    return reader.ReadToEnd();
                }
            }
        }
    }
}

Running that against a running workflow instance will (not surprisingly) result in this output:

In a future post I will try to show an "end-to-end"-demo that actually integrates a lot of what was shown previously and achieves bidirectional communication with a service in the cloud and has your workflow doing something that the service requests.

Codename "Dublin" - Microsoft's Distributed Application Server

aerben — Wed, 17 Sep 2008 18:01:44 GMT

(German version below / deutsche Version weiter unten)

I did not find blog entries about this elsewhere, so here we go. Disclaimer: Nobody shared this information actively with me, and no confidential information was leaked to me, I happened to find it in public sources and derived my conclusion:

It seems that Microsoft's SOA/BPM strategy has found another codename complementing "OSLO". While OSLO focuses more on the integrated and system-wide modeling experience, the codename "DUBLIN" stands for the Distributed Application Server.

Previously the Distributed Application Server was thought to be part of the "wave of OSLO related technologies". I conclude that this means that the product roadmap is maturing.

Welcome new codename :)

(German version/ Deutsche Version)

Da ich sonst keine Blogeinträge hierüber gefunden habe. Diese Information wurde mir weder in irgendeiner Form aktiv zugetragen, und es wurde mir auch keine vertrauliche Information mitgeteilt, sondern ich habe dies aus öffentlich zugänglichen Quellen und dann meine eigenen Schlüsse gezogen:

Es scheint, dass die SOA/BPM-Strategie von Microsoft einen neuen Codenamen gefunden hat, der "OSLO" ergänzen soll. Während OSLO mehr auf die integrierte und systemweite Modellierungsbotschaft abzielt, steht der Codename "DUBLIN" für den Distributed Application Server.

Vorher hat man über den Distributed Application Server meist nur als Teil der Welle der OSLO-relevanten Technologien gesprochen. Ich schließe daraus, dass die Produkt-Roadmap deutlich gereift ist.

Willkommen neuer Codename :)

Clouding the flow of work / BizTalk Workflow Services Intro

aerben — Tue, 05 Aug 2008 10:44:00 GMT

(German version maybe coming later / deutsche Version folgt eventuell später)

http://workflow.biztalk.net now offers a CTP of BizTalk Workflow Services. Let's look at what that means.

First you should download the latest version of the SDK. Right now this is the file "BizTalk Services SDK Setup 0.12.185.2.exe". Please note that the availability of this site and all sub-sites of biztalk.net is at present not reliable at all. It can be taken down temporarily or even for extended periods of time. Please note that the information in this article is based on a very early pre-release version of something that might become a product. So, by the time you read it, this information may be outdated and plainly wrong.

If you do not have an account for BizTalk Services yet, now is the time to create one. Vista users, I recommend creating an information card. When setting a username/password. I also recommend not setting a password that you really want to be secure. Reason: There will be things like deployment samples where the password will be visible.

Assuming you did that, let's look at the SDK:

To actually see what is happening in the samples, you have to start another sample in
Program Files\Microsoft BizTalk Services SDK\Samples\Communication\ExploringFeatures\ConnectionModes\Multicast. This is the place where you will receive a friendly "Hello" from your workflow via the Internet Service Bus (ISB). Use "watchdog" as your chat session name.

In Program Files\Microsoft BizTalk Services SDK\Samples\Workflow\GettingStarted, you can find a definition of a simple "Cloud" Workflow together with rules.

To get started really quickly, you can look at

Program Files\Microsoft BizTalk Services SDK\Samples\Workflow\ExploringFeatures\CreateWorkflowAPIs.

This sample will, when you start it, ask for your credentials and upload a simple workflow to your BizTalk Services account.

I was a little paranoid, so I blanked out the password (now you know why you should not use a relevant password that you use elsewhere, since you might show this sample to someone and bang - there goes your password) and even the authentication token (even though the latter should not really be necessary... but you never know :) ). When doing that, leave it running for a bit before doing "Press any key to terminate workflow instance".

What should happen? Your workflow will start and will try to send a HTTP request to http://www.microsoft.com. If the HTTP-request status is less than 400, then it will send a message to the ISB (to "your" session) that it can reach the Microsoft website. If the site is not responding, then you will receive this information via ISB. The workflow will repeat this procedure every 30 seconds.

Look at the output of your MulticastSample:

(Again, paranoid me did not want to disclose the chat-name right now)

When setting it up, you should see something like that:

You can also create / edit your workflows online without using Visual Studio. No designer support though right now. So, let's edit this. First click on the line with the name of your workflow type ("mywatchdog" in this case). It will be marked in the browser and then click on "Edit".

(Note that "Add New" is not much different other than that you have to also specify a name for your new workflow type)

You see that only two tabs are present: Xoml and Rules. This means that the only thing that is uploaded are the XAML (.xoml) and including the rules definitions of your workflow. With other words - no code-behind/developer defined partial C# classes!

Typically you would just copy/paste your relevant XAML (XOML) and rules here.

In "Type Management" you can also "Create Instances". Doing that will add an instance to the "Manage Instance" page:

You could start an instance (if it is in a startable state) by selecting it and then clicking "Start". Note that when you see an instance that displays "Terminated" and the termination was because of an exception, then you can actually click on the link behind the word "Terminated" to get the top-level exception that caused the Workflow to terminate.

But what can you actually do with the Workflow Services right now? Remember, you are running them in the "cloud". And if you could do just anything, this could result in the whole platform getting vulnerable. So what Microsoft did was, to limit the types of activities you can run in the "cloud".

Right now those activities are:

CloudDelay
CloudHttpReceive
CloudHttpSend
CloudIfElse (and CloudIfElseBranch)
CloudSequence
CloudServiceBusSend
CloudWhile

This is a severely limiting subset of Workflow activities.

If you do not limit yourself to those activities, e.g. by adding something like

to your XOML, you will get "The workflow failed validation" when trying to save your changes.´

Now let's look at the workflow again in Visual Studio. I use Visual Studio 2008, the samples are made for Visual Studio 2005 with the Visual Studio 2005 Extensions for .Net Framework 3.0 (Windows Workflow Foundation).

We are working with Program Files\Microsoft BizTalk Services SDK\Samples\Workflow\GettingStarted now again.

Your workflow should look like this:

Open in the Menu Tools / Choose Toolbox Items... or select Choose Items... directly in the context-menu when right-clicking in the toolbox. In this window go to the tab "Activities".

The click "Browse..." and select the DLL "System.ServiceBus.Workflow.dll" in Program Files\Microsoft BizTalk Services SDK\Assemblies and choose "OK".

You should see something like that.

Select "OK" again and your toolbox should see some new activities at the bottom of the list.

And your project should look similar to this.

Now you are basically ready to build your own cloud-hosted workflows.

I think it is worth noting, that the workflow is at the root-level still a regular SequentialWorkflowActivity as seen in the code (which is however not used in the cloud but still it is still there in the project file. Do not put logic here. :) ):

public partial class Workflow1 : SequentialWorkflowActivity
{
}

and more importantly in the root node of the XAML:

<SequentialWorkflowActivity x:Class="WorkflowProject1.Workflow1" x:Name="Workflow1" xmlns:ns0="clr-namespace:System.ServiceBus.Workflow;Assembly=System.ServiceBus.Workflow, Version=0.12.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/workflow">

When looking at the rules, you will further notice that the rules have nothing cloud-specific besides of accessing the cloud-specific activities.

The next posts will look closer at the new activities and at some of the inner workings of the samples, we will further try to stretch what can be done.

daenet wins German innovation prize 2008 for SOA / daenet gewinnt den Innovationspreis 2008 für die Kategorie SOA

aerben — Thu, 06 Mar 2008 15:41:43 GMT

(German version below / deutsche Version weiter unten)

Now I can finally talk about it. Our daenet SOA Suite now has officially been awarded with an important prize. "http://www.imittelstand.de/auszeichnungen/innovationspreis2008/kategoriesieger/soa.html" The "Innovationspreis 2008" (innovation prize 2008) specifically considers the needs of the so called "Mittelstand". The "Mittelstand" is the engine and the driver of the economy in Germany. Even though it means roughly "medium sized businesses", many of them are international, globalized companies with 10000 employees and more that in the US most often would be called enterprises. What is special about them is the down-to-earth "can-do" attitude and the need for fast return of investment (ROI) coupled with a high level of innovation.

So we are very proud that our SOA solution is being recognized as the BEST SOA solution for the most important customers that possibly could exist for all the right reasons.

The jury was huge and impressive, both academically apt and still with the mindset of delivering value is the key differentiator in life.

Why did we target the needs of the "Mittelstand"? Because we see that a lot of SOA approaches are far too complex for most companies and therefore too much being talked about and too little is being actually done. Being suitable for "Mittelstand" in my opinion automatically means being suitable for enterprises with the advantage that you can "scale" the approach down even to the departmental level.

In future posts I will likely talk more about what the daenet SOA Suite can do... until then: just ask me if you are interested.

(German version / deutsche Version)

Nun kann ich endlich darüber sprechen. Unsere daenet SOA Suite wurde offiziell mit einem wichtigen Preis ausgezeichnet. "http://www.imittelstand.de/auszeichnungen/innovationspreis2008/kategoriesieger/soa.html" Der "Innovationspreis 2008" berücksichtigt besonders die Bedürfnisse des sogenannten "Mittelstand". Der Mittelstand ist der Motor der deutschen Wirtschaft. Auch wenn es eigentlich "Mittelgroße Firmen" bedeutet, sind viele dieser in Wirklichkeit internationale, globalisierte Firmen mit 10000 und mehr Angestellten, die in den USA oft "enterprises" genannt würden. Besonders am Mittelstand ist die Bodenständigkeit und die "wir machen's möglich"-Einstellung, welche aber mit der Notwendigkeit einhergeht, einen schnellen Investitionsrückfluss (ROI) zu erreichen, der mit einem hohen Innovationsbedarf und hoher Innovationskraft gekoppelt ist.

Also sind wir sehr stolz, dass unsere SOA Lösung als die BESTE SOA Lösung für diese Kundenzielgruppe anerkannt wurde, welche sicherlich aus all den richtigen Gründen heraus gesehen die wichtigste Kundenzielgruppe überhaupt ist.

Die Jury selbst war groß und beeindruckend: Akademisch qualifiziert und gleichzeitig mit dem Bewusstsein, dass "Werte schaffen" der Hauptunterscheidungsgrund im Leben ist.

Warum haben wir speziell die Bedürfnisse des "Mittelstand" adressiert? Weil wir sehen, dass viele SOA Ansätze bei weitem zu komplex für die meisten Firmen sind und deshalb zu viel geredet und zu wenig gehandelt wird. Wenn eine Lösung für den Mittelstand geeignet ist, heisst das meiner Meinung nach, dass sie automatisch auch für Konzerne geeignet ist aber den Vorteil mitbringt, nach "unten" skalierbar zu sein, also selbst auf Abteilungsebene einsetzbar zu sein.

In künftigen Artikeln werde ich wahrscheinlich mehr darüber schreiben, was die daenet SOA Suite alles kann... bis dahin: Bitte fragen Sie mich, wenn Sie Interesse haben!

Huge surprise today around daenet and SOA / Heute große Überraschung rund um daenet und SOA

aerben — Thu, 06 Mar 2008 12:35:18 GMT

(German version below / deutsche Version weiter unten)

Expect a huge surprise today. I am waiting for the official press info to leak out so nobody is upset with me that I talk about it. What I can tell you is that it is around daenet and SOA. It will be one more reason to talk to us when it comes to this topic :)

(German version / deutsche Version)

Heute kommt noch eine große Überraschung auf uns zu. Ich warte noch darauf, dass eine offizielle Presseinfo raussickert, so dass niemand sauer auf mich sein kann, dass ich darüber rede. Was ich jetzt schon sagen kann ist, dass es um daenet und SOA geht. Es wird ein weiterer Grund sein, mit uns über dieses Themengebiet zu sprechen :)

German/deutscher BizTalk RFID Webcast as part of the German/als Teil des deutschen BizTalk Server 2006 R2 Launch

aerben — Thu, 15 Nov 2007 18:49:00 GMT

(German version below, English version is very minimal since this post is targeted to the German audience)

On November 15, 2007, I presented BizTalk RFID in a webcast format to the German audience in German as part of the launch of BizTalk 2006 R2.

(German version)

Am 15. November 2007 durfte ich BizTalk RFID der deutschen Community im Rahmen des deutschen Microsoft BizTalk Server 2006 R2 Launch-Events vorführen.

Anbei stelle ich gerne allen die Slides hier zum Download zur Verfügung. Für Code-Beispiele und ähnliches möchte ich auf mein vorheriges Blog-Post zur TechEd Developers 2007 in Barcelona verweisen.

Leider war ich durch eine starke Erkältung und damit zusammenhängendem Doping, um den Webcast überhaupt durchführen zu können schwer "gehandicappt" und ich bitte die Teilnehmer um Nachsicht. Gerne spreche ich mit Interessierten im Nachgang über BizTalk RFID.

Der Webcast war leider nur eine Stunde lang und hatte den Anspruch, die technischen Aspekte einem gemischtem Publikum etwas näher zu bringen. Dies ist ein schwieriges Unterfangen, da das Produkt zu umfangreich und die Interessengruppen zu verschieden sind, um es allen recht zu machen. Ich hoffe, dass dennoch ein erstes Gefühl dafür entstand, was man mit Biztalk RFID erreichen kann, über viele Bereiche musste ich leider sehr schnell rüberfliegen und sehr oberflächlich bleiben. Wir wollten dennoch bewusst vermeiden, nur einen Feature-Rundflug mit Marketing-Slides über das Produkt zu machen, sondern zumindest einen kurzen Einblick in das "doing" geben, daher gab es in der Veranstaltung zum Beispiel kurz "Code" zu sehen und auch ein kommendes "SOA-Integrations Pattern", der Sensor Service Bus, wurde kurz vorgestellt.

Nach meiner Meinung wäre es sinnvoll, künftig mehrere Veranstaltungen zum Thema durchzuführen, welche sich beispielsweise wie folgt aufgliedern könnten:

Zielgruppe	Beschreibung
Alle	Allgemeiner Überblick ohne Entwicklung usw – im Gegensatz zu dem „alles in einer Stunde“
Entscheidungsträger/BDMs (Business Decision Maker), Business Analysten, Solution-Architekten	business value: typische Business Szenarien und wie man diese mit BizTalk RFID lösen kann, welchen Business Value BizTalk RFID bietet (z.B. Supply Chain, Asset Management usw.)
Software-Architekten, Entwickler	Architektonische und Integrations Patterns mit BizTalk RFID (vielleicht mit Vertiefung von Sensor Service Bus in gesonderter Session)
Softwareentwickler	Einführung in die synchronen BizTalk RFID APIs
Softwareentwickler	Einführung in die asynchrone BizTalk RFID Entwicklung
Softwareentwickler	Einführung in die DSPI Entwicklung
Architekten, Softwareentwickler	Best Practices, Business Rule Engine, Logging, Performance Aspekte... (lässt sich beliebig ausweiten)
Administratoren, IT-Pros	BizTalk RFID für den IT Pro
Entscheidungsträger/BDMs (Business Decision Maker)	Kundenstories
Alle	Workshops - mit Einbeziehung von Hardware

BizTalk RFID@Work at TechEd EMEA Developers 2007 by daenet

aerben — Thu, 08 Nov 2007 10:55:30 GMT

(German version below)

Today we presented about Microsoft BizTalk RFID at the TechEd EMEA Developers conference in Barcelona. Some content was similar to the presentation we did last week at the Microsoft SOA&Business Process Management conference in Redmond, but since the audience at TechEd is more developer centric, we prioritized on showing demos and code. You can find our slide deck here: SBP306_Microsoft BizTalk RFID @ Work.zip. This slide deck will also contain additional material not presented in the "Backup slides" section at the end.

Please check out Damir's blog posts to get the bits we talked about:

(German version)

Heute präsentierten wir über Microsoft BizTalk RFID auf der TechEd EMEA Developers Konferenz in Barcelona. Naturgemäß ist einiger Inhalt ähnlich zu dem, was wir letzte Woche auf der Microsoft SOA&Business Process Management conference in Redmond vortrugen. Da die TechEd Developer-fokussiert ist, haben wir den Schwerpunkt auf Demos und Programmierung gesetzt. Das Slide-Deck ist hier verfügbar: SBP306_Microsoft BizTalk RFID @ Work.zip. In der PowerPoint-Datei gibt es zusätzliches Material welches wir leider nicht vorstellen konnten im "Backup slides"-Bereich.

Damir hat in verschiedenen Posts die relevanten vorgestellten Beispiele veröffentlicht.

Presentation at the / Präsentation auf der Microsoft SOA & Business Process Conference 2007

aerben — Fri, 02 Nov 2007 09:18:00 GMT

(German version below)

Damir and I presented at the Microsoft SOA & Business Process Conference 2007 at the Microsoft Conference Center in Redmond.
We talked about interesting topics surrounding BizTalk RFID, a completely new component of BizTalk 2006 R2, and a new concept named "Sensor Service Bus". It was a relatively technical session, but demonstrates business value in an RTI (Reusable Transport Item) scenario.
If you are interested, we invite you to check out our slide-deck.
We are happy about follow-ups, specifically regarding the "Sensor Service Bus", please do not hesitate to contact us.

(German version / deutsche version)

Damir und ich präsentierten auf der Microsoft SOA & Business Process Conference 2007 im Microsoft Conference Center in Redmond.

Wir stellten interessante Themen rund um BizTalk RFID, eine komplett neue Komponente von Microsoft BizTalk Server 2006 R2, und um das neue Konzept des "Sensor Service Bus" vor. Es handelt sich um eine relativ technische Session, dennoch wird Mehrwert für Kunden in einem RTI (Reusable Transport Items - wiederverwertbare Transportmaterialien) - Szenario demonstriert.
Wir laden interessierte Leser herzlich ein, unser Slide-Deck hierzu anzuschauen.

Wir freuen uns über Folgegespräche, besonders bezogen auf den "Sensor Service Bus". Zögern Sie nicht, uns zu kontaktieren.