Introduction to ColdFusion

What is ColdFusion?

ColdFusion is a rapid web-application development platform built around CFML (ColdFusion Markup Language). It lets you query databases, send email, consume web services, and render HTML responses with far less ceremony than most general-purpose languages. A single CFML tag can replace dozens of lines of boilerplate in other languages.

The platform has two layers:

• CFML — the language itself: a hybrid of HTML-like tags (<cfquery>, <cfloop>) and a modern ECMAScript-style scripting block (<cfscript>).
• The CFML engine — the Java-based runtime that compiles .cfm/.cfc files to bytecode and executes them inside a servlet container (historically JRun, today Apache Tomcat).

CFML offers two syntaxes that compile to identical bytecode — tags (left) and cfscript (right).

A brief history of CFML

The story of ColdFusion starts in 1995, long before Ruby on Rails or Node.js, with a small startup called Allaire Corporation.

Allaire Corporation, founded in 1995 — the original home of ColdFusion and HomeSite.

Thirty years of CFML: from Allaire's 1995 launch through three corporate owners to today's Adobe CF 2025 and the parallel open-source Lucee track.

CFML was one of the web's original "batteries included" platforms. While other stacks require composing separate libraries for database access, file I/O, and HTTP clients, ColdFusion ships all of that in the core runtime. This philosophy still defines it today.

Problems ColdFusion solves

1. Database access without boilerplate

In most languages you open a connection, prepare a statement, bind parameters, iterate a result set, and close the connection. In CFML:

<cfquery name="users" datasource="myDB">
  SELECT id, name, email FROM users WHERE active = 1
</cfquery>

<cfoutput query="users">
  #users.name# — #users.email#<br>
</cfoutput>

The engine manages the connection pool, parameterises the query, and returns a strongly-typed query object you can iterate with a single tag.

2. File and email operations in one line

<!--- Send email --->
<cfmail to="user@example.com" from="app@example.com" subject="Welcome" type="html">
  <p>Your account is ready.</p>
</cfmail>

<!--- Upload a file --->
<cffile action="upload" fileField="myFile" destination="/var/uploads" nameConflict="makeUnique">

3. HTTP and web-service consumption

<cfhttp url="https://api.example.com/data.json" method="GET" result="resp">
  <cfhttpparam type="header" name="Authorization" value="Bearer #token#">
</cfhttp>

<cfset data = deserializeJSON(resp.fileContent)>

4. Rapid page rendering

ColdFusion pages are compiled to Java bytecode on first request and cached. Subsequent requests hit the bytecode cache directly, giving competitive throughput without a separate compile step during development.

How ColdFusion's architecture works

The ColdFusion request pipeline: browser → (optional) reverse proxy → Tomcat → CFML engine → JDBC datasource pool → response.

Key architectural points:

• Everything runs on the JVM. You can call any Java class from CFML, use Java libraries on the classpath, and read JVM metrics with standard tools.
• Datasources are named connection pools configured in the CF Admin or via Application.cfc. Pages reference them by name, not by connection string.
• Application scope is shared across all requests within one application context, making in-memory caching trivial.
• The web root is a folder watched by the engine; dropping a .cfm file there makes it immediately accessible with no restart or deploy step.

ColdFusion and the JEE platform

ColdFusion is built on top of the Java Enterprise Edition (JEE) platform and uses a JEE application server for its core services — database connectivity, naming and directory services, and other runtime infrastructure. This is not just an implementation detail: it directly shapes what you can do with ColdFusion applications.

ColdFusion can be deployed in two ways:

• Server configuration — ColdFusion ships with a bundled JEE server (Apache Tomcat). This is the standard setup and what you are using in this lab.
• JEE configuration (Enterprise only) — ColdFusion can be deployed as a WAR/EAR on an independent JEE application server such as IBM WebSphere, Oracle WebLogic, or JBoss.

By running on top of the JEE platform, ColdFusion inherits its power while hiding its complexity behind CFML tags and functions. This also means ColdFusion pages can integrate directly with the Java ecosystem:

Adobe ColdFusion vs. Lucee

Both engines execute the same CFML language core, but they differ in licensing, extension model, and some built-in capabilities.

Adobe ColdFusion 2025 (port 8500) and Lucee 7 (port 8888) — both run in your lab environment.

• Greenfield projects can use either. Lucee + CommandBox is popular for local development because of fast cold starts and zero licensing cost.
• Enterprise Adobe shops use CF for support contracts, CF Admin policies, and built-in PDF/Office features.
• This course uses both: Adobe ColdFusion 2025 on port 8500 is the primary engine; Lucee 7 on port 8888 lets you verify cross-engine compatibility.

Your lab environment

Your lab microVM is pre-configured with both engines running:

The iximiuz Labs interface: lesson content and task checklist on the left, live lab environment on the right.

Your lab microVM boots with CF 2025 (8500), Lucee 7 (8888), and VS Code all ready — no installation needed.

Tip: Files you create in VS Code land directly in the CF 2025 webroot. Open a Terminal inside VS Code to also write to the Lucee webroot.

Right-click the CF Admin button → "Open Link in New Tab" to get a full-screen view.

CF Admin in full-screen — enter password admin to log in.

Verify services

Open the Terminal tab in your lab and run each command. A 200 status code confirms the service is ready.

# Verify Adobe ColdFusion 2025 (should return HTTP 200)
curl -s -o /dev/null -w "%{http_code}\n" http://localhost:8500/index.cfm

# Verify Lucee via CommandBox (should return HTTP 200)
curl -s -o /dev/null -w "%{http_code}\n" http://localhost:8888/index.cfm

Create and test your first ColdFusion page

1. In VS Code, create a file called hello.cfm in the webroot.
2. Add this content:

<cfset greeting = "Hello from ColdFusion 2025!">
<cfoutput>#greeting#</cfoutput>

3. Verify it through the engine:

curl -s http://localhost:8500/hello.cfm
# Expected output: Hello from ColdFusion 2025!

If you see the greeting text (not the raw CFML source), the engine compiled and executed your file correctly.

When all the checks above are green, this lesson is complete. Your progress is saved automatically — move straight on to the next lesson.

Key concepts reference