Import license from another installation
Licenses can be moved from one Genero installation to another.
Moving a license is an alternative to uninstalling and reinstalling a license. An additional advantage is that you do not need to reactivate the license by registering it with Four Js.
- When using Four Js License Manager:
-
- A license or all licenses can be moved from one License Manager to another License Manager,
using the
flmprg import-license
or theimport-all-licenses
command. - A license installed in a License Manager can be moved to the product installation, using the
flmprg import-license
command.
- A license or all licenses can be moved from one License Manager to another License Manager,
using the
- When local licensing:
-
- A Genero BDL license can be moved to another Genero BDL
installation or to a License Manager, using the
fglWrt import-license
command. - A Genero Report Engine (GRE) license can be
moved to another GRE installation or to a License Manager, using the
greWrt import-license
command.
- A Genero BDL license can be moved to another Genero BDL
installation or to a License Manager, using the
- The source and target installations are on the same system.
- The licensing tools in the target installation are version 6.00.13 or greater or can be upgraded to run in compatibility mode with a license tool 6.00.13 or greater. Use the table below to determine the actions you have to take based on the version of the licensing tools in the target installation.
Target installation | Description | Actions |
---|---|---|
Genero product using licensing tools 6.00.13 or greater |
The licensing tools in the target installation have the
import-license feature. |
|
Genero product running in compatibility mode using licensing tools 6.00.13 or greater |
The licensing tools in the target installation have the
import-license feature. |
|
Genero product using licensing tools 5.20 |
The licensing tools in the target installation need to be brought up to version
6.00.13 or greater to use import-license . |
|
Scenarios when you may need to move licenses
- You licensed a Genero 4.00 installation (license controller version 6.00.13 or greater) and you
want to move the license to another Genero 4.00 installation (license controller version 6.00.13 or
greater). In this example, the Genero BDL license in the specified directory is imported into the
current
installation:
fglWrt import-license --from /opt/fourjs/fglgws
- You licensed a Genero 3.20 installation (license controller version 5.20) and you want to move
the license to a Genero 4.00 installation (license controller version 6.00.13 or greater). In this
example, the Genero BDL license in the specified directory is imported into the current
installation:
fglWrt import-license --from /opt/fourjs/fglgws320
- You licensed a Genero 4.00
product installation (license controller v6.00.13 or greater) and you want to move the license to a
Genero 3.20 installation (license controller version 5.20). In this example:
- Patch the license controller in the Genero 3.20 installation to bring it up to version 6.00.13 or greater.
- Import the Genero license in the specified directory to the 3.20
installation:
fglWrt import-license --from /opt/fourjs/fglgws4
- Configure the Genero 3.20 installation for compatibility. Set
flm.server="compatv6"
in the product installation /etc/fglprofile file.
- You have a License Manager 5.20 installation and you want to move a license to a Genero 4.00
product installation (license controller version 6.00.13 or greater). In this example, the specified
license from the License Manager 5 installation is moved into the current Genero
installation:
fglWrt import-license --from /opt/fourjs/flm5 --license XXX#XXXXXXX
Log files and debugging
The output from a command to move a license is recorded in a log file. Log files are found in the Genero installation /etc/license directory where the command is run.
Log filenames are in the format move-license.log. If more than one log file is present, the most recent log will have the highest number in the sequence: move-license.1.log, move-license.2.log, and so on.
The log file records the event of moving a license. It contains the result of the analysis of the source and destination installations. If the move is successful, the details of where the license was moved from and moved to is given. If the move fails for some reason, such as the license.dat file not found, the cause is explained in detail in the file. This file is useful if you need to troubleshoot issues moving a license.