Skip to main content

For the new FME Server 2016.1, is there a way to automate the licensing/uploading of a license file at installation time?

Scenario (Windows 2012 R2 DC):

Installing FME Server via silent installation still means that you have to login to FMEServer to setup the licensing. Is there a way to do this at installation time by either supplying an option or by placing a license file somewhere on the file system(restart of fme services required)?

How does the licensing work if you have the possibility of trashing your environment and rebuilding regularly? Do we need to revoke the license or can we just re-use the license over again?

Thanks,

Dan.

Hi Dan @batman1007

OK, second question first, you can re-use the license I believe, but the backup/restore tools won't do that automatically, so it's a manual process either way.

No, I don't think the silent installer allows licensing. I will file an enhancement request because it does seem like a useful capability. If your silent installation was scripted then you could use the REST API and I think it's possible to license a machine that way.

Hope this helps.


Hi Dan @batman1007

OK, second question first, you can re-use the license I believe, but the backup/restore tools won't do that automatically, so it's a manual process either way.

No, I don't think the silent installer allows licensing. I will file an enhancement request because it does seem like a useful capability. If your silent installation was scripted then you could use the REST API and I think it's possible to license a machine that way.

Hope this helps.

I also found out we have an enhancement request to allow the license to reside on a UNC path, meaning you could (in effect) have a remote license "server" - easier to use and quicker when you are trashing and rebuilding your system on a regular basis. If you are interested in that, please contact our support team (safe.com/support) and mention PR#70457


I also found out we have an enhancement request to allow the license to reside on a UNC path, meaning you could (in effect) have a remote license "server" - easier to use and quicker when you are trashing and rebuilding your system on a regular basis. If you are interested in that, please contact our support team (safe.com/support) and mention PR#70457

Thanks Mark. I will look at the REST API as that sounds an interesting avenue to go down for now.


Reply