- ColdFusion User Guide
- Introduction to ColdFusion
- Adobe ColdFusion (2021 release)
- Install ColdFusion- Zip Installer
- Install ColdFusion- GUI Installer
- ColdFusion Licensing and Activation
- ColdFusion Package Manager
- CFSetup configuration tool
- SAML in ColdFusion
- ColdFusion and Amazon S3
- ColdFusion and DynamoDB
- ColdFusion and Amazon SQS
- ColdFusion and Amazon SNS
- ColdFusion and MongoDB
- ColdFusion and Azure Blob
- ColdFusion and Azure Service Bus
- New and updated language enancements
- Multi-cloud storage services
- Multi-cloud RDS databases
- ColdFusion and Azure Cosmos DB
- Install ColdFusion
- ColdFusion server profiles
- Prepare to install ColdFusion
- Install the server configuration
- Install the JEE configuration
- Install ColdFusion Express
- Install integrated technologies
- Configure your system
- Troubleshoot installation issues
- Install ColdFusion silently
- Install Adobe ColdFusion (2016 release) hotfix
- ColdFusion (2018 release) - Install JEE configuration
- Use ColdFusion
- Performance Monitoring Toolset
- Auto-discovery of ColdFusion nodes and clusters
- Code profiler in ColdFusion Performance Monitoring Toolset
- Configure ColdFusion Performance Monitoring Toolset settings
- Install ColdFusion Performance Monitoring Toolset
- Overview of ColdFusion Performance Monitoring Toolset
- View cluster and node metrics
- View data source metrics
- View external services
- View incoming services
- View list of sites and busy connections
- View topology of sites
- Datastore Health Monitoring
- Performance Monitoring Toolset Update 1
- Secure Performance Monitoring Toolset with HTTPS/SSL
- Performance Monitoring Toolset deployment guide
- Adobe ColdFusion Builder extension for Visual Studio Code
- Getting started with Adobe ColdFusion Builder extension for Visual Studio Code
- Add a ColdFusion server
- Project Manager
- Work with ColdFusion code
- Profile preferences
- Debug applications
- Refactoring
- Services Browser
- RDS support
- PMT Code Profiler integration
- Security Analyzer report integration
- Known issues in this release
- Getting started with Adobe ColdFusion Builder extension for Visual Studio Code
- Use ColdFusion Builder
- About ColdFusion Builder
- System requirements | ColdFusion Builder
- Install ColdFusion Builder
- Edit code in ColdFusion Builder
- Manage servers in ColdFusion Builder
- Manage projects in ColdFusion Builder
- What’s new in Adobe ColdFusion Builder (2018 release)
- Frequently Asked Questions (FAQ) | Adobe ColdFusion Builder (2018 release)
- Debug applications in ColdFusion Builder
- ColdFusion Builder workbench
- ColdFusion Builder extensions
- Debugging Perspective in ColdFusion Builder
- Build mobile applications using ColdFusion Builder
- Bundled ColdFusion Server
- Debug mobile applications in ColdFusion Builder
- Use extensions in ColdFusion Builder
- Coldfusion API Manager
- Overview of Adobe ColdFusion API Manager
- Features in ColdFusion API Manager
- Get started with ColdFusion API Manager
- Install ColdFusion API Manager
- Authentication types
- Create and publish APIs
- Administrator
- Subscriber
- Throttling and rate limiting
- Notifications
- Connectors
- Set up cluster support
- Integrate ColdFusion and API Manager
- Metrics and Logging in API Manager
- Generate Swagger documents
- Configure SSL
- Known issues in this release
- Policies in ColdFusion API Manager
- Create a Redis cluster
- Multitenancy in API Manager
- Docker images for ColdFusion API Manager
- Configure and administer ColdFusion
- Administer ColdFusion
- Use the ColdFusion administrator
- Data Source Management for ColdFusion
- Connect to web servers
- Deploy ColdFusion applications
- Administer ColdFusion security
- Basic Troubleshooting and FAQs
- Work with Server Manager
- Use multiple server instances
- WebSocket Enhancements (ColdFusion 11)
- Security Enhancements (ColdFusion 11)
- Work with Server Monitor
- ColdFusion Administrator API Reference
- CFML Reference
- Introduction to CFML Reference
- Reserved words and variables
- ColdFusion tags
- ColdFusion functions
- Ajax JavaScript functions
- Ajax JavaScript functions
- Function summary Ajax
- ColdFusion.Ajax.submitForm
- ColdFusion.Autosuggest.getAutosuggestObject
- ColdFusion.Layout.enableSourceBind
- ColdFusion.MessageBox.getMessageBoxObject
- ColdFusion.ProgressBar.getProgressBarObject
- ColdFusion.MessageBox.isMessageBoxDefined
- JavaScriptFunctionsinColdFusion9Update1
- ColdFusion ActionScript functions
- ColdFusion mobile functions
- Application.cfc reference
- Script functions implemented as CFCs
- ColdFusion Flash Form style reference
- Styles valid for all controls
- Styles for cfform
- Styles for cfformgroup with horizontal or vertical type attributes
- Styles for box-style cfformgroup elements
- Styles for cfformgroup with accordion type attribute
- Styles for cfformgroup with tabnavigator type attribute
- Styles for cfformitem with hrule or vrule type attributes
- Styles for cfinput with radio, checkbox, button, image, or submit type attributes
- Styles for cftextarea tag and cfinput with text, password, or hidden type attributes
- Styles for cfselect with size attribute value of 1
- Styles for cfselect with size attribute value greater than 1
- Styles for cfcalendar tag and cfinput with dateField type attribute
- Styles for the cfgrid tag
- Styles for the cftree tag
- ColdFusion Flash Form Style Reference
- ColdFusion event gateway reference
- ColdFusion Event Gateway reference
- addEvent
- CFEvent
- CFEventclass
- Constructor
- Gateway development interfaces and classes
- getStatus
- setCFCPath
- setCFCMethod
- getOriginatorID
- getLogger
- getBuddyList
- getBuddyInfo
- IM gateway message sending commands
- IM Gateway GatewayHelper class methods
- onIncomingMessage
- onIMServerMessage
- onBuddyStatus
- onAddBuddyResponse
- onAddBuddyRequest
- IM Gateway CFC incoming message methods
- IM gateway methods and commands
- CFML CFEvent structure
- warn
- info
- setOriginatorID
- data command
- submit Multi command
- submit command
- setGatewayType
- setGatewayID
- setData
- setCFCListeners
- outgoingMessage
- getStatusTimeStamp
- numberOfMessagesReceived
- numberOfMessagesSent
- removeBuddy
- removeDeny
- removePermit
- setNickName
- setPermitMode
- setStatus
- SMS Gateway CFEvent structure and commands
- SMS Gateway incoming message CFEvent structure
- getStatusAsString
- getProtocolName
- getPermitMode
- getPermitList
- getNickName
- getName
- getDenyList
- getCustomAwayMessage
- getQueueSize
- getMaxQueueSize
- getHelper
- getGatewayType
- getGatewayServices
- getGatewayID_1
- getGatewayID
- getData
- getCFCTimeout
- setCFCTimeout
- getCFCPath
- getCFCMethod
- GatewayServices class
- Gateway interface
- GatewayHelper interface
- addPermit
- addDeny
- addBuddy
- error
- debug
- Logger class
- stop
- start
- CFML event gateway SendGatewayMessage data parameter
- restart
- fatal
- SMS gateway message sending commands
- ColdFusion C++ CFX Reference
- ColdFusion Java CFX reference
- WDDX JavaScript Objects
- Develop ColdFusion applications
- Introducing ColdFusion
- Changes in ColdFusion
- Changes in ColdFusion
- Replacement of JRun with Tomcat
- Security enhancements
- ColdFusion WebSocket
- Enhanced Java integration
- ColdFusion ORM search for indexing and search
- Solr enhancements
- Scheduler enhancements
- Integration with Microsoft Exchange Server 2010
- RESTful Web Services in ColdFusion
- Lazy loading across client and server in ColdFusion
- Web service enhancements
- Displaying geolocation
- Client-side charting
- Caching enhancements
- Server update using ColdFusion Administrator
- Secure Profile for ColdFusion Administrator
- Introduction to application development
- The CFML programming language
- Building blocks of ColdFusion applications
- Develop CFML applications
- Develop CFML applications
- Design and optimize a ColdFusion application
- Handle errors
- Use persistent data and locking
- Use ColdFusion threads
- Secure applications
- Client-side CFML (for mobile development)
- Use the ColdFusion debugger
- Debugging and Troubleshooting Applications
- Develop globalized applications
- REST enhancements in ColdFusion
- Authentication through OAuth
- Social enhancements
- Develop mobile applications
- Access and use data
- ColdFusion ORM
- ColdFusion and HTML5
- Flex and AIR integration in ColdFusion
- Request and present information
- Office file interoperability
- ColdFusion portlets
- Work with documents, charts, and reports
- Use web elements and external objects
- Use external resources
- Send and receive e-mail
- Interact with Microsoft Exchange servers
- Interact with remote servers
- Manage files on the server
- Use event gateways
- Create custom event gateways
- Use the ColdFusion extensions for Eclipse
- Use the data services messaging event gateway
- Use the data management event gateway
- Use the FMS event gateway
- Use the instant messaging event gateways
- Use the SMS event gateway
Adobe ColdFusion includes archive and deployment options that let you package applications and create archive files.
Archive and deployment options
ColdFusion includes the following archive and deployment options.
- ColdFusion archive files You can package your ColdFusion application's pages, data sources, and settings in a ColdFusion Archive (CAR) file. For more information, see Packaging applications in CAR files.
- JEE archives You can package your ColdFusion application as an Enterprise Application Archive (EAR) or Web Application Archive (WAR) file for easy deployment to a JEE application server. For more information, see Packaging applications in JEE archive files.
- Cfcompile utility The cfcompile utility lets you precompile the ColdFusion pages of your application, into Java class files. In addition, you can compile ColdFusion pages to bytecode and save this bytecode in files with the CFM, CFC, or CFR extension. For more information, see Using the cfcompile utility.
Packaging applications in CAR files
CAR files let you archive and deploy website configuration information, files, and applications. Use this feature to deploy your website applications to another location or to back up your files quickly and easily. You can manage CAR files using the Packaging & Deployment > ColdFusion Archives area of the ColdFusion Administrator.
Note: CAR file archiving and deployment is different from JEE archiving and packaging through EAR and WAR files. |
Perform the following steps when you archive and deploy site information:
- Create the archive definition. Identify the type of information to archive about a site. You can archive almost anything about the site, including directories, files, CFX tags, ColdFusion mappings, Solr collections, automated tasks, and server settings. Each archive definition that you create is assigned a name. You use this name each time you build or deploy its content.
- Build the archive. Select the name of the archive definition and specify a location to which you store the CAR file.
Deploy the archive .Specify the location of the CAR file and the location to which you restore the contents.
Note: ColdFusion_ does not deploy Administrator and RDS passwords, nor does it unpack archives created in earlier versions of ColdFusion._ |
For more information on creating, building, and deploying CAR files, see ColdFusion Administrator online Help.
While packaging your datasource setting in a CAR file keep the following in your mind, if there are data sources with the following drivers:
- MS Access,
- MS Access with Unicode, and
- Derby
or any other data sources referring to a directory path, CAR deployment does not show directory translation for these.
To fix this, do the following:
Go to Administrator and edit the data sources or use AdminAPI to edit those data sources.
OR
Back up the CAR file, un-archive it and then open file server_setting.xml.
In server_setting.xml, change the directory path for the required data sources.
Settings that are not migrated after applying Update 2 to ColdFusion (2016 release)
After you apply Hotfix 2 to ColdFusion (2016 release), some settings are not migrated.
You can view the list in the Archive Summary page (under the section Settings Never Migrated) while creating CAR as well as during deploying the CAR.
They are:
- Data and Services > Data Sources > Default data sources.
- Debugging and Logging > Debug Output Settings > Connector Port
- Extensions > CORBA Connectors > Registered CORBA Connectors
- Security > RDS > Enable RDS Service
- Security > Sandbox Security > Enable ColdFusion Sandbox Security
- Security > Secure Profile > Enable Secure Profile
- Server Settings > Settings > Default ScriptSrc Directory
- Server Settings > Font Management > User-defined fonts
- Server Settings > Mappings > Active ColdFusion Mappings > /CFIDE
- Server Settings > Mail > Password
- Server Settings > Mail > KeyStorePassword
- Server Settings > Mail > KeyPassword
Packaging applications in JEE archive files
When running ColdFusion in the JEE configuration, you deploy the ColdFusion application, in enterprise application archive (EAR) or web application archive (WAR) format, on a JEE application server. You then create your ColdFusion application, configuring resources (such as data sources), and storing CFM, CFC, and CFR files in the web application root or in the web server root. In earlier ColdFusion versions, your JEE administrator had to redo each of these steps when deploying your ColdFusion application onto a production JEE server.
The ColdFusion Administrator lets you create an EAR or WAR file that contains the entire application. This archive file contains the ColdFusion web application, settings for ColdFusion (such as data source definitions), and the CFM, CFC, and CFR files that your application uses.
Application packaging
The JEE Archive feature lets you quickly create an archive file that a JEE administrator can use to deploy your ColdFusion application.
Add a new archive definition and create an archive file
- Open the ColdFusion Administrator.
- Specify a unique name for the archive file (no extension) in the Archive Name field.
- Click Add. The Add New Archive screen appears.
- Specify archive settings on the Add New Archive screen.
- Click Create. ColdFusion creates an EAR or WAR file in the specified application distribution directory.
The following table describes the settings you make when creating or modifying an archive:
Setting |
Description |
---|---|
Archive Type |
Select EAR or WAR. |
Context Root (EAR only) |
Each JEE web application running in a server is rooted at a unique base URL, called a context root (or context path). The JEE application server uses the initial portion of the URL (that is, the portion immediately following http://hostname) to determine which web application services an incoming request. For example, if you are running ColdFusion with a context root of cfmx , you display the Administrator using the URL http://_hostname_/cfmx/CFIDE/administrator/index.cfmMost JEE application servers allow one application in each server instance to use a forward slash |
Serial Number |
Specifies a ColdFusion Enterprise Edition serial number. If you do not specify a valid ColdFusion Enterprise Edition serial number when creating the archive file, it is deployed as an Enterprise Edition evaluation version, which reverts to the Developer Edition after 30 days. |
COM Support |
If your application doesn't use COM support, you can reduce the size of the archive file by omitting the supporting files. |
Debugging |
If the current ColdFusion server is running with debugging enabled, you can disable debugging in the application contained in the archive file. |
Include CFML Source |
You can optionally deploy Java bytecode instead of CFML source code. For more information, see Sourceless distribution. |
ColdFusion Administrator |
If your application does not require modification by using the ColdFusion Administrator, you can reduce archive size and reduce security issues by omitting the Administrator files. |
Data sources |
The data source definitions to include in the archive file. |
Deployment considerations
After the archive file is created, you deploy by using standard ColdFusion JEE configuration deployment techniques. For more information, see Installing an EAR file or WAR files in Installing the JEE Configuration of Installing ColdFusion.
Post-deployment considerations
Depending on your application, the resources that it uses, and the environment in which it is deployed, you may need to perform post-deployment configuration, as follows:
- Mappings The ColdFusion mappings in the archived application refer to directories on the original computer. If those directories do not exist on the deployment computer, modify the ColdFusion mappings by using the ColdFusion Administrator or the Administrator API.
- Serial number JEE deployment is a ColdFusion Enterprise feature. To upgrade to the Enterprise Edition, use the ColdFusion Administrator or the Administrator API to enter a serial number .For more information on the Administrator API, see Administrator API.
Deployment considerations
After the archive file is created, you deploy by using standard ColdFusion JEE configuration deployment techniques. For more information, see Installing an EAR file or WAR files in Installing the JEE Configuration of Installing ColdFusion.
Using the cfcompile utility
You can use the cfcompile utility for the following purposes:
- Precompiling ColdFusion pages Precompile your application's CFM pages into Java class files. At runtime, ColdFusion does not have to compile CFM pages.
- Sourceless distribution Create CFM pages as Java bytecode. You can deploy these CFM pages instead of CFML source code. The cfcompile utility is located in the cf_root/bin (server configuration) or cf_webapp_root/WEB-INF/ cfusion /bin (JEE configuration) directory. Before you can use the cfcompile utility in the JEE configuration, set the CFUSION_HOME, JEEJAR, and WEBINF variables in the cfcompile.sh/cfcompile.bat file.
Precompiling ColdFusion pages
You can use the cfcompile utility to precompile ColdFusion pages (CFM, CFC, and CFR files). This can enhance initial page loading time at runtime.
Use the following command to compile ColdFusion pages into Java classes:
cfcompile webroot [directory-to-compile] |
The following table describes these parameters:
Parameter |
Description |
---|---|
webroot |
Fully qualified path to the web server root; for example, C:\Inetpub\wwwroot or C:\coldfusion10\cfusion\wwwroot. |
directory-to-compile |
Fully qualified path to the directory where the files to be compiled are located. This directory must be under the web root directory. If not specified, all ColdFusion templates in the web root directory are compiled. |
Sourceless distribution
You can use the cfcompile utility with the deploy option to create ColdFusion pages (CFM, CFC, and CFR files) that contain Java bytecode. You can then deploy the bytecode versions of the ColdFusion pages instead of the original CFML source code.
Use the following command to compile CFML files into bytecode format that you can deploy instead of CFML source code:
cfcompile -deploy webroot directory-to-compile output-directory |
The following table describes these parameters:
Parameter |
Description |
---|---|
webroot |
Fully qualified path to the web server root; for example, C:\Inetpub\wwwroot or C:\coldfusion10\cfusion\wwwroot. |
directory-to-compile |
Fully qualified path to the directory where the files to be compiled are located. This directory must be under the web root directory. This is required for the deploy option. |
output-directory |
Fully qualified path to the directory to contain the compiled deployable files. This cannot be the same directory as the source directory. |
After you run the cfcompile utility, perform the following steps:
- Back up your original CFML files
- Copy the generated bytecode CFML files to the original directory
Deploy the application.
Note: The JEE Archive screen of the ColdFusion_ Administrator lets you create an EAR or WAR file that contains bytecode versions of your application's CFML files._
Sign in to your account