Database Connections in Deployed Apps

Dale --

The problem existed when attempting to change the connection from one

Sybase Database to another on the same machine. Basically, I was moving

from the development environment to the test environment. We tried

repartitioning, reseting the SO's in the partition workshop and even hard

coding the environment variables in the UNIX shell script that ran the

Forte process. Finally, we went into $FORTE_ROOT/userapp/app_name/cl0 and

deleted all the files and then redeployed. That seemed to do the trick and

we finally got it working. I am still trying to figure out why...

Thanks to you and all who helped me with this.

Dave Radzialowski

Nac Reinsurance

Greenwich, CT

203-622-5305

dvgeorg@ibm.net on 02/02/98 04:57:04 PM

To:David_J._Radzialowski@nacre.com

cc:(bcc: David J. Radzialowski/HomeOffice/NAC)

Subject: Re: Database Connections in Deployed Apps

On Mon, 2 Feb 1998 12:13:35 -0500, David J. Radzialowski wrote:

>In one of our applications, we are using several DBSession service objects

>to attach to a database. When running the application in debug mode, the

>application attaches to the correct database and returns the correct

>values. After deploying the application, the deployed version attaches to

>a different database and thus does not return the correct values. When in

>the partition workshop, I have set all the service objects to point to the

>proper database, but it still does not work. Any ideas?

If you could give me some more details, I'll try to help. Are your

development and deployment servers the same, or are they different

machines? When you say that the deployed application connects to a

different database, do you mean a different database on the same

database server, or a different database server altogether?

Dale

================================================

Dale V. Georg

Systems Analyst

Indus Consultancy Services

dgeorg@indcon.com

================================================

Fax Cover Page:

at 2007-6-29 9:22:07 >