Guidance for Setting up Remote DataPortal Hosting

Guidance for Setting up Remote DataPortal Hosting

Old forum URL:

FrazerS posted on Sunday, February 28, 2010


I have used CSLA in a couple of projects now, but I have always run with a local data portal.  In my current project, I will need to use a remote data portal (WCF).  I have searched through the book (C# 2008 Business Objects) and while I can find information about how to configure the remote data portal and client, I can't seem to find any guidance on how to implement and host the WCF remote data portal service.  Can someone point me to the right place or other resources that will get me started?



RockfordLhotka replied on Sunday, February 28, 2010

Maybe I'm missing the point of the question?

There's really nothing to it. If you get it configured as described in the book it will just work. There's no implementation required. The whole point of the data portal is that it is implemented for you, so you don't have to spend a lot of time on n-tier plumbing issues.

  1. Create an ASP.NET web or service app
  2. Add the svc file
  3. Add the config file entries
  4. Make sure your business assemblies and Csla.dll are in the bin directory
  5. Configure the client to call your svc file
  6. Enjoy the n-tier deployment of your app

Setting up and using a basic 3-tier deployment should take less than 5 minutes.

That's hosting in IIS.

There are, to be sure, more advanced hosting scenarios. Namely WAS or a custom Windows service.

Setting up WAS is like IIS - but first you need to install/activate the WAS component of Windows (because it isn't installed by default). Otherwise it uses a svc file and config file, so the process is pretty comparable to IIS.

Setting up a custom Windows service does require that you actually implement a Windows service. This isn't terribly hard in the simplest sense, and hosting a WCF service requires just a few lines of code. But making a production-worthy Windows service is really quite hard, at least if you want any sort of manageability, configurability and the other "ilities" most people want from a server component. I strongly recommend using IIS or WAS if at all possible, because they already provide those features.

FrazerS replied on Sunday, February 28, 2010

No, Rocky, it was me that was missing the point - stumbling around in the forest, looking for trees apparently.

Thanks for the fast Sunday morning reply.


Copyright (c) Marimer LLC