Using server variables

Server variables are associated with a single ColdFusion Server. They are available to all applications that run on the server. Use server variables for data that must be accessed across clients and applications, such as global server hit counts.

Server variables do not time out, but they are lost when the server shuts down. You can delete server variables.

Server variables are stored on a single server. As a result, you should not use server variables if you use ColdFusion on a server cluster.

You access and manipulate server variables the same way use Session and application variables, except you use the variable prefix Server.

Caution: To preserve data integrity, put code that uses server variables inside cflock tags. You do not have to lock access to built-in server variables.

ColdFusion provides the following standard built-in read-only server variables:

Variable

Description

Server.ColdFusion.AppServer

The name of the J2EE application server ColdFusion is using. For ColdFusion MX Server editions, which have an integrated application server, the name is JRun4.

Server.ColdFusion.Expiration

The date, in ODBC date format, on which the ColdFusion Server license expires. (A null string in all but trial versions of ColdFusion.)

Server.ColdFusion.ProductLevel

The server product level, such as Enterprise.

Server.ColdFusion.ProductName

The name of the product (ColdFusion Server).

Server.ColdFusion.ProductVersion

The version number for the server that is running, such as 6,0,0.

Server.ColdFusion.Rootdir

Directory under which ColdFusion is installed, such as C:\cfusion.

Server.ColdFusion.SerialNumber

The serial number assigned to this server installation.

Server.ColdFusion.SupportedLocales

The locales, such as English (US) and Spanish (Standard), supported by the server.

Server.OS.AdditionalInformation

Additional information provided by the operating system, such as the Service Pack number.

Server.OS.arch

The processor architecture, such as x86 for Intel Pentium processors.

Server.OS.BuildNumber

The specific operating system build, such as 1381

Server.OS.Name

The name of the operating system, such as Windows NT.

Server.OS.Version

The version number of the operating system, such as 4.0.

Developing ColdFusion MX Applications with CFML
Using Persistent Data and Locking

Variable	Description
Server.ColdFusion.AppServer	The name of the J2EE application server ColdFusion is using. For ColdFusion MX Server editions, which have an integrated application server, the name is JRun4.
Server.ColdFusion.Expiration	The date, in ODBC date format, on which the ColdFusion Server license expires. (A null string in all but trial versions of ColdFusion.)
Server.ColdFusion.ProductLevel	The server product level, such as Enterprise.
Server.ColdFusion.ProductName	The name of the product (ColdFusion Server).
Server.ColdFusion.ProductVersion	The version number for the server that is running, such as 6,0,0.
Server.ColdFusion.Rootdir	Directory under which ColdFusion is installed, such as C:\cfusion.
Server.ColdFusion.SerialNumber	The serial number assigned to this server installation.
Server.ColdFusion.SupportedLocales	The locales, such as English (US) and Spanish (Standard), supported by the server.
Server.OS.AdditionalInformation	Additional information provided by the operating system, such as the Service Pack number.
Server.OS.arch	The processor architecture, such as x86 for Intel Pentium processors.
Server.OS.BuildNumber	The specific operating system build, such as 1381
Server.OS.Name	The name of the operating system, such as Windows NT.
Server.OS.Version	The version number of the operating system, such as 4.0.

Using server variables

Comments