about oracle license ?
Christophe Conduché
Hi !
which is the oracle license given with livewire pro ???
i thought that ES was seen has a single user and that the dbpool
launched several threads in order to do simultaneous connection, but was
only using one user license. and as we can't expect how many people will
be connected, we need to give a 'high' number of connection to each
pool. so the 'by processor' mode of licensing that enables an unlimited
number of session should be the default for oracle in livewire pro.
I've just seen that it's not like that. and if we ask in a pool 20
connections, twenty sessions are opened.
and the limit of sessions in the license given with livewire pro is 50.
how can I run two livewire apps that each need 30 connections in the
pool ?
i thought we were unlimited and that the license was 'by processor', not
by user.
how can i solve that ?
is it a configuration problem ?
--
--------------------------------------------------
Christophe Conduché Tél:01.53.02.48.48
C-Ware SA Fax:01.53.02.48.49
email: c...@c-ware.fr
URL:
--------------------------------------------------
Willy Mena
I don't know the legal issues regarding licenses. If you are being told
that you are limited to 50 licenses, then create 2 apps with 25 connections
in each pool stored in the project object.
In addition, you can or store the pool in the server object and have all of
your apps share that pool.
If you are grabbing and releasing connections as needed, then 25 per app
should be more than enough. I think my heaviest used app only uses 5
connection.
How many concurrent users are you expecting?
Willy Mena
Christophe Conduché
the databases are differents (differents users).I need for the busiest
app a pool for the 'login & orders database' and a pool for each
agencies of the firm (1 'catalog database' per agency).
I will have when the deployement will be achieved at max 30 users
simultaneously per agencies, and 6 agencies.
Users always connect quite simultaneously, because in each agencies,
people have the same way of working. they connect to pass order at about
8:00, 12:00, 14:00 and 17:00
in peak activity i can expect the folloqing for the main app:
6 agencies, plus 'login&order' database = 7 pools
on 'login&order' pool, at max 180 ( 30 * 6 ) people 'simultaneously', on
each 'catalog' pool 30 users 'simultaneously' at max.
for the admin app:
database is used rather than dbpool (an "old" app...):
2 connections needed
for sqlplus (for admin purpose) 2 connections
so I should need in the worst situation : 364 connections !!
but I acknoledge what the very worst situation never happens.
what should be the best way to distribute the connections ?
according to your experiences, how many 'simultaneous' users can you
deal with a 5 connection pool ?
thanks a lot for any figures about number of simultaneous users vs
number of connections.
best regards