D
dbeavon
Guest
I am eager to start using PASOE. I was wondering if anyone can offer some advice on how to make a switch from "classic" appserver. Some of our biggest challenges in moving forward are non-technical. Given that "classic" appserver is essentially deprecated (and is not receiving much innovation or investment or support) we'd like to switch to PASOE. Our technical evaluation of PASOE shows that it will be a suitable replacement, and my interaction with Progress tech support leads me to believe that there is ongoing development on PASOE (unlike with "classic" appserver). Unfortunately non-technical issues are delaying our migration to PASOE, and may prevent it altogether. The main problem is in the negotiating of the price for changing from one type of appserver to the other. Progress sees these as two totally different products and will give us only a small credit for "classic" appserver purchases that we have under maintenance. It seems that customers are basically being asked to start from scratch as we attempt to migrate to PASOE. This is a very hard thing for Progress to ask - since the portions of PASOE that we are prepared to use (APSV transport against standard ABL applications) are largely the same as they were in "classic" appserver. Ideally there would be an "Express" version of PASOE that would remove new functionality (SOAP, REST transports, scale-out architecture, etc). Such a version would allow "classic" appserver customers a migration path without forcing us to re-purchase something from scratch that feels substantially the same as what we already have with the "classic" appserver. Keep in mind that the new bells and whistles are only a small factor in the drive to make the switch. This switch is mostly about staying on a well-supported product which receives ongoing software maintenance. Our yearly maintenance dollars that are intended for "classic" appserver support are probably being re-invested in PASOE, since little has been changing on the "classic" side of things. It seems that the past five years of those maintenance dollars should be counted as credit towards PASOE as well, right? I'm interested to hear any alternative perspective, or tips on how we might move forward. Does the idea of a PASOE "express" version have any potential? That would allow Progress to charge customers for new features (in a separate "advanced enterprise" edition), while not imposing their costs on customers who don't necessary need them. Finally, I was wondering how long it might be before Progress has their own reasons for encouraging customers to get out of "classic" appserver. Perhaps they won't want it to be included anymore in OE 13 and will be removing these significant barriers that are preventing customers from switching.
Continue reading...
Continue reading...