on 06-02-2015 6:27 PM
Hello,
We have something unexpected with the licensing of a newly set up distributed SAP Dev/Test system. Well, unexpected to us; I'm hoping that's just down to my ignorance and someone will leap in and say "Yup, perfectly normal, don't worry about it!" (or maybe not?) ...
There's a CI (or whatever you wish to call it now) and an DI (application instance) running on one server. That was installed about a year ago and licensed at the time - if we run "SLICENSE" it shows itself as being perfectly happy with the licenses (well, except the maintenance one as we haven't needed to renew that recently, but we can ignore that at the moment).
We've just added a second DI, running on a second server. If we run "SLICENSE" on that, it shows the hardware key and license information from the CI. It still seems quite happy with it, but the license isn't actually for the hardware key from that second server.
So we, as we would normally with any SAP system build, requested a license. We obtained the second server's hardware key by using "saplicense -get" (because "SLICENSE" just shows us the hardware key for the first server), applied for, and obtained, the licenses. But when we install them on the second server (using "SLICENSE"), they show up as being "Valid (inactive hardware key)".
Interestingly, running "saplicense -test" fails (every test passes until "test result: license test failed", "*** no valid license found ***" at the end), but it fails on both servers, even the one which we know is correctly licensed. So I don't think that actually indicates any sort of licensing failure ...
So is the system actually correctly licensed? Does it just need a valid license installing on the CI, and any additional DI (whether running on the CI server or not) will be happy with that license?
Thanks,
Hi Tistram ,
The license for the additional application server is not required . ( As you have already installed the license for the DB and CI server )
Thanks ,
Manu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That is correct.
You need the license only for the hardware key of the server where the Message Server process is running at.
Any instance (CI, DI) you have on any server (the same of the Message Server or not) will connect to the Message Server to get the hardware key, and it will check if a license for that hardware key exists.
You would need more than one license only on HA (High Availability) scenarios, where the Message Server is running at an ASCS instance. The ASCS would be part of a cluster that can have two or more nodes. In this case, you would need one license per cluster node (as the Message Server could run on any cluster node, and it will calculate a different hardware key at each node).
Regards,
Isaías
User | Count |
---|---|
80 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.