Macromedia colfusion mx 7 Manual
20
Chapter 2: Using the ColdFusion MX Administrator
You can also specify whether to use J2EE session variables. When you enable the J2EE session
variables, ColdFusion creates an identifier for each session and does not use the CFToken or
CFID cookie value. For more information, see ColdFusion MX Developer’s Guide.
variables, ColdFusion creates an identifier for each session and does not use the CFToken or
CFID cookie value. For more information, see ColdFusion MX Developer’s Guide.
Note: When using J2EE sessions, ensure that the session timeout, specified in the
WEB-INF/web.xml
WEB-INF/web.xml
session-timeout
element is longer than the session timeout that you specify in
the ColdFusion MX Administrator and longer than any
sessiontimeout
attribute specified in a
cfapplication
tag.
Mappings page
You use the Mappings page of the ColdFusion MX Administrator to add, update, and delete
logical aliases for paths to directories on your server. ColdFusion mappings apply only to pages
processed by ColdFusion MX with the
logical aliases for paths to directories on your server. ColdFusion mappings apply only to pages
processed by ColdFusion MX with the
cfinclude
and
cfmodule
tags. If you save CFML pages
outside of the web_root directory (or whatever directory is mapped to "/"), you must add a
mapping to the location of those files on your server.
mapping to the location of those files on your server.
Assume that the "/" mapping on your server points to C:\CFusionMX7\wwwroot, but all your
ColdFusion header pages reside in C:\2002\newpages\headers. In order for ColdFusion MX to
find your header pages, you must add a mapping in the ColdFusion MX Administrator that
points to C:\2002\newpages\headers (for example, add a mapping for /headers that points to
C:\2002\newpages\headers). In the ColdFusion pages located in C:\CFusionMX7\wwwroot, you
reference these header pages using /headers in your
ColdFusion header pages reside in C:\2002\newpages\headers. In order for ColdFusion MX to
find your header pages, you must add a mapping in the ColdFusion MX Administrator that
points to C:\2002\newpages\headers (for example, add a mapping for /headers that points to
C:\2002\newpages\headers). In the ColdFusion pages located in C:\CFusionMX7\wwwroot, you
reference these header pages using /headers in your
cfinclude
and
cfmodule
tags.
Note: ColdFusion mappings are different from web server virtual directories. For information on
creating a virtual directory to access a given directory using a URL in your web browser, consult your
web server’s documentation.
creating a virtual directory to access a given directory using a URL in your web browser, consult your
web server’s documentation.
Mail Server page
You use the Mail Server page of the ColdFusion MX Administrator to specify a mail server to
send automated e-mail messages. ColdFusion MX supports the Simple Mail Transfer Protocol
(SMTP) for sending e-mail messages and the Post Office Protocol (POP) for retrieving e-mail
messages from your mail server. To use e-mail messaging in your ColdFusion applications, you
must have access to an SMTP server and a POP account.
send automated e-mail messages. ColdFusion MX supports the Simple Mail Transfer Protocol
(SMTP) for sending e-mail messages and the Post Office Protocol (POP) for retrieving e-mail
messages from your mail server. To use e-mail messaging in your ColdFusion applications, you
must have access to an SMTP server and a POP account.
The ColdFusion MX Enterprise Edition supports mail server failover as well as additional mail
delivery options.
delivery options.
The ColdFusion implementation of SMTP mail uses a spooled architecture. This means that
when a
when a
cfmail
tag is processed in an application page, the messages generated might not be sent
immediately. If ColdFusion is extremely busy or has a large queue, delivery could occur after some
delay.
delay.
Note: For more information about the
cfmail
tag, see “Sending SMTP e-mail with the cfmail tag” in
Chapter 39, “Sending and Receiving E-Mail,” in ColdFusion MX Developer’s Guide.