Does anyone know if it is possible to use an Adobe “Standard” license with commandbox?
I ask because I have setup the license through cfconfig I do not see any errors that reject the license key, yet Coldfusion 11 is still running in developer mode. Slightly stumped and am looking for requirements of the standard license or any answers.
ColdFusion detects CommandBox as a j2ee install so a standard license won’t work. That was going to be changed for us in 2018 but it… wasn’t
If CF is coming up as developer, I’m guessing the license isn’t being applied correctly. Do a console start and watch for any log messages after the licensing service starts.
I should add, you can still use developer mode in non-production environments with no issue. You just can’t deploy a production adobe server on commandbox with their current licensing. If you were hoping to use commandbox in prod, I would encourage you to let Adobe know so they’re aware of the demand.
There is a workaround that will allow you to use CommandBox to orchestrate the server and Runwar as the servlet container, but it requires some manual work. Here are the steps:
Run the Standard Installer, entering your license key along the way and making sure the auto-start option is not enabled
In the directory where ACF is now installed add a symlink or virtual directory of WEB-INF, which points back to the same directory the symlink is in
In your server.json file, set the app.serverHomeDirectory to the location of the ACF installation.
Start the server normally and CommandBox will use the installed ACF file system as its server root.
The manual workaround given does seem to mostly work, but CFIDE isn’t quite happy. Where it would normally show the top tab bar, instead I get this error
“Object Instantiation Exception.
Class not found: com.adobe.coldfusion.entman.ProcessServer”
Most settings are still accessible, but not all of them.
That’s most likely because that class doesn’t exist. entman is short for “enterprise manager” and it doesn’t exist on a standard server. My guess is CF is confused about what version it is. I don’t know if there’s a fix. The workaround you’re using is certainly not something “supported” by Adobe.
Is it still true today with Adobe® ColdFusion® 2023™ that an Enterprise® license is required for a production environment when CommandBox starts and manages the adobe@2023 CFML engine? Obviously, I’d love to only be required to provide a Adobe® ColdFusion® 2023™ Standard® license, but I suspect nothing has changed here.