<@U0BJHDX1Q> <@U01EY27APNH> Quick licensing questi...
# adobe
b
@priyank_adobe @Mark Takata (Adobe) Quick licensing question-- I want to make sure none of this changed in ACF 2021. Using CF with an Enterprise license allows you to create more than one JVM instance on the same server and they are covered by the same license. Just to confirm • Is there a limit to the number of JVM instances on a single server that are covered by a single Enterprise license • For the sake of discussion, lets's assume the number of cores is small enough to not matter And now, the corollary question is-- does it matter how those JVM instances are created? What if they are not created by the Enterprise Instance manager, but instead • A separate installation of CF on the same server • More than one WAR deployment on a servlet container like Tomcat or JBoss Undertow • More than one CommandBox server started Are any of those bullets limited in any fashion, or would a single ColdFusion Enterprise license cover any number of those on a single server with an acceptable number of cores?
👀 1
cc/ @Grant Copley
m
Kicking this up a level and will share the answer with you.
❤️ 4
b
@Mark Takata (Adobe) Any reply?
m
Annoyingly, nothing yet. Just punted this back with an annoyed comment to try and get SOMEONE to reply. Two of our more experienced licensing folks are on PTO and have been for the past week so that might be part of it, but SOMEONE should be able to answer. Sheesh. Sorry Brad. 😞
👍 1
b
Thanks for staying on it
m
OK, so, don't shoot the messenger (that would be me!) but the response I received was to direct you to email coldfusionsales@adobe.com and ask them directly, as they would need to determine use case, apparently. You can CC me as well so they know I directed you their way. Sorry, I know that's almost certainly not the answer you were hoping for.
b
Hmm, sounds like a non answer...
These use cases should be well defined.
Not "let's-see-what-we-can-charge-this-guy" sort of things
they would need to determine use case
I thought the use case was pretty well described in the question itself
For anyone who was curious about the licensing questions I asked here, I had a call today with an Adobe rep from the licensing department to try and nail down some of these basic questions. We chatted for over an hour, but sadly I was unable to get a single solitary answer from him on anything. He wouldn't even commit to confirming the most basic details of CF's licensing and EULA. Everything "depended" on them knowing all the specific details of • The actual customer and who they are • The actual app and what it does • How the app was deployed • What the "needs" of the customer were • Whether the app was a SASS or "service bureau" • etc So I basically couldn't get any answers for anything outside of that full context being provided. Needless to say, it was disappointing that the sauce is so secret, no one is allowed to know how it works. (And Ortus is an Adobe CF reseller!) One of my questions I asked was
If a company has an Enterprise Adobe CF server with the traditional Tomcat install which is already known to be in compliance with Adobe's licensing, would it be acceptable for them to change only the servlet container over to CommandBox (and make no other changes) and still be in compliance?
But even that question could not be answered without "the customer" reaching out to Adobe and performing a full re-evaluation of their business needs.
🤦 2
d
This is why we're migrating away from Adobe. Licensing is no longer something clear cut, but something Adobe seems to want to decide on based on how much money they think they can get from the client. I know it's also the reason some hosting providers (who used to be really premier SPs) are moving away from ACF and do not offer the latest versions of the product. And if you want to create a SaaS-based product, do not even look at ACF. They want you to buy a license for every single customer using your product (not each user, but each of your customers). Not only is that ridiculous, it's in no way practical.
d
Brad, my experience with Adobe support is something different. I never met more un-knowledge people. My issue was getting the server copy registered (under JBOSS on Linux). It would appear that ACF (administrator) for registration ONLY uses port 80. Our servers don't support anything other that SSL ports and not port 443. It basically took 5 phone calls (at least an hour each time) and they STILL COULDN'T get an answer. The only change that had to be done on the registration was to remove the http: from the http:// url line. This would have allow the protocol to match whatever was needed. We finally solved the issue by changing Apache to handle port 80 for 10 minutes. Does make one wonderful what is exactly going on. Anyway, thought I would share that story.