All,

I had been told that whenever a user logs-in that the profile would verify or ping or something for every db connection and to keep the db connections low (or managed) by removing old non-working db connections.

Just wondering if this is true and if there's any benefit from managing the db connections?

Thanks,
--wg

This message has been edited. Last edited by: Winfred Gunter,

It may do that or at least the first connection per db type, don't know for sure, but it doesn't seem to affect anything in our environment. We have many 10's of connections in our global profile, probably close to 50. I just did a test using edastart -t which does run edasprof.prf and I got my double-carat immediately.

Thanks Ginny,

That's been my observation... we've added tons of connections and we don't notice a problem. Makes me think I didn't understand the person or he was mis-informed.

Now, I do have a problem with test environment connections... that is, we add a test db instance and 3 months later, it's gone, but they don't tell me and I never remove the connection.... I've got to do something about that....

Been thinking of doing a test of ALL connections about every 3 months and remove any that fail. Or make a policy to only add test db's on our dev/test webfocus server.

Thanks for the feedback,
--wg

As far as I know, the DB connections you add via the WebFOCUS Server Console are stored in a file: C:\ibi\srv76\wfs\etc\edasprof.prf. The only way they can disappear is if they are deleted via the Console or if the file is edited or refreshed with an old copy. I find the Test environment here to be quite unreliable, people are constantly changing things - meta-data, db connections, user accounts, etc.

quote:

I find the Test environment here to be quite unreliable

Isn't that what test environment are for ... sort of.

Having many connections in your edasprof will very probably not have any performance issues, unless there are a huge number of them. All connections will be read by the agent and needs to be stored in the agents memory. Having a lot of connections might fill up the available memory faster than you want. I do not know if there is a limit to the number of connections, but I would advise to keep the number as low as possible. I don't think that the agent will try to connect to each and every connection. If that would be the case, then any connection that is no longer active would wait for a timeout to occur, thereby lengthening the startup process unacceptably. You would have noticed. But, if you want to be very very sure of this, switch on traces, run a small request, switch off traces and examine the trace file.