Scott:
Thanks for the insight. We will investigate further using some
of your recommendations. I agree that it appears to be the STARTUPURL
as the taf can be run manually just fine.
In our case, domain scope is required although we also use "cross domain"
custom scope vars as you mentioned.
John
-----Original Message-----
From: Scott Cadillac [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 19, 2003 7:12 PM
To: [EMAIL PROTECTED]
Subject: RE: Witango-Talk: Startup URL and Domain Variables
Hi John,
I'm going to guess that the problem might be more to do with STARTUPURL then
<@URL>.
Maybe the Server cannot find the address of the TAF specified in STARTUPURL?
The "HOSTS" file is handy for these kinds of things.
Do you know if STARTUPURL is successfully calling the TAF at all?
Because the execution of the TAF in this case is not easy to see, try
putting something like a File/Write Action in the TAF that records something
in a text/log file - just to verify the TAF is executed.
And no, I don't think it's possible to initialize Domain Variables from
outside the Domain - unless you use <@URL> of course.
Custom Scope works almost exactly like Domain Scope, except the Variables
are visible across all Domains present on the Server. Just watch your
naming, to make sure things don't get stepped on.
Sometimes having the Variables visible across Domains is a good thing
because then sites with more than one address on the same Server (e.g.,
www.mydomain.com and mydomain.com) can share one Custom Scope Variable as
opposed to two Domain Scope Variables that are supposedly the same value.
Hope this helps. Cheers....
Scott Cadillac,
Witango.org - http://witango.org
403-281-6090 - [EMAIL PROTECTED]
--
Information for the Witango Developer Community
---------------------
XML-Extranet - http://xml-extra.net
403-281-6090 - [EMAIL PROTECTED]
--
Well-formed Development (for hire)
---------------------
-----Original Message-----
From: John Hotaling [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 19, 2003 4:34 PM
To: [EMAIL PROTECTED]
Subject: Witango-Talk: Startup URL and Domain Variables
I have the need to reinitialize domain variables for
several domains from values stored in a db. It is
critical that these values are current any time Witango starts
or restarts. In the past, we have used the startup URL
to call a taf (ironically we can run this taf by hand in a
browser fine) that told us which domains required initialization.
This taf in turn uses an @URL tag to "restore" domain vars for
each respective domain. However, we have not had success
using this logic with V5 of Witango and do not know why.
We have tried the new parameters for the @URL tag without
any luck. Is there any reason why our startup URL will not
run with the @URL tag used in it? It is not reporting any errors
in the log files during startup.
Also, is there a way to set domain vars for a specific domain from
within a different domain? Although it does not intuitively
make sense to me that you could, I thought I would still pose
the question.
Thanks in advance for any assistance.
Witango Application Server (Multiple Edition) 5.0.1.054 Chimera (Win32)
Windows2000/5.0; INTEL
John
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
