
unixODBC, see www.unixODBC.com.
You must have the 'postmaster' process running on your system in order to use the PostgreSQL database. For
more information on PostgreSQL, see http://www.postgresql.org/.
In order to populate your PostgreSQL database with the example application data sources, see the
file /opt/coldfusion/database/PostgreSQL/README.
Changing the way Tokens are generated
Current behavior in ColdFusion is as follows:
l
CFID is assigned sequentially per machine. The entire value must consist of all decimal digits (0-9).
l
CFTOKEN - by default assigned as a random long integer. The value range is 0 < x < 2,147,483,647.
ColdFusion no longer validates any part of this token, allowing users to re-assign this to any value they
choose.
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 Solaris registry to ColdFusion 4.5.1
NOTE: This applies to Solaris only. 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.1 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.1.
The cfregup.sh script must be run as root on a machine with a running ColdFusion 3.x or 4.0 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.1 registry. Please note that since the new registry is created in a different place than the old
Page 16 of 26Release Notes - ColdFusion Server 4.5.1
08/22/2000file://C:\TEMP\cfserver451_release_notes.htm
Kommentare zu diesen Handbüchern