The ColdFusion MX 7 Verity search capability has been redeployed in a new client/server architecture. This means that ColdFusion and the Verity K2 server can be running on two different machines. This was not the case in versions prior to ColdFusion MX 7.
Note: For ColdFusion MX 7.0.1, additional attributes were added to the cfindex tag and modifications were made to the ColdFusion MX Administrator to facilitate this process, so updating to ColdFusion MX 7.0.1. is recommended before proceeding. More information regarding these changes is located in the ColdFusion MX 7.0.1 Release Notes.
There are several undocumented items regarding this configuration to be aware of:
- For the Verity K2 server to run on a different server, it must be installed separately from ColdFusion. To install it in this configuration:
- Be sure to enter the IP address of the ColdFusion MX 7 server machine when prompted. Remember, ColdFusion MX 7 and Verity can run on different machines, so enter the IP address of the server that ColdFusion is running on.
- On the ColdFusion MX 7 server, open the ColdFusion MX Administrator. Select the Verity K2 Server link in the left pane. Enter the name or IP address of the server that the Verity search server (K2) is running on.
- Verity will only accept requests from a single ColdFusion server. In other words, if Verity is installed on ServerV and ColdFusion is installed on ServerC, Verity will only accept requests from ColdFusion instances running onServerC. Note that there can be multiple instances of ColdFusion running on ServerC and Verity will accept requests from all of them.
- When indexing a Verity file collection, the file/directory structure must be the same on both the Verity and ColdFusion servers. If you are creating a file-based collection, the path needs to be the same from either server. This can be accomplished by mapping drives in Windows or by using symbolic links in Unix.
If ColdFusion MX 7 is running on ServerC and Verity is running on ServerV and you want to index all HTML files in c:\inetpub\wwwroot on ServerC, then you need to setup twomapped drives, one on each server that both point to c:\inetpub\wwwroot on ServerC. On ServerC, setup a drive mapping (K:\, for example) that points to the local directory c:\inetpub\wwwroot. Then, on ServerV, setup a drive mapping K:\ that points to the remote directory c:\inetpub\wwwroot on ServerC. Note that the drive letter on both servers does not have to be K:\ but they both have to be the same letter.
If ColdFusion MX is running on ServerC and Verity is running on ServerV and you want to index all HTML files in /opt/apache/2.0.47/htdocs on ServerC, then you would need to setup symbolic links, one on each server that both point to /opt/apache/2.0.47/htdocs on ServerC. On ServerC, setup a symbolic link that points to the local directory /opt/apache/2.0.47/htdocs. Then, on ServerV, setup a symbolic link that points to the remote directory /opt/apache/2.0.47/htdocs onServerC. Note that both symbolic links must be the same.
To create a Unix symbolic link, the syntax is similar to a copy or move: existing file first, destination file second. For example, to link the /opt/apache/2.0.47/htdocs directory to /webhome, use the following command: ln -s /opt/apache/2.0.47/htdocs/ /webhome
- As previously mentioned, when you install the standalone Verity search engine, it prompts you for the IP address of the ColdFusion MX server that will be accessing it. If you later wish to specify a different ColdFusion server, without reinstalling Verity, make the following change to the configuration file:
- Put the IP address of the new ColdFusion MX server in theclient mask property ofverity_root/data/host/admin/admin2.xml (orcf_root/verity/data/host/admin/admin2.xml).