Where can I find ColdFusion_2018_WWEJ_java.jar ?

[another_admin]

In the installation documentation there is reference to installing CF on Unix (Other) by using ColdFusion_2018_WWEJ_java.jar but I can't seem to find that installer file.

[Charlie Arehart]

Do you notice on the page that the sentence referring to that starts with: "If you are deploying the JEE configuration on a platform other than Linux or Solaris, use the ColdFusion_2018_WWEJ_java.jar."

So first, you have said you are on Unix, and so the second bolded point applies.

But are you really "deploying the JEE configuration"? I'll clarify for readers that that is about deploying CF on some other app server (like weblogic, websphere, jetty, etc.) That's a pretty rare implementation approach, though it is indeed supported.

Finally, if you really ARE wanting to deploy CF that way, can you clarify if you are saying that you found that once you went to the CF download feature (where you login, and fill out the form asking lots of questions) that then the resulting drop-down appeared and you picked Unix? If so, did you happen to notice what file WAS available to download at that point? And did you try it, even if not the same name as the doc?

[another_admin]

Yes Charlie, and thank you for responding. The target system is FreeBSD running WildFly as the app server. I was on that page, which lead me to this https://helpx.adobe.com/coldfusion/installing/installing-the-jee-configuration.html. That, in turn, lead me right back where I started.

My initial search for a download was through the Adobe Licensing site which only provides the standard issue Windows, Linux, Mac, Solaris installers.

The form that asks a bunch of questions, I assumed was the same as far as Developer or Free Trial. However, as usual with assumptions...only the Free Trial option gives the dropdown , where the Developer download automatically tosses me a win64 installer. The dropdown does not have a Java only or Unix (other) option. Only Windows, Linux, Mac, Solaris and then the Japanese versions of those four.

[Charlie Arehart]

I don't know if cf supports freebsd. Did you try the Solaris installer? Or would it not possibly work?

I will say that if you run the installer of any OS, to create the ear or war (which the jee install process creates), you SHOULD then be able to implement THAT on any OS.

Otherwise, I'd think your next best bet is to reach out to cfinstal@adobe.com. They offer free install support and should be able to offer more clarification.

If you learn something, pro or con, I hope you'll update folks here. 

[another_admin]

I think I'll give that a shot and see where it goes. As suggested, I contacted cfinstal this morning and I'm not filled with confidence with the response after being pointed to Java JRE installers when asking for the CF java installation jar. Further clarifying my intention they asked if it was to be a standalone or WAR deployment, figuring the only option is a WAR deploy, they directed me here

https://helpx.adobe.com/pdf/coldfusion2018-support-matrix.pdf

Which seems to indicate the option to run the installer on another OS to generate the ear/war file and try to deploy that way.

[Charlie Arehart]

As for their replying ultimately by pointing you to that PDF, it could be because you mentioned a specific wildfly version, and that page clarifies how CF 2018 supports only v14. Or perhaps you mentioned freebsd, and that page clarifies that CF only "supports" (offers installers for) the listed variants of Windows, Mac, Linux, and Solaris (the point I was getting at in my previous reply).

Without seeing specifically what you said and their reply, I don't know why they'd not address specifically: "where is that jar that the doc points to?", which was your intial question. But if you mentioned freebsd, their defaulting to the support matrix would be somewhat understandable.

Again, if you let go any hope of running the CF installer on freebsd, and instead run it elsewhere, that installer will offer an option to create the CF ear or war (there is no current provision to "just get that"), and then if you run that (on bsd or really any version of wildfly, on any os), it may just work. The ear/war is self-contained, and as far asa I know OS-agnostic. I can't say with certainty.

But this is again a very low-use scenario (deploying CF as a war/ear), so you may find relatively little on it, and few who can help. (It's been several years since I last did it, but I may still be able to help here, or via direct consulting if that may interest you.)

[another_admin]

Charlie, thank you for the guidance! The war deployment was the way to go, worked a treat! I now have CF 2018 running on FreeBSD 12.1 with WildFly 18.

After another few emails with the cfinstal group, it would appear that the reference to the WWEJ_Java.jar installer is an erroneous one. The intention is to use one of the other OS installers to generate the EAR or WAR as you like and deploy it on your OS of choice.

For the benefit of anyone else with the desire to do this for whatever reason on this OS

https://helpx.adobe.com/in/coldfusion/installing/coldfusion-2018-install-jee-configuration.html under the WildFly section, ignore the bit about installing WildFly, downloading, extracting etc...

instead here's what I ended up doing:

1. Generate the WAR file using Windows machine

run the windows installer and selected JEE WAR

unchecked all sub-components (I don't need them for this)

left defaults (unchecked) for other servlets

set the hostname of the target machine's hostname

2. Install WildFly on BSD machine

~ #  pkg install wildfly18

wildfly is then installed to /usr/local/wildfly18

From this point you can follow the "Access ColdFusion on WildFly" starting at step 2.

The path to drop the expanded war into is /usr/local/wildfly18/standalone/deployments

With that out done, you may need to make a change to the standalone.xml config file located /usr/local/wildfly18/standalone/configuration/standalone.xml by default it's setup to bind the management and web interfaces to 127.0.0.1, you'll want to change that to the host's IP.

start up WildFly with ./standalone.sh under /usr/local/wildfly18/bin

Then to finish up

http://<ipaddress>:8080/cfusion/CFIDE/administrator/index.cfm

You'll of course want to set that up to startup on boot and using a different user. 🙂