Automatic license Transfer

[trymes]

I am really sick of having to move my license into a new version of QM every time yum updates it. Why can't the license be stored in a Database or somewhere else that doesn't require manual intervention at every upgrade?

Just a thought,

Tom

[QueueMetrics]

The reason why is that when you install a new system, it will have a license key embedded. Otherwise the oldest license would be copied over (even if expired).

[trymes]

I don't understand. Why couldn't a post-install script copy the file from a previous installation if it existed? If the key is expired, you are no worse off than you were to start, as your old copy was expired, too, and you were going to have to manually update it anyway.

Maybe even a step added to the GUI (say as part of dbtest?) that would allow you to clikc and have the file moved? Better yet, follow the standard method of saving the new config file as filename.rpmnew and keeping the old one. That would require a new location for the file, but...

Maybe you could store the license in the DB?

It's really annoying to have to move the license with each upgrade. I have never seen another piece of software where this is needed.

Tom

[QueueMetrics]

Yes I agree. We really need to make it better.

[trymes]

Another side effect I noticed of the current method is that the other settings for the software, such as "default queue_log file" are overwritten at each upgrade. If you're using the real-time queue_log feature, this breaks QM until you modify it again.

Tom

[QueueMetrics]

This is fixed in the upcoming version 163

[trymes]

Excellent? How will this be accomplished, If I might ask?

[QueueMetrics]

There is a new file called tpf.properties that is copied through the versions by the yum installer.
It works if you upgrade 163 to 170 or whatever it will be using yum.
The release notes should contain more details on how to fix that.
Thanks for proposing this change! I'm sure everybody will like it.

[trymes]

Thanks for the change, I'm looking forward to taking advantage of it!

Two questions, though:

1.) This will not move current settings over to a new version? I'm thinking realtime queue_log, etc?
2.) I just updated to 1.6.3.1-74 from 1.6.3.0 via yum, and the license reverted to demo. Any idea why?

Many thanks,

Tom

[QueueMetrics]

Yes settings should be copied as well.
It works if you use the new tpf.properties file. The web,xml is always overwritten.