The ColdFusion Getting Started Server enables you to quickly setup a development or production instance of a Server without following the installation procedure. The ColdFusion Getting Started Server is a new ‘lighter’ version of the ColdFusion Server and is ideally suited for developers to quickly setup and run a ColdFusion Server for testing and debugging purposes.
Also, since setting up a Getting Started Server involves just extracting the Server directory, it can be used on headless production servers too by enabling the secure profile. However, to enable secure profile for the server, you need to use the ColdFusion Administrator Console.
You can quickly get your Getting Started Server up and running by performing the following simple tasks.
Using the compressed archive (.zip)
To uncompress and use the ColdFusion Getting Started Server, perform the following tasks:
- Get the compressed archive for your platform.
- Extract the archive.
- (Optional) Go to <ARCHIVE_ROOT> and open the config.ini file for editing.
- (Optional) Add valid values for the following parameters:
- password_admin – Enter a password for accessing the Administration Console.
- password_rds – Enter a password for the RDS access (if needed). Note that RDS is enabled by default for the Getting Started Server with default password. However, you can change the credentials.
- license_key – Enter a valid license key or leave it blank for using the developer version.
- license_key_previous – In case of upgrade or upsell, enter a valid license key of the previous version of ColdFusion. Or, you can just leave this field blank.
- Save the file.
- Go to <ARCHIVE_ROOT>/cfusion/bin and invoke the startup script for your platform. A compatible JRE is included along with this Server. However, if you wish to change the JRE, ensure.:
- You have Java SE runtime installed and is available in the PATH
- You have the JAVA_HOME environment variable pointing to JRE 1.7 or later. If you don’t want the Server to pick up the JRE details from the system variable, you can set it up in the jvm.config file that is under cfusion\bin. For instance, java.home= C:\Program Files (x86)\Java\jre . Note that it has to be the server JRE. For information on server JRE you can refer to this document.
- On Windows – Double-click the cfstart.bat file to start the Getting Started Server.
- On Linux – From a terminal window, run the cfstart.sh file as a privileged user.
- Login to Administration Console at http://127.0.0.1:8500/CFIDE/administrator/ and start configuring your server.
|Note: If you are planning to use the server for development purpose only, steps 3 and 4 are optional. For development purpose, just extract the archive and run the executable. The default admin password is 'admin'.|
Using the EAR file
Optionally, you can download the EAR version of the ColdFusion Getting Started Server and deploy it on any ColdFusion-supported application server.
If you want to deploy on a 64-bit application server you have to deploy the 64-bit cfusion.war with application server’s Java set to 64-bit. Similarly, you can deploy a 32-bit cfusion.war on a 32-bit application server.
After you extract the compressed archive, you will see the sub-directories under the cfusion directory. The following list describes what each sub directory contains:
- bin: Programs for starting, stopping, and viewing information for the ColdFusion Getting Started Server. It also contains the password reset script for server administrator.
- cache: Repository for temporary files.
- cfx: Sample C++ and Java CFX files with their supporting files.
- charting: Files for the ColdFusion Getting Started Server graphing and charting engine.
- CustomTags: Repository that will contain your custom tags.
- db: The sample Apache Derby databases for all platforms.
- gateway: Files for ColdFusion event gateways.
- jintegra: (Applies only for Windows) JIntegra programs, libraries, and other supporting files.
- lib: JAR, XML, property, and other files that are base libraries for the ColdFusion Getting Started Guide.
- logs: Repository for the log files. JRE-specific log files are in the runtime/logs directory. Console outputs are logged in to start.log instead of cfserver.log.
- Mail: Repository for spooled mail and mail that cannot be delivered.
- registry: (UNIX only) Contains a file to store registry settings.
- runtime: Programs and supporting files for running the Server. Also, this directory contains the Tomcat libraries. The conf directory in runtime contains all Tomcat configuration files.
- stubs: Contains the web service files.
- wwwroot: The default web root directory for the built-in web server. Do not remove this directory.
The ColdFusion Getting Started Server can be used for quickly evaluating the ColdFusion Server. You need to understand that not all the features of the ColdFusion Server are available in the ColdFusion Getting Started Server.
The following limitations are applicable for the ColdFusion Getting Started Server:
- No support for SOLR service.
- No support for the Microsoft .NET platform.
- No support for remote administration.
- No PDF generation support.
- To configure any of these previously mentioned services with the server, you can download and install the standalone .NET installer and the Remote Admin component installer, which contains SOLR server/Remote admin component and has PDF Generation support.