2 Replies Latest reply on Sep 6, 2013 4:11 PM by Aegis Kleais

    Can CF10 be configured to use a non-jakarta directory?

    Aegis Kleais Level 3

      Long story short, we are installing Groupwise WebAccess on our ColdFusion 10 web server to offer webmail, and it is hard-coded to use the jakarta directory for it's own ISAPI_redirect.dll.  ColdFusion was installed and integrated into IIS 7.5 rather than set to run standalone.

       

      I'm not sure if the underlying Tomcat services that ColdFusion installs are being utilized, but I know that it requires the jakarta folder to run CF.  So is it possible to configure somewhere in CF's files a different name of this virtual directory?  I could create a cf-jakarta and map it to CF's ISAPI_redirect.dll file and this should not conflict with WebAccess' need for it's own ISAPI_redirect.dll.

        • 1. Re: Can CF10 be configured to use a non-jakarta directory?
          carl type3 Level 4

          Hello, I do not think that will work. CF is using a customised tomcat and when I trialled native tomcat org ISAPI_redirect.DLL files in place of CF customised ISAPI_redirect.DLL, for the most part CF did not connect to IIS with syntax errors. Do not let me put you off tho, perform some trial and error, see what happens.

          Regards, Carl.

          • 2. Re: Can CF10 be configured to use a non-jakarta directory?
            Aegis Kleais Level 3

            Been doing a thing here and there, but to no avail.  What takes the most amount of time actually is wondering if the changes I made require a restart with CF.  I must have done enough changes and restarted CF 40+ times.  It seems Tomcat and Jakarta go hand in hand.

             

            WebAccess uses Tomcat 5.5; I'm not sure yet what version of Tomcat CF is using, but we noted that if you request the GW WebAccess URL on port 8080, the application loads just fine!  (While ColdFusion continues to render)

             

            That would lead me to think that Tomcat 5.5 is running on 8080 port.  I did a netstat command and saw that our CF server was listening on some other 8000-range ports, which I thought was kind of odd, because I was under the assumption CF was only listening on the port that it was tied to in IIS (ie, the default port 80)