You will find connection pooling much faster for your web connections. I presume they are using uniobjects (.net or java). IF they are not pooled, each connection has to login, do its work, and logout. Pools are ideal if your web transactions are in and out pretty quick. If your web connections come in and stay in for a while then you had best stick with non pooled. The idea of a pooled connection is that a smaller number of connections stay logged in and can then handle lots of web transactions coming in and out. Device licensing means you can have up to ten connections from one ip using a single licence. This is meant for a single PC user who may have a telnet client and a .net client using uniobjects open at the same time, in reality they are just one user so should not be taking multiple licences. However non pooled uniobjects connections from a web server will also use device licensing so the first 10 connections will use 1 licence and any subsequent ones take a full licence each. Whether this is in the spirit of device licensing i am not sure...
From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: 21 October 2010 20:08 To: [email protected] Subject: [U2] Licensing Hello, We have always used only RDBMS licenses and have always had plenty of seats. Recently we are hitting our limit. We also access our Unidata dabases from web apps. I am hoping for some advise on connection pooling and device licensing as a way to allow more sessions without more licenses. Charles Shaffer Senior Analyst NTN-Bower Corporation _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users _____ No virus found in this message. Checked by AVG - www.avg.com Version: 10.0.1136 / Virus Database: 422/3210 - Release Date: 10/21/10 _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
