Table of Contents
Advertisement
Open the ColdFusion MX Administrator in a browser, using http://localhost/context-
13
root/CFIDE/administrator/index.cfm (external web server) or http://localhost:8300/context-
root/CFIDE/administrator/index.cfm (built-in JRun web server). Because opening the
ColdFusion MX Administrator for the first time automatically invokes the Configuration
Wizard, it is best to open the Administrator at this time.
Note: If you are accessing ColdFusion MX 6.1 from a remote computer, use the previous URL with
the host name or IP address of the remote computer instead of
Answer the questions asked by the Configuration Wizard.
14
Completion of the Configuration Wizard and display of the ColdFusion MX Administrator
indicates a successful install of ColdFusion MX.
Configure and manage your system, as described in
15
on page
49.
Code and test ColdFusion MX CFM pages. If you configured an external web server, store
16
CFM pages under your web root directory. If you are using the built-in web server, store CFM
pages under the web application root (jrun_root/servers/cfusion/cfusion-ear/cfusion-war) and
access these pages using a URL of the form http://hostname:8300/context-root/filename.cfm, as
follows:
hostname The machine name, IP address, localhost, or 127.0.0.1.
contextroot The context root for the ColdFusion MX web application. For more
information, see
filename The directory path and file to display. The path is relative to the cfusion-war
directory.
For example, to display a CFM file located at /opt/jrun4/servers/cfusion/cfusion-ear/cfusion-
war/eisapp/index.cfm using the built-in JRun web server and a context root of cfmx, you
specify the URL as http://127.0.0.1:8300/cfmx/eisapp/index.cfm.
Installing an EAR file or WAR files
If your computer is already running a J2EE application server, the installation wizard creates an
EAR file or WAR files, which you deploy using application-server-specific tools.
The ColdFusion MX J2EE configuration must run out of an expanded directory structure.
Different J2EE application servers have different functionality with regard to deployment and an
expanded directory structure, as follows:
•
Deploy compressed archive to working directory
as IBM WebSphere), the deployment process expands the EAR/WAR file into a working
directory and from that point forward, the expanded directory is considered to be the
application. For these application servers, you deploy the compressed EAR/WAR file and work
in the resulting directory structure.
•
Deploy expanded archive as working directory
4 and BEA WebLogic), the deployment process expands the EAR/WAR file into a temporary
directory and (conceptually), the compressed EAR/WAR file is still considered to be the
application. For these application servers, you must expand the EAR/WAR file manually and
then deploy the expanded directory structure, which becomes your working directory.
The following discussions provide installation procedures for Windows and UNIX. For more
about deployment and configuration, see
on page
43.
"Context root" on page
"ColdFusion MX J2EE deployment and configuration"
localhost
Chapter 4, "Configuring Your System,"
33.
On some J2EE application servers (such
On other application servers (such as JRun
Installing an EAR file or WAR files
.
39
Advertisement
Table of Contents
