D
dbeavon
Guest
I'm going to assume it is totally legal to do what the KB says and install PDSOE, then use the license update utility to remove the license afterwards. Those unusual steps seem to have the intended effect of enabling adminserver/OEE. We don't seem to lose OEE again after removing the license. An added bonus is that once adminserver/OEE are in place, you can easily enable the "sonic-adapter-broker-service-thingy" if needed (... which is a component of the AdminServer infrastructure that doesn't have an additional charge if you already own PASOE, per the information provided to us by our account representative.) Here is a screenshot of that KB article as it is written now. Progress KB - PASOE installation does not install the AdminServer There are some things that still concern me about the recommendation for installing PDSOE. It may have negative side-effects and consequences that aren't fully explained in that very short KB article. For example, I suspect that it might set in place components that may allow programs to be *dynamically* compiled in production - possibly even programs that *update* the database. I haven't fully investigated whether or not the KB leads to these side-effects, but will do so before moving ahead. It would be nice if Progress provided a formal utility, rather that telling PASOE customers to install PDSOE in production...
Continue reading...
Continue reading...