Multiple PowerHouse Licenses on a single node

[Steve Heaslip]

The Development license is only for a small number of users, and the Runtime
license allows a lot more people to run the application. 
My knowledge of how the licensing works is very limited (and what I do know
is rusty!) - but I think if we try to have everybody running under the Dev
license we'll max out around 4 or 5 users.

  _____  

From: powerh-l-bounces+heaslips=ozemail.com.au at lists.sowder.com
[mailto:powerh-l-bounces+heaslips=ozemail.com.au at lists.sowder.com] On Behalf
Of Pickering, John (NORBORD)
Sent: Thursday, 6 December 2007 13:20
To: heaslips at ozemail.com.au; powerh-l at lists.sowder.com
Subject: Re: Multiple PowerHouse Licenses on a single node



I'm no Vax expert but if you put a full development license on the
production server, why would you want or need a run-time license?



-----Original Message-----
From: powerh-l-bounces+john.pickering=norbord.com at lists.sowder.com
<powerh-l-bounces+john.pickering=norbord.com at lists.sowder.com>
To: PowerHouse List <powerh-l at lists.sowder.com>
Sent: Wed Dec 05 20:15:38 2007
Subject: Multiple PowerHouse Licenses on a single node

Hi all

PowerHouse 7.10g on OpenVMS.

We have a legacy client who have the usual configuration of 2 Alphas
clustered together - one Alpha licensed for PowerHouse Development and one
licensed for PowerHouse Runtime/Reporting for Production.
There has been no development work done on the system in years and the
client wants to know if they can put both PowerHouse licenses onto a single
Alpha.

In all the PowerHouse environments I've encountered there has always been
(at least) 2 nodes so that development/production didn't interfere with one
another in terms of performance, so I've never seen an instance where both
licenses are on the one box. .

Can anyone tell me if there's any reason why both PowerHouse licenses can't
run on the one node?

And if both licenses CAN be installed on the same node are there any traps
to watch out for?



Thanks in advance


Steve Heaslip

Email:  heaslips at ozemail.com.au <mailto:heaslips at ozemail.com.au>




-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.sowder.com/pipermail/powerh-l/attachments/20071206/fac705b3/attachment.html