D
dbeavon
Guest
Good point about the CLI. That probably comes in handy, especially if the instance is deployed without adminserver and is not managed via OEE/OEM. Are there only the two variations of PASOE : production and development? I was thinking the other day that it might be nice to have another version of the production PASOE which would be limited to the APSV transport, without any of the other "bells and whistles". Perhaps Progress could make it available to existing classic appserver customers in a cost effective way. (So customers might finally get out of the classic appserver, which seems to be a pretty outdated technology, and hasn't seen any recent innovation.) As you say, it is costly to move from the old appserver to the new. Progress seems to consider PASOE an entirely different product than classic appserver. But it accomplishes the same goals so it is hard to explain to management why we should need to "purchase all over again". In general we think of PASOE as an updated version of classic appserver and has the features that classic appserver might have today if it had been receiving a bit more TLC (ie. better resource utilization, multi-session threading, etc). If you look beyond the differences introduced as a result of tomcat, it is surprising how similar classic and PASOE really are. For example, it was interesting to notice that even our "event procedures" (session startup, shutdown, connect) can be run unmodified, and they share the same set of calling parameters as the classic appserver.
Continue reading...
Continue reading...