So, it has been a very long time since I last blogged here. My day job has been keeping me very busy which is never a bad thing! I'm back now though and after having attended a NAV 2009 technical workshop, I am energised and ready to go.
As I say I have just had the pleasure of attending a Microsoft-run "What's new in NAV 2009 (technical)" workshop. Got some great exposure to NAV 2009 and built on what I had already picked up in CTP3 and CTP4 (there are noticeable differences between these two!!!). The workshop was attended by a number of very experienced and like-minded developers/consultants and we managed to raise a number of interesting questions, which are going to be passed on to the NAV development team. They are coming to report back to us in a future session – so all positive news on that end, and good to be able to feedback to MS directly. NAV 2009 seemed to be very stable during the course which again was very good to see.
The course has however alerted me to the new Service Tier layer, and there still seems to be great confusion about what we are actually getting here... We are told that there is some integration with IIS, however as we demonstrated we could stop the IIS services and yet still run the RTC. We came to the conclusion that NAV must simply be implementing its own proprietary service layer using the IIS components. I'm preparing to pass on some of the things I learnt to my colleagues in the office tomorrow, and so am installing 2009 on a clean Windows XP virtual pc image. Interestingly this image does NOT have IIS installed at all – so what is really going on here? Does anyone have any more info on this, and can tell us exactly what is going on with this service tier. I'm particularly interested on whether this layer is cluster-aware, and how we can scale this model.
I'll continue to post about the things I pick up and any answers that we get back from MS!
Although this post is "some days" old I want to try to provide an answer.
I asume that the web services are built on top of the Windows Communication Foundation (WCF msdn.microsoft.com/.../aa663324.aspx). I come to this conclusion because NAV 2009 requires the .Net Framework 3.5 and the technology is included since .Net 3.0.
WCF Services can be self-hosted, previous .Net Webservices were based on ASP.Net which required the IIS.
WCF is the recommended way to create webservice since its release because the ASP.Net Webservices had some compatibility issues.
I must admit that I have been hearing conflicting stories about the use of IIS (or not). As it is such a new product I expect that everyone is still coming to terms with it. Perhaps someone from Microsoft or the team that put NAV 2009 together could give us some insight?
Could it be that IIS is used for publishing the reports from report services?