Import license from another installation

Licenses can be moved from one Genero installation 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.

Using Four Js License Manager:

Transfer a single license:
- Use the command flmprg import-license to move a license from one License Manager to another.
Transfer all licenses:
- Use the command flmprg import-all-licenses to transfer all licenses from one License Manager to another.
Move a license to the product installation:
- Use the command flmprg import-license to transfer a license from the License Manager to the product installation.

Using local licensing:

Move a Genero BDL license:
- Use the command fglWrt import-license to transfer the license to another Genero BDL installation or License Manager.
Move a Genero Report Engine (GRE) License:
- Use the command greWrt import-license to transfer the license to another GRE installation or License Manager.

When moving your license from one Genero product version to a different product version, ensure these conditions are met:

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.

Table 1. Moving a license to a Genero 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.	Run the import license command: `fglWrt/greWrt 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: `fglWrt/greWrt 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: `fglWrt/greWrt import-license` Set compatibility mode: set `flm.server="compatv6"` in the product installation /etc/fglprofile file.

Scenarios when you may need to move licenses

These are some scenarios when you might import licenses. In the worst case that the move fails, you can move the license back into your old installation.

Move a license from one Genero 4.00 installation to another: 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
```
Move a license from a Genero 3.20 installation to a Genero 4.00 installation: 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
```
Move a license from a Genero 4.00 installation to a Genero 3.20 installation: 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:
1. Patch the license controller in the Genero 3.20 installation to bring it up to version 6.00.13 or greater.
2. Import the Genero 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 product installation /etc/fglprofile file.
Move a license from an FLM 5.20 installation to a Genero 4.00 product installation: 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
```
You want to upgrade a license version 5.20 to version 6.00 in a Genero installation. In this example, fglWrt import-license upgrades the license in the current product installation directory if it is a license version 5.20:
```
fglWrt import-license
```

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.