Product

• Brisque^® Serve 4.0.35
• Brisque Serve 4.0.21
• Timna™ 3.x

Platform

• E30—Victory
• 43P–140—Tiger1
• 43P–150—Tiger2
• F50—Wildcat (2 and 4 CPUs)
• 44P–170—Hammerhead
• 6F1—Condor (2, 4, and 6 CPUs)

Operating system

IBM^® AIX^® 4.2.2 or 4.3.3

Symptoms

When you start Brisque Serve, Timna@Web™ Internet access software does not launch automatically, and has to be started manually.

The following is an example of a Timnaweb log file demonstrating this problem:

# Timnaweb
Timn@Web log file Information: /sites/netscape/suitespot/timnaweb.log
Starting Timn@web Tue Apr 29 09:43:47 PST 2003
Netscape Admin daemon is already running...
Timnaweb[82]: /sites/netscape/suitespot/httpd-ripro01/start: not found.
Netscape Admin daemon is already running...
Start netscape FastTrak daemon
Error Netscape http daemon is not running !
Database selected.
Routine dropped.
Routine created.
Database closed.
Clear cache now Tue APR 29 09:43:47 PST 2003
-----------------------------------------------------------
Timn@web started Tue APR 29 09:43:49 PST 2003
-----------------------------------------------------------

Cause

The customer has configured a public Internet domain name and server name for Brisque Serve or Timna that is different from the domain and server names that were initially configured when Brisque Serve or Timna was installed. The initial domain name for Brisque Serve or Timna is usually riproxx or something similar.

When Timna@Web software was installed:

• The installation extracts the customer's server and domain names that was entered. For example, if timna.sdsp.net was entered, the installation extracts the server name timna and the domain name sdsm.net.
• The Netscape Navigator^® application creates start and stop executable files for httpd daemon in the directory of the server (name) that was configured in step 2. For example, /sites/netscape/suitespot/httpd-timna.

Timna@Web cannot start up automatically because the Timnaweb startup script requires the host name /sites/netscape/suitespot.

Solution

To ensure that the httpd dameon starts in the correct path, add a line to the Timnaweb start script:

1. Open the Timnaweb script in a text editor.
2. Comment the line x="hostname". The line should read: #X="hostname"
3. Press Enter and type x="timna".
4. Save the Timnaweb script, and close the text editor application.

This change does not affect other Timna@Web settings because the directory /sites/netscape/suitespot/httpd-timna is only used to store the start and stop files of the httpd daemon.

The following is an example of a Timnaweb log file with the problem corrected:

# Timnaweb
Timn@Web log file Information: /sites/netscape/suitespot/timnaweb.log
Starting Timn@web Tue Apr 29 09:48:41 PST 2003
Netscape Admin daemon is already running...
Netscape-FastTrack/3.01 B97.275.0903
startup: listening to http://ripro01.sdps.net, port 80 as informix
Netscape Admin daemon is already running...
Start netscape FastTrak daemon
Netscape http daemon is running...
Database selected.
Routine dropped.
Routine created.
Database closed.
Clear cache now Tue Apr 29 09:48:41 PST 2003
-----------------------------------------------------------
Timn@web started Tue Apr 29 09:48:44 PST 2003
-----------------------------------------------------------

Technical contact(s)

Lev Weissman

Submitted by

Lev Weissman

Date submitted

04 June 2003