Lucee 7.0.0.395 Installation issues

dev support
1

I set up lucee 7.0.0.395 - The original site ran fine.
added 3 more through IIS and the custom tags for the first site are being pulled into the others.
I tried installing a new instance of Lucee 7.0.0.395 installed into a new directory. Admin pages for both work and I change the default Tomcat Web Service Port, Tomcat Shutdown Port, and Tomcat AJP Port from the default incremented each by 1.
Now I get service is unavailable for both actual sites. (admin for both runs)

Any insight would be helpfule
thanks,Trevor

OS: 21H2
Java Version: 21.0.9 (Eclipse Adoptium) 64bit
Tomcat Version: Apache Tomcat/11.0.13
Lucee Version: 3.0.0.395

2

I read this but was for an older version of lucee

and was using railio as the example. When I install like it says, there is no AJP installed.
if I do one install for testing, the custom tag folder seem to get mixed up.

3

I did not get the multiple instances to work, but did make sure the custom tag paths were set in the various application.cfc’s and not in the Lucee admin.
Seemed to work and to allow us to test and prepare for moving to 7.

4

Steps to Run Dual Lucee Servers with IIS (for Testing)
(Example: Lucee 6.2 and Lucee 7.0)
Install the first Lucee server with all default ports (e.g., 8888, 8009, 8005).
Install the second Lucee server with customized ports (e.g., lucee:8889, AJP:8008, shutdown:8004).
Create two different IIS sites with two different root directories.
Each server points to a different root directory and hostname in IIS.
One server runs on the default AJP port (8009), and the other runs on a custom port (8008).

Initially, installing the AJP connector globally caused both sites to run through the same BonCode instance.

Fix: Uninstall the global AJP connector from C:\lucee\AJP13.

Instead, configure Handler Mappings in each site’s web.config from the root of the site.

web.config

<handlers>
            <remove name="BonCode-Tomcat-CFM-Handler" />
            <remove name="BonCode-Tomcat-CFC-Handler" />

            <add name="BonCode-Tomcat-CFM-Handler"
                path="*.cfm"
                verb="*"
                type="BonCodeIIS.BonCodeCallHandler"
                modules="ManagedPipelineHandler"
                resourceType="Unspecified"
                requireAccess="Script"
                preCondition="integratedMode" />

            <add name="BonCode-Tomcat-CFC-Handler"
                path="*.cfc"
                verb="*"
                type="BonCodeIIS.BonCodeCallHandler"
                modules="ManagedPipelineHandler"
                resourceType="Unspecified"
                requireAccess="Script"
                preCondition="integratedMode" />

            <!-- Explicit Lucee Admin forwarding -->
            <add name="BonCode-Lucee-Admin"
                path="lucee/*"
                verb="*"
                type="BonCodeIIS.BonCodeCallHandler"
                modules="ManagedPipelineHandler"
                resourceType="Unspecified"
                requireAccess="Script"
                preCondition="integratedMode" />
        </handlers>

Add Required Files to Each Site’s /BIN Folder
BonCodeIIS.dll
BonCodeAJP13.settings (site-specific configuration)
:warning: Note: Update each BonCodeAJP13.settings file to point to the correct AJP port (e.g., 8009 for one site, 8008 for the other).
:point_right: Copy these files from C:\lucee\AJP13 before uninstalling the global AJP connector, then paste them into each site’s /BIN folder.

5

Thank you for this. I was able to run with one instance for now, but may attempt this before moving to Lucee 7 officially. Luckily, using the customTag paths in the application.cfc seems to be working.
only have one site in issue. It loads the login screen, but will not login or created the web context as is.
also on qa and production, we have it broken out to different servers.