Search results matching tag 'WCF'

Distributed Systems and Service Patterns Session – University of Applied Sciences Frankfurt am Main

ddobric — Sat, 13 Apr 2013 08:13:22 GMT

Here is the recap of the session Distributed Systems and Service Patterns.

Cumulative Updates for Workflow Manager, Service Bus (SharePoint 2013 – Workflow Engine)

ddobric — Thu, 28 Feb 2013 10:23:12 GMT

The first Cumulative Update for Workflow Manager and Service Bus or formally known SharePoint workflow is online. which actually includes Suspend/Resume of instances support. (It will also be available via WebPI soon).

WF Manager:

KB article (KB2799754): here

Download page: here

Service Bus:

KB article (KB2799752): here

Download page: here

Setting up authorization rights on Service Bus entities

ddobric — Thu, 31 Jan 2013 06:18:00 GMT

Service Bus for Windows Server provides two ways to setup access rights to its entities (queues/topics). Since the Windows Azure Access Control Service (ACS) is not available on Windows Server, the Service Bus for Windows Server includes a simple Service Bus Security Token Service (SBSTS). The SBSTS integrates with the Windows security model, and silently issues a Simple Web Tokens (SWTs) based on Windows identities (for domain users, or roles for domain groups).

If you setup the rights on the namespace-level the user will automatically get all permissions: Manage, Listen and Send. Additionally rights can be managed at entity level more precisely. When setting up rights on that level you have to deal with two different types of claims. Currently there are two types of claims supported. First type is used when the right is setup for domain user, and second one when the right is setup to domain group.
In general, both types can be described by short name and full name. Below are the supported types:

Domain Group claim type is called RoleType:

shortname: "role"

fullname: "http://schemas.microsoft.com/ws/2008/06/identity/claims/role"

Domain User Claim Type is called IdentityType:

shortname: "nameidentifier"

fullname: "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier"

For better understanding take a look on following example:

QueueDescription myQueue = new QueueDescription(QueueName);

AuthorizationRule identifierRule = new AllowRule("WorkflowDefaultNamespace","nameidentifier",
"username@yourdomain.com",new List<AccessRights>(){ AccessRights.Listen, AccessRights.Send });

myQueue.Authorization.Add(identifierRule);

AuthorizationRule groupRule = new AllowRule("WorkflowDefaultNamespace","role",groupname@yourdomain.com,
new List<AccessRights>(){ AccessRights.Listen, AccessRights.Send });

myQueue.Authorization.Add(groupRule);

namespaceManager.CreateQueue(myQueue);

This example adds the send and listen rights to one user and one group. Note that that the first argument (issuer name) can be obtained by command-let Get-SbNamespace. Usually this equals to the name of namespace. In my example I used the namespace of the Workflow Manager (“WorkflowDefaultNamespace”).

Following example shows hot enumerate rights:

QueueDescription q = namespaceManager.GetQueue(QueueName);

            var en = q.Authorization.GetEnumerator();

            while (en.MoveNext())
            {
                AuthorizationRule rule = en.Current;

                string rights = "";

                foreach (var r in rule.Rights)
                    rights += r;

Console.WriteLine("type:{0}, value:{1}, rights: {2}", rule.ClaimType, rule.ClaimValue, rights);
}

The official MSDN article which gives a better high-level overview: http://msdn.microsoft.com/en-us/library/windowsazure/jj193003(v=azure.10).aspx

Announcing my Session “Connecting Web Systems” at Advanced Developer Conference 2012

ddobric — Sat, 27 Oct 2012 12:45:15 GMT

If you are professional developer or architect who focus Microsoft technologies, then ADC is the conference of great choice. Internationally recognized and legendary experts will present most popular technology topics.
One of best things at this conference I personally like is “NO MARKETING”. All session content is pure experience with pre-filtered sponsoring and marketing noise.

At the upcoming Advanced Developer Conference 2012 in Germany I will give two session. Here is the first look on agenda for “Connecting Web Systems” session. Because this session is not related to some product, it will focus new peaces of technology at the Microsoft’s development platform. This time I decided to talk about technologies which might dramatically change the web soon. However this might also influence the way how we thing about applications and it will definitely change the architecture of future applications. As Integration MVP in last two years I was involved in some more or less hidden and still not well documented technology areas with focus on WebSockets, SignalR and communication in Web in general.
Content presented in this session is pure result of this work. You are welcome.

Download Service Bus 1.0 and Workflow Manager 1.0 RTM

ddobric — Fri, 19 Oct 2012 21:29:53 GMT

RTM Build of Service Bus and Workflow Manager 1.0 is available for download in Microsoft Download Center: It is up to now still not officially announced in term of marketing drums, but first posts published 1 hour ago by team members are out there. Anyhow the bits which can be downloaded (click on image below) correspond to official RTM. If you are currently using Release Candidate or Beta version I would highly recommend to install new bits, because it fix some major bugs.

Service Bus Documentation: http://msdn.microsoft.com/library/jj193022(Azure.10).aspx
Service Bus Explorer: http://code.msdn.microsoft.com/windowsazure/Service-Bus-Explorer-f2abca5a
Service Bus Client (NuGet): http://nuget.org/packages/ServiceBus.v1_0
Release Notes:http://msdn.microsoft.com/en-us/library/jj203548(v=azure.10).aspx
All Service Bus Examples: http://code.msdn.microsoft.com/windowsazure/site/search?f%5B0%5D.Type=Topic&f%5B0%5D.Value=Service%20Bus
Converting Service Bus application Service Bus 1.0 (OnPrem Service Bus: http://msdn.microsoft.com/en-US/library/jj218331(v=azure.10).aspx

Workflow Manager documentation: http://msdn.microsoft.com/library/jj193528

Workflow Manager Samples:
http://msdn.microsoft.com/en-us/library/jj193482(v=azure.10).aspx
http://code.msdn.microsoft.com/site/search?f%5B0%5D.Type=User&f%5B0%5D.Value=Dave%20Cliffe%20-%20MSFT

Quick Start:
German:http://daenet.de/de/stream.daenet?sta=3&pid=179&kat=62
English: http://daenet.eu/eu/stream.daenet?sta=3&pid=180&kat=3

Service Bus and Workflow Manager RTM download and useful resource.

Visual Studio 2012 does not create Service reference properly

ddobric — Fri, 05 Oct 2012 10:20:13 GMT

When you add service reference you might figure out that proxy source code is empty:

//------------------------------------------------------------------------------
// <auto-generated>
//     This code was generated by a tool.
//     Runtime Version:4.0.30319.17929
//
//     Changes to this file may cause incorrect behavior and will be lost if
//     the code is regenerated.
// </auto-generated>
//------------------------------------------------------------------------------

If you take a look under warnings after executing of Update Service Reference you will figure out following message (which is in fact a critical error):

Warning 7 Custom tool warning: Cannot import wsdl:port
Detail: There was an error importing a wsdl:binding that the wsdl:port is dependent on.
XPath to wsdl:binding: //wsdl:definitions[@targetNamespace='http://tempuri.org/']/wsdl:binding[@name='BasicHttpBinding_IXService']
XPath to Error Source: //wsdl:definitions[@targetNamespace='http://tempuri.org/']/wsdl:service[@name='ControlOrderService']/wsdl:port[@name='BasicHttpBinding_IXService']

This problem occurs only if you generate references with “Reuse Types in referenced assemblies”.

To workaround the problem, remove reference to Newtonsoft.Json.dll update service references manually and then add the reference to Newtonsoft.Json.dll again.

Few facts about Windows Azure Mobile Services

ddobric — Thu, 27 Sep 2012 10:46:00 GMT

Insert big amount of data is not the best option

If you want to insert a bigger amount of data the Mobile Services SDK is not the best way to do that. Following code snippet shows how to insert 1000 records in a simple table.
By using WLAN with approximately 15 MBit upload rate we can expect 240-260 ms per insert-record. If you need higher rate the solution is to build application (backend or desktop on – system32)
and to insert records directly in the table.

var tbl = App.MobileService.GetTable<Movie>();

Stopwatch w = new Stopwatch();

for (int i = 0; i < 1000; i++)
{
await tbl.InsertAsync(new Movie() { Title = "Otac na sluzbenom putu" + i.ToString(), Description = "Ma dosta ga je ba" + i.ToString(), ChannelUrl = App.CurrentChannel.Uri });
}

Btw. 1000 records is never ever a big amount :)

Reading is relative fast

In contract to insert operation reading is a bit faster. By using WLAN with approximately 50MBit download rate, we can achieve 2ms per records.

List<Movie> movies = await tbl.Where(i => i.Title.StartsWith("Otac")).Take(1000).ToListAsync();

In this test the table has contained up to 2000 records.

You can get maximum 1000 records per requests

You cannot retrieve any number of records from table. The maximum number of records which can be retrieved is 1000. If you execute the code below, you will get following exception:
The value of the $top query option cannot exceed 1000. (400 BadRequest - Details: {"code":400,"error":"The value of the $top query option cannot exceed 1000."})

var tbl = App.MobileService.GetTable<Movie>();

List<Movie> movies = await tbl.Where(i => i.Title.StartsWith("Otac")).Take(1500).ToListAsync();

Default number of returned records is 50

If you do not specify the number of records to be retrieved, the default number of records is limited to 50. For example, folowing code will retrieve 50 records, although the table contains more than 1000 records.

List<Movie> movies = await tbl.Where(i => i.Title.StartsWith("Otac")).ToListAsync();

How to activate WCF on IIS8 and Windows 8?

ddobric — Mon, 24 Sep 2012 15:03:18 GMT

When you start working with WCF on Windows 8 and IIS8, you might run into following problem.

HTTP Error 404.3 - Not Found

The page you are requesting cannot be served because of the extension configuration. If the page is a script, add a handler. If the file should be downloaded, add a MIME map.

To make this working you have enable (install/activate) Advanced .NET 4.5 Features, which are mostly related to WCF:

Announcing the session at Mobility Day: Windows Azure Mobile Services

ddobric — Mon, 24 Sep 2012 09:59:24 GMT

This year (2012) I will traditionally talk at Mobility Day in Zagreb. As always in context of mobile technologies I will try to share a content related to strong architectural approaches with lot of demos and fun { :) }.

In this session we will talk about some new approaches covered by Windows Azure Mobile services which are mainly related to Windows 8, for now at least.
This sessions will focus development of Windows 8 Store Applications which need to expand the logic out of WinRT boundary. I will show how Mobility Services (new thing of Business Platform Division)
can simplify such tasks by using of predefined services hosted in Windows Azure.

Hope to see you there :)

ServiceBus Message Broker Service is starting and starting…(Cannot Deploy SPS Workflow)

ddobric — Tue, 18 Sep 2012 05:21:00 GMT

When working with Windows Azure Workflow, Workflow Host Manager or Share Point 2013 Workflow you might experience several problems related to Message Broker Service.

Issues related to broker In SharePoint are manifested through workflow deployment issues. For example, if you try to deploy the workflow you might get following error:

Error 1 Error occurred in deployment step 'Activate Features': System.IO.InvalidDataException: A response was returned that did not come from the workflow service. Status code = 503:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>Service Unavailable</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD>
<BODY><h2>Service Unavailable</h2>
<hr><p>HTTP Error 503. The service is unavailable.</p>

If you are rather Service Bus guy, you will figure out that Broker Service does not start. It is all the time in starting status. In both cases, take a look on status of Windows Fabric Host Service. You will probably notice that this service is not running. If so start it, stop the broker and start the broker again.
If you cannot stop the broker service while starting, got to task manager and kill Microsoft.ServiceBus Message Broker process. Then start the broker service.