After installation, might have to configure HP-UX to work with ColdFusion Server. This section addresses the following topics:
If you did not instruct ColdFusion Server to configure your Web server automatically during the ColdFusion Server installation, you must manually configure your Web server. This section explains how to configure Web servers manually in HP-UX. The following Web servers are covered in this section:
The ColdFusion Server NSAPI plug-in has been tested with Netscape/iPlanet Enterprise Web Server 3.5.1 and 4.1 and the Netscape FastTrack Web Server 3.5.1 and 4.1. The installation script prompts you to configure either of these servers automatically.
Netscape/iPlanet plug-ins for ColdFusion Server are installed in the opt/coldfusion/webserver/nsapi directory.
The following procedure assumes that you installed the Netscape/iPlanet server in
/usr/netscape/server4 on the system named smurf.
coldfusion
in your server directories.
mkdir /usr/netscape/server4/plugins/coldfusion cp /opt/coldfusion/webserver/nsapi/coldfusion35.so \ /usr/netscape/server4/plugins/coldfusion/coldfusion.so
/usr/netscape/server4/https-smurf/config/mime.types
file to add a new ColdFusion Server type. Add the line:type=magnus-internal/cold-fusion exts=cfm,dbm,cfml,dbml
/usr/netscape/server4/https-surf/config/obj.conf
file to add new service and init directives. Add all of the following on one line:Init fn="load-modules" shlib="/usr/netscape/server4/ plugins/coldfusion/coldfusion.so" funcs="DoCFRequest"
Service fn="DoCFRequest" method="(GET|POST)" type="magnus-internal/cold-fusion"
Note If you run the Netscape/iPlanet Server Manager, the browser-based administrator, you get a warning about edits to the Netscape configuration files. This is normal. To reload the new configuration files, follow the instructions and click Apply. |
If your server does not restart, ensure that the path name for the plug-in you specified in the obj.conf file is correct for your installation and that it is on a single line.
ColdFusion Server attaches to Apache using a dynamically-loaded shared library (DSO). To use ColdFusion Server with Apache, you must have a version of the ColdFusion DSO that matches the version of Apache you're running.
httpd -V
If the output contains the line -D EAPI
, you are running an EAPI version of Apache.
Copy the appropriate module into the libexec subdirectory of your Apache installation.
Note For more information, see the Readme file located in /opt/coldfusion/webserver/apache. |
httpd -l
If the output does not include a line containing something like mod_so.c
, you must enable DSO support by running the configure
script with the enable-module
option included; for example:
LIBS1= -lcl -lm -lpthread
If it does not contain -lcl
, add it.
LoadModule
, add the following line:LoadModule coldfusion_module libexec/mod_coldfusion.sl
If you are running an EAPI, add the following line:
LoadModule coldfusion_module libexec/mod_coldfusion-EAPI.slAddModule
, add the following line: AddModule mod_coldfusion.c
After the install is completed, but before you can set up a data sources in the ColdFusion Administrator, you must edit the /opt/coldfusion/bin/start
script to include information about the database(s) you use.
Normally this requires two changes per database: setting a database-specific environment variable, and adding the path to the client-side database libraries to your SHLIB_PATH environment variable. The start script provides examples to help you.
After editing the start script, you must stop and restart ColdFusion Server for the changes to take effect. After that finishes, proceed to the ColdFusion Administrator to set up your data sources.
Note For more information, see "Managing Data Sources". |
The following table includes important database compatibility information for ColdFusion Server 5 in HP-UX: