I know a bit about this, so hopefully this'll help point you in the right
direction :)
Tango-Talk wrote:
> Hello:
>
> We're attempting to set our system up with Tango App servers running on
> separate CPUs. While the diagrams are fairly straightforward, the actual
> execution is a bit unclear. Are the t4server.ini files and t4client.ini
> files supposed to be identical on all systems, or do they vary by the
> specific app servers running on a particular box.
As far as I know, the t4client.ini can be different, and the t4server.ini file
must have some sort of reference to the other box.
> Also in terms of access
> to config directories (error.htx, etc), do you simply replicate that
> structure or mount a shared directory.
We replicated our files.
> Finally, do the taf files live on
> the web server, or do they too have to be replicated and/or shared on each
> app server box?
We have a separate web server that stores all of our .taf files. Any .taf
that gets executed is handled by the Tango Servers.
>
>
> Any help appreciated.
>
> Regards,
>
> T
>
Hope this helped :)
>
> ------------------------------
> Tim Kelley
> MIS Director
> Harvard University - DCE
>
> Phone : 617.495.9095
> FAX : 617.495.9176
> e-mail: [EMAIL PROTECTED]
>
> ________________________________________________________________________
> TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
> with unsubscribe witango-talk in the message body
--
____________________________________________
Mark Horseman
Programmer Intern
College and Department Applications and Data
Administrative Information Services
Information Technology Services Division
University of Saskatchewan
Phone: 966-7008
E-Mail: [EMAIL PROTECTED]
____________________________________________
Things Mark Shouldn't Do #184
"When operating a military vehicle I may *not* attempt something 'I saw in a
cartoon'."
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
