Applying a LANSA license to Version 14 Service Pack 2 (EPC142050 and above)

Date: 30 April 2019
Product/Release: LANSA V14 SP2 EPC142050
Abstract: You must be at V14 SP2 EPC142050 to use these steps to apply LANSA licenses
Submitted By: LANSA Technical Support

IMPORTANT: The information on this page relates to applying a license at Visual LANSA V14 SP2 EPC142050 level, including the new LANSA development licensing introduced in EPC142050. To apply a V13 LANSA license, click here.

In EPC142050 for V14 Service Pack 2, changes have been made how LANSA development licenses are applied to Visual LANSA. These changes affect licenses of type LANSA Development License Code(s). Your LANSA License email notification states what type of license you have received. Select the appropriate type below:


Server/Runtime License Code

This type of LANSA licensing generally applies to runtime licenses applied to a server, for example, LXX (superserver), JME (LANSA Integrator), WEB (Web execution).

Note: The license you have received is only valid for the CPU that you have requested it for.

Select the Operating System to apply this license to:


LANSA Development License Code (Local or Remote License server)

In EPC142050, LANSA has replaced the existing 3rd party softkey licensing with a new development licensing model.

Note: The license you have received is only valid for the CPU that you have requested it for.

Select the type of LANSA Development License:


Server License Code - Windows

Visual LANSA V14 server license codes will be provided in a file named
x_lic_<model>_Serial number>_<request number>.xml
See image below for an example.

Exame of email containing a license code file

To install your new license details, perform the following steps:

  1. Copy the x_lic_*.xml file to a local location on your PC. While you can copy the license file to any local location, the recommended location is the Visual LANSA \X_LANSA folder as this is the default location that the license facility will look in. For example, <root>\X_WIN95\X_LANSA
  2. From the LANSA folder, Open the Settings and Administration folder and select the Licensing - Server Licenses shortcut.
    Select Server Licenses from the Settings and Administration folder
  3. This will open the Server Licenses utility. Before continuing, make sure that the title states Server License V14 SP1
    Server Licences - V14 SP1
    The user interface for V14 SP1 has changed. New in V14 SP1 is a license file location, which can be local or shared. There are 3 license screens ...Applied, Add Licenses and Advanced Settings.
  4. Applied
    The Applied tab sheet will indicate whether the active license file location is Local or Shared. If this is a new V14 installation, no licenses will be listed yet.
    V14 SP1 Server Licenses has 3 screens: Applied, Add Licenses and Advanced Settings
    • File Location - Active This attempts to load the license file for the current LANSA environment. If a license file exists locally, this will be loaded. If there is no license file locally, the shared location will be searched for a license file (refer to Advanced Settings for the Shared location details).
    • File Location - Local This attempts to load the local license file. The Local location defaults to <root>:\x_win95\x_lansa\ where <root> is the current LANSA system. 
    • File Location - Shared This option indicates if a license file exists in the location specified as the shared location. A shared license file can be accessed by more than 1 LANSA system on the same CPU.
    • File Location - Other Selecting Other allows you to navigate to a location where a license file exists for any CPU and loads the licenses for review.
    • Delete Selected This allows you to deleted 1 or more selected licenses from a license file, for example, expired licenses or duplicates. Care should be taken when selecting and deleting licenses.
  5. Add Licenses
    This screen allows you to navigate to a location and select an XML file containing licenses to be applied.
    Loading Server Licences Codes from file
    • Save to File Location Active When you apply licenses with Active selected, they will be added to the license file that is Active.  
    • Save to File Location Local When you apply licenses with Local selected, they will be added to the license file for the current LANSA environment..
    • Save to File Location Shared When you apply licenses with Shared selected, they will be added to the license file in the location specified for Shared in Advanced Settings.
    • Save to File Location Temp When you apply licenses with Temp selected, a license file will be created in the %TEMP% location. If a license file for this CPU already exists in %TEMP%, they will be added to the license file. Save to Location Temp is useful if you are generating license files for other CPUs.
  6. Note: If you have any expired licenses, for example, expired temporary licenses, you should use the Delete Selected button to remove them. The list of licenses on this screen should only include valid, unexpired licenses. Refer to Cleaning up of unwanted license records for further details on License Maintenance.
  7. Advanced Settings
    Allows you to review and set default locations for license files. The current Shared location is displayed at the top of the screen.
    Advanced Settings
  8. Set the location for shared LANSA license location.  You can set the location of where you want the Shared license file to be located. This might be an existing LANSA location or the default LANSA Common location: C:\Program Files (x86)\Common Files\LANSA. You can type in a location or use the button to navigate to a location.
  9. Default If you wish to set the Shared license file location to the defaut, you can select the Default button, which sets the shared LANSA license location to C:\Program Files (x86)\Common Files\LANSA. If you now go back to the Applied tabsheet and select Shared, the new location set in Advanced Settings will be shown.
  10. Copy This option allows you to copy the LANSA license file from the set Shared license file location to the Local license file location. This is useful if you install a new Visual LANSA configuration and you only want to add licenses to this configuration. A Copy message box will be issued asking if you wish to proceed.
    Copy license file to shared location
  11. Move This option allows you to move a license file to the shared location. This option is useful if you applied a license locally but want all Visual LANSA configurations on this CPU to access the licenses. A dialog will be issued asking if you wish to proceed.
    Move license file to shared location
    If no license file exists in the location you are moving from (or if you have already moved the license file from this location), the move will fail and a message will be issued.
    Attempt to move file failed
  12. Generating an invalid license error? See troubleshooting

Note: If the licenses are to be applied to a Windows server running the LANSA Listener, you must stop the listener before adding LANSA license codes and restart it again for the new license codes to be recognized.


Server License Codes - IBM i

A few points to consider regarding LANSA for iSeries V14 licensing

  • New licenses are required for V14. The license details are provided in an xml document in the same way as the Visual LANSA Server License codes
  • A new V14 install or an upgrade to V14 will create a License folder in the LANSA_<pgmlib> tree on the IBM i IFS. For example, /LANSA_dcxpgmlib/license
  • The x_lic_*.xml file you receive from LANSA licensing should be copied to this IFS location. You IBM i administrator can provide the steps to move a file to the IBM i IFS. The most common methods are to use the QNTC file system, AS/400 NetServer or iSeries Navigator.
  • The following steps assume that the V14 license file is already located in the IBM i IFS location /LANSA_<pgmlib>/license

Steps to apply a license:

  1. Sign on to the IBM i using one of the following profiles:
    QSECOFR user profile or partition security officer profile for SYS partition.
  2. From an i5/OS command entry (CALL QCMD), execute the LANSA license facility using the command:
    <pgmlib>/LANSA LICENSE
  3. All current licenses will be listed with their status. Note: If this is a new V14 install, you will see a standard list of 7 day temporary licenses which are provided with the new install.
    View current licenses
  4. Select F6 to launch the Request New License File screen. On this screen, you need to enter the full IFS path to the license file, including the license file name, as per the screen below.
    Hint: To avoid mistakes in the path, use WRKLNK to navigate to the location and press option 5 to view the XML file. Then you can copy the full path from the Browse field at the top of the screen and paste it into the New License File Path.
    Enter the path to the license file
  5. After pressing Enter, the New License screen will be re-displayed. Existing and new licenses will be indicated.
    The new license will now be added to the list of existing licenses
  6. Press F6=Apply to apply the licenses. Your license file will be updated with the new license codes details.
  7. Note: If you have any expired licenses, for example, expired temporary licenses, you should use the F22 Delete function key ont he main screen to remove them. The list of licenses on this screen should only include valid, unexpired licenses. Refer to Cleaning up of unwanted license records for further details on License Maintenance.
  8. Generating an invalid license error? See troubleshooting

Server License Codes - UNIX/Linux

Instructions to come.

Generating an invalid license error? See troubleshooting


LANSA Development License Code - Local Visual LANSA Development and Web development (Windows only)

Pre license steps: Applying EPC142050 to V14 SP2 will introduce the new LANSA development licensing and all previous licenses will no longer be valid. EPC142050 will install

  • A LANSA Development License Manager
  • A LANSA Development License Studio
  • A LANSA License service

Shortcuts will also be created on your desktop to the LANSA Development License Manager and the LANSA Development License Studio.

  1. You will receive an email from LANSA License with the LANSA Development License Code. The mail will contain a file named licenses_<CPU>_<Serial Number>_<ID>.DAT. For example, LICENSES_170A_1DD2557A_9140000435.DAT
  2. Copy the supplied file to a temporary location on your hard drive.
  3. Open the LANSA Development License Manager from the desktop shortcut.
    LANSA Development License Manager screen
  4. Select the Add Licenses tab and use the browse button to navigate to the location where you copied the license .DAT file in step 2.
  5. Select the file and open it.
  6. The Add Licenses screen will now show the list of licenses from the DAT file. Generally, you will see DEV and WEB codes which make up the VLW group. The display will also show the start and end dates and whether the codes are valid.
    Note: If you see DEV and WEB and WRT codes which make up the VLN group, after adding the license, you must then follow the instructions in step 13 to nominate a Remote License Server, even if the remote license server is your own PC.
    Apply a license in LANSA Development License Manager
  7. If all the details look correct, click the Add Licenses button to apply the licenses.
  8. A confirmation screen will be shown with details of the actions to be taken. Click Yes to proceed.
    License Service restart confirmation
  9. The licenses will be applied and the LANSA License Service will be started (or restarted).
    LANSA License service restarted
  10. Once the licenses are applied, click the Current Licenses tab to see the currently applied licenses.

    Current Development licenses
  11. You are now ready to use Visual LANSA.
  12. Generating an invalid license error? See troubleshooting

LANSA Development License Code - Remote Visual LANSA Development and Web development (Windows only)

Notes:

  • These steps must be performed on the CPU that is nominated as the Remote License server.
  • The Remote License server does not require any Visual LANSA installation. You can install the independent License Server software on this CPU.
  • The X_CPU details are generated here and the license is applied here.
  • The client PCs (where Visual LANSA is installed) must point to the Remote Licene Server to obtain a license slot.

Pre license steps: Applying EPC142050 to V14 SP2 will introduce the new LANSA development licensing and all previous licenses will no longer be valid. Both installing the independent License Server software or applying EPC142050 to a V14 SP2 VL installation will install

  • A LANSA Development License Manager
  • A LANSA Development License Studio
  • A LANSA License service

Shortcuts will also be created on your desktop to the LANSA Development License Manager and the LANSA Development License Studio.

On the Remote License Server PC, perform the following steps:

  1. You will receive an email from LANSA License with the LANSA Development License Code. The mail will contain a file named licenses_<CPU>_<Serial Number>_<ID>.DAT. For example, LICENSES_170A_1DD2557A_9140000435.DAT
  2. Copy the supplied file to a temporary location on your hard drive.
  3. Open the LANSA Development License Manager from the desktop shortcut on the License Server.
    LANSA Development License Manager screen
  4. Select the Add Licenses tab and use the browse button to navigate to the location where you copied the license .DAT file in step 2.
  5. Select the file and open it.
  6. The Add Licenses screen will now show the list of licenses from the DAT file. Generally, you will see DEV and WEB and WRT codes which make up the VLN group. Note that a VLN will include a number of VL seats. The display will also show the start and end dates and whether the codes are valid.
    Add VLN LANSA Development License Manager
  7. If all the details look correct, click the Add Licenses button to apply the licenses.
  8. A confirmation screen will be shown with details of the actions to be taken. Click Yes to proceed.
    Add VLN restart server screen
  9. The licenses will be applied and the LANSA License Service will be started (or restarted).
    Add VLN restart server confirmation screen
  10. Once the licenses are applied, click the Current Licenses tab to see the currently applied licenses.
    Current VLN LANSA Development License Manager
  11. The Remote License Server is now ready for use.
  12. Once the Remote License Server is ready, up to 5 Visual LANSA IDE's can be launched using this development license.
  13. The next step is performed on the PCs where the Visual LANSA development is to be done. You must make the VL development PC aware of this Remote License Server. On each Visual LANSA Development PC, open the LANSA Licensing Studio from the shortcut on the desktop and perform the following steps
    • Set the License Server radiobutton to Host Name and enter the name of the Remote License Server Computer Name or IP Address in the entry field (ask your network administrator for this information if you cannot access this information).
    • Press the Refresh License Status button. This will load the license details from the nominated Remote License Server and will enable the Use License Server <Name> for Development button.
    • Click the Use License Server <Name> for Development button and Close the Studio.
      LANSA Development License Studio screen
  14. Any VL development PCs that have performed these steps will now use the nominated Remote License Server for obtaining a development license when opening the Visual LANSA Development environment.
  15. Generating an invalid license error? See troubleshooting

 

LANSA Development License Code - License Consolidation across versions of Visual LANSA.

The new development licensing model is only available for supported versions of LANSA, currently V14 SP2 (at the latest EPC level) and V13 SP2 (at the latest EPC level). The following steps assume you are using the new LANSA Development licensing model for both V14 and V13.

If you currently have a Remote License Server servicing V14 Visual LANSA and you wish the same the same Remote License Server to also service V13 Visual LANSA, perform the following steps

  1. Request your V13 License Server license(s) by providing the CPU details of your Remote License Server CPU.
  2. When you receive your licenses_<CPU>_<Serial Number>_<ID>.DAT file, copy it to a temporary location on the Remote License Server PC.
  3. Follow steps 3 to 14 in Visual LANSA Development multi-seat Licence Server (Remote Windows only)
  4. Once you have completed the steps, your Remote license server will service license seats for both V14 and V13.