Install the server configuration


The installer images may seem a bit pixelated in 150% scale. We recommend changing that to 100%.

Gathering information necessary to install the server configuration

Note: The cf_root directory refers to your installation directory. By default, this directory is C:\ColdFusion2021 in Windows, and /opt/ColdFusion 2021 in UNIX.

Although the Adobe ColdFusion (2021 release) installer provides an intuitive interface, it helps to plan your answers to the questions asked by the installer. Use the steps below to install the server configuration of Adobe ColdFusion (2021 release).

License Agreement

License agreement
License agreement

Accept the license agreement.

ColdFusion Install Type

ColdFusion install type
ColdFusion install type

Enter the serial number.

Developer edition: This free, fully functional version of ColdFusion is for local host development of applications that will be deployed on either standard or enterprise servers — and that can be simultaneously accessed from only two remote IP addresses.

30-day trial: If you choose this option, you get a fully functional ColdFusion Enterprise edition for a trial period of 30 days. You can add a license key through the ColdFusion Administrator also.

Previous Serial Number: Enter the serial number if:

  • You are upgrading from ColdFusion (2018 release) to ColdFusion (2021 release).
  • You are uprading from ColdFusion Standard to ColdFusion Enterprise.

Choose the type of installation:

Installer configuration

Installer configuration
Installer configuration

Deployment type

Deployment type
Deployment type

Deployment Type:

  • Production: Must only be licensed for commercial use. License is based on deployment per core.
  • Development: Licensed only for internal development and testing.
  • Staging: Licensed only for testing and reviewing one or multiple versions of applications before deployment.
  • Testing: Licensed only for testing and development purposes and not for staging or live.
  • Disaster Recovery: Licensed only for usage during interruption of business critical services.

ColdFusion Server Profiles

ColdFusion server profiles
ColdFusion server profiles

Select one of the supported Server profiles. For more information on the profiles, see Understanding ColdFusion Server Profiles.

Sub-components Installation

Sub-components installation
Sub-components installation

Select the sub-components to install. 

ODBC is greyed out because ODBC is pre-installed in this version of ColdFusion.

Enable or Disable Servlets

Enabling or disabling servlets
Enabling or disabling servlets

Enable/disable the servlets to use.

Note: this option is valid only for the following profiles:

  • Production profile
  • Production + Secure Profile

All JEE web applications have a file in the WEB-INF directory called web.xml this file defines the servlets and servlet mappings for the JEE web application. A servlet mapping defines a URI pattern that a particular servlet responds to. For example, the servlet that handles requests for .cfm files is called the CfmServlet the servlet mapping for that looks like this:

<servlet-mapping id="coldfusion_mapping">




The servlets are also defined in the web.xml (ColdFusion install dir/cfusion/wwwroot/WEB-INF) file. The CfmServlet is also defined in web.xml as follows:

<servlet id="coldfusion_servlet">


  <display-name>CFML Template Processor</display-name>

  <description>Compiles and executes CFML pages and tags</description>


  <init-param id="InitParam_1034013110656ert">






You can remove servlet mappings in the web.xml to reduce the surface of attack. You don’t typically want to remove the CfmServlet or the *.cfm servlet mapping, but there are other servlets and mappings that you can remove, depending on the situation.

For more information on making changes to web.xml, and enabling/disabling servlets, see Pete Freitag's ColdFusion (2018 release) lockdown guide.


Access add-on services remotely
Access add-on services remotely

Access add-on services remotely by allowed certain IP addresses.

If you selected PDFg or Solr sub-components (when installing sub-components), the add-on services are installed.

When you leave the option Access Add-on Services Remotely unchecked, you can only access the add-on services from localhost. If you want to access the services from multiple ColdFusion servers and not just the localhost, choose the option Access Add-on Services Remotely, and specify the IP addresses of the remote ColdFusion servers.

ColdFusion Installation Directory

ColdFusion installation directory
ColdFusion installation directory

Enter the installation folder for ColdFusion.

Web Server Port

Port of web server
Port of web server

Specify the port of the built-in web server.

The default port is 8500.


Performance Monitoring Toolset
Performance Monitoring Toolset

Enter the host for Performance Monitoring Toolset.

Set Administrator Password

Set Administrator password
Set Administrator password

Confirm the administrator password.

Check for Server Updates

Check for server updates
Check for server updates

Specify if you want to check for server updates.

Pre-installation Details

Pre-installation details
Pre-installation details

View the pre-installation details.

Installing ColdFusion using the server configuration

Once you have determined the answers to the questions in the above section Gathering information necessary to install the server configuration, you can install the ColdFusion server configuration in Windows or UNIX, as applicable.

Installing ColdFusion server configuration in Windows or MAC


(Windows only) The Windows installer requires a computer that supports at least 256 colors.

Install ColdFusion in Windows or MAC

  1. Read the online version of the Release Notes for any late-breaking information or updates. For more information, see
  2. Ensure that your operating system meets the system requirements described on the Adobe website at
  3. Review Installation considerations for Windows and Installation considerations for all platforms .
  4. Determine the answers to the questions in the above table in "Gathering information necessary to install the server configuration" section.
  5. Close any applications that are currently running on your computer.
  6. If you plan to configure an external web server, ensure that the web server is running.
  7. Insert the DVD or download the setup file from the Adobe website.
  8. Follow the instructions in the installation wizard, and let it run to completion.
  9. Click OK to open the ColdFusion Administrator and configure the server.
  10. To install any other integrated Adobe or third-party technologies, see Installing Integrated Technologies.
  11. Configure and manage your system, as described in Configuring your System your System.
  12. To learn about ColdFusion, read the documentation, which is accessible through the Documentation link on the Resources page of the ColdFusion Administrator.

Installing the ColdFusion server configuration in UNIX

By default, ColdFusion installs into the /opt/coldfusion2021 directory. You can also choose to install ColdFusion in a different directory.


The default user is nobody for the UNIX installer running ColdFusion.

Install the ColdFusion server configuration in UNIX

  1. Read the online version of the Release Notes for any late-breaking information or updates. For more information, see
  2. Ensure that your operating system meets the system requirements described on the Adobe website at
  3. Review Installation considerations for UNIX and Installation considerations for all platforms.
  4. Determine the answers to the questions in the above section "Gathering information necessary to install the server configuration".
  5. If you plan to configure an external web server, ensure that the web server is running.
  6. Log in as root.
    Copy the installation file that is appropriate for your platform and locale from the DVD or Adobe website, and save it to a directory on your local disk. The following installation files are those for the supported server configuration platforms:

  • ColdFusion_2021_WWEJ_linux64.bin (64-bit systems)




  1. Using the cd command, go to the directory that contains the installation file.
  2. Ensure that you have executable permission for the installation file. You can change permissions on the file by using the following command:

    chmod 777 ColdFusion_2021_WWEJ_solaris64.bin


  3. Start the installation with the following command:



To run the Linux installer in GUI mode, type ./<filename> -i gui.

  1. Follow the prompts in the installation program, and let it run to completion.

For security reasons, it is crucial that you do not use root for the runtime user.

  1. Start ColdFusion with the following command:

/cf_root/cfusion/bin/coldfusion start

If you specified the use of an external web server when you ran the installer, ColdFusion automatically runs the cf_root/cfusion/bin/ script when it starts the first time. This shell script runs the Web Server Configuration Tool by using the settings that you specified during the installation. If there are problems running this script, review the configuration and bin directory specifications, modify as necessary, and rerun the script. You can also configure your web server by using the scripts in cf_root/cfusion/bin/connectors, as appropriate. To stop ColdFusion, use the following command:

/cf_root/cfusion/bin/coldfusion stop

For more information on managing processes, see Managing the ColdFusion process in UNIX.


  1. Open ColdFusion Administrator to run the Configuration wizard.
  2. Configure and manage your system, as described in Configuring your System.
  3. To install any other integrated Adobe or third-party technologies, see Installing Integrated Technologies.
  4. To learn about ColdFusion, read the documentation, which is accessible through the Documentation link on the Resources page of the ColdFusion Administrator.

ColdFusion installation directory structure

By default, ColdFusion2021 is your installation directory. The following table describes the directory structure:




Contains the following directories:

  • bin: Programs for starting, stopping, and viewing information for ColdFusion, and to run Crystal Reports (Windows only). It also contains the password reset scripts for server administrator and Admin Component for remote server start and  stop .
  • cache: Repository for temporary files from ColdFusion.
  • cfx : Sample C++ and Java CFX files with their supporting files. You can also store your CFX files in this directory (although you can put them in any location that is defined in your classpath).
  • charting: Files for the ColdFusion graphing and charting engine.
  • CustomTags: Repository for your custom tags
  • db : The sample Apache Derby databases for all platforms.
  • gateway: Files for ColdFusion event gateways.
  • jetty: Solr configuration files and files related to remote instance start and stop.
  • jintegra : (Applies only to Windows) JIntegra programs, libraries, and other supporting files (for example, to integrate Java and COM code; manage access to ActiveX controls (OCXs) that are hosted in a graphical user interface (GUI) container ; and  register the JVM and type libraries). (Applicable only for Windows.)
  • jnbridge : Files for .NET Integration Services.
  • lib: JAR, XML, property, and other files that are the foundation of ColdFusion, for functionality such as queries, charting, mail, security, Solr, and system probes.
  • logs: Repository for ColdFusion log files. JRE-specific log files are in the runtime/logs directory. Console outputs are logged in to coldfusion -out.log instead of cfserver.log.
  • Mail: Repository for spooled mail and mail that cannot be delivered.
  • META-INF: XML metadata for the ColdFusion Administrator.
  • registry: (UNIX only) Flat file to store registry settings
  • runtime: Programs and supporting files for the ColdFusion runtime. Also, contains the Tomcat libraries. The conf directory in runtime contains all Tomcat configuration files.
  • stubs: web services.
  • wwwroot : Default web root directory for the built-in web server. When running on other web servers, this directory contains the CFIDE and WEB-INF directories; do not remove this directory.


Contains instances.xml and connector configuration files. Also, contains cluster configuration file, cluster.xml.


Java runtime files.


Files to uninstall ColdFusion.



The ColdFusion_install\cfusion\bin directory contains the Jvm.config file.

Using the built-in web server

ColdFusion provides in-built Tomcat application server that you can use to develop ColdFusion applications.


The version of Tomcat application server bundled with Adobe ColdFusion (2021 release) is 9.0.x.

During the ColdFusion installation, choose a web server. If you select the built-in web server, your web root directory is located in the  cfroot / wwwroot  directory. By default, the web server runs on port 8500. It means that to display a page in your application, append:8500 to the host name or IP address in the URL; for example, http://localhost:8500/YourApp1/index.cfm. If the page does not appear, ensure that the document is located in the built-in web server's web root directory; for example, C:\ColdFusion2021\cfusion\wwwroot\YourApp1\index.cfm.


If port 8500 is in use, the installer checks up to 100 ports (starting with 8501) to find a port that is not used. ColdFusion uses that port and displays a message to indicate the selected port.

If you select an external web server during installation, the built-in web server is deactivated.

Change the port of the built-in web server

  1. Back up the server.xml file. This file is in the cfroot\cfusion\runtime\conf directory.
  2. Open the original server.xml file for editing.
  3. Search for internal webserver start.Update the port number.

port="8500" protocol="org.apache.coyote.http11.Http11Protocol"
redirectPort="8445" compression="on" useSendfile="no" compressableMimeType="text/html,text/xml"/>
  1. Save the file and then restart ColdFusion.

Configuring the built-in web server (Tomcat)

While installing, if you have configured ColdFusion on an external web server, do the following to configure ColdFusion on in-built Tomcat:

  1. Open the cfroot\cfusion\runtime\conf\server.xml file.
  2. Search for internal webserver start.Uncomment the following connector XML.

port="8500" protocol="org.apache.coyote.http11.Http11Protocol"

Save the file, and then restart ColdFusion.

To enable OS Symbolic links after switching to Tomcat, edit the context.xml file found in /cfusion/runtime/conf/ to add allowLinking="true" attribute to the context element.

Starting, stopping, and restarting ColdFusion

On Windows

At prompt, go to the directory cfroot\cfusion\bin and run the following command: coldfusion.exe -start -console. To stop ColdFusion, use the command coldfusion.exe -stop -console. To restart, use the command coldfusion.exe -restart -console.Alternatively, you could also start, stop, and restart ColdFusion server using Windows Services.


Paused tasks misfire when restarting ColdFusion.


As possible in previous versions of ColdFusion, you can also use the cfstart script to start/stop the ColdFusion sever.


The -console argument is optional. If it is not provided, the logs are saved in the cfroot\cfusion\logs directory.

On UNIX/Linux/Solaris/MAC OSX

At prompt, go to the directory cfroot\cfusion\bin and run the following command: ./coldfusion start}}To stop ColdFusion, use the command ./{{coldfusion stop. }}To restart, use the command {{./coldfusion restart.


Paused tasks misfire when restarting ColdFusion.


Use the status command to find the status of ColdFusion server.

Editing the JVM settings

To edit the JVM settings, open the cfroot\cfusion\bin\jvm.config file and update the following details:

  • java.home: Java home. If not set, ColdFusion verifies the default JRE in the cfroot\jre folder, in the registry, or in the J{{AVA_HOME}} environment variable.
  • java.args: Settings for -Xmx, ColdFusion classpath, and so on.
  • java.library.path: Settings for library path.
  • java.class.path: Additional classpath settings in a comma-separated list.
  • application.home: Default is cfroot\cfusion

Creating and editing a new ColdFusion instance

After installing ColdFusion in stand-alone mode, create an instance of ColdFusion using the ColdFusion Administrator.

  1. In the ColdFusion Administrator, go to Enterprise Manager > Instance Manager.
  2. Click Add New Instance.
  3. Enter the server name and server directory.
  4. (Optional) Check Create Windows Service.
  5. Click Submit. In the Instance Manager, start, stop, restart, delete, access website, or access administrator.
  6. Click the Edit icon to edit the instance manager.
  7. Edit the internal webserver port and load balancing factor.Load balancing factor represents the load the instance takes up. Load balancing factor is applicable only if the instance is part of the cluster. For example, the load balancing factor for the first instance is 1 and that of the second instance is 2. The second instance receives two times more requests.
  8. Click Submit.

Registering a remote instance

Register a new remote instance of ColdFusion using the ColdFusion Administrator.

  1. In the ColdFusion Administrator, click Enterprise Manager > Instance Manager > Register Remote Instance.
  2. Specify the details such as instance name, remote host, remote port, http port, and JVM route. Instance name is a string that is used to identify the instance. Remote port and HTTP port are displayed in the Instance Manager page. These ports are provided in the server.xml file available in the runtime\conf folder of the instance. Remote port is the AJP port and the instance port is the connector port.JVM route is the remote instance name. The JVM route is an attribute that acts as an identifier for a particular Tomcat worker. JVM route is provided in the server.xml file available in the runtime\conf folder of the instance. For more information on JVM route, see


A remote instance and a local instance cannot have the same JVM route if they are added in a cluster with sticky session enabled.

  1. If you want remote start and stop functionality over HTTP, enter Admin Component port, Admin Component user name, and Admin Component password. The default Admin Component port is 8985.

To enable this feature, install admin component on the remote host.

  • In the remote host, open the ColdFusion_installtion\cfusion\jetty\etc\jetty.xml.
  • Search for the string,
  • Update the host with the IP address of the remote host.
  • Restart the jetty server.
  1. Click Submit.

Adding start and stop functionality to a remote instance over HTTPS

You can start and stop a remote instance over HTTPS or HTTP. To enable this feature, install admin component while installing ColdFusion. You can install Solr, admin component, or both while installing ColdFusion.

  1. Do the following in the remote host.
    1. In the remote host, generate a private key in a keystore file. Provide the details at prompt.
cfroot\jre\bin\keytool -genkeypair -alias certificatekey -keyalgRSA -validity 7 -keystore keystore.jks

                b. Export the certificate. You can have a self-signed certificate or a certificate from a                               Certificate Authority.

cfroot\jre\bin\keytool -export -alias certificatekey -keystorekeystore.jks -rfc -file selfsignedcert.cer

                c. Copy the jks file created in the jetty\etc directory.
                d. Open the jetty\etc\jetty.xml file.
                e. Search for the string, To add an HTTPS SSL Listenerand add the following entry:

<New class="">
<Set name="Port">8443</Set>
<Set name="maxIdleTime">30000</Set>
<Set name="keystore"><SystemProperty name="jetty.home" default="." />/etc/jks-file.jks</Set>
<Set name="password">changeit</Set>
<Set name="keyPassword">changeit</Set>
<Set name="truststore"><SystemProperty name="jetty.home" default="." />/etc/jks-file.jks</Set>
<Set name="trustPassword">changeit</Set>

                f. Update the keystore name, password, key password, and jks file in the entry.
                g. Search for the string
                h. Update the host with the IP address of the remote host.
                i. Restart the jetty server.


If the remote server is running on Windows Vista, Windows 7, or Windows Server 2008, start the jetty sever with admin privileges.

  1. Do the following in the local host from where you add the remote instance:
    1. Copy the .cer file created in the remote host to any of the locations.
    2. Import the certificate.
cfroot\jre\bin\keytool.exe -importcert -keystore"cfroot\jre\lib\security\cacerts" -file selfsignedcert.cer -storepass password

                c. Register the remote instance using the ColdFusion Administrator. For more information,                       see Registering a remote instance section in this document.

                d. In the Register Remote Instance page, enter the admin component port, admin                     component user name, and admin component password (user name and                     password. These details you specified while installing the Remote Instance                     Administrator). The default https port is 8443.

                e. Select the HTTPS check box.

                f. Click Submit.

Managing clusters

  1. In the ColdFusion Administrator, click Enterprise Manager > Cluster Manager.
  2. Enter a cluster name and then click Add.
  3. Click the cluster name and move the servers to the cluster based on the requirement.
  4. (If necessary) Edit the multicast port. Multicast port is used to group the cluster members together. Default value of multicast port is 45564. After you create a cluster, the port is added in the cfroot\config\cluster.xml file. For more information on multicast port, see
  5. Specify if you need sticky session.Sticky session ensures that after a session is established on an instance, all future requests from the client are mapped to that instance.
    Click Submit.


Restart the web server if cluster instances are modified.

Adding a remote instance to a cluster

To add a remote instance to a cluster, add the cluster block to the remote instance's server.xml. Then, register the remote instance and add the instance to the cluster. For more information on configuring clusters on Tomcat, see

  1. Register the remote instance to the local machine.
  2. Create a cluster in the local machine.
  3. Open the cfroot_instance-name_runtime\conf\server.xml file of the remote instance.
  4. Add the following block between the entries </host> }}and {{</engine>:

<Manager notifyListenersOnReplication="true"
expireSessionsOnShutdown="false" className="org.apache.catalina.ha.session.DeltaManager">
<Channel className="">
<Membership port="45565" dropTime="3000" address="" className="org.apache.catalina.tribes.membership.McastService" frequency="500">
<Receiver port="4003" autoBind="100" address="auto" selectorTimeout="5000" maxThreads="6" className="org.apache.catalina.tribes.transport.nio.NioReceiver">
<Sender className="org.apache.catalina.tribes.transport.ReplicationTransmitter">
<Transport className="org.apache.catalina.tribes.transport.nio.PooledParallelSender">
<Interceptor className="org.apache.catalina.tribes.
<Interceptor className="
<Valve className="org.apache.catalina.ha.tcp.ReplicationValve"
<Valve className="org.apache.catalina.ha.session.JvmRouteBinderValve">

<ClusterListener className="org.apache.catalina.ha.session.
<ClusterListener className="org.apache.catalina.ha.session.ClusterSessionListener">

  1. In the entry, update the membership port with the multicast port of the cluster.
  2. Using the ColdFusion Administrator of the local host, add the local instance and the remote instance to the cluster.


If you enable sticky session, the JVM route of the remote instance and local instance must not be the same.

  1. Restart all the instances.

When adding a remote instance in a cluster, ensure that you comment out <Manager pathname="" /> in content.xml file located in <cf_home>\runtime\conf directory.

Configuring other web servers

Use the Web Server Configuration Tool to configure other web servers.

  1. Run cfroot\runtime\bin\wsconfig.exe.
    You can also configure web servers using the command-line interface as follows.
    Configuring IIS

wsconfig.exe -ws iis -site <site_no>


wsconfig.exe -ws iis -site <site_name>

Configuring cluster

wsconfig.exe -ws iis -site <site_no> -cluster <cluster-name>

Configuring Apache

(Linux or MAC only) ./wsconfig -ws apache -dir <apache_conf_directory>


(Windows only) wsconfig.exe ws apache dir <apache_conf_directory> bin <apache_bin_directory>/httpd script <apache_bin_directory>/apachectl
(Linux or Mac only) ./wsconfig ws apache dir <apache_conf_directory> bin <apache_bin_directory>/httpd script <apache_bin_directory>/apachectl

Configuring cluster

(Linux or MAC only) ./wsconfig -ws apache dir <apache_conf_directory> -cluster <cluster-name>

Unconfiguring IIS

wsconfig.exe -remove -ws iis -site <site_no>


wsconfig.exe -remove iis -site <site_name>

Unconfiguring Apache

./wsconfig -remove ws apache dir <apache_conf_directory>


Unconfiguring all webservers

./wsconfig -uninstall

Seeing the list of webservers

./wsconfig -list

Configuring Secured Socket Layer (SSL)

SSL allows the browser and the server to communicate over a secured connection. Data that is sent is encrypted at one side, transmitted, and then decrypted at the other end. For more information about SSL configuration on Tomcat, see

To configure SSL for ColdFusion using the keytool utility, do the following:

  1. Create a certificate file:
    1. Run the following command:cfroot\jre\bin\keytool -genkey -alias tomcat -keyalg RSA
    2. Type the details as per the instruction.

      If you do not provide a password, the default password for keystore and key is changeit. If you don't want to use the default password, ensure that you provide the same password for the keystore and the key.

      Running this command creates a certificate.keystore in the following location:

    • Windows: C:\Documents and Settings_user's_director_y
    • Linux: usr/home
  2. Open the cfroot\cfusion\runtime\conf\server.xml file and search for the string Define a SSLHTTP/1.1.
  3. Uncomment the connector details and update the section as follows:

<Connector port="8443" protocol="HTTP/1.1"
SSLEnabled="true" maxThreads="150" scheme="https"
secure="true" keystoreFile="<certificate_location>\.keystore" keystorePass="<password>" keyAlias="tomcat" clientAuth="false" sslProtocol="TLS" />
  1. Restart ColdFusion.
  2. Access ColdFusion using the following URL: https://<ip-address>:8443/CFIDE/administrator

Changing virtual directory and the doc root

Do the following to change the virtual directory and doc root:

  1. Open CFInstallation\cfusion\runtime\conf\server.xml.
  2. Under host block, search for the string, "To add virtual directory."
  3. Uncomment the entry context path below.
  4. To add a virtual directory, add the aliases attribute as shown below:
<Context path="/" docBase="<absolute_path_to_cfrootectory>\wwwroot" WorkDir="<cf_home>\runtime\conf\Catalina\localhost\tmp" aliases="/path1=<absolute_path_to_directory1>,/path2=<absolute_path_to_directory2>"></Context>

Alias path must include a leading /.

To change the doc root, change the docBase value in the above entry. For more details on the Context attributes, see

Changing the connector port for cfstat

You can use the connector output for logging cfstat metric. The cfconnector port is defined in the CFInstallation/cfusion/lib/neo-metric.xml file. If you have configured a connector, update the port with the connector port. The connector port (AJP port) is provided in the CFInstallation/cfusion/runtime/conf/server.xml.
To update the connector port using the Administrator console:

  1. Login ColdFusion Administrator.
  2. Click Debugging & Logging > Debug Output.
  3. Update the connector port and click Submit Changes.

Enabling Search Engine Safe URLs

Search Engine Safe URL (SES) helps the search engines to index dynamic web pages. SES URLs pass parameters using slashes instead of default URL pattern. By default, SES is enabled for stand-alone installation of ColdFusion on Tomcat.


SES is applicable only for stand-alone installation of Tomcat. It does not work if ColdFusion is deployed as a WAR file on Tomcat.


If you wish to use custom SES URLs, also add the URL entry to the file found in the wsconfig folder for your web server.

To enable SES URLs on an app server other than Tomcat, add the tags mentioned below to the web.xml file present inside WEB-INF.

This is applicable from ColdFusion 11 Update 12 and ColdFusion (2016 release) Updates 3 and 4.

<servlet-mapping id="coldfusion_mapping_6">
<servlet-mapping id="coldfusion_mapping_7">
<servlet-mapping id="coldfusion_mapping_8">
<servlet-mapping id="coldfusion_mapping_24">
<servlet-mapping id="coldfusion_mapping_25">
<servlet-mapping id="coldfusion_mapping_26">
<servlet-mapping id="coldfusion_mapping_27">
<servlet-mapping id="coldfusion_mapping_28">
<servlet-mapping id="coldfusion_mapping_29">

Enabling Secure Profile

ColdFusion allows you to secure ColdFusion server furthermore by enabling or disabling certain settings. When installing ColdFusion, you can enable Secure Profile by selecting the option when prompted on the Secure Profile screen. Further, you could provide a comma separate list of IP addresses that may be allowed to access the ColdFusion Administrator. In ColdFusion, IP address restriction is supported at the connector-level. For more information, see this document.

Changing the log rotation settings

You can change the log rotation settings such as maximum number of backup files and the size of the backup files.

  1. Specify log file settings in the neo-logging.xml, located in the <ColdFusion_Home>\lib directory.
  2. The size of coldfusion-out.log and coldfusion-error.log is set to 20MB by default. You can change the size of the log in the neo-logging.xml file by changing the maxOutLogSize setting.
  3. You can also change the maximum number of backups of coldfusion-out.log and coldfusion-error.log that ColdFusion takes during log rotation within the neo-logging.xml file. Change the maxOutFileBackup setting.

You can change the settings of the remaining files in the ColdFusion Administrator by going to the Debugging and Logging > Logging Settings section. Change the Maximum file size and Maximum number of Archives settings accordingly.

Enabling persistent session

To persist a session after a Tomcat restart, do the following:

  1. Open the cfroot\cfusion\runtime\conf\context.xml file.

Uncomment the Manager pathname node.


Flex sessions are not persisted after a Tomcat restart.

Updating from an earlier version

If you have skipped the migration or you have to make modifications to the previous installation that has to be migrated, do the following:

  1. Stop the server.
  2. Create a folder named cfXsettings (in which X is the earlier version of ColdFusion) in cf_webapp_new_installation_root_directory/cfusion/lib. For example, name the folder cf2016settings.
  3. Save settings by copying the files cf_webapp_root/WEB-INF/cfusion/lib/neo-*.xml (of previous installation) to cfXsettings.
  4. Edit the ColdFusion cfusion/lib/adminconfig.xml file by setting the value of the  runmigrationwizard  and the {{migratecf}}X (in which X is the earlier version of ColdFusion) switch to true.
  5. Restart the ColdFusion application.
  6. To run the migration wizard, launch ColdFusion Administrator.

Uninstalling ColdFusion

Uninstalling ColdFusion deletes all program files and related components from your computer.

Uninstall ColdFusion from Windows

  1. Select Start > Settings > Control Panel > Add/Remove Programs > Adobe ColdFusion 2021.
  2. Click Change/Remove.
  3. When the program completes, remove any remaining files and directories in the cf_root directory.

Uninstall ColdFusion from UNIX

  1. Log in as root.
  2. To go to the cf_root/uninstall directory, enter the following command:

cd cf_root/uninstall
  1. Enter the following command:
  1. When the program completes, remove any remaining files and directories in the cf_root directory. ColdFusion is deleted from your server.


Schneller und einfacher Hilfe erhalten

Neuer Benutzer?

Adobe MAX 2024

Adobe MAX
Die Konferenz für Kreative

14. bis 16. Oktober in Miami Beach und online

Adobe MAX

Die Konferenz für Kreative

14. bis 16. Oktober in Miami Beach und online

Adobe MAX 2024

Adobe MAX
Die Konferenz für Kreative

14. bis 16. Oktober in Miami Beach und online

Adobe MAX

Die Konferenz für Kreative

14. bis 16. Oktober in Miami Beach und online