Blog

Blog2016-11-26T18:23:46+00:00
1505, 2014

Automating Neuron ESB install

By |maj 15th, 2014|Categories: Integration, Neuron ESB|0 Comments

Installing Neuron ESB is very easy. You run setup.exe and click next a couple of times and once installed you create the Neuron SQL-database from the Neuron ESB Explorer. Finally you point it to the folder containing the ESBConfiguration XML files and you are up and running. But this can also be fully automated and we chose to do so using PowerShell. We have [...]

1404, 2014

Dynamic web service routing in Neuron ESB

By |april 14th, 2014|Categories: Integration, Neuron ESB|0 Comments

When you are developing ESB solutions, you very often need to perform som sort of dynamic service routing. In this case we had 10 applications, SharePoint, BizTalk, xRm, .net and custom legacy applications, all calling each other. In total approximatly 160 web services and each application needed a more or less complete list of all services, WCF configurations and their URLs. Deploying was always [...]

1404, 2014

Dynamically generating a WCF proxy without using a .config file

By |april 14th, 2014|Categories: .Net|0 Comments

Recently we had to create a WCF proxy with a common datamodel and serviceinterface, which had to be hosted in several applications (SharePoint, custom .Net services, xRm etc.). To avoid messing around with various .config-files, we chose to create the WCF-proxy and configuration in code. And all contained in a single project/DLL. This might come handy some other time and I am posting the [...]

1302, 2014

State in Neuron ESB (context.Properties and context.State)

By |februar 13th, 2014|Categories: Integration, Neuron ESB|0 Comments

When you work with processes in Neuron ESB, you quite often need to store some kind of state. There are several ways to do this and in particular it is important to know the difference between context.Properties and context.State. 1. Use Push / Pop The most simple way is to use the Push with the message you need to store and retrieve it later [...]

908, 2013

BizTalk Art ?

By |august 9th, 2013|Categories: BizTalk, Integration|0 Comments

The following BizTalk orchestration is wrong for more reasons that I can count. Basically it is a wrapper, which ensures that we only have a specific number of sub orchestrations running in parallel at a given time to avoid crashing a subsystem. The obviuos question is, why not just create a seperate host and throttle it appropriatly? That is one of the main reasons [...]

2811, 2012

Automatic testing of WCF Receive locations and send ports

By |november 28th, 2012|Categories: BizTalk|0 Comments

We are using the Powershell BizTalk Adapter when deploying our BizTalk solution. And since we depend on a lot of external services and expose som WCF-services as well, we might as well do a quick test to see if the respond properly. Even a simple check to see if the URL responds with HTTP 200-OK will catch a lot of configuration and setup related [...]