It may be useful to capture output from the Namesvc proxy to a file. This can be enabled by editing /opt/SUNWjdt/cgi-bin/namesvc. Comment the line:
# $JAVA_HOME/bin/java sunw.jdt.dex.server.Namesvc
# $JAVA_HOME/bin/java sunw.jdt.dex.server.Namesvc | tee /tmp dex.last |
If you perform a search and this file doesn't get created or updated, then the httpd server is having problems launching the cgi-bin script. If the output in the file indicates some type of error:
Content-type: text/plain <DBError>:6
then the database probably couldn't be found or the permissions on the file are not set correctly. Make sure the database files have read access for world.
If you have enabled capturing output to /tmp/dex.last and this file isn't being updated, then check the httpd server error log file. This may indicate that there was some sort of cgi-bin error. The server may not be configured to run cgi scripts or might not be able to find the namesvc script.
Make sure the database files you have created have read access set for world (chmod 664).
The 1.1 back end is not compatible with 1.0 clients. If you need to support both 1.1 and 1.0 clients, you have several choices. The easiest solution is to install the 1.1 back end on a different server than the 1.0 back end. In this configuration you simply follow the steps that have already been outlined above. If you want to support 1.1 and 1.0 clients from the same server, follow these instructions:
Install 1.1 on the server, but do not install it on top of your 1.0 installation. Put 1.1 under /opt/SUNWjdt1.1 or something similar.
In your web server cgi-bin directory create a symbolic link from webserver/cgi-bin/jdt1.1 to /opt/SUNWjdtd1.1/cgi-bin.
Edit the namesvc file in /opt/SUNWjdtd1.1/cgi-bin. Change the JDT_HOME environment variable from /opt/SUNWjdt to /opt/SUNWjdt1.1.
Edit /opt/SUNWjdt1.1/lib/props/standard/nameview.props. Change the value of the dex.db.cgi.proxy property to /cgi-bin/jdt1.1/namesvc.2.0.
Edit /opt/SUNWjdt1.1/lib/props/namesvc.props to point to your database.
This release of HotJava Views has an error message logging capability that is used most extensively by NameView. If you want to enable this capability, use the following procedure on the system running your web server.
Assuming you have installed HotJava Views in /opt/SUNWjdt, create a symbolic link called jdt from within your httpd server's cgi-bin directory (this location varies among servers) to /opt/SUNWjdt/cgi-bin.
For example, if you are running the Apache server, you can use the following commands:
# pwd # /opt/WWW/Apache/httpd/cgi-bin Your httpd server's cgi-bin dir # ln -s /opt/SUNWjdt/cgi-bin ./jdt # ls jdt # getidsvc.2.0 jdtlogsvc namesvc.2.0
Some web servers require that you explicitly turn on cgi-bin support before cgi-bin scripts can be executed. Refer to your httpd server's documentation to determine your server's requirements.
Edit the /etc/syslog.conf file and add the following line:
# local0.info /var/opt/SUNWjdt/jdt.log
Make sure that you use tabs, not spaces, between the values.
Create /var/opt/SUNWjdt/jdt.log and modify its permissions:
# mkdir /var/opt/SUNWjdt # touch /var/opt/SUNWjdt/jdt.log # chmod 666 /var/opt/SUNWjdt/jdt.log
# kill -HUP `cat /etc/syslog.pid
HotJava Views uses CGI to send error messages to the jdtlogsvc script on your web server. The jdtlogsvc script uses syslog to log the errors.