Jiwa

Hi Guys

Just a quick question regrading how CALs operate under Jiwa, so that I can get my head around it and explain the technicals correctly to a client, if a website was calling Jiwa under the following first two options how would the counting of used/logged in CALs work:

1. Website that connected at the application level i.e. at start up logged in say as Admin but served multiple users, in this scenario would is also be possible to set/changed the last modified by on certain object to the web user

2.Website that logins as multiple users and each session actually logged in as an actual different user but all in the same application space.

3. Also for Jiwa itself if you open multiple copies on the one machine is this one or many?

Thanks

SBarnes wrote:Hi Guys

Just a quick question regrading how CALs operate under Jiwa, so that I can get my head around it and explain the technicals correctly to a client, if a website was calling Jiwa under the following first two options how would the counting of used/logged in CALs work:

1. Website that connected at the application level i.e. at start up logged in say as Admin but served multiple users, in this scenario would is also be possible to set/changed the last modified by on certain object to the web user

If you establish a connection as user "Admin", then all actions using our libraries are for that user. We don't support switching users once a connection is established. So no, you can't login as user "Admin" and perform actions on behalf of a different user. You could disconnect, and reconnect as another user as required.

SBarnes wrote:2.Website that logins as multiple users and each session actually logged in as an actual different user but all in the same application space.

Each user consumes one CAL per database. You'd need a CAL for each unique user, as it's a different connection. You can connect multiple times as the same user to the same database, and that only uses one CAL.

SBarnes wrote:3. Also for Jiwa itself if you open multiple copies on the one machine is this one or many?

It uses one CAL per user per database. Opening Jiwa 10 times and connecting to the same database with the same user only uses 1 CAL.

We insert an uncommitted transaction into the SY_LicenceUsages table upon login, and perform a read uncommitted count to check if the licence limit has been reached. You can see this yourself by running the following query:

Code: Select all

SET transaction isolation level read uncommitted
SELECT * FROM SY_LicenceUsages

You can also see the currently used licences from the Licences form within Jiwa itself.

Note that for services, it is recommended to use a named licence, and your service connect using the Jiwa username of the named licence. This way your service does not compete with other users for a concurrent licence - it has it's own licence and should be guaranteed a connection regardless of how many other users are in the system. You can request a named licence by contacting [email protected] and specifying the Jiwa username for the licence.

Thanks Mike,

You have pretty well confirmed what I had assumed although I didn't know about the named license, which is a good idea if you need to guarantee a certain process can connnect.