RUNNING COLDFUSION ON AWS MANUAL

I didn't find any noticeable differences between the 20 version besides the logo. So, enter the web server configuration tool. Nevertheless, if they are not in sync with the virtual directory versions, then you are out of luck.

Note that the file path is virtually the same save for the root folder. Here is the 2018 tomcat ISAPI filter configured below:

RUNNING COLDFUSION ON AWS MANUAL

Below are how those directories look in IIS.īut there are shortcomings to the manual approach - namely, the ISAPI filter configuration/addition/removal. It turns out that the ISAPI filter is not as easy to manipulate as virtual directories, with both inherited and local configurations.

I've gotten used to manipulating the cf_scripts and jakarta virtual directories manually in IIS rather than use the website configuration tool that comes with CF. But just after upgrading to 2021, we discovered the date bug, and so needed to revert a site or two back to CF 2018. When CF 2021 came out just before CF Summit back in November of 2020, I was chomping at the bit to try the new features, including SAML, AWS, and Azure integration from the administrator's configuration.

Running coldfusion on aws