|
Home > Archive > WebSphere HATS > October 2005 > Licence Problem:discrepancy between HATS and WAS
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Licence Problem:discrepancy between HATS and WAS
|
|
| Alberto Todeschini 2005-10-11, 7:45 am |
| Hi, we have this (big!) problem: a project that works perfectly on HATS
websphere test environment (5.1) BUT gives the licence problem HPS5142 when
published on the W.A.S. (version 5.1.1.5). Checked the
runonserver.properties and runtime.properties on HATS machine and they're
ok: 100 licences and the hardcoded value.
On WAS there is only runtime.properties but it is has empty encrypted value
(licenseHardLimit) and numlicences=1 !!
Of course, trying to change these values here and restarting the application
has no effect at all, nor to change it from the administrative console
(nameapp/hatsamin/admin) as suggested somewhere.
ANY help would be greatly apreciated, thank you.
| |
| Angelea XXX 2005-10-12, 5:45 pm |
| The quick solution is to simply ocpy the license information from
runonserver file into the runtime.properties file. Did you do this?
HATS uses the runonserver file when in the test environment and
runtime.properties when deployed
--
Alberto Todeschini wrote:
> Hi, we have this (big!) problem: a project that works perfectly on
> HATS websphere test environment (5.1) BUT gives the licence problem
> HPS5142 when published on the W.A.S. (version 5.1.1.5). Checked the
> runonserver.properties and runtime.properties on HATS machine and
> they're ok: 100 licences and the hardcoded value. On WAS there is
> only runtime.properties but it is has empty encrypted value
> (licenseHardLimit) and numlicences=1 !! Of course, trying to change
> these values here and restarting the application has no effect at
> all, nor to change it from the administrative console
> (nameapp/hatsamin/admin) as suggested somewhere. ANY help would be
> greatly apreciated, thank you.
|
|
|
|
|