ColdFusion Server 4.5
Release Notes -- Updated November 22, 1999


Contents

Welcome to ColdFusion Server 4.5. One of our goals in this release is moving to a new platform-independent code base. This evolution means changing many of the core libraries that support functionality like CFMAIL, CFPOP, CFHTTP, and CFLDAP.

Use these release notes to stay apprised of important information relating to ColdFusion Server installation and configurations. On this page, you'll also find details about known problems.

Many new features and enhancements make this a significant upgrade, as well. For information about new features and enhancements, see the New Features page.


ColdFusion Server System Requirements

ColdFusion Server 4.5 Enterprise Edition for Windows

System

Web servers

NOTE: Load-balancing and fail-over support is available only on IIS (4.0) and Netscape (3.5 and 3.6)

ColdFusion Server 4.5 Professional Edition for Windows

System

Web servers

ColdFusion Server 4.5 Enterprise Edition for Linux

System

Web servers

NOTE: Load-balancing and fail-over is supported only on Apache (1.3.6 and 1.3.9) Web servers.

ColdFusion Server 4.5 Professional Edition for Linux

System

Web servers

NOTE: Load-balancing and fail-over is supported only on Apache Web servers.

ColdFusion Server 4.5 Enterprise Edition for Solaris

Patches Required for Solaris 2.5.1:

Solaris 2.5.1 with ClusterCATS load balancing:

Patches Required for Solaris 2.6:

Patches Required for Solaris 7:

[These patches are available at access1.sun.com]

Packages Required:

The following package must be installed on your system:

Web servers

NOTE: Load-balancing and fail-over support is available only on Apache (1.3.6 and 1.3.9) and Netscape Web servers.


Before installing ColdFusion on Linux

Before installing ColdFusion on Linux, please note the following considerations:


Upgrading to ColdFusion 4.5

Note the following when upgrading to ColdFusion 4.5 from previous releases of ColdFusion:



Known Issues: All platforms


Known Issues in this release: Windows NT


Known Issues in this Release: Linux


Known Issues in this Release: Solaris


Changing the way Tokens are generated

Current behavior in ColdFusion is as follows:

However, by setting the registry key HKEY_LOCAL_MACHINE\Software\Allaire\ColdFusion\CurrentVersion\Clients\ UuidToken to be the string value "1", ColdFusion assigns CFTOKENS using the same random number concatenated with a UUID, which is guaranteed to be globally unique.

We use the random number to avoid simple guessing of the uuids, since only a small portion of a uuid changes with each assignment, and to make database lookups more efficient.

A typical CFTOKEN using this method looks like this: 57c6419-f0c43bb2-9e8d-11d3-8b87-00c04fa35ba5

If you turn on the UuidToken switch and you are storing client variable information in a database, you will need to increase the column width of the 'cfid' column in the CDATA and CGLOBAL tables. You should change the current width of 20 characters to at least 50 characters, due to the increased length of CFTOKEN.

You may also have to change other applications if they are storing the CFTOKEN value in a fixed length field.


Migrating a ColdFusion UNIX registry to ColdFusion 4.5

PLEASE NOTE: You only need to use this utility if you want to preserve your registry from a previous version of ColdFusion. If you do not, a simple pkgrm of the previous installation prior to installing 4.5 is all that is required.

The CFREGUP utility package consisting of cfregup.sh and this README file is being provided to migrate the ColdFusion registry (formerly maintained by WindU) to the native format used in ColdFusion Application Server 4.5.

The cfregup.sh script must be run as root on a machine with a running ColdFusion 3.x or 4.x installation. You should run this script prior to doing a pkgrm of the cfusion package.

Run the shell script using the following command:

  ./cfregup.sh

This shell script will locate the existing ColdFusion installation and export the WindU registry from it, creating the new ColdFusion 4.5 registry. Please note that since the new registry is created in a different place than the old one, this script will not damage, or even write to the existing WindU registry. The script will also preserve your start script and your odbc.ini files so they can be upgraded.

Once the script has completed, you are free to do a package remove of the existing ColdFusion installation.

During the installation, ColdFusion 4.5 will access the migrated registry and complete the initialization process so it can be used. It will also restore the saved start script and odbc.ini file, making the necessary changes to them so they are version 4.5 compliant.

All intermediate files are saved into a directory called migration, in the ColdFusion installation directory for reference.


Redirecting processing to a Custom Error Page for specific errors

In certain cases, when the communication between the stub (residing in the webserver process space), and the ColdFusion Application Server is disrupted or broken, the following error page is rendered:

"Server busy or unable to fulfill request. The server is unable to 
fulfill your request due to extremely high traffic or an unexpected 
internal error. Please attempt your request again (if you are repeatedly 
unsuccessful you should notify the site administrator)."

In ColdFusion Server 4.5, processing can be redirected to a user-specified location when this error condition occurs in the stub program. Please edit the cfremote.ini file located in your <ColdFusion Installation Directory>, and add a key/value pair specifying the error condition and the redirection location. In this release only the ERROR_PIPE key is supported.

The follwing is an example where the error processing is redirected to nopipe.htm

ERROR_PIPE = "http://127.0.0.1/ErrorPages/nopipe.htm"

NOTE: Please note the ColdFusion Administrator cannot be used to specify these settings. Furthermore every attempt should be made not to change the other settings in this file. Please see Advanced CF documentation for details about the use of the other settings in this file.


Load Balancing and Failover with ClusterCATS

ClusterCATS consists of two components, the ClusterCATS Server and the ClusterCATS Explorer. ClusterCATS Server provides fail-over support, load balancing, and other features to help you guarantee the availability of your ColdFusion applications.

For more information about configuring Web server clusters, refer to Administering ColdFusion Server.

Configuring ClusterCATS on Windows NT:

ClusterCATS and secure Web servers

Secure Web Servers, such as the Netscape Enterprise Server in secure mode, and secure Apache servers, require a keyfile password to be started. The Allaire ClusterCATS installation script will not restart the Netscape Enterprise Server or Apache server during installation, if the web server is running with security enabled. You may start the web server after the installation using your preferred method. The ClusterCATS web server monitor will not be able to restart a web server with keyfile passwords on startup.

Support for multiple web servers on a single platform

ClusterCATS does not support being configured to run with different types of web servers on the same system. For example, if an NT system is configured to run both the Netscape Enterprise Server and IIS, you can choose to configure ClusterCATS with only one of these web servers.

ClusterCATS Cluster Members must have a unique IP address

ClusterCATS Cluster members must have unique IP address. The name used to cluster a web server, or virtual server must not be either Round Robin or the name of a software virtual server. It should be the name that maps to the IP address of the web server that is being clustered.

Virtual Host Headers on IIS and Software Virtual Servers on Apache are not Supported

Virtual Host Headers on IIS and Software Virtual Servers on Apache allow you to run many Web sites on a single computer. In technical terms, this allows you to support multiple host names with a single IP address. ClusterCATS currently requires a different IP addresses for each virtual server.

Minimum version of Cisco Local Director Software required is 3.1.4

Prior to enabling ClusterCATS Load Balancing with Cisco Local Director, the Local Director software version must be at version 3.1.4 or greater.

Configuring ClusterCats IP Failover With Cisco Local Director

When a Cisco Local Director is being used for load balancing and failover do not configure ClusterCats to perform IP Failover (IP Aliasing). If ClusterCats does IP aliasing, the Cisco Local Director will not be able to reconnect to the system after it has become available again and recovered the failed-over IP address.

Configuring Cisco Local Director Update Frequency

Set the Cisco Local Director load balancing update frequency to a value between 5 and 30 seconds. Set a longer time as greater numbers of web servers become configured in clusters doing Cisco Local Director load balancing so as to not create too much overhead traffic to the Local Director. The dyamic-feedback timeout value should be set to a value larger then the update frequency. We recommend you set the value to at least two times the update frequency.

Configuring ClusterCats DFP Agent Listen Port with Cisco Local Director

If two or more web servers on the same system are in clusters using Cisco Local Director load balancing, than each cluster must have the same DFP Agent Listen Port number configured. The Clustercats DFP Agent can only listen on one port.

Configuring the Cisco Local Director dynamic-feedback retry value

The dynamic-feedback retry value should be set to zero (0) to insure that the Cisco Local Director will continue connection attempts to the ClusterCats DFP Agent in the event of a lengthy period of system unavailability.

Cisco Local Director dynamic-feedback security not supported

Do not enable the dynamic-feedback-pw. Clustercats does not support secure DFP host.

Gradual redirection load management and Session State Management

When session aware load management is enabled (the default) then gradual redirection load management does not apply. You can still set a gradual redirection load threshold value, but it will have no effect when session aware load management is enabled.

Configuring a ColdFusion Application Probe

The ColdFusion Application Probe dialog box creates a default probe for that web server to determine if ColdFusion Server is functioning. The default action is set to NORESTART, this will not restart the ColdFusion server if the probe fails, the web server will however be automatically set to the restricted state. See the online help available from the ColdFusion Application Probe dialog box for more information.

Configuring ClusterCATS Explorer Web Addition with Apache

For security reasons we recommend that if you wish to run the Web Addition of the ClusterCATS Explorer you create a separate instance of the Apache server to do so. We also recommend that you password protect access to this server. Below are the configuration changes required to configure the btweb for Apache.

Make the following additions to httpd.conf to get btweb working and to require user/password authentication:

# - make btweb a virtual doc root directory 
Alias /btweb/ "/usr/lib/btcats/btweb/"
# - allow execute in btweb directory and protect it with authentication
<Directory "/usr/lib/btcats/btweb/">
Options ExecCGI 
AllowOverride None
Order allow,deny
Allow from all
AuthName "btcats admin tools"
AuthType Basic
AuthUserFile /usr/local/apache/conf/users
require user admin
</Directory>
# -added .exe file type so that btcluadm.exe will work
AddHandler cgi-script .cgi .exe

You use the Apache 'htpasswd' utility to create/manage the Authentication list file: (create file and add user 'admin')

htpasswd c /usr/local/apache/conf/users admin

Improving Responsiveness When Integrating with Cisco Local Director

By default the frequency at which the ColdFusion load and availability information is sent to Cisco Local Director is every 30 seconds. Users may set Update Frequency to a lower value for better response to change in the server load condition. To update the load frequency refer to ColdFusion documentation.

ColdFusion Application Probe and Application.cfm files

If other than the default URL to query (http://<myserver>/btauxdir/cfprobe.cfm) is used, than you must insure that no Application.cfm files are in the path of the ColdFusion page to be tested.

Configuring ClusterCATS on UNIX platforms:

ClusterCATS requires that the group btcats exist. It will attempt create this group during the ColdFusion installation using groupadd. If you are using NIS or NIS+, please make sure that either nsswitch.conf allows for group resolution from the group file, or that the group btcats gets created in NIS/NIS+ prior to installing ClusterCATS.

UNIX support

In order to run the ClusterCATS the management command, btadmin, on Red Hat the ksh shell must be installed.

Adding appmgr to inittab

It may be desirable to add appmgr to your inittab file, to ensure it always running.

Apache Web server

ClusterCATS and Apache Web Servers

Cluster members can appear to be available when the associated web server managing is actually down. In such cases the ClusterCATS server will display a load of 100%. Also, if the ColdFusion probe is enabled, the server will also be restricted.

Apache Loadable's Support

ClusterCats and ColdFusion Apache support requires that mod_so.c module be compiled into Apache (httpd or httpsd). You can verify this with the -l option to httpd (or httpsd): For example:

# /usr/local/apache/bin/httpd -l
Compiled-in modules:
  http_core.c
  mod_so.c

Windows NT support

Multiple instances support and Windows NT

Only a single Netscape Enterprise Server instance per system can be configured run with Allaire ClusterCATS on NT.

ClusterCATS virtual directory btauxdir is not always being created on system running IIS

ClusterCATS requires that the virtual directory btauxdir exists, under each virtual server which will be clustered and that it points to the <install-directory>/brighttiger/btauxdir. ClusterCATS will attempt to create the directory when a cluster member is added. If there is no IP address bound to the site, ClusterCATS will be unable to add the virtual directory to the web. Use the MMC to add the specific IP address to the web site, then stop and restart the ClusterCATS Service. The btauxdir virtual directory should get created automatically.

Known problems

Adding or Creating a Cluster under heavy load

When creating a cluster or adding a web server to a cluster with the ClusterCats Explorer and that web server is under heavy load you may get a popup message indicating that the "session aware bit could not be set". The ClusterCats Explorer will display the web server with the 'unreachable or unknown' icon. In this case, click OK to dismiss the popup message, hide the cluster ('Hide Cluster' in the View menu), then show the cluster again ('Show Cluster' in the View menu).

Netscape Enterprise Administrator Server

After installing Allaire ClusterCATS, you will see a warning from the Netscape Administrative Server the next time you attempt to manage your Server via the Netscape Administrator. The warning will inform you that the Netscape configuration files have been modified by "hand". Once you've clicked OK to accept this warning, you must choose to Apply the manual updates. If you do not apply the manual updates, Allaire ClusterCATS may be removed from the Netscape plugin list. If this should happen, re-install Allaire ClusterCATS.

Failover problems when routers are not configured to timeout their ARP cache

When ClusterCATS appears to be ARPing correctly but there are persistent connectivity problems after Failover as occurred, there may be problem with one of the adjacent router's ARP cache timeout settings. If the ARP cache timeout is off then set it to some value, which is not too large, such as 2-30 seconds. Accessing the router configuration settings will be vendor specific; please refer to associated h/w and s/w documentation for router box.

ClusterCATS IP Failover subsystem for NT IIS creates and removes the "Aliased IP addresses" Web Site

The ClusterCATS IP failover subsystem creates an IIS Web Site named "Aliased IP addresses" when at least one IP address is 'aliased' on the local system. This Web Site is removed when the local system is no longer 'aliasing' any IP addresses. This Web Site must not be managed with the Microsoft Management Console (MMC). If this Web Site is selected or has its properties enumerated after the IP failover subsystem has deleted it, but while the MMC still has it displayed, various MMC error messages will be displayed. An MMC refresh operation can be performed to update the list of Web Sites and eliminate the stale view of the IP failover Web Site.

Uninstall Netscape NT (ONLY)

Uninstall may encounter difficulties removing the ClusterCATS entries from the obj.conf file. It will inform you that you must remove these entries by hand. To remove these entries, edit your Netscape Enterprise Server obj.conf file and remove the following files from your obj.conf file:

Init fn=load-modules shlib="<install-dir>/program/teserver_nes.dll" funcs="btcats_server_init,btcats_nsapi_AuthTrans,btcats_nsapi_NameTrans,btcats_ErrorFixup" 
Init fnInit fn="btcats_server_init"

NameTrans fn=btcats_nsapi_NameTrans

AuthTrans fn=btcats_nsapi_AuthTrans

Error fn=btcats_ErrorFixup reason="BrightTiger"

You will need to recycle you Netscape Enterprise Server for these Changes to take effect.

Multiple ClusterCATS Explorers viewing the same SmartClusters

Multiple ClusterCATS Explorers viewing one or more clusters simultaneously do not correctly handle displaying cluster deletions. Only the ClusterCATS Explorer where the delete requests were performed will see that the cluster has been deleted (cluster is removed from view). All other ClusterCATS Explorers will show the last cluster member as unreachable. To work around this problem, hide the deleted cluster from view.


Configuring the Apache Web Server

For information on Linux and Solaris, see Configuring Apache on Linux and Configuring Apache on Solaris.

Apache 1.3.6 and 1.3.9 are supported with the current module on all platforms. The current ColdFusion Apache 1.3.6 module will work without change with Apache 1.3.9.

Configuring Apache on Windows NT

The ColdFusion Module can be found in the installation directory (usually c:\cfusion\bin).

We assume below that your Apache installation is found in c:\Apache .

  1. Copy the module (ApacheModuleColdFusion.dll) to your modules directory under the Apache source directory.
    ex. c:\Apache\modules\ApacheModuleColdFusion.dll
  2. Edit the "httpd.conf" configuration file to contain the following line, this can be found in c:\Apache\conf:
    LoadModule coldfusion_module modules/ApacheModuleColdFusion.dll

Configuring Apache on Linux

For detailed instructions on installing and configuring Apache Web Server on Linux, refer to the /opt/coldfusion/webserver/apache/README file installed with ColdFusion.

Other issues:

Configuring Apache on Solaris

For detailed instructions on installing and configuring Apache Web Server on Solaris, refer to the /opt/coldfusion/webserver/apache/README file installed with ColdFusion.

The ColdFusion Server installation process can optionally autoconfigure the Apache web server for you.


Running Allaire Forums under ColdFusion 4.5

If you are running Allaire Forums with ColdFusion Server 4.5 you should be running with Allaire Forums 2.0.5. You should download Allaire Forums 2.0.5 from our product page if you are running an earlier version.

Allaire Forums is not supported on Linux.


Back to top