BizTalk Server 2013 (Beta) – Help page

BizTalk Server 2013 (Beta) – Help page

I have recently been pointed towards a help page written by Microsoft with a wealth of information regarding BizTalk Server 2013 which I was unaware of (thanks to Kundan Karma in the LinkedIn BizTalk Elite group) – http://msdn.microsoft.com/en-US/library/jj248691(v=bts.80).aspx What with all us bloggers writing about the release of BizTalk 2013 Beta I found that the […]
Blog Post by: Johann

BizTalk Innovation Event London UK!

So people, it’s happening in the UK. The BizTalk Crew (SaravanaKumar, Nino Crudele, Steef-JanWiggers, Sandro Pereira and me, TordGlad Nordahl) are presenting all new presentation in London January 16th 2013! We have all seen that BizTalk2013Beta has been released and I will focus on the new things in BizTalk 2013, Windows Server 2012 and SQL […]
Blog Post by: Tord Glad Nordahl

Dynamic send port improvements in BizTalk Server 2013

Dynamic send port improvements in BizTalk Server 2013

One of the big problems with BizTalk Server 2010 and earlier is that it isn’t possible to change which host you want your dynamic send port to run on. This is now possible in BizTalk Server 2013 and this will show you how to do it.

I will just do a very simple sample where I receive a file and send it to a hardcodet destination. In really life this might depend on the message or the content of the message or it can be something you look up in a database.

So first the orchestration:

Where the DySP port is set to have a dynamic binding. You configure the DySP port inside the Expression_1 shape like this:

And now you are ready to build and deploy. Once you have deployed the solution it is time to configure the send handler for you dynamic send port. You open you send port, where you see a button that lets you configure your send handler:
After you click the Configure button in the screen above you will be able to configure on which host that you want your messages to be send. There an option for every adapter that you have installed in your environment as in first on runtime that we know which adapter to use:
This feature alone will be enough to upgrade to BizTalk Server 2013 if you are using Dynamic send ports a lot as you will have a lot more control over where your workload gets executed. 
Random posts:


Welcome BizTalk 2013 beta

Welcome BizTalk 2013 beta

Microsoft recently released the beta release of BizTalk Server 2013. The first good news is that the initial name (BizTalk 2010 R2) has changed to BizTalk 2013, indicating it will be a major release, providing longer support to our customers! The beta contains the following capabilities: Integration with Windows Azure Service Bus – these are […]
Blog Post by: DipeshA

BizTalk Server 2013 BETA-Window 8 Configuration issues

In the last post BizTalk Server 2013 BETA I mentioned BizTalk Server 2013 beta will allow me install the software on a Windows 8 laptop and continue my BizTalk development, without getting stuck in the old OS. Thanks to the platform alignment in 2013. There were few comments on the blog asking whether BTS 2013 […]

The post BizTalk Server 2013 BETA–Window 8 Configuration issues appeared first on BizTalk360 Blog.

Blog Post by: Saravana Kumar

Avoid sending a partially written e-mail | Eviter d’envoyer un e-mail en cours d’écriture

I regularly use the following trick while writing an e-mail so that I don’t send it by error before it is fully written: J’utilise r%u00e9guli%u00e8rement le truc suivant lorsque j’%u00e9cris des e-mails, de fa%u00e7on %u00e0 ne pas envoyer par erreur un message encore en cours de r%u00e9daction et que je n’ai pas encore relu:
I put a user called “attendre” (this means “wait” in French). Je mets un utilisateur “attendre” en copie.
If by mistake, I press the send button before removing attendre, the e-mail doesn’t get sent because attendre does not exist, and it is not a valid address either. Si par erreur, j’appuie sur le bouton d’envoi avant d’avoir supprim%u00e9 attendre, l’e-mail ne part pas car attendre n’existe pas, et ne correspond pas non plus %u00e0 une adresse e-mail valide.
I use the trick with Outlook but I suppose this would work with most e-mail clients as well. J’utilise ce truc avec Outlook mais je suppose que cela fonctionnerait %u00e9galement avec la plupart des clients de messagerie %u00e9galement.

Benjamin

Blog Post by: Benjamin GUINEBERTIERE