Import licenses from another installation (flmprg)

You can use the Four Js License Manager (FLM) or license controller (fglWrt/greWrt) import-license feature to move a license from one Genero installation to another or from one license manager to another.

When you move a license, you take a license from one Genero installation and make it available to another. The license is no longer available in the installation it was moved from.

Tip:

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.

For example, if you need to install a new product version, install it in a directory separate to your existing product installation. Move the license from your existing product installation using the flmprg import-license command. In the worst case scenario that the move fails, you can move the license back into your old installation.

A Genero BDL license can be moved to another Genero BDL installation or to a License Manager.
A Genero Report Engine (GRE) license can be moved to another GRE installation or to a License Manager.
A license or all licenses can be moved from one License Manager to another License Manager.
A license installed in a License Manager can be moved to the product installation.

Licenses can be moved from any Genero product version to a different product version provided:

The source and target installations are on the same system.
The licensing tool in the target installation is 6.00.13 or greater or can be upgraded to run in compatibility mode with a license tool 6.00.13 or greater.
Important: Genero Report Writer for Java, C#, and PHP
Genero Report Writer for Java, C#, and PHP 3.20 and earlier cannot run in compatibility mode with licensing tools version 6.00. To use 6.00 licensing tools, you must upgrade to Genero Report Writer for Java, C#, and PHP 4.00 or greater. For more information on compatibility with 6.00 licensing tools, refer to the Install and License Genero Report Writer manual.

For details, refer to Table 1. The actions you can take depends on the version of the licensing tools in the target installation.

Table 1. Moving a license to a Genero installation
Target	Description	Actions
Genero product using licensing tools 6.00.13 or greater	The licensing tools in the target installation have the `import-license` feature.	Run the import license command: `flmprg import-license`
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.	Run the import license command: `flmprg import-license`
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`.	Patch the license controller to 6.00.13 or greater. Run the import license command: `flmprg import-license` Set compatibility mode: set `flm.server="compatv6"` in the product installation /etc/fglprofile file.

Scenarios when you may need to move licenses

You have a Genero 4.00 BDL installation license (fglWrt v6.00.13 or greater) and you want to move it to another Genero 4.00 BDL product installation (fglWrt v6.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 have a Genero 3.20 BDL installation (fglWrt v5.20) and you want to move a license you use in a Genero 4.00 BDL product installation (fglWrt v6.00.13 or greater). In this example:
1. Patch the license contoller in the Genero 3.20 BDL installation to bring it up to version 6.00.13 or greater.
2. Import the Genero BDL license in the specified directory to the 3.20 installation:
```
fglWrt import-license --from /opt/fourjs/fglgws4
```
3. Configure the Genero 3.20 installation for compatibility. Set flm.server="compatv6" in the FGLDIR/etc/fglprofile file.
You have a License Manager 5.20 installation and you want to move a license or licenses from it to a License Manager 6.00 installation (flmprg 6.00.13 or greater). In this example, you have two options:
1. To move all licenses, use the import-all-licenses command:
```
flmprg import-all-licenses --from /opt/fourjs/flm5
```
2. Alternatively, to move a specific license, use the import-license command and specify the license number:
```
flmprg import-license --from /opt/fourjs/flm5 --license TAB#XXXXXXXX
```
You have a License Manager 5.20 license and you want to upgrade to a License Manager 6 license. Licenses installed by FLM version 5 have a different license file format than licenses installed by FLM 6.00. This example imports the specified license from the current installation directory ($FLMDIR) and upgrades it to FLM 6.00:
```
flmprg import-license --license XXX#XXXXXXXX
```

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.