From: Andreas N. <an...@kl...> - 2005-09-03 06:15:13
|
Hi folks, after several months of just working w/o an contemplation, we are now seeing the results of living with some unsolved problems, which I want to share here, since we are discussing, how to react to them and there are so many bright people on this list.. ;-) The system we are running is an Intranet application server for serving mainly callcenter agents for various purpuses ( e.g. outbound telefonie, order entry, messaging, news, production time and mis capturing etc ) for about 1000 users. This is a very dynamic business, where we need to install new packages / updates almost every day. We reacted to this by making things dynamic as much as possible, so you can do e.g. an MIS with Excel export only by dynamically defining things in the database. Still the statement is true, that OpenInteract 1 is not very well suited for that many changes. Another problem in with this is, that one package can easily turn down the whole site. This is also true for databases. It does not help in all cases to distribute the load to many databases, because the failure of one database might render OpenInteract unusable, even if they are only used for one application. One condition where this happens is when you are using field discovery and are restarting OpenInteract while one database is down - it will never start... To make one point clear: I am only focussing on the problems here, because we are really heavy users or OI and ran into some design issues, because of not thinking about them - we still like all the pros about OI. So bright list folks - any suggestions for us? cheers Andreas -- Andreas Nolte <an...@kl...> |