| Contents > Configuring and Administering ColdFusion MX > Web Server Management > Web server configuration > Configuration files |
|
|
|
|
||
The Web Server Configuration Tool stores properties in configuration files, as follows:
The following table describes the web server connector properties in the web server configuration files. The web server connector uses these settings to help it find the ColdFusion server and know which servers to connect to.
Property |
Description |
|---|---|
bootstrap |
The IP address and port on which the JRun server's proxy service is listening for connector requests. JRun must also be configured to listen on this port/address combination, the ProxyService must be activated, and the JRun server must be running. For example, 127.0.0.1 51010. |
serverstore |
The name of file that contains information on for the associated JRun server. The connector creates this file automatically. The default is jrunserver.store. |
verbose |
Creates more detailed web server log file entries for the connector. Enabling this option can cause the web server's log files to fill quickly. Specify true or false; the default is false. In Apache, the connector writes to the error log; on iPlanet, to errors; and on IIS, the connector writes to its own log in the related wsconfig subdirectory. |
scriptpath |
IIS only. Points to the virtual /JRunScripts directory on the web server. |
errorurl |
(Optional) Specifies the URL to a file containing a customized error message. This property is commented out by default. |
ssl |
(Optional) Enables SSL between the web server and the JRun server. Specify true or false. Because most web servers are already inside a firewall, you typically leave this property set to false (the default). |
apialloc |
Enables native OS memory allocation rather than the web server's allocator (for use on Solaris with iPlanet at the direction of Macromedia Support staff). |
Each time you run the Web Server Configuration Tool, it creates a new directory beneath cf_root/runtime/lib/wsconfig. For example, the first time you run the tool, it creates files under cf_root/runtime/lib/wsconfig/1, the second time, it creates cf_root/runtime/lib/wsconfig/2, and so on. Each of these subdirectories contains the appropriate platform-specific connector module and web server-specific supporting files.
To help describe the web server configuration file parameters, this section provides examples of connector-specific web server properties. These examples assume that JRun and the web server are on the same computer.
A typical httpd.conf file for an installation of ColdFusion on the same machine as an Apache 2.0 web server follows.
... LoadModule jrun_module /opt/coldfusionmx/runtime/lib/wsconfig/1/mod_jrun20.so <IfModule mod_jrun20.c> JRunConfig Verbose false JRunConfig Apialloc false JRunConfig Ssl false JRunConfig Ignoresuffixmap false JRunConfig Serverstore "/opt/coldfusionmx/runtime/lib/wsconfig/1/jrunserver.store" JRunConfig Bootstrap 127.0.0.1:51010 #JRunConfig Errorurl <optionally redirect to this URL on errors> AddHandler jrun-handler .cfm .cfc .cfml .jsp .jws </IfModule>
For IIS, JRun uses the jrun.ini file to initialize jrun.dll (jrun_iis6.dll on IIS 6). A typical jrun.ini file follows:
verbose=false scriptpath=/JRunScripts/jrun.dll serverstore=C:/CFusionMX/runtime/lib/wsconfig/1/jrunserver.store bootstrap=127.0.0.1:51010 apialloc=false ssl=false ignoresuffixmap=true #errorurl=<optionally redirect to this URL on errors>
A typical obj.conf file for Netscape/iPlanet web servers follows:
... <Object name=default> NameTrans fn="jrunfilter" serverstore="C:/CFusionMX/runtime/lib/wsconfig/2/jrunserver.store" bootstrap="127.0.0.1:51010" ... ObjectType fn=type-by-exp exp=*.cfm type="jrun-internal/" ObjectType fn=type-by-exp exp=*.cfc type="jrun-internal/" ObjectType fn=type-by-exp exp=*.cfml type="jrun-internal/" ObjectType fn=type-by-exp exp=*.jsp type="jrun-internal/" ObjectType fn=type-by-exp exp=*.jws type="jrun-internal/" ObjectType fn=type-by-extension ObjectType fn=force-type type=text/plain Service method=(GET|POST) type="jrun-internal/" fn="jrunservice" Service type="magnus-internal/jsp" fn="NSServletService" Service method=(GET|HEAD) type=magnus-internal/imagemap fn=imagemap Service method=(GET|HEAD) type=magnus-internal/directory fn=index-common Service method=(GET|HEAD|POST) type=*~magnus-internal/* fn=send-file AddLog fn=flex-log name="access" </Object> ... <Object name="jrun"> PathCheck fn="jrunfilter" Service fn="jrunservice" </Object> ...
A typical magnus.conf file for Netscape/iPlanet web servers follows:
... Init fn="load-modules" shlib="C:/CFusionMX/runtime/lib/wsconfig/2/jrun_nsapi35.dll" funcs="jruninit,jrunfilter,jrunservice" Init fn="jruninit" serverstore="C:/CFusionMX/runtime/lib/wsconfig/2/jrunserver.store" bootstrap="127.0.0.1:51010" verbose="false" apialloc="false" ssl="false" ignoresuffixmap="false"
|
|
||
| Contents > Configuring and Administering ColdFusion MX > Web Server Management > Web server configuration > Configuration files |
|
|
ColdFusion 9 | ColdFusion 8 | ColdFusion MX 7 | ColdFusion MX 6.1 | ColdFusion MX | Forums | Developer Center | Bug Reporting
Version 6.1
Comments are no longer accepted for ColdFusion MX 6.1. ColdFusion 8 is the current version.