108
CONFIGURING AND ADMINISTERING COLDFUSION 10
Deploying ColdFusion Applications
L
ast
u
p
dated
7/9/2
01
2
Deployment considerations
After the archive file is created, you deploy by using standard ColdFusion J2EE configuration deployment techniques.
For more information, see Installing an EAR file or WAR files in Installing the J2EE 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
J2EE 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
” on page 65.
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
(J2EE configuration) directory.
Before you can use the cfcompile utility in the J2EE configuration, set the CFUSION_HOME, J2EEJAR, 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.