I've run multi-tiered setups in the past (and supported them when I was with EveryWare/Pervasive). I currently have a multi-tiered system set up right now but not in use.
To answer your first question, your TAF's, TCF's, include files, etc. all need to be on the webserver/Witango client machine. Your database connections need to be set up on your server machine. Hope this helps, Steve Smith Oakbridge Information Solutions Office: (519) 624-4388 GTA: (416) 606-3885 Fax: (519) 624-3353 Cell: (416) 606-3885 Email: [EMAIL PROTECTED] Web: http://www.oakbridge.ca > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of John McGowan > Sent: December 13, 2002 8:51 AM > To: Multiple recipients of list witango-talk > Subject: Witango-Talk: True Multi Tier Witango Setup > > > Hi, > > Anobody out there running Witango in a true multi tier setup? Web Server > and App Server as completely separate machines? I would like to move in > this direction, but I want to figure out my deployment issues right now. > For instance, One thing I need to figure out, is if I have my Wiango App > Server on a separate machine, do I need to have all my taf/tcf > files on both > the webserver/appserver, or does tango access the files it needs > (includes, > branches.. etc) through the witango client running on the web server. > > Please let me know if you have experience in this area so I can > ask you some > more detailed questions. > > /John > > P.S. I'm also going to be moving toward an environment where I > have multiple > application servers handling the same cluster of sites, so if you've got > experience with setting up multiple app servers, let me know too. > > Thanks. > > ________________________________________________________________________ > TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body > ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
