Azure : BizTalk Service will come soon

Hi everybody, Mick’s Breeze announce a great thing on his blog. Azure will sooner have BizTalk as an application service. Its name simply BizTalk Service. For the moment only customer who joined the preview programs can use it. I hope they deliver it as soon as possible :

biztalk service

What can we do with this service,  Mick said :

  •  a RESTful endpoint
  •  one or more transforms
  •  a RESTful exit point (or it could be a request , response)

For more information please click here

Publicités

Impersonation vs Delegation

In WCF security, it exist two ways to specify how to access to a tiers resources. It called impersonation and delegation.

Impersonation

Impersonation permit to the service to use the client credential to access to another resource which is located on the same machine

Delegation

delegation permit to the service to use the client credential to access to another resource which could be located anywhere on the network. The only one prerequesite is that the resource must be on the same AD

To summarize :

Impersonation level Service can perform cross-process delegation Service can perform cross-machine delegation
Identification (no impersonation) No No
Impersonation Yes No
Delegation Yes Yes

For more information you can check that in the MSDN :

http://msdn.microsoft.com/en-us/library/ff647248.aspx#ImpersonationDelegation2

http://msdn.microsoft.com/en-us/library/ms730088.aspx

cannot resolve imported service

When you have multiple called orchestration stage in different BizTalk project, you can get this error : « cannot resolve imported service »

It’s an old bug from visual studio 2005. Let me explain you when this bug appears :

you have 3 orchestrations A, B, C

  • A references B
  • B references C

When you compile you obtain the error cannot resolve imported service.

To clear this issue just add C in A’s references