Licence Usage


Hi all JDE Consultants and Gurus,

Please shed some light regarding licence usage:

1) Definition of a concurrent user.
2) Purpose of the deployment factor.
3) Definition of a named user.
4) How is number of concurrent users measured?
5) How are database users handled in relation to application users?

Many thanks in advance for your input.



Well Known Member
If you have your licence agreement with JDE available, all User licence
definitions should be in there, they can vary from Customer to Customer.

In general a concurrent user is based on the number who can access JDE at
onetime, named users mean you have a licence for each and every user by

JDE does not have any mechanism in OneWorld to measure or control
concurrency, which is why new Customers only get offered Named user

The Deployment factor is written into the contract, and is used to define
how many Client Installations are allowed for a given number of Concurrent
or Named users. This factor is used by Response to generate a specific
software key for your Site, this key will set a maximum number of Clients
which can be Installed, this is controlled, if you try to do a client
install on machine 101, when the limit is 100, you get bounced. This does
cause some issues, as not all Client uninstalls release the counter, often
machines get junked or renamed and then you have to reset the Licence
Authorisation to get it released. A log is kept of valid Client PC machine

Note if you use Citrix, each Citrix server is ONE machine ID, so ONE
licence, so if you have a key for 100 users but only 3 Citrix servers, you
will only use 3!!!

As far as Database licensing is concerned OneWorld doesn't care. You need to
address this separately with your database vendor, and ensure you have
control it.

Because of the way JDE connects to the database you only need ONE database
userid and lots of connections, all JDE user id's can share one Database
userid, you can change this if you want to.

OW733.3 Xe SP 14.2
Enterprise Server - Intel NT + Oracle 8.0.6
Client - Citrix TSE + 4 NT PC's for development


VIP Member

OW technically controlls licences in counting the number of workstations (Fat Clients) installed. There is no concurrent users counting.
Concurrent and named users are purely sales concepts. As there is no concurrent counting, JDEdwards allows for a deployment factor (I think it´s deviding by .6) the number of concurrent users purchased. This formula does not apply to named users (named users are cheaper). As an example: if you buy 100 concurrent users and 50 named users you may install 100/0.6 + 50 = 216.66 licences, thats 217 WSs installed (usually you get one more for the deployment server).
About the database: as far as I know you are supposed to buy as many licences for your database as you buy for OW (as an agreement between JDE and the database software vendors). Actually OW uses many more connections then that. In case of SQL it´s about one connection to the database for each Datasource. For Oracle it´s more like one connection for each OW, plus UBEs running, plus quite a few connections for the application server(s).

Hope this helps.

Em Wednesday, August 15, 2001 em 12:57:23 AM, escreveu:

Gerd J. Renz
InfoJBS Consultores Associados
Gerente de Tecnologia
fone: 011 5505-3750

ISM - Solucoes na Internet


Reputable Poster
Hi there :

I've got some of the answers, and share some of your doubts too...

1) Concurrent users define how many people run OneWorld processes and
applications at the same time. Technically speaking, it defines network,
RAM and CPU sizing for your/s Enterprise server/s. Don't know details
related to its marketing blablabla.
2) and 3) Don't know.
4) You have to perform some kind of survey on the company, plus apply
a few commercial guidelines given by JDE.
5) It's not directly related. For example, on SQL you may license
per Seat (how many PCs access the DBMS) or per Server (how many concurrent
users ask requests to the DBMS). On a typical OW installation, I would
use per Seat because, as a matter of fact, JDE is licensed that way.

There's a lot of marketing blablabla on the licensing bureaucracy,
but the crude reality is that "One installed JDE client = One license",
i.e. : you install a JDE client, your license count decrements by one;
you uninstall it, you gain an extra free license.
Finally, JAS licenses on a very different basis : per transaction
volume or per company size.

Sebastian Sajaroff

B7321 to Xe, NT/W2K/SQL
JAS, Interoperability
Grupo ASSA - Application Software SA


Active Member

I can add something to that - a named user is actually one install on a
single PC. There are no concurrent users any more, but at the times when
there were, one concurrent user was equal 1.6 (or 1.4, don't remember)
of a named user. Surprisingly enough the license cost was also 1.6 times

You have not requested information on moderate and inquiry user
licenses. Talk to your JDE rep, and then consider the facts in the last
paragraph of Sebastian's letter. ;-)

Don't know nothing about JAS.

Vladimir Ponomarev


Active Member
Re: RE: Licence Usage

Just one further note:

If you are using a SQL Server backend, Microsoft's licensing model now says that if you're going to access that data from the internet, NO MATTER HOW INDIRECTLY, you MUST license SQL in "per processor" mode, which is $17k - $19k per processor, depending on where you buy it. In that mode, SQL is licensed for unlimited number of users.

Enabling html customer self service, or a JAS server, for examples, would certainly trigger this requirement.

The "indirectly" part is to keep the crafty among us from trying to claim the browser client is really only connected to the JAS server (for example), and it is really the only thing connected to the database, so I only need 1 user license.

OneWorld Xe SP15
Clustered Windows 2000 + SQL 2000