Hi Heinz,
Good news and bad news:
First the bad news. I can't really advise you much on which WDHT license
to get as I am not familiar with the licensing terms or whatever but I can
help you to understand how it works. So as far as the licensing terms go
whether you need n or 2*n licenses to run n users on two WF apps I don't
have the answer. Nor do I know the cost for per-user or processor based
licenses but maybe after some number of users the processor based license
is more economic? However, I will ask about and see what I can find out
for you - I'm just a lowly developer y'know, not a sales/marketing guru
:-)
Now the good news (or at least something that I know a bit about). You
are correct in that a "user" equates to a browser session in WebFacing. So
ten users running one session each or two users running five sessions each
both are seen by the server as equivalent to ten sessions in use. The
session gives up the license back into the pool when the session ends,
either by the WF'd app ending normally or by session time-out. This
means that when you are considering the number of licenses you need to
take into account that there could be some licenses held in use by
orphaned sessions until they time out. This can happen when the user has
lost the connection or whatever. This can be influenced by the stability
of the application and the manner in which users run the program as well
as the session time-out duration itself.
Mike
Mike Hockings, P.Eng.
System i Application Development Tools - CODE/Designer & WebFacing !
IBM Canada Ltd. Laboratory
hockings@xxxxxxxxxx
voice 1-905-413-3199 T/L 313-3199 ITN 23133199
<Heinz.Sporn@xxxxxxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
02/28/2008 04:16 AM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
To
<wdsci-l@xxxxxxxxxxxx>
cc
Subject
[WDSCI-L] HATS licenses
Hi list!
We are currently planning to move to a new iSeries plus to upgrade from
WDSC 6 to 7 (or maybe even skip that in favour of RDi - but that's a
different story).
WebFacing is our thing so for the first time we have to deal with HATS
licensing. I have no words to describe what an unbelievable nightmare this
issue has turned into since we started investigating.
So I thought maybe there's someone out there who could share some first
hand practical experience regarding HATS licenses.
Here's what we got:
- iSeries
- 2 WebSphere Application Servers V6.1 (productive and backup)
running on identical Windows 2003 systems with Xeon processors (two
cores).
- our mission critical WebFacing application
- roughly 200 users with an average of 2 concurrent sessions each
What we know so far:
- Licenses are applied to WebFacing projects
- 2 models: processor based or user based ("Every person that
benefits from access to the application is defined as a user and must have
a Proof of Entitlement")
Where's the problem?
- ATM we believe that the user based licensing scheme would be a
better choice since we wouldn't stick with a specific system running WAS.
But we simply don't believe that the user based model works as described
but is actually concurrent session based. Proof: WDSC 7 comes with 2
licenses - one user can only open 2 concurrent sessions, 2 concurrent
users can only open 1 session each.
- Licenses have to be applied to projects. So let's assume I have
2 projects and 10 users that may use both applications at the same time.
Will I need 10 or 20 licenses in that case?
- The biggest problem is that 2 IBM business partners plus an
"IBM specialist" are not able to deliver definite answers.
So maybe someone could tell us what you got and how it REALLY works?
Kind regards
Mit freundlichen Grüßen
_________________________________
Heinz Sporn
TE - iSeries Systeme & Kommunikation
voestalpine Stahl Service Center GmbH
Industriezeile 28
4020 Linz, Austria
T. +43 / 50 304 / 19 - 466
M. +43 / 664 / 83 62 355
F. +43 / 50 304 / 597 - 466
mailto:heinz.sporn@xxxxxxxxxxxxxxx
http://www.voestalpine.com/stahlservicecenter
voestalpine - Einen Schritt voraus.
As an Amazon Associate we earn from qualifying purchases.