The ColdFusion Administrator is a full-scale, Web-driven administration system for ColdFusion servers. The Administrator provides the capability to control many aspects of the ColdFusion operation, from data sources to extensions to logging to scheduling. Essentially, the only main administrative task not achieved through the Administrator is starting and stopping the server services, which is done through the Services Control Panel applet in Windows NT and 2000 and from the Start menu in Windows’ 98. The Coldfusion Administrator is divided into six sections of multiple pages:
• Data Sources
• Automated Tasks
Accessing the ColdFusion Administrator
To access the ColdFusion Administrator, point your Web browser to an address such as the following:
http://coldfusionhelp.net The hostname part of the URL should be the IP address or host name of the Web server on which your Coldfusion server is installed. In the case of a local server, you can use local host of 127 .0.0.1 for the hostname part of the URL.
This will display the login screen for the ColdFusion Administrator shown in Figure 35.1.
During installation of the ColdFusion server, you specified a password for administration. Provide that password in the field and click the Password button to log in. You should be presented with the first page of the ColdFusion Administrator, the Server Settings page, shown in Figure 35.2.
The Server section of the Administrator is used to set basic settings of the server, including tirneouts, cache size, and other general settings, along with basic security, client variable storage, and directory mappings. The screens in the Server section are:
• Basic Security
• Advanced Security
• Version Info
The Server Settings screen is used to set several of the following general settings of your ColdFusion server: Limit Simultaneity Requests to X By limiting the number of requests that can be
simultaneous processed, you can improve system performance. At the same time, though, if you get a large number of near-simultaneous requests, many of these requests will need to be queued until other requests finish processing. The default value of five should be suitable for most small Web servers.
Timeout Requests after X Seconds
At times requests will take an extremely long time to process and will use server resources for extended periods, effectively limiting the server’s performance. By enabling this option, requests that take longer than the number of seconds you specify will be terminated when they cross the threshold. You can override this timeout limit for any particular request by appending? requests meout=<seconds> to a URL.
Restart at X Unresponsive Requests
Sometimes it is possible for the ColdFusion server process to become extremely slow, using up an enormous percentage of the CPU resources on the computer it is running on. This often happens because of problems in third-party components such as ODBC drivers or CFX tags. When this setting is editable, ColdFusion will track requests to these components that time out and when the specified number have occurred, will restart the ColdFusiort service in an attempt to alleviate problems that develop over time.
Restart when requests terminate abnormal
Sometimes, requests will suffer an “unexpected exception” error. If too many of these occur, the ColdFusion service should be restarted. When this setting is enabled, ColdFusion will track these errors and, if too many occur, will restart the ColdFusion process.
Suppress whitespace by default
Depending on how your ColdFusion templates are formatted, large numbers of spaces, tabs, and carriage returns can occur in sequence leading to larger than necessary files being sent to browsers and making the HTML received by browsers hard to read. When this setting is enabled, Coldfiusion Will compress these sequences to eliminate unnecessary white space in the final code sent to browsers. .
Enforce Strict Attribute Validation
‘When enabled, the rules by which ColdFusion tags are processed will be stricter than the way standard HTML tags are processed. Normally, both HTML and ColdFusion tags can include irrelevant, extraneous attributes that are not part of the specification for the tag in question. Usually these extra attributes are ignored. When this setting is enabled, however, any ColdFusion tag with extra attributes will generate an error. This setting’s goal is enhance performance as ColdFusion won’t have to process and then reject extraneous attributes.
Missing Template Handler
This field specifies a custom template to execute when ColdFusion cannot find a requested template. Consult, “Error Control,” for details on handling errors in templates.
Site-wide Error Handler
This field specifies a custom template to execute when an error occurs while processing a request. Consult , “Error Control,” for details on handling errors in templates. If this option is enabled and the error-handler document is not present, debugging your application may be nearly impossible.