Upgrading lmadmin
Before installing a new version of lmadmin:
|
•
|
If you have configured lmadmin as a system service, shut down the service. |
|
•
|
Shut down any lmadmin processes running on the system. |
|
•
|
Do not run the 32-bit lmadmin and the 64-bit lmadmin on the same system. If you are upgrading from the 32-bit lmadmin to the 64-bit lmadmin, you must stop and deinstall the 32-bit lmadmin first. |
The lmadmin installer provides the option Import Files from Previous Installation. This option enables you to upgrade lmadmin while retaining a previous lmadmin configuration.
The following files and folders are imported from an existing lmadmin installation:
|
•
|
lmadmin configuration data—Permanent lmadmin settings that were configured either via the license server management interface or via the command-line. For example, these settings include the license server port number, vendor daemon path and port, three-server redundant port, and the maximum size of a file import. These and other configuration data are held in the file server.xml which is imported to the conf directory. |
|
•
|
Vendor daemon files and license files—The vendor daemon executable, the license file used to start the vendor daemon, and additional license files imported via the license server management interface after the initial import of a vendor daemon. A copy of the directory structure is created and these files are imported. |
|
•
|
Log files—The log file (<vendor>.log) for each vendor daemon. |
This section describes the upgrade procedure when you are installing the latest version of lmadmin and want to import files from a previous lmadmin installation. To determine which version of lmadmin you are using, see the Release Version value displayed on the System Information page.
To upgrade an existing lmadmin installation:
|
1.
|
Run the lmadmin installer. |
|
2.
|
In Choose Install Folder, set the installation root directory. Ensure that the installation root directory is not a sub-directory of the existing installation. (On Windows, the default path is C:\Program Files\FlexNet Publisher 64-bit License Server Manager for the 64-bit lmadmin or C:\Program Files (x86)\FlexNet Publisher License Server Manager for the 32-bit lmadmin.) |
|
3.
|
(Windows only) In Choose Data Folder, set the runtime data directory. The default path is C:\ProgramData\FLEXlm\lmadmin. |
|
4.
|
In Import Files from Previous Installation, you can select to import data from a previous installation. To do so, select the Import check box and provide the path to the installation root directory of the relevant lmadmin installation. |
Provide the following information:
|
•
|
Previous Installation Path—Specify the path to the installation root directory of the lmadmin installation that you want to import. |
|
•
|
Previous Data Folder Path—(Windows only) Specify the path to the runtime data folder of the lmadmin installation that you want to import. This enables you to import data files from a previous installation. |
Note:If you have uninstalled the previous lmadmin installation and saved the configuration files in a separate directory (for example, C:\temp\<previous_installer_data>\conf\server.xml and C:\temp\<previous_installer_data>\logs\lmadmin.log) , specify the path to the directory that contains the conf and logs folders (C:\temp\previous_installer_data>).
If your previous installation did not distinguish between an installation root directory and runtime data directory, specify the path to the installation root directory in both fields.
|
6.
|
If you have configured the TCP/IP port that the Web server uses to listen for communication with clients connecting to the license server management interface, in Launch Configuration enter the HTTP port number. (See License Server Manager Not Starting.) |
|
7.
|
Complete the remaining installation dialogs. |
Note:Note the following when upgrading lmadmin:
|
•
|
The lmadmin installer imports an existing vendor daemon and its associated files only when the license file used to import the vendor daemon contains the license file path as a relative path on its VENDOR line. |
|
•
|
Any existing demo vendor daemon and associated license files and log files are not imported. The installer always installs an up-to-date version of the demo vendor daemon and the files required to run it. |