Installing The Verity Search Server Separately; Coldfusion Mx 7 J2Ee Deployment And Configuration - MACROMEDIA COLFUSION MX 7 - INSTALLING AND USING COLDFUSION MX Using Manual

Hide thumbs Also See for COLFUSION MX 7 - INSTALLING AND USING COLDFUSION MX:
Table of Contents

Advertisement

Installing the Verity search server separately

To enable searches using Verity, you must install the Verity search server separately if either of the
following is true:
You are running ColdFusion in a J2EE configuration with a WAR or EAR file.
You want to install the Verity search server on a different machine from the one where you
install ColdFusion MX 7.
You should start by planning the answers to questions asked by the Installer:
"Where would you like to install?" _______________________________
Macromedia recommends that you specify a location that is not a subdirectory of the
application server directories.
The IP address of the ColdFusion Server that this machine will accept requests
from__________________
The IP address is necessary only if you are installing Verity search server on a different computer
from the one where you installed ColdFusion MX 7. If you do not specify an IP address, the
Installer uses the default 127.0.0.1, which is localhost.
To install the Verity search server separately:
Download your platform-specific installer from the Macromedia website at
1.
www.macromedia.com/go/verity
Windows - coldfusion-search.win.exe
Linux - coldfusion-search-lin.bin
Solaris - coldfusion-search-sol.bin
Close any applications that are currently running on your computer.
2.
Run the platform-specific installer using the appropriate command.
3.
Note: Only console installations are available for UNIX systems.
(UNIX only) If you chose not to start the Verity search server automatically, start, stop, and
4.
restart Verity by running verity_root/bin/cfmxsearch -start | -stop | -restart.

ColdFusion MX 7 J2EE deployment and configuration

The J2EE specification allows application servers to handle compressed and expanded
deployments in a server-dependent manner; each application server has its own deployment and
configuration mechanism, as the following table shows:
Application server
JRun 4
IBM WebSphere
BEA WebLogic
or copy it from the ColdFusion MX CD, as follows:
Deployment mechanism
Auto deploy to server root
IBM WebSphere Administrative
Console
WebLogic Administration Console

ColdFusion MX 7 J2EE deployment and configuration

Expanded or compressed
deployment
Expanded
Compressed
Expanded
39

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents