Administering ColdFusion MX
Trademarks Afterburner, AppletAce, Attain, Attain Enterprise Learning System, Attain Essentials, Attain Objects for Dreamweaver, Authorware, Authorware Attain, Authorware Interactive Studio, Authorware Star, Authorware Synergy, Backstage, Backstage Designer, Backstage Desktop Studio, Backstage Enterprise Studio, Backstage Internet Studio, ColdFusion, Design in Motion, Director, Director Multimedia Studio, Doc Around the Clock, Dreamweaver, Dreamweaver Attain, Drumbeat, Drumbeat 2000, Extreme 3D, Fireworks, Flash, Fontographer, FreeHand, FreeHand Graphics Studio, Generator, Generator Developer's Studio, Generator Dynamic Graphics Server, JRun, Knowledge Objects, Knowledge Stream, Knowledge Track, Lingo, Live Effects, Macromedia, Macromedia M Logo & Design, Macromedia Flash, Macromedia Xres, Macromind, Macromind Action, MAGIC, Mediamaker, Object Authoring, Power Applets, Priority Access, Roundtrip HTML, Scriptlets, SoundEdit, ShockRave, Shockmachine, Shockwave, Shockwave Remote, Shockwave Internet Studio, Showcase, Tools to Power Your Ideas, Universal Media, Virtuoso, Web Design 101, Whirlwind and Xtra are trademarks of Macromedia, Inc. and may be registered in the United States or in other jurisdictions including internationally. Other product names, logos, designs, titles, words or phrases mentioned within this publication may be trademarks, servicemarks, or tradenames of Macromedia, Inc. or other entities and may be registered in certain jurisdictions including internationally. This product includes code licensed from RSA Data Security. This guide contains links to third-party websites that are not under the control of Macromedia, and Macromedia is not responsible for the content on any linked site. If you access a third-party website mentioned in this guide, then you do so at your own risk. Macromedia provides these links only as a convenience, and the inclusion of the link does not imply that Macromedia endorses or accepts any responsibility for the content on those third-party sites. Apple Disclaimer APPLE COMPUTER, INC. MAKES NO WARRANTIES, EITHER EXPRESS OR IMPLIED, REGARDING THE ENCLOSED COMPUTER SOFTWARE PACKAGE, ITS MERCHANTABILITY OR ITS FITNESS FOR ANY PARTICULAR PURPOSE. THE EXCLUSION OF IMPLIED WARRANTIES IS NOT PERMITTED BY SOME STATES. THE ABOVE EXCLUSION MAY NOT APPLY TO YOU. THIS WARRANTY PROVIDES YOU WITH SPECIFIC LEGAL RIGHTS. THERE MAY BE OTHER RIGHTS THAT YOU MAY HAVE WHICH VARY FROM STATE TO STATE. Copyright 19992002 Macromedia, Inc. All rights reserved. This manual may not be copied, photocopied, reproduced, translated, or converted to any electronic or machine-readable form in whole or in part without prior written approval of Macromedia, Inc. Part Number ZCF60M400 Acknowledgments Project Management: Stephen M. Gilson Writing: Michael Stillman Editing: Linda Adler and Noreen Maher
First Edition: May 2002 Macromedia, Inc. 600 Townsend St. San Francisco, CA 94103

CONTENTS

ABOUT THIS BOOK. V
Developer resources. vi About Macromedia ColdFusion MX documentation. vii Printed and online documentation set. vii Viewing online documentation. viii Getting answers. viii Contacting Macromedia. viii
CHAPTER 1 Administering ColdFusion. 1
About the ColdFusion Administrator.2 Accessing user assistance.2 Administrator layout.3 Server Settings section.4 Data & Services section.4 Debugging & Logging section.5 Extensions section.5 Security section.5
CHAPTER 2 Basic ColdFusion MX Administration. 7
Initial administration tasks.8 Server Settings section.9 Settings page.9 Caching page.9 Client Variables page.10 Memory Variables page.12 Mappings page.13 Mail Server page.13 Charting Settings page.15 Java and JVM Settings page.15 Archives and Deployment page.16 Settings Summary page.16 Data & Services section.17 Data Sources page.17 Verity Collections page.17 Verity K2 Server page.18 Web Services page.18
Debugging & Logging section.19 Debugging Settings page.19 Debugging IP Addresses page.22 Logging Settings page.22 Log Files page.23 Scheduled Tasks page.24 System Probes page.24 Code Compatibility Analyzer page.24 Extensions section.25 Java Applets page.25 CFX Tags page.25 Custom Tag Paths page.25 CORBA Connectors page.25 Security section.27 CF Admin Password page.27 RDS Password page.27 Sandbox Security page.27 Custom Extensions.28
CHAPTER 3 Data Source Management. 29
About JDBC.30 Supplied drivers.31 Adding data sources.32 Adding data sources in the Administrator.32 Connecting to DB2 UDB for OS/390.36 Connecting to DB2 Universal Database 6.2, 7.2.37 Connecting to Informix 9.x.38 Connecting to Microsoft Access.39 Connecting to Microsoft SQL Server 7.x, 2000.41 Connecting to MySQL.43 Connecting to ODBC Socket.44 Connecting to Oracle R3 (8.1.7), Oracle 9i.45 Connecting to other data sources.46 Connecting to Sybase 11.5, 11.9, 12.0, and 12.5.47

Limit the maximum number of cached queries on the server to [n] queries

Client Variables page

Client variables let you store user information and preferences between sessions. Using information from client variables, you can customize page content for individual users. You enable client variable default settings in ColdFusion MX on the Client Variables page of the Administrator. ColdFusion MX lets you store client variables in the following ways: In a data source If your data source uses a bundled JDBC driver, ColdFusion can automatically create the necessary tables. If your data source uses the ODBC Socket or a third-party JDBC driver, you must manually create the necessary CDATA and CGLOBAL database tables. For more information, see Developing ColdFusion MX Applications with CFML.
As cookies in users web browsers In the operating system registry
Caution: Macromedia recommends that you do not store client variables in the registry because it can critically degrade performance of the server. If you do use the registry to store client variables, you must allocate sufficient memory and disk space.
You can override settings specified in the Client Variables page using the attributes of the cfapplication tag. For more information, see Developing ColdFusion MX Applications with CFML.
The following table compares these storage options:
Storage type Data source Advantages Disadvantages

Can use existing data

source Portable: not tied to the host system or operating system
Requires database transaction to

read/write variables

More complex to implement
Browser cookies Simple implementation Good performance
Users can configure browsers to

disallow cookies

Can be set to expire
automatically Client-side control
ColdFusion MX limits a cookies

data to 4 KB

Netscape Navigator allows only 20
cookies from one host; ColdFusion MX uses three cookies to store read-only data, leaving only 17 cookies available

System registry

Simple implementation Good performance Registry can be exported

easily to other systems

Server Port

Connection Timeout (seconds) Spool Interval (seconds) Verify Mail Server Connection
Mail Logging Settings area Select preferences for handling mail logs, as described in the following table:
Setting Error Log Severity Description From the drop-down list box, select the type of SMTP-related error message to write to a log file. The options are: Debug, Warning, Debug, Information, and Error. Enable this option to save to a log file the To, From, and Subject fields of all e-mail messages.
Log all e-mail messages sent by ColdFusion
ColdFusion MX writes sent mail and mail error logs to either of the following directories: \cfusion\Log, in Windows /opt/coldfusion/log, on Solaris, Linux, and HP-UX The following table describes the e-mail log files:
Log mailsent.log mail.log Description Records sent e-mail messages Records general e-mail errors

Charting Settings page

The ColdFusion charting and graphing engine lets you produce highly customizable business graphics, in a variety of formats, using the cfchart tag. You use the Charting page in the Administrator to control characteristics of the engine. The following table describes the caching and thread settings for the ColdFusion charting and graphing engine:
Setting Cache Type Maximum number of images in cache Max number of charting threads Disk cache location Description Set the cache type. Charts can be cached either in memory or to disk. In memory caching is faster, but more memory intensive. Specify the maximum number of charts to store in the cache. After the cache is full, if you generate a new chart, ColdFusion discards the oldest chart in the cache. Specify the maximum number of chart requests that can be processed concurrently. The minimum number is 1 and the maximum is 5. Higher numbers are more memory intensive. When caching to disk, specify the directory in which to store the generated charts.
Java and JVM Settings page
The Java and JVM Settings page lets you specify the following settings, which enable ColdFusion MX to work with Java:
Setting Java Virtual Machine Path Description The absolute file path to the location of the Java virtual machine (JVM): jvm.dll in Windows or jvm.so in Solaris, Linux, and HP-UX. The JVM initial heap size. Default is 8196 MB. The JVM maximum heap size. Default is 512 MB. The file path(s) to the directories that contain the Java classes used by ColdFusion MX. Use a comma-delimited list for multiple entries; for example, c:\foo,d:bar The arguments to the JVM. Use a space to separate multiple entries; for example, -Xint -Xincgc

Switch -n -s # -h -p Description/Comment Suppress column headers (useful for saving output to a file). Display output in a single line (delay display of the first line so cfstat can display meaningful values in the per-second counters). Where # is an integer, delay display output by # seconds. If you do not specify an integer, cfstat returns one line. Web server hostname (localhost is the default). Web server listening port number (80 is the default).
The following figure shows cfstat output in a Windows 2000 environment:
Debugging IP Addresses page
You use the Debugging IP Addresses page to restrict debugging output to one or more IP addresses. You can add and remove IP addresses.
Note: If you do not specify IP addresses, and debugging options are active, debugging output displays for all users.

Logging Settings page

You use the Logging Settings page of the Administrator to change ColdFusion MX logging options. The following table describes the settings:
Setting Log directory* Description Directory to which error log files are written.
Maximum file size Set the maximum file size for log files. Once a file hits this size, it will be (kb) automatically archived. Maximum number of archives Use operating system logging facilities Set the maximum number of log archives to create. After reaching this limit, files will be deleted in order of oldest to newest. Log messages using your operating system logging facility (EventLog in Windows; syslog on Solaris, Linux, and HP-UX). ColdFusion log messages are also written to the standard ColdFusion MX log files.
Log the names of pages that take longer than the specified interval to Log slow pages taking longer than process. Logging slow pages can help you diagnose potential problems or bottlenecks in your ColdFusion applications. Entries are written to [n] seconds server.log.
Setting Log all CORBA calls Enable logging for scheduled tasks
Description Log all CORBA calls. Log ColdFusion Executive task scheduling.

Log Files page

The Log Files page of the Administrator lets you perform operations on log files, such as searching, viewing, downloading, archiving, and deleting. Click on a Log File icon, located in the Actions column of the Available Log Files table, to search, view, download, archive, or delete a log file. For more information, see the online Help. The following table describes the ColdFusion MX log files:

Log rdservice.log Description Records errors occurring in the ColdFusion Remote Development Services (RDS). This service provides remote HTTP-based access to files and databases. Records every ColdFusion MX error reported to a user. Application page errors, including ColdFusion MX syntax, ODBC, and SQL errors are written to the log file. Records errors that occur in the web server and the ColdFusion MX stub. Records stacktraces for exceptions that occur in the server. Records scheduled events that have been submitted for execution. Indicates whether task submission was initiated and whether it succeeded. Provides the scheduled page URL, the date and time executed, and a task ID. Records errors for ColdFusion MX. Records errors generated in custom tag processing. Records errors associated with Site Archive and Restore operations. Records errors generated by an SMTP mail server. Records messages sent by ColdFusion MX.

application.log

webserver.log exceptions.log scheduler.log
server.log customtag.log car.log mail.log mailsent.log

Scheduled Tasks page

You use the Scheduled Tasks page to schedule the execution of local and remote web pages and to generate static HTML pages. The scheduling facility is useful for applications that do not require user interactions or customized output. ColdFusion developers use this facility to schedule daily sales reports, corporate directories, statistical reports, and so on. Information that is read more often than written is a good candidate for scheduled tasks. Instead of executing a query to a database every time the page is requested, ColdFusion MX renders the static page with information generated by the scheduled event. Response time is faster because no database transaction takes place. You can run scheduled tasks once; on a specified date; or at a specified time, daily, weekly, or monthly. You can run a scheduled task daily, at a specified interval, or between specified dates. The Schedule Task page lets you create, edit, and delete scheduled tasks. For more information, see the online Help.

System Probes page

System probes help you evaluate the status of your ColdFusion applications. Like scheduled tasks, they access a URL at a specified interval, but they can also check for the presence or absence of a string in the URL. If the URL contents are unexpected, or if an error occurred while accessing the URL, the probe can send an e-mail alert to the address specified in the System Probes page. The probe can also execute a script to perform a recovery action, such as restarting the server. All probe actions are logged in logs/ probes.log. The System Probes page also displays the status of each probe. You use the buttons in the Actions column in the System Probes table to perform the following actions:

Note: JDBC is not an acronym; however, it is often believed to stand for Java DataBase Connectivity.
The following table describes the four types of JDBC drivers:
Type 1 Name JDBC-ODBC bridge Description Translates JDBC calls into ODBC calls, and sends them to the ODBC driver. Advantages Allows access to many different databases. Disadvantages The ODBC driver, and possibly the client database libraries, must reside on the ColdFusion server computer. Performance is also below par. Macromedia does not recommend this driver type unless your application requires specific features of these drivers. 2 Native-API/ Converts JDBC calls into database-specific calls. partly Java driver Advantages Better performance than Type 1 Driver. Disadvantages The vendors client database libraries must reside on the same computer as ColdFusion. Macromedia does not recommend this driver type unless your application requires specific features of these drivers. 3 JDBC-Net pure Java driver Translates JDBC calls into the middle-tier server, which then translates the request to the database-specific native-connectivity interface. Advantages No need for vendors database libraries to be present on client computer. Can be tailored for small size (faster loading). Disadvantages the middle-tier. 4 Database-specific code must be executed in
Native-protocol/ Converts JDBC calls into the network protocol used directly by all-Java driver the database. Advantages Fast performance. No special software needed on the computer on which you run ColdFusion. Disadvantages Many of these protocols are proprietary, requiring a different driver for each database.
Chapter 3 Data Source Management

Supplied drivers

The following table shows the database drivers supplied with ColdFusion and where you can find more information:
Driver DB2 UDB for OS/390 DB2 Universal Database 6.2, 7.2 Informix 9.x Microsoft Access Microsoft SQL Server 7.x, 2000 MySQL ODBC Socket Oracle R3 (8.1.7), Oracle 9i Other Sybase 11.5, 11.9, 12.0, 12.Type Reference Connecting to DB2 UDB for OS/390 on page 36 Connecting to DB2 Universal Database 6.2, 7.2 on page 37 Connecting to Informix 9.x on page 38 Connecting to Microsoft Access on page 39 Connecting to Microsoft SQL Server 7.x, 2000 on page 41 Connecting to MySQL on page 43 Connecting to ODBC Socket on page 44 Connecting to Oracle R3 (8.1.7), Oracle 9i on page 45 Connecting to other data sources on page 46 Connecting to Sybase 11.5, 11.9, 12.0, and 12.5 on page 47

Adding data sources

In the ColdFusion Administrator, you configure your data sources to communicate with ColdFusion. Once you add a data source to the Administrator, you access it by name in any CFML tag that establishes database connections; for example, cfquery. During a query, the data source tells ColdFusion which database to connect to and what parameters to use for the connection. The ColdFusion Administrator organizes all the information about a ColdFusion MX servers database connections in a single, easy-to-manage location. In addition to adding new data sources, you can use the ColdFusion Administrator to correct for changes to your database, such as relocation, renaming, or changes in security permissions.

The Administrator configures the following ODBC connection string:
DSN=odbcdsnname;APP=RaiseGenerator;WSID=TWriter01
In the preceding string, odbcdsnname is the name of the ODBC DSN. This is the string that the Microsoft Access or ODBC Socket driver uses to connect to the data source at runtime.
Note: The connectstring tag attribute is not supported in ColdFusion MX.
Adding data source notes and considerations When adding data sources to ColdFusion MX, keep these guidelines in mind: Data source names should be all one word. Data source names can contain only letters, numbers, and the underscore. Data source names should not contain special characters. Although data source names are not case-sensitive, you should use a consistent capitalization scheme. A data source must exist in the ColdFusion Administrator before you use it on an application page to retrieve data.
Connecting to DB2 UDB for OS/390
Use the settings in the following table to connect ColdFusion to DB2 UDB for OS/390 data sources:
Setting CF Data Source Name Server Port Username Description The data source name (DSN) used by ColdFusion to connect to the data source. The name of the server that hosts the database that you want to use. If the database is local, enclose the word local in parentheses. The number of the TCP/IP port that the server monitors for connections. The user name that ColdFusion passes to the JDBC driver to connect to the data source if a ColdFusion application does not supply a user namefor example, in a cfquery tag. The password that ColdFusion passes to the JDBC driver to connect to the data source if a ColdFusion application does not supply a passwordfor example, in a cfquery tag. (Optional) A description for this connection. A field that passes database-specific parameters, such as login credentials, to the data source. ColdFusion establishes a connection to a data source for every operation that requires one. Enable this option to improve performance by caching the data source connection. The maximum number of minutes after the data source connection is made that you want ColdFusion to cache a connection after it is used. The time (in seconds) that the server waits between cycles to check for expired data source connections to close.

Use the settings in the following table to connect ColdFusion to Microsoft Access data sources:
Setting CF Data Source Name Database File System Database File Description The data source name (DSN) used by ColdFusion to connect to the data source. The password required to connect to the data source. If you want to secure access to the specified database file, click Browse Server to locate and enter a database that contains database security information. The system database is usually located in winnt\system32\system.mdw. If selected, ColdFusion does not pass a user name or password when requesting a connection. The Microsfot Access driver uses the default user name and password. (Optional) A description for this connection. The user name that the driver uses to connect to the data source if an application requests a connection without supplying a username. The password that the driver uses to connect to the data source if an application requests a connection without supplying a password. The user name that ColdFusion passes to the JDBC driver to connect to the data source if a ColdFusion application does not supply a user namefor example, in a cfquery tag. The password that ColdFusion passes to the JDBC driver to connect to the data source if a ColdFusion application does not supply a passwordfor example, in a cfquery tag. The time (in tenths of a second) before a request for a ColdFusion page times out. The total number of bytes that ColdFusion uses to cache application pages. Enter a value to optimize ColdFusion performance. A field that passes database-specific parameters, such as login credentials, to the data source. ColdFusion establishes a connection to a data source for every operation that requires one. Enable this option to improve performance by caching the data source connection. The maximum number of minutes after the data source connection is made that you want ColdFusion to cache a connection after it is used. The Timeout setting does not return a connection to the cache after a specified period of time, regardless of how infrequently it is used. The default is "" or 0, which means that the connection timeout is never enforced. Interval (sec) The time (in seconds) that the server waits between cycles to check for expired data source connections to close.
Use Default Username Description Default Username Default Password Username
Page Timeout Max Buffer Size Connection String Maintain Connections Timeout (min)

Setting BLOB

Description Select to return the entire contents of any BLOB/Image columns in the database for this data source. If unchecked, ColdFusion retrieves the amount specified in the Blob Buffer setting.

Connecting to MySQL

Use the settings in the following table to connect ColdFusion to MySQL data sources:
Setting CF Data Source Name Database Server Port Username Description The data source name (DSN) used by ColdFusion to connect to the data source. The database to which this data source connects. The name of the server that hosts the database that you want to use. If the database is local, enclose the word local in parentheses. The number of the TCP/IP port that the server monitors for connections. The user name that ColdFusion passes to the JDBC driver to connect to the data source if a ColdFusion application does not supply a user namefor example, in a cfquery tag. The password that ColdFusion passes to the JDBC driver to connect to the data source if a ColdFusion application does not supply a passwordfor example, in a cfquery tag. (Optional) A description for this connection. A field that passes database-specific parameters, such as login credentials, to the data source. ColdFusion establishes a connection to a data source for every operation that requires one. Enable this option to improve performance by caching the data source connection. The maximum number of minutes after the data source connection is made that you want ColdFusion to cache a connection after it is used. The time (in seconds) that the server waits between cycles to check for expired data source connections to close.
Connecting to ODBC Socket
Use the settings in the following table to connect ColdFusion to ODBC Socket data sources:
Setting CF Data Source Name ODBC DSN Description Username Description The data source name (DSN) used by ColdFusion to connect to the data source. Select the ODBC DSN to which you want ColdFusion to connect. (Optional) A description for this connection. The user name that ColdFusion passes to the JDBC driver to connect to the data source if a ColdFusion application does not supply a user namefor example, in a cfquery tag. The password that ColdFusion passes to the JDBC driver to connect to the data source if a ColdFusion application does not supply a passwordfor example, in a cfquery tag. A field that passes database-specific parameters, such as login credentials, to the data source. ColdFusion establishes a connection to a data source for every operation that requires one. Enable this option to improve performance by caching the data source connection. The maximum number of minutes after the data source connection is made that you want ColdFusion to cache a connection after it is used. The time (in seconds) that the server waits between cycles to check for expired data source connections to close.

Security and ColdFusion edition differences
If you have the Enteprise Edition of ColdFusion MX, you can configure several security sandboxes. If you have the Standard Edition of ColdFusion MX, you can configure the root security sandbox.
Chapter 4 Administering Security
In the Enterprise Edition of ColdFusion MX, when you click the Security > Sandbox Security page link, it opens the following page:
Default security behavior
The ColdFusion Administrator installs with secure access enabled. The password that you enter during installation is saved as the default. When you open the Administrator for the first time, you are prompted to enter the password. If you configured password protection for RDS accesswhen you installed ColdFusion, you are prompted for the password when you attempt to access ColdFusion MX from Dreamweaver MX, HomeSite+, or ColdFusion Studio. Sandbox security in not enabled by default. You must enable it on the Security > Sandbox Security page before you can configure it.
ColdFusion Administrator password protection Password protection for accessing the ColdFusion Administrator helps guard against unauthorized modifications of ColdFusion MX, and Macromedia highly recommends using passwords. You can disable password protection by clearing the check box on the Security > CF Admin Password page. You can also change the password on that page by entering a new password twice. RDS password protection You can enable file and data source security for RDS access from the Security > RDS Password page. You can also change the password on that page by entering a new password twice. If you enable this security, you rely on web server security settings to set permissions to ColdFusion application and document directories. In addition, you rely on your database settings to control access to data sources.

Using sandbox security

Sandbox security uses the location of your ColdFusion pages to control access to ColdFusion resources. A sandbox is a designated directory of your site to which you apply security restrictions. By default, a subdirectory (or child directory) inherits the sandbox settings of the directory one level above it (the parent directory). If you define sandbox settings for a subdirectory, you override the sandbox settings inherited from the parent directory. For example, consider the following directories:

C:\pat\*

C:\pat\
The following table shows the relationship between permissions of a file and of a directory:
Permission Read Write Execute Delete Affect on files View the file Write to the file Execute the file Delete the file Affect on directories List all files in the directory Not applicable Not applicable Delete the directory
You combine the file path and permissions settings to secure permissions on files and directories; for example, setting the read permission on C:\pat\* lets you do the following tasks: List all files in the C:\pat\riots\ directory. List all files in the C:\pat\riots2\. Read the C:\pat\a.txt file.

Adding a sandbox

The Root Security Content is the default sandbox for your ColdFusion MX server. If your security requirements are minimal and you do not need additional sandboxes, configure the default sandbox so that the child directories will inherit its security settings.

To add a sandbox:

1 Open the Security > Sandbox Security page in the ColdFusion Administrator. The Root Security Context appears in the list of Defined Directory Permissions, as the following figure shows:
2 In the Add Security Sandbox box, enter the name of the new sandbox. This name can be a relative URL or a webserver mapping. In this example, mytestapps corresponds to C:\Neo\wwwroot\mytestapps.
3 Select New Sandbox from the drop-down list to create a sandbox based on the default sandbox, or select an existing sandbox to copy its settings to your new sandbox. 4 Click Add. The new sandbox appears in the list of Defined Directory Permissions, as in the following figure:

Configuring a sandbox

You use the ColdFusion Administrator to configure a sandbox.

To configure a sandbox:

1 Open the Security > Sandbox Security page in the ColdFusion Administrator. 2 In the list of Defined Directory Permissions, click the name or the Edit icon for the directory that you want to edit.

Extensions section, ColdFusion Administrator 25
files and directories, security 57
sandbox adding 55 configuring 56 security, using 53 Sandbox Security page, ColdFusion Administrator 27 security about 50 ColdFusion functions 57 ColdFusion tags 56 data sources 56 default behavior 51 directories and permissions, about 53 files and directories 57 IP/Port 58 RDS password 52 resources, restricting 53 root security content 55 sandbox, adding 55 sandbox, configuring 56 sandbox, using 53 Security section, ColdFusion Administrator 27, 50 Server Settings section, ColdFusion Administrator 9 session variables 12 Settings Summary page, ColdFusion Administrator 16 Simple Mail Transfer Protocol (SMTP) Mail Server 13 Sybase, connecting to 47
Informix, connecting to 38 installation, support vi IP/Port, security 58
Java and JVM Settings page, ColdFusion Administrator Java Applets page, ColdFusion Administrator 25 JDBC about 30 driver types 30 driver types, supplied 31 15
Log files, created by ColdFusion 23
Macromedia ColdFusion developer resources vi training resources vi Mail Server page, ColdFusion Administrator 13 Mappings page, ColdFusion Administrator 13 Memory Variables page, ColdFusion Administrator 12 Microsoft Access, connecting to 39 Microsoft SQL Server, connecting to 41 migrating client variable data 11 MySQL, connecting to 43
training. See Macromedia ColdFusion
ODBC Socket, connecting to 44 Oracle, connecting to 45 other data sources, connecting to 46
Verity Collections page, ColdFusion Administrator 17 Verity K2 Server page, ColdFusion Administrator 18
password ColdFusion Administrator 51 RDS 52 Post Office Protocol (POP) Mail Server 13
Web Services page, ColdFusion Administrator 18
RDS Password page, ColdFusion Administrator 27 RDS password, security 52 root security content 55