A previous post of mine had some sample code on creating BizTalk Server Orchestrations programmatically, opening up template based guidance packages. The sourcecode for the sample can now be found here.
For storing configuration data, Jon Flanders’s SSOAppConfig tool is my preferred answer. On my recent migration from 2004 to 2006, my good buddy discovered that the BizTalk Admin Group and BizTalk User Group are hard-coded into Mr. Flanders’s solution. We tossed around the idea of looking up the values, but weren’t very sure where to get them. I think I have an answer. The registry contains a couple of useful values under
While I’m dreaming, I want to add command line parameters to the tool so that I can script out installs (using Import) and uninstalls (using Delete).
There seems to have been some confusion generated by readers trying to implement dynamic direct bound ports that I wanted to clarify. A dynamic direct bound port is merely a direct bound port whose address is set at runtime. It is not a dynamic send port. Dynamic send ports allow you to determine at runtime which send adapter the message will be routed to which is derived from the prefix of the address of the endpoint you have provided. If you try to set the address of a dynamic send port using the msgbox: prefix you will get a routing exception (transport cannot be resolved) as msgbox: is not an alias for any send adapter.
The ability to modify the address of a direct bound port is only available in BizTalk Server 2006.
Comecei recentemente a aventurar-me na produ%u00e7%u00e3o de screencasts, na peugada das Curtas do Luis Abreu, com conte%u00fado original e em portugu%u00eas. O primeiro tema que escolhi foi BizTalk Server, como se poderia esperar, e gravei j%u00e1 dois v%u00eddeos, o primeiro sobre a arquitectura do produto e o segundo com uma demonstra%u00e7%u00e3o que apresenta o cen%u00e1rio que vou desenvolver e que ilustra a cria%u00e7%u00e3o de schemas e configura%u00e7%u00e3o de portos, entre outros temas.
Todos os v%u00eddeos est%u00e3o e v%u00e3o estar dispon%u00edveis nesta p%u00e1gina, e farei um post de aviso cada vez que publicar um novo.
A m%u00fasica %u00e9 a autoria do meu amigo e colega Hugo Lopes.
Quaisquer coment%u00e1rios e sugest%u00f5es ser%u00e3o bem extremamente bem vindos.
There seems to have been some confusion generated by readers trying to implement dynamic direct bound ports that I wanted to clarify. A dynamic direct bound port is merely a direct bound port whose address is set at runtime. It is not a dynamic send port. Dynamic send ports allow you to determine at runtime which send adapter the message will be routed to which is derived from the prefix of the address of the endpoint you have provided. If you try to set the address of a dynamic send port using the msgbox: prefix you will get a routing exception (transport cannot be resolved) as msgbox: is not an alias for any send adapter.
The ability to modify the address of a direct bound port is only available in BizTalk Server 2006.
Recharge the batteries and look out for that Rabbit 🙂
I’m back from Perth survived the ‘Red-Eye’
Take care,
Mick.
Convoying is one of BizTalk’s real strengths but it has a lot of pitfalls (I’m talking performance, zombies etc). This article is really good at explaining the different patterns used for creating convoys. It also makes some deep dives into how the subscriptions are solved, why zombies are created and how to deal with them.
Even if you feel you […]
I was trying to signup for a service, and I was prompted the following form to fill out.
I’m afraid I’m not human anymore.
Any other human out there who can help me?