I always thought it would be good if the
Witango server, when configured as a development server, ie. only
from 127.0.0.1 using the key generated with the purchase of a dev studio, would
also use the development settings. I actually think this is how T2K worked, but
I’ve never sat down and tested that.
Ideally, it would be great to have a config
variable called “dsType=development | deployment” in which case the
server type could be configured explicitly in either way, and with scoping, you
can run one user session against a dev database, while the server was still working
with real data, or one domain would be dev and one domain would be live, both
on the same server.
You can achieve something close to this if
you use variables for the deployment datasource information, but I think a
config var is a little more graceful, simpler to implement, and from what I
gather, solves the Oracle issue as well.
Robert
-----Original Message-----
From: Steve Smith
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 09, 2003
1:47 PM
To: [EMAIL PROTECTED]
Subject: Re: Witango-Talk: RE:
Deployment/Development Datasources
The Development/Deployment heading are a little
misleading. Development refers to the Dev Studio, Deployment refers to the App
Server. So when you set up separate Development/Deployment data sources in your
taf files, it is simply giving the appropriate application direction on where
to go for data source connectivity. If your taf has separate Dev/Deploy data
sources, when you open the file in the Dev Studio, it will use the Development
data source. When the file is run through the App Server, it uses the deployment
data source.
Other than the suggestion mentioned regarding setting up the datasource name
the same on both machines OR setting up a dynamic (i.e. variable) which stores
the data source information, you are pretty much stuck. In your environment, I
don't believe that either of these options would work, simply because you are
not using either ODBC or JDBC.
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
On Tuesday, September 9, 2003, at 01:31 PM, Jim Kass wrote:
We are using Solaris Servers, and Oracle DBs, so we
don't use ODBC right
now.
The TNSNAMES will be different for the DEV and PROD databases.
I read Scott's article - but I'm still a LITTLE confused as to how to use
this for our purposes.
Thanks.
Jim Kass
Web Developer
--
Forestweb: The Source for Industry Intelligence
Best Content -- Most Relevant -- Best Delivery
http://www.forestweb.com
(310) 553 - 0008
-----Original Message-----
From: Ted Wolfley [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 09, 2003 10:29 AM
To: '[EMAIL PROTECTED]'
Subject: RE: Witango-Talk: RE: Deployment/Development Datasources
Hi,
Make sure the datasources are defined on each server through ODBC with the
same name and leave the Development/Deployment Datasources in the default
settings.
Ted
-----Original Message-----
From: Jim Kass [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 09, 2003 1:20 PM
To: [EMAIL PROTECTED] Com
Subject: Witango-Talk: RE: Deployment/Development Datasources
Hey Folks,
I'm having trouble understanding how to really use Development/Deployment
Datasources from the Tango documentation.
We have two "identical" servers and databases, one set is for
development.
What I would like to be able to do is to use the same file, and put it on
two different servers, and not have to re-set datasources every time.
In theory, the Dev/Deploy functionality should do what I want, but I can't
figure out how to use it properly. Can someone help me on this?
Thanks in advance,
Jim Kass
Web Developer
--
Forestweb: The Source for Industry Intelligence
Best Content -- Most Relevant -- Best Delivery http://www.forestweb.com
(310) 553 - 0008
________________________________________________________________________
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
