· Dec 8, 2017

Different NumberOfDaysToKeep for different interfaces in the same namespace

Hi community,

I got quite a busy namespace with lots of services, processes and operations. The Ensemble purge that runs daily keeps the last 10 days. I would like to increase the NumberOfDaysToKeep to 60, but only for a small number of the interfaces in the namespace, and I would like to do it in a way that will be seamless to the users, so they will not have to change the URL of their calls, or will even be aware of the change.
The one idea that I had is to move these few interfaces to a new namespace , but how do I then do it without affecting the URL? with a Pass-Through interface somehow?

The other idea is obviously to write custom purge routines for each interface or a group of interfaces, but that is too much of a hassle because it is basically a temporary  thing that we need, and wouldn't like to spend too much time on it.

I would like to hear what you guys think about these ideas as well as if you got any other ideas for me.

Thank you

Discussion (2)2
Log in or sign up to continue

Hi Motti,

Sounds like you could get in a tangle trying to do this.

My approach would be to throw more disk space at it and keep everything at 60 days, lowest TCO solution with minimal effort.

If you were to move some of the interfaces, then you could use your web servers config to reverse proxy specific URL paths to different namespaces. If your using the default apache web server then you might look to implement a dedicated installation.

Alternative suggestions.

1. Write your own message purge utility.

2. Use an enterprise message bank (latest versions of Ensemble recommended)...

Hi Motti,

in some projects we faced similar situations. We finally took as Sean mentioned as #2  the Enterprise Message Bank solution and spent some effort in having build specialised SearchTables  - which are populated through Ens.Enterprise.MsgBank.BankHelperClass and implement its OnBankMsg().

The regular message searches are now done in the MessageBank.

And sure, some custom purge methods would help to leave everything in one namespace as you mentioned.

Kind regards,