MACROMEDIA COLDFUSION 4.5-ADMINISTRING COLDFUSION SERVER Technical Information Page 79

  • Download
  • Add to my manuals
  • Print
  • Page
    / 174
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 78
74
CONFIGURING AND ADMINISTERING COLDFUSION 9
Deploying ColdFusion Applications
Last updated 2/21/2012
cfcompile webroot [directory-to-compile]
The following table describes these parameters:
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:
After you run the cfcompile utility, perform the following steps:
1 Back up your original CFML files
2 Copy the generated bytecode CFML files to the original directory
3 Deploy the application.
The J2EE Archive screen of the ColdFusion Administrator lets you create an EAR or WAR file that contains bytecode
versions of your application’s CFML files.
Parameter Description
webroot Fully qualified path to the web server root; for example, C:\Inetpub\wwwroot or
C:\coldfusion9\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.
Parameter Description
webroot Fully qualified path to the web server root; for example, C:\Inetpub\wwwroot or
C:\coldfusion9\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.
Page view 78
1 2 ... 74 75 76 77 78 79 80 81 82 83 84 ... 173 174

Comments to this Manuals

No comments