kereni
9th April 2003, 11:06
We have a production server with license installed.
We want to share this license with 2 others tests servers.

What are the steps to share the licenses (licence6.1 etc)?

pmontavon
9th April 2003, 11:48
We use one server for production and two "Test-server"
for development.
The licence is installed on our "Production server".
On the "Test-server", in file licence6.1 we have indicate the name of the "Production Server" and we can open sessions
on all servers.

OmeLuuk
9th April 2003, 12:09
See solutions below.
82511 How does the Baan licence server (LICD) work: Part I
102338 How does the Baan licence server (LICD) work: Part II

Be aware that the validation machines use the same DBMS (or that both different DBMSses are validated).

We have had problems with sharing licences, due to the fact that in /etc/services the port is determined where licmon runs:
licence6.1 6096/tcp # Baan licence daemon
This must be the same port on both machines.

kereni
9th April 2003, 12:21
Is there any others steps to perform after the licence6.1 changing to avoid 'illegal objects' errors?

OmeLuuk
9th April 2003, 12:53
You have to patch your objects with the new licensecode using session ttiex3225m000

estotz
13th April 2003, 19:51
One note. Whatever server you put your "license server" on, if it is down for maintenance, then you will not be able to run Baan on the other servers. e.g. if you put your license server on production, if production is down, then you won't be able to run Baan on your test servers.

This may impact you if you use your test servers for development, or for other situations when production is down.

You can put a license server on pretty much any size CPU as it does not take much processing at all, so you may want to use a "spare" server as the license server for all 3 or your servers.

If you feel going down on production does not matter for your test servers, then you don't need to worry about it.

Kingsto88
15th December 2006, 03:44
Hi experts,

After reading this thread, I find myself confused. I am new in this sharing licenses. Can someone clarify this steps.

1) lets say prod server name is King, license6.1 contain 'king'
2) lets say dev server name is Queen, license6.1 in dev server also enter 'king'?
3) Is that all?
4) then I should run ttiex3225m000?

How do i have a third server to keep the license for king and queen?
Let's say third server is Jack.
Do I just copy license6.1 over to Jack and then enter 'Jack' into the license6.1 in King and Queen?

Please help.

thanks and rgds

suhas-mahajan
26th December 2006, 10:25
King,

If you have activated licence daemon on KING then you have to use this hostname for each BSE setup may be Queen or Jack into licence6.1, if you would to share licences from KING, otherwise you can use that software for 30 days only.

regards,

-Suhas

ecarceller
28th December 2006, 00:52
Your Majesty ;)

You can have your license running on multiple servers with one licd6.1 on each box sharing the same pool of licenses (for high availability architectures)

or

you can have it running in only one box and have the other servers point to it

The option of having Baan's license running in multiple servers used to cause all sorts of problems so it more or less became common practice to have licd6.1 running in just one box with the others pointing to it.

I have never tried the option of the third server but it may work. You need to install Baan on that third box as well, only that you don't need your application there. You do need tools because you need to be able to validate tools set, and you need at least your company 000's license tables. Then you need to have "Jack" in all 3 servers' licence6.1 file. The idea here is that having a license only servers allows you to stop prod and dev without affecting each other.

I think the license only server is too much trouble. In practice if you use your production server to run the license you'll be fine over 99% of the times. Think it this way: how often do you stop production? probably not to often. And when you stop it, what day of the week do you stop it? I bet that doesn't happen on Mondays :) So what are the chances of having developers and testers needing to access Baan during Production downtime? Not null that is for sure but in my experience they are low enough.

Darren Phillips
28th December 2006, 05:06
I have a seperate licence server, it works fine. all you need on that server is the portingset.

suhas-mahajan
28th December 2006, 06:56
Hi ecarceller,

Can you please elaborate more on first option? Is it a different mechanism rather than BaaN's HA licence?


Baan's license running in multiple servers used to cause all sorts of problems

What kind of problem you are talking about? I think it will be advantage.

We have licence daemon running on Production Server and other dev, qa and test pointing to that.

regards,

-Suhas

ecarceller
28th December 2006, 17:41
Suhas,

This is Baan's HA license I am talking about.

The problems I talk about used to happen a long, long time ago. Around 1997. If you have 3 servers sharing say 300 licenses and one of them goes down after some time (72hrs?) your licenses are chopped down to 200 (one third less). The problem was that some times (like once a month) the license daemons lost connectivity with each other for no apparent reason. When that happened the licenses were reduced by a third or two leaving a bunch of people out of the system. Even the fact that the servers were bounced weekly (for other reasons, not just license) did not prevent that from happening. Things got so bad politically that Baan agreed to give them three separate full sets of permanent licenses, one per server. Needless to say that was not a very smart thing to do. Until the time I lost contact with that customer Baan was still trying to convince them to change to a two servers HA license architecture under which the problem had been solved.
Anyways, that's ancient history. The reason why I brought this up is because these events moved some Baan consultants (me included) to recommend running licenses in only one server. It made sense back then and in the end it works fine even today. For HA architectures in the event of the server with the license going down it is a matter of patching objects after system crash on the fail-over box and live with the warning messages until you get a new license (one day at the most?).
I personally don't like having production licenses on development servers but it is just a matter of taste (I am getting old and grumpy! ;) ). However as long as your downtimes on dev are less than the license threshold for # of lics reduction no one will notice a thing.

By the way I think 2 is still the magic number of servers for HA licenses, anybody knows?

Eduardo

ecarceller
28th December 2006, 17:48
I have a seperate licence server, it works fine. all you need on that server is the portingset.

Hi Darren,

How did you create your ".brand"? With brand6.1?

Darren Phillips
29th December 2006, 01:13
Hi ecarceller
yes with the brand.exe

brand.exe -o "organisation name" -c "customer number" -l "licence code" -b "security code" -a "validation tools key"

abhay1207
19th June 2009, 07:08
Hi,
I have shared the licenses of my production server (Baan IVc4, SP14)to another server by pointing in the License6.1 file. It works for all modules except Tools. When I try to open any tools session it gives me error : Illegal Objects<Object Path/Object> (Error 2). I am also unable to run Patch Object Session(ttiex3225m000;ttiex3226m000).
Can anyone help me out?

Thanks

dheerendra_gosw
19th June 2009, 08:43
Hi,

Please run the session ttiex3227m000 (Patch Object for Tools Developement Package) and run ttiex3228m000 also..
Now restart the licence service and shared memory also...


Thx,
Dheerendra Goswami

vktonk
15th March 2010, 13:10
I have a seperate licence server, it works fine. all you need on that server is the portingset.

Hi,
Did you install Separate SLM Servers on both the boxes?
Please send me the all the steps involved.

Thanks in Advance

nitesh_sh
17th October 2010, 16:06
hi,

i am also facing same problem.Not able to run tools session when i shared the licence to my test server.

Please help me if anyone has idea how to resolve this problem

Rammie
13th December 2013, 13:36
I'm also having this problem.

license6.1 on our new test server points to the server running the license daemon but tools sessions crash with "illegal object" errors.

Can't run the patch object sessions as suggested as I get the error "Validation key software unknown".

Another test server is set up in the same way and it works perfectly, so any help would be greatly appreciated!

Thanks,

Dave

jclju1
19th April 2019, 18:20
I have the same issue: "license6.1 on our new test server points to the server running the license daemon but tools sessions crash with "illegal object" errors."
I did the same many times and never before had this problem.

Can somebody help here?

ln_tools
9th August 2019, 16:30
We have a production server with license installed.
We want to share this license with 2 others tests servers.

What are the steps to share the licenses (licence6.1 etc)?

you want to request 2 new test license...it is not legal to share the same license.

mimran
23rd September 2019, 08:56
Thanks, This is helpful.